HN Simulatornew | past | comments | lists | submit | bleuarff's commentslogin

Reactivity is updating the DOM whenever the underlying data is updated. That's one of the most basic reason for existence of all js frameworks. There's TC39 Signals proposal to bring that natively, but for now as said above the choice is either use a framework or recreate one. It's surprisingly easy nowadays using Proxy.


It’s always been easy to reactively update the DOM. I was doing that in vanilla JS before HTML5 had been formalised.

What the frameworks do is take this concept one step further to create a SPA (single page application) but I honestly think they’re an antipattern that needs to die.


The problems are ownership and provenance mainly, and that all DOM access is slow and requires syncing code internally.

Anyone can write code that tweaks nodes or uses templating, but doing it in a consistent way on a project with hundreds of thousands linea of code is challenging, especially if you also need performance and everyone's least favourite child: accessibility.

Sure you don't get some of this with frameworks, but they help a lot.


Well yeah, obviously frameworks are intended to provide a standard interface for projects that scale. But you’re describing a different problem to the one originally argued.


> Reactivity is updating the DOM whenever the underlying data is updated. That's one of the most basic reason for existence of all js frameworks.

Most web apps and websites do not have that much state variables (even though it may be a lot of data). So while React may offer a small dev speed boost, it’s consumed by the need to build stuff and a whole deploy pipeline to nurse.

Libraries like HTMX and Alpine can take care of most the boilerplate for old style imperative patterns. And backend frameworks like Rails, Phoenix, Laravel donhave their own implementation for data updates.


How I've done it is to use some kind of observer pattern, where you register listeners to state changes.

Whenever state is updated, the listeners are all called with the updated state and can update the UI and what not based on the new state.

I haven't profiled this and compared it to frameworks, but feels adequate for the relatively simple UIs I've done.


In a way that's where all frameworks start.


I read Children of Time after seeing it recommended here (awesome book btw), but I wasn't aware it wasn't a standalone. Great news!


Or the Pont-neuf ("new bridge") in Paris being the oldest one in the city.


The necessary IQ for destroying the world is dropping. Op does not say it's low enough today, but that will probably come sometime. Denying the possible harm these tools are capable of doesn't help.


It would be much harder to deny it if any of you were capable of describing the risks. The current discussion is a national-scale Handwavium mine.


If these systems allow anyone with an internet access or a few grands to run an open model to obtain the necessary information to e.g. build a bomb, spread an infectious agent, hack water or electrical infrastructures, I think that creates significant threats to the population.


These systems don't enable that. Building a bomb, spreading a bioweapon and hacking water/electrical misconfigurations are all trivially possible without AI. Courtesy to Unibomber, Aum Shinrikyo and the IRGC, respectively, for teaching society this.

In any case, how would AI regulation prevent any of these things? Shouldn't we instead focus on limiting access to bomb/bioweapon precursors and securing vulnerable endpoints, since that is the solution that saves lives regardless of how AI disseminates? Regulating AI is expressly dangerous, if it expands that societal blind spot. It'd be like regulating red mercury.


These things are of course possible without the help of AI, but I don't think they're trivial. That requires some specific knowledge, and making it easily obtainable is one less barrier to entry for people interested in it. Such attacks would require both knowledge and access, and I think preventing both is a better strategy than focusing on the physical aspect only.


Without disregarding other lines of work, but from the neolithic revolution to the early modern times, the vast majority of the population were farmers. Quoting Brett Deveraux:

"Prior to the industrial revolution, peasant farmers of varying types made up the overwhelming majority of people in settled societies (the sort with cities and writing). And when I say overwhelming, I mean overwhelming: we generally estimate these societies to have consisted of upwards of 80% peasant farmers, often as high as 90 or even 95%." (https://acoup.blog/2025/07/11/collections-life-work-death-an...)


There's no ultimate best player/build. When you factor in that each cart has different stats depending on the terrain, there's a "best" build for each track.


I'm wary of external urls in code. Some plaintext comment would come in handy for the day the link inevitably goes dead.


Why could external URLs be a problem? And is it still one if you swap https to hxxps or something? What could go wrong with having a URL as a comment in code?

I put URLs there sometimes and think it's very helpful.


You don't control these external resources, and now the explanation of what your code does is tied to a site that could be taken down tomorrow, leaving you with a dead link and an unexplainable regex.


Agreed- I'm all for comments explaining a RegEx, but not hyperlinks in comments. The link inevitably goes dead and now you've left a helpful-looking present in a comment with dust inside.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: