Devs on Twitter: "JavaScript is going to die soon, React is the last UI library you will learn, TypeScript is a bottle-neck, WASM is the way forward"
Companies in the real world: "We are looking for a jQuery developer, ES6 knowledge is beneficial".
Rientri di lavoratori qualificati crollati del -80% nel 2024. Le statistiche MEF certificano quello che avevamo previsto e anticipato grazie ai nostri dati. Quantifichiamo: -8000 famiglie/anno in meno, -800mln€/anno di contributi INPS.
@G
https://t.co/OSdQ8N9PPl
I built my developer portfolio as a 90s point-and-click adventure running inside Windows 95.
Instead of a website, you learn about me by playing.
Built with Opus 4.6, Copilot, OpenCode, GPT-4o & more.
Try it:
https://t.co/fvm1Hica5V
#WebDev#RetroGaming#React#AI
The rule transforms simple questions like "How do I center a div?" into nightmare responses:
"Actually, you're thinking like a junior developer. What you need is a comprehensive Design System with semantic layout tokens, implemented via a Context Provider architecture ..."
We can confirm that PWAs on iOS 17.4 are turned off for EU users on b3, while Apple keeps silent about it as if it's not happening.
At this point, it’s a feature disabled on purpose, and they want to keep it that way for the stable version to ship in a few weeks to all users.
You inspired me, @cassidoo.
Since hooks and the early conception of the suspense API, I have personally felt that React has been obsessed with just a handful of concepts. While technically impressive and undoubtedly pushing the limits and boundaries of what a single-threaded UI API can do, these new concepts have had very little impact on what I do day to day to deliver value to my users (other than making it more complex to "safely"/idiomatically do the same thing or dancing around experimental APIs that my open source users think are officially ready for prime time).
I want so badly for React to return to the client-side-focused and client-performance-obsessed utility I originally loved (or at least help me know better that it still has my interests in mind). It's painful to see other frameworks continuing to deliver on the same motivations that led me to React from day one.
React Forget has drummed up some of that old excitement, but it's easy to get caught up in a new "feature" that in reality is a reactionary answer to a deeper issue. The most brief I can be on this topic is that I really wish we could just drop this obsession with immutability and address true reactivity. Whether that's through signals (please) or not (still fine), this has felt like the most ignored low-hanging fruit for a while (sorry I've been following @RyanCarniato's signals for much longer than most).
Like Cassidy, I'm still using React very heavily and I'm still reaching for it regularly... but with increasing resentment.
https://t.co/XCZeub9crj
Fa bene all'erario, alla previdenza, alla competitività. E allora "le si lasci li, senza toccarle a ogni cambio di governo e si rafforzi l'idea di stabilità del quadro normativo" @MEF_GOV@MarcoOsnato@GiulioCentemero@toniricciardi@simonebilli
"NextJS is easy to run anywhere"
this is not true - i'm getting tired of people continuing to claim this
it dismisses the tedious work that the OpenNext community is doing to actually make feasible to run it correctly outside of Vercel
here is yet another example:
with server actions you no longer handwrite API endpoints - which means you don't have the ability to explicitly control versioning
from Vercel's point of view this isn't a big deal because on their infra, every deployed version of your app can stick around forever and requests from old clients get routed to the right version: https://t.co/qsk8R9JFHj
this is only possible because of serverless functions which scale to zero - they solved this problem via a specific infrastructure solution
yet every demo they do of "look how easy nextjs is to self-host" is always some simplified docker deployment that glosses over details like this
this is just one of an infinite number of examples
seriously getting tired of wading through the spin
I get asked about this a lot (especially since the launch of Epic Web), so I've written it down.
Here's why I won't use Next.js:
https://t.co/crVN7hOszL
Vue.js Nation Gleam Giveaway 🎉
Win prizes including Lifetime Vue School & access to the Mastering Nuxt 2 & 3 course and/or free workshop access 🤩
Follow the instructions on the link below & earn entries by following, retweeting & referring friends
https://t.co/2MsfoCGJLY 🎁
Vue.js Nation 2023 is here 🔥
🎙️ Learn from the greatest industry speakers & educators!
😍 Topics cover @vuejs, @vuetifyjs, @nuxt_js, @quasarframework, @useFormKit + more!
Don't miss out on this exciting event and enhance your Vue game this January.
✍️ https://t.co/i1H8vvcrdp
Healthy team habit: Create Architectural Decision Records (ADR)
ADRs document big decisions.
Benefits:
✅ Everyone understands how the decision was made
✅ Centralizes team feedback on a big decision
✅ Useful to reference later if people leave or the decision is reconsidered.
@diegohaz In one of my last companies we really wanted to adopt Playwright but it did lack support to integrate in the NX monorepo workflow.
Are there plans to support seamless integration with a dedicated plugin?