We spent our civilisation to go from “What’s that loud boom with bright light in the sky? Must be Gods angry at us” to “Oh, it’s thunder, caused by rapid heating and expansion of air”
As long as the global population is still rising, they will be carnage between competitions. The author and many others might be foresee the (near) future where the global population start declining, maybe then, we can do things just because we can.
Exactly. Many senior devs don’t want talk about the latest updates but those topics are usually what’s trending on X/YouTube/or even HN.
Let’s face it, how many times does those new features really “revolutionise” or make a real dent in our work? Or are the content creators just using them as click baits to get views and engagements which eventually can turn into monetary or network values for them?
Real talks are getting hard to find in this attention economy plus bots rampage across the internet.
So for a React developer who doesn't want to include Shadcn/Radix, but also doesn't have time to build every component/a11y/compat/edge cases from scratch, what are the better alternatives?
Would be nice to list them here so developers can know a midpoint between DIY <-> Shadcn/Radix
I’m already seeing colleagues at work using AI to generate documentations and then call it a day. It’s like they are oblivious to how _ugly_ and _ineffective_ the AI generated AI slops are:
- too many emojis
- too many verbose text
- they lack the context of what’s important
- critical business and historical context are lost
- etc..
They used AI to satisfy the short-term gain: “we have documentation”, without fully realising the long-term consequences of low quality. As a result, imo we’ll see the down spiral effects of bugs, low adoption, and unhappy users.
Merge rates is definitely a useful signal, but there are certainly other factors we need consider (PR small/big edits, refactors vs deps upgrades, direct merges, follow up PRs correcting merged mistakes, how easy it is to setup these AI agents, marketing, usage fees etc). Similar to how NPM downloads alone don’t necessarily reflect a package’s true success or quality.
This type of comment doesn't contributing to anything. Rememebr most devs just code for work, and don't want to learn a new language/ecosystem _just_ so they can use a different framework.
Good to see I'm not the only who wants a cleaner newsfeed to cut through this information overload noises. Coincidentally, I also spent the last weekend building a curated, HN-based newsfeed for the busy web developers: lessnews.dev[1]