1,334 karma · joined September 15, 2023
echo '0.0.0.0 news.ycombinator.com' >> /etc/hosts
https://en.wikipedia.org/wiki/Caterham_7
People generally build kits resembling this design with more powerful motors. This is a factory build with a streetable config.
Alternatively, because there are now (often ridiculous) build systems and compilation steps, we might expect similar behavior to other compiled binaries. Instead we get the worst of both worlds.
Yes, JS as it is is some kind of standard, but at a certain point we might ask, "Why not throw out the bad designs and start from scratch?" If it takes ten years to sunset the garbage and offer a compatibility shim, that's fine. All the more reason to start now.
A purely compiled WASM approach with first class DOM access or a clean scripting language with a versioned standard lib, either option would be better than the status quo.
I would omit the left-wing characterization as a debatable generalization. Perhaps it would be better described as the specific platforms being opposition partisans, rather than the Internet itself.
And when we made mistakes there, it was usually because we took short cuts instead of respecting clean abstractions.
>So you have to think of all the machinery to change as few DOM nodes as possible.
This is where I get off the train in regards to JS frontend frameworks. We should know the state our data. We should also know the state of our display components, whether they are canvas elements rendering more complex data or mere tables. KISS principles apply here.
"All the machinery" of a framework isn't necessary to handle the synchronization between the two. Especially when it mandates ridiculous build steps, thousands of dependencies, opaque "magic", huge blobs of minified JS and loading spinners.
>The difficulty usually comes from people mixing up two concepts: the state of data, and the state of the UI.
Agreed 100%. Which is why I like the <template> element. It is a dose of sanity allowing explicit separation of code and document. I suspect this is the other poster's objection to HTML inside of JS.
I find it strange that so many developers struggle to maintain the state of a page. Then they turn to "magic" frameworks to handle it for them. What's wrong with having a canonical Object or other data structures to represent the state? Why would anyone want a generalized framework to (mis)represent the core model of your application?
We've been creating applications with internal state for decades now. GUI applications with an internal state existed before the web. Typically it is achieved via code hygiene and sane abstractions. As an example, the template element keeps your document structure out of your logic.
Yet in the modern JS world, display, state and now even the backend are all shoveled together into an unmanageable monstrosity. From this point, even more magic is added to duct tape over the madness. As a result, the accepted norm is now 10mb of cruft to display a static page.
I've always found this to be weird and off-putting. Okay, ask if it is important, but if they don't understand the response, that's on them. I understand that people frame things through their own experiences, but it is strange when wage based employment is assumed to be the only way to earn or live. It is a poor way to start a casual conversation.
As an example, consider the claim, "Steam shovel adoption is destroying entry level jobs in ditch digging"
Yes, we want more productive technologies to be used where applicable. We want workers to specialize and become more productive with less hours worked. This isn't destructive at all. Framing it as such is either deliberately misleading or demonstrates a misunderstanding of basic econ.
Another reason I like <template> is the ease of prototyping. A very straightforward approach is to mock up your HTML+CSS with placeholders of what your populated elements might look like. Instead of translating that into JS element generation code, you can simply remove the populated data and enclose the barebones element in a <template> tag.
Back in JS, you might have a simple initializer to add these elements as needed and a function to (re)populate them.
Simple, to the point and no libraries or frameworks required.
For me the time spent coding is the last step. The more important task is always in identifying a problem worth solving and formulating what I hope to be a coherent design.
The actual typing, while tedious, is the least important part. Just the same, I am sometimes feeding a snippet to a LLM and having it fill out the tedium. Results vary, but the verbose style and longWindedDescriptiveNames seem to help. A few inline comments pick up the rest. The LLM will also expand these into Javadoc type comments.
Once you know what is actually going to be on your site, you can style the output with CSS and add the necessary interactivity with JS. Browser APIs have mostly standardized as compared to the bad old days. Using them directly instead of libraries or frameworks will keep your site lean and fast.
All of your CSS, HTML and browser API knowledge will continue to serve you for the years to come. In a few years, people will be arguing about a new magic framework.
I was somewhat surprised when I noticed simple Next.js landing pages would break in Firefox. Worse yet, the failure mode was to overlay all of the content with a black screen and white text, "An application client side error has occurred". It was surprising in that a simple landing page couldn't render, but when I discovered that the cause was a JS frontend framework, I felt that it was par for the course.
Perhaps it makes sense to the advocates, but for those of us not on the bandwagon, it can be sincerely baffling.
Before you begin, take some time to outline the tasks you need to complete. Now when you return to the home office, you are only there for one reason.
If problems persist, you may need to find more interesting projects.
In fairness, I would allow that when emotions run high, the individuals involved are not as precise as they could be. Alternatively, we might take their words as stated and simply interpret it as Scientism. Either way a pattern is emerging.
If the individual resigning truly wished to communicate the potential harm, he would have been better served by explaining it more precisely. Assuming malicious intent makes it hard to take seriously, especially in today's media landscape.
Okay, that's fine if he's the master of and exclusive license holder for "scientific reality", but I do take exception with his ability to divine malicious intent. Maybe I am missing something here. Did this person uncover a massive conspiracy? If documents were found where this malicious intent was outlined, I would like to see some citations. Perhaps it is more probable that this is a highly charged partisan issue and the statement is marred by hyperbole.