One time I found some #JavaScript in an app that was constructing a full blown SELECT statement in SQL, sending it to the server, and then blindly executed on that server.
It is still the most glorious, beautiful code I've ever seen.
@cspray I did that once for a project as a joke (against a read-only SQL API) and found it was actually a really neat way to rapidly iterate on my project!
You can view source on https://sf-trees.com to see a demo of the pattern I built
@baumannzone This has to do with how floating point numbers are stored (essentially, they’re fractions, not decimals). This occurs in most programming languages, not just JS. Look up “floating point rounding error”
Diving back into a project that used Vue and it seems to be throwing an error when I add a data- attribute to a HTML element. It's a static string which I use for something else.
Spent a bit of time early this morning to knock out the most basic vector editing features in my SCI0 pic editor. The SCI0 pic byte-code is very terse; it doesn't even have closed polygons, just lines that happen to touch each other when rendered to the frame-buffer.
I'm sure this whole UI layer will need a refactor soon, but its definitely another step in a "useful" direction. Just a few core features left before a "beta" is viable.
@javedAB Other ways to achieve it include removing Javascript altogether and replacing it by server-side scripting, as well as serving most if not all of your sources over a fast CDN.
@aeveltstra server side rending is a valid approach. i started with @astro and @solid_js . however, from what i guess, server side rendering is more cost intensive than static html
Here's a very-niche but then-very-useful #javascript trick I realized today -- you can create empty text-nodes to use as node references, for things like DOM insertion, range boundaries, or whatever.
I needed this to set the end of a range immediately before an element's closing tag, when references to existing child nodes might be invalidated by race conditions.
You don't even need to persist the references for removal, since a single call to context.normalize() cleans them all away.
@ollicle Oh you were asking about dealing with sibling text nodes? Yeah, that :-) Normalizing isn't something you tend to need very often, but it's uniquely useful when you do.
That's a good point about spotting in dev tools, I guess it would depend on what you needed. If the nodes need to be around for a while, it would be more useful to be able to inspect them. My use-case is very transient, they're added and gone again in the space of a synchronous function call.
⌛ The End of an Era: Microsoft Phases Out VBScript for JavaScript and PowerShell | @thehackernews
"Both NTLM and VBScript are known to be abused by threat actors to conduct malicious activities, prompting Redmond to remove features in an attempt to minimize the attack surface"
Question #Javascript folks! If I use destructuring assignment as below, is an actual array allocated for the function's return value, or does the runtime recognize this and optimize it away?
Could someone help me solve this problem with javascript? Palindrome Check: Write a function to check if a string is a palindrome. he's number 3 on this list - https://chat-to.dev/post?id=141
On the left hand side you should see a column with methods the string type contains. You can use several of these to accomplish a palindrome check. String.slice(), String.charAt(), String.at(), String.match(), and String.substring() are all methods that you can use to write your check.
In addition to those, I would recommend looking at String.toLowerCase()/String.toUpperCase() to avoid issues with capitalization, and String.trim() to avoid trailing or leading whitespace.
Also you will need a variable to store your result, my general recommendation is to start this variable as true and set it to false when you detect any inconsistency, and probably one to store the index you are currently checking. Last little tip is that many String methods accept negative indices to count from the end rather than from the start. Good luck!
One more giant tip because I don’t know what your experience with JavaScript is, but pay attention when comparing that you don’t use == when you should use === and vice versa. The difference is that == will try to coerce the values to the same type before comparison, which can lead to.unintuitive behavior
Theo's main point is that const doesn't mean "this value will never change" (since objects and arrays can obviously still be mutated), but that let means "pay attention, this value will be reassigned further down", and I totally agree.
