Daniel Morrison
adactio.com/links/19449 This. I’m told there are good React apps out there, but they aren’t the ones I keep running into.
The self-fulfilling prophecy of React - Josh Collinsworth blog
Matcalfe’s Law in action:
Companies keep choosing React because they know there’s a massive pool of candidates who know it; candidates keep learning React because they know companies are hiring for it. It’s a self-sustaining cycle.
But the problem is:
React isn’t great at anything except being popular.
Responses
Related links
The Neverending Story
Since the early days of the web, large corporations have seemingly always wanted more than the web platform or web standards could offer at any given moment. Whether they were aiming for cross-platform-compatibility, more advanced capabilities, or just to be the one runtime/framework/language to rule them all, there’s always been a company that believes they can “fix” it or “own” it.
Applets. ActiveX. Flash. Flex. Silverlight. Angular. React.
HTML Web Components: An Example - Jim Nielsen’s Blog
Here’s an excellent case study of an HTML web component. Jim starts by showing how you’d create the component in React; then he shows how you’d do it as a JavaScript web component; finally he shows the way to do it as an HTML web component:
The point is we’re starting with a baseline, core experience that will provide basic functionality and content to a wide array of user agents before any JavaScript is required.
Once you’ve done everything you can in vanilla HTML to provide core elements of your baseline experience, you can begin enhancing the existing markup with additional functionality.
This is where HTML web components shine.
How to (not) make a button - Tomas Pustelnik’s personal website
A demonstration of how even reinventing a relatively simple wheel takes way more effort than it’s worth when you could just use what the brower gives you for free.
The radium craze | Eric Bailey
The radioactive properties of React.
as days pass by — Hammer and nails
We don’t give people a website any more: something that already works, just HTML and CSS and JavaScript ready to show them what they want. Instead, we give them the bits from which a website is made and then have them compile it.
Spot-on description of “modern” web development. When did this become tolerable, much less normal?
Web developers: maybe stop insisting that your users compile your apps for you? Or admit that you’ll put them through an experience that you certainly don’t tolerate on your own desktops, where you expect to download an app, not to be forced to compile it every time you run it?
Related posts
Frustration
Applying the principle of least power to tools and technologies.
Whatever works for you
There are many ways to style a cat.
Lightweight
Minimum viable television and minimum viable websites.
Less JavaScript
The Google developer relations team are dishing out some inconvenient truths.
Mind the gap
If you’re making a library or framework, treat it like a polyfill.