In agriculture, annual crops are crops that you have to plant annually. For example corn - the plant dies after producing its fruit, and you have to plant new corn seeds.
In contrast, perrenial crops are those you can harvest every year without having to plant new ones. For example, strawberries don't die after bearing fruit, you can collect fruit over and over from the same plant.
It's a shame Surplus (Adam Haile's, not my succession of it) isn't cited nor is he mentioned, given that at least two of the listed frameworks were heavily and directly inspired by his work. S.js is probably one of the most incredible JavaScript libraries I've used that should be the reference for a signal API, in my opinion.
No Lit Element or Lit or whatever it's branded now, no framework just vanilla web components, lit-html in a render() method, class properties for reactivity, JSDoc for opt-in typing, using it where it makes sense but not junking up the code base where it's not needed...
No build step, no bundles, most things stay in light dom, so just normal CSS, no source maps, transpiling or wasted hours with framework version churn...
Such a wonderful and relaxing way to do modern web development.
I love it. I've had a hard time convincing clients it's the best way to go but any side projects recently and going forward will always start with this frontend stack and no more until fully necessary.
This discussion made me happy to see more people enjoying the stack available in the browser. I think over time, what devs enjoy using is what becomes mainstream, React was the same fresh breeze in the past.
> I think you can vibe code the basis of something really quickly, but the AI starts to get confused and trip over it's own shitty code
Or you can get back to vibecoding after fixing things and establishing a good base. then it helps you go faster until you feel like understanding and refactoring things because it got some things wrong. It is a continuous process.
You see, although what you say makes sense, paid software can also be extremely brittle systems. The only benefit is you can put the blame on someone else, which for the corporate life is a great hack. But that is not good engineering, much less use NextJS which is the same problem.
Customized software is as good as the team developing them are and trusting others to do that is proven to not work all the time, React proving it to all of us the last days with 4 different CVEs.
yep and thankfully Lee will always be at cursor and definitely not switch companies in the future
the chance of the software that does one thing well being maintained by the dedicated company is higher than the chance of Lee not switching jobs once the once vesting cliff has been reached again
React did not have this kind of security vulnerability in 10 years. The Vercel/NextJS/RSC rugpull is responsible for that and the people that made those changes should be named. The lack of shared governance is abysmal.
First, look how forgotten Puerto Rico is.
reply