London based software development consultant
Programming @programming.dev Understanding Spec-Driven-Development: Kiro, spec-kit, and Tessl
Programming @programming.dev Devdle — Daily Dev Puzzle
Web Development @programming.dev Hooks vs. Signals: The great reactivity convergence explained
Web Development @programming.dev Dead framework theory
Programming @programming.dev CamoLeak: Critical GitHub Copilot Vulnerability Leaks Private Source Code
www.legitsecurity.com /blog/camoleak-critical-github-copilot-vulnerability-leaks-private-source-code
Web Development @programming.dev The History of Core Web Vitals
Programming @programming.dev The Legacy Code Survival Guide: Add Features Without Fear
Programming @programming.dev Comprehension Debt: The Ticking Time Bomb of LLM-Generated Code
Programming @programming.dev Don't make Clean Code harder to maintain, use the Rule of Three
Programming @programming.dev If Releases Are Experiments, What’s Your Hypothesis?
Programming @programming.dev What Are The “Objects” in “Object-Oriented Programming”?
Programming @programming.dev Duplicate Delete
Programming @programming.dev Duplicate Delete
Programming @programming.dev The illegible nature of software development talent
Programming @programming.dev A Developer’s Guide to Secrets Scanning
Tech @programming.dev AI company Vercel loses hundreds of developers after CEO posts about meeting with Netanyahu
Programming @programming.dev Too DRY DRY, Hush Hush
Opensource @programming.dev LibreOffice turns 15: a celebration of freedom, collaboration and open technologies and standards
These are all very good points, and there is in value of having a common framework for front-end development. However, I would argue React isn't always the right tool for the job, yet it has become the dominant framework, and that dominance is being further bolstered because of generative AI.
So even if a better framework came along, and ideally one that's not owned by Meta, it would be very difficult for it to take hold because of this.