Lakshan Perera
@0xlakshan.bsky.social
Programmer / github.com/0xlakshan
Reposted by Lakshan Perera
The thesis of this post is that React isn't innovating and other UI libraries are. But the real issue is that React's innovations are overshadowed by it's own success.
www.lorenstew.art/blog/react-w...
www.lorenstew.art/blog/react-w...
React Won by Default – And It's Killing Frontend Innovation | Loren Stewart
Exploring how React's dominance by default stifles frontend innovation, and why deliberate framework choices lead to better tools for performance, developer experience, and ecosystem diversity.
www.lorenstew.art
September 16, 2025 at 2:24 PM
The thesis of this post is that React isn't innovating and other UI libraries are. But the real issue is that React's innovations are overshadowed by it's own success.
www.lorenstew.art/blog/react-w...
www.lorenstew.art/blog/react-w...
mbrizic.com
July 10, 2025 at 7:48 AM
Reposted by Lakshan Perera
btw if anyone is using `dotenv` (great library!), be aware that the new major defaults to logging an advert for `dotenvx` (worth checking out: dotenvx.com)
if you don't need the features it offers, this might also be a time to consider migrating to native node `.env` file support (from v20.6.0+)
if you don't need the features it offers, this might also be a time to consider migrating to native node `.env` file support (from v20.6.0+)
New promotion on log message · Issue #876 · motdotla/dotenv
I don't mind the default log message in v17 and respect the general promotion of dotenvx, but this statement is confusing in a team project where encrypting an .env.test file is not applicable: 🔐 e...
github.com
June 30, 2025 at 12:36 PM
btw if anyone is using `dotenv` (great library!), be aware that the new major defaults to logging an advert for `dotenvx` (worth checking out: dotenvx.com)
if you don't need the features it offers, this might also be a time to consider migrating to native node `.env` file support (from v20.6.0+)
if you don't need the features it offers, this might also be a time to consider migrating to native node `.env` file support (from v20.6.0+)