Richard MacManus explaining Daniel Kehoe’s approach to building websites:
There are three key web technologies underpinning Kehoe’s approach:
- ES6 Modules: JavaScript ES6 can support import modules, which are also supported by browsers.
- Module CDNs: JavaScript modules can now be downloaded from third-party content delivery networks (CDNs).
- Custom HTML elements: Developers can now create custom HTML tags, via Web Components.
Using a no build process and only features that are built into browser, and yet that still buys you a pretty powerful setup. You can still use stuff off npm. You can still get templating. You can still build with components. You still get isolation where needed.
I’d say today you’re:
- Giving up some DX (hot module reloading, JSX, framework doodads)
- Gaining some DX (can jump into project and just start working)
- Giving up some performance (no tree shaking, loads of network requests)
- Widening your hiring pool (more people know core technologies than specific tools)
But it’s not hard to imagine a tomorrow where we give up less and gain more, making the tools we use today less necessary. I’m quite sure we’ll always still find a way to jam more tools into what we’re doing. Hammer something something nail.
Direct Link to Article — Permalink
The post Web Frameworks: Why You Don’t Always Need Them appeared first on CSS-Tricks.
You can support CSS-Tricks by being an MVP Supporter.
source https://thenewstack.io/case-against-web-frameworks/
No comments:
Post a Comment