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


Java script frameworks are just extra boiler plate that isn't needed in the age of ai-coding.

Server side page generation with a sprinkle of js will give you the same results with GBS less of packages and comple time


The whole reason for switching from server-side to SPAs and frameworks was increasing responsiveness for users, better transitions, and allowing optimistic updating.

All of these thing still matter no matter what you are coding with.


As perTFA, the pure HTML/JS page did worse. In some theoretical sense you are correct if you assume an infinitely intelligent model. Given a smart enough system then writing in a mixture of HTML/JS and the JS is mostly a wrapper for WASM/Rust is the best. Any cognitive system has limitations and at a certain point developing intelligent abstractions and tools for thinking will give it better results. We can debate whether React or Svelte is better as a tool for thinking about the DOM and State, but they are both much better than pure HTML for any sufficiently complicated website. As the article shows it doesn't even need to be that complicated of a website to get a benefit for using a framework.


I disagree. Even if you don't put too much weight into this test's results, if you stick with vanilla JS your agents (or human devs) are going to write `element.addEventListener` and `document.querySelectorAll` countless times, and each one is going to drift a bit of time.

Having some sort of reusable framework is important for maintainability, always has been. Sure, you can have an agent "write a small JS framework that covers common functionality", but then you need to know what should fit into that framework. Having a framework pre-defined saves a lot of decision making and helps avoid drift.

In my opinion, this has always been true and it hasn't changed with AI-coding.


The vanilla advantage is also there in a pure client-side pwa. Arguably it’s even bigger, because the bundle size ends up way smaller and the agent needs to hold less in context.

Plus all the other vanilla advantages: fewer dependencies, lower maintenance, less retraining, etc…


They also were unnecessary even before AI, the biggest advantage of React over HTMX-style apps was that you could recruit someone more easily but the SPA complexity wasn't worth it and it scaled terribly.

Now that you don't write the code, I don't see why I would pick React style libraries unless the codebase is already there.


We just write different stuff. For content driven websites you can skip js frameworks altogether. For web apps it would not be a good idea.

It's all about how much interactivity you need. A lot of business web apps are full featured commercial software packed in SPA form. You will need a lot of stuff client side and without framework it will be a mess. Unless you write framework yourself but the you are reinventing a wheel.


I'm currently working at an enterprise SPA and it also doesn't work well.

I think unless you have a very low number of features or employees (and are sure from the start to keep it this way) I don't see it working.

In my 3 previous companies I had similar issues so I think it's widespread.


I'm reading that agents can now mash up video games that were written in assembly. At that point I have to wonder if the abstractions are adding anything.

Of course, there is the question of "the human can still understand what is going on", but it's not clear the new frameworks are optimizing for that...


[flagged]

LOL


I mean maybe I'm too grumpy, but never in my life did I think I'd have to fight against a strong contingent of people who really don't see the value of abstraction. Taking crazy pills must feel like this.


Abstraction can be done well, or terribly, and there seem to be both objective and subjective dimensions to it.

For example, the program runs 20,000x times slower, or you need to go thru 12 layers of indirection to find a boolean. (Not making up either of those examples, sadly.)

So I don't think it makes sense to be for or against abstraction. It depends on the context, and on the execution.

That said, my point earlier was, it's silly to me that people are designing abstractions specifically "for AI" when AI can happily work on minified outputs, raw weights, etc. (It builds up its own abstractions in the transformer layers.)

There's probably a difference in efficiency, but we might be surprised, and I haven't seen anyone measure that.

So considering the LLM can happily ingest the entire codebase, in abstraction-free form, and operate productively on that level, then the value of abstractions, as far as I can tell, is for the humans alone — so that we can continue understand what is going on. Otherwise we might as well accept defeat and let the AI do its business in assembly.


Your mistake is trying to fight people. You don't have to do that. You can just let them suffer from the consequences of their own decisions.


All web pages should be WASM binaries now.


In typical HN style, you are both pretentious and wrong. Javascript frameworks save you the complexity of an agent holding the entire library code in their context. For example, an agent can work with 2-4 react components for a current ticket without needing to know each line of internal React code.


Makes sense Microsoft is placing it self as a model host and os providing open weight models for much cheaper on their infra already.

No wonder openai and anthropic are terrified


Makes sense for Microsoft. Copilot is already capable of being model agnostic (both GH Copilot, obviously, and M365 as well). They're an enterprise software & services company, they want to sell integrated AI tooling in their stack, powered by whatever models their customers want rather than any specific model.

Models are quickly becoming a dumb pipe, like an ISP. Just a commodity. The labs should rightfully be terrified, eventually the value isn't going to come from the model itself but the tools & integrations built on top. Non-tech businesses and non-tech employees don't want to buy API access to a model, they want to buy off the shelf software with its capabilities packaged up into a pretty, easy to use GUI.


I don't know about that, a lot of those bloated enterprise solutions are becoming obsolete fast, and integrations becoming a moot point as these models advance.


Maybe for startups or simple orgs, but in any regulated industry/high compliance requirements they are still useful or outright required.

Claude Team w/ Cowork still only lets you set R/W permissions globally for each MCP connector for the whole team, they still don't offer config on a per-user basis. The enterprise controls are sorely lacking first party. Maybe fine for most startups or flat orgs, but any established enterprise with strong identity & access governance is going to have an issue with that. You can make it work, but you need to make your own agent/harness and give it an identity in Entra or whatever else you use, so for a non-tech company without a dev team, right back to square one of preferring to just buy a COTS solution vs trying to hand out direct model access with minimal governance.

(M365) Copilot sucks but Microsoft is putting a ton of work into agent governance & identity that sorely lacking elsewhere.


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

Search: