It’s the space after the colon in the submission title (was that the infamous HN title normalizer?). The original has SQL:2023, which makes sense if you know that the ISO naming scheme introduces the year with a colon (e.g. “C99” is officially ISO 9899:1999, “C95”—that is ANSI C plus wchar.h and wctype.h—is ISO 9899:1990/Amd 1:1995).
It made perfect sense to me at first but now that you mention it, the title is quite funny. I guess if "SQL" says 2023 is over, who are we to argue - happy new year everyone!
In my experience in tech, most teams directly access and manipulate production frequently. Bigger companies usually have restrictions on this but in the start up world not so much.
I had a similar experience after switching to DVORAK as a nerdy teenager, however I found by just leaving my smartphone on QWERTY, I'm able to switch and still type 40 - 50wpm with minimal practice on a real keyboard. I'm more like 100wpm on DVORAK.
Practicing both layouts a little may make it possible to keep both modes in your head, but I don't know if a completely different input mode would make this harder.
I believe Solid has also kinda shown that.. Well, I like its low-touch approach compared to svelte's need for heavy compiling and a new language essentially.
With Solid can use JSX and it doesn't even need, last I checked, anything beyond standard JSX transformation to get pretty good results. It's the better direction IMHO even if the Solid APIs feel like they need another iteration or so.
Solid.js is even faster than inferno, and it doesn't really use a VDOM strategy, uses a strategy much more like svelte. IMO svelte is just poorly implemented from a benchmark perspective.
In reality, most of these benchmarks are not meaningful when talking about real app performance. What's meaningful is how you do global state updates in your app. If you use a react app with react-hook based context providers that unnecessarily update hundreds of components on simple changes, you perf is going to suck. If you use a react app and don't use React.memo anywhere, perf is going to suck. If you use react very carefully and are fully aware of when the vDOM is going to run and use small components that only update when their data actually changes, and ideally avoid running vDOM 60 - 120fps a second for animations, performance is going to be good.
I like Solid.js because it does all this for you by nature of just using the framework. Svelte does some of this for you so for real world apps performance is likely to better than react, but it doesn't do it as well as Solid by nature of it's state management strategy, not by nature of it's DOM update strategy.
The less you update, the faster your app will be. Then the DOM diffing strategy doesn't matter.
Fun idea, but pretty unfun to play. Half the questions are just five, six different words you need to `|` together, and not enough time to even type out that many words.
Feels like the author thinks regex is a useful way to match a bunch of unrelated words in a paragraph. Not really the point of regex.
Yeah I'm on mobile and can't see the text above while I type because of the space for the on screen keyboard and can't type fast enough anyways on mobile so just gave up instantly :)
A successful Web3 (if we want to use the term) project should be unfundable to capitalists. That's what makes this so hard. Teach people how to not be wage slaves, then people won't throw away all their power to the already-wealthy.