fergie

Hackers remotely override settings on thousands of freezers, fridges and chiller cabinets, pushing them from as low as -27C to well over 50C. Intermarché, Coopérative U, Carrefour, Leclerc and Monoprix chains among those affected.

And like 950 of them were probably closed for being "off-topic".

Its not so much the moderation, its more the random nature of the links, and the anonymization of user contributions.

One thing is that there are lots of bots on the site, another is that the site now seems to be specifically designed for bots.

No idea why this idea is being downvoted, because it is totally correct, even more so in the LLM-coding era.

I really think that you should actually read the article.

How does this actually work? Are they talking about browser fingerprinting or something else?

All of this is correct, but it still requires PHP on the server- this will not work in HTML itself.

As a philosophy major, I can confirm that the field generally rewards those who make good arguments for bad ideas, and that for reasons that I never fully understood, texts always seem to be far more verbose than necessary.

Ultimately you still need somebody to decide what we are going to tell the machines what to do, and then actually tell the machines what to do, and it doesn't really matter if that is in JavaScript or plain English.

There does _seem_ to be some pressure on the top end of SWE salaries. Its possible that this is just wishful thinking, but if true, I suspect that it has more to do with an increase in job applicants rather than a decrease in actual work. AI seems to have driven up the amount of applications received for every vacant position.

In web development:

Frameworks- possibly.

TypeScript, and other metalanguages- probably not.

Agree that handling state is also a big part of js frameworks.

> It would tie in an additional feature with potential future incompatibilities

No offense but this is a bit of a non-argument that could be applied to just about any development in HTML.

> There’s also just not a super great reason to do it.

Most web dev frameworks exist in large part to solve the problem of templating. (yes, they do other stuff, but templating is the central problem that they are solving)

They embed webpages into other webpages and definitely have their place, and could arguably be used more, but they are definitely not a way to consolidate a single piece of HTML from constituent pieces.

mate, I've been a full time web developer for 26 years, plus the time I spent at uni :)

Big fan of what you did there- baffling that it was beaten out by Webcomponents. I feel like <imports> should be brought back.

Yes, partial refresh strategies are interesting, but its an adjacent problem.

Thats XSLT which is tragically being removed from browsers as we speak: https://developer.chrome.com/docs/web-platform/deprecating-x...

I say tragically, because XSLT was indeed the only sort-of workaround that was available for templating in the browser, even if it was limited to v1 rather than the much more useful v2 and v3.

This made me chortle:

> Did I read this paper? Of course not. No one at OpenAI read this paper either, so why should I? I did what every other mathematician in the world does with AI slop mathematics: I fed it back into the slop machine and ran an information retrieval session with a chatbot interface to extract salient facts. Anthropomorphically speaking: I asked ChatGPT what it thinks about its own output. This is how we do mathematical research now. What a world.

Not wrong, but applies to any software whether open source or not.

SSIs are not widely supported any more, and were never a part of the HTML standard

(but yes- I used these a lot like 25 years ago)

Yes, but then you need php

Why is there no direct support for templating in HTML itself?

W3C: Why can't we just have <includes src="./header.html"> and be done with it?

The colours are suspiciously consistent across every svg. Like why should the bike always be that shade of red for example? It does seem to be trained on this problem.

I read this article and was beginning to feel like it wasn't really going anywhere or making good arguments. Was disappointed, although in hindsight not surprised to find out that it was AI-slop.

Stop upvoting AI-slop people!

I am suspicious of "articles" in this format. They seem to be simultaneously pushing an agenda whilst deliberately targeting midwits.

Its called "free movement of labor" and its a very good thing. Arguably the reason that Silicon Valley happened in the first place.

For me, the actual thing that git is not fantastic for is versioning data(bases), but this article doesn't seem to address that. In fact I am struggling to parse the article's proposed problem/solution.

Right- but why not let the LLM program directly in Java?

In the age of LLMs, I get why you would dump portablity in favour of close-to-the-metal Swift and Javascript codebases. However I don't really understand the need for Kotlin- surely thats just an unnecessary complication and performance hit?