5 ms·
A brief history of web development, and why your framework doesn't matter
- quantum_state 3y agoThanks for sharing a great and fun-to-read piece! :-)
- deleted 3y ago[deleted]
- mediumsmart 3y agoTrue, as long as the web developed page fits in the frame of the screen on the device of the user who does not care which framework, that does care about the users device, was used by the web developer caring about the readability of their framework generated framed content.
- onion2k 3y agoYour framework does matter. It just doesn't matter to the end user of your web app. It matters to your dev team. A framework is a way of aligning how you approach writing things. It's a way of sharing responsibility between functional blocks of code. A framework is guardrails for how you think - it stops you just wandering off and doing whatever you want, and in a team that's vital.
- KingOfCoders 3y agoWith that theory in mind, why do dev teams switch from Angular to React or Svelte?
- strogonoff 3y agoReact is not a framework, it’s a tiny lib that renders stuff reactively. There are no guardrails, and it is not even specific to Web. You can use it to render to hardware LCD if you want. When people switch from Angular to React, it’s not a framework-to-framework move. They may have outgrown a ready-made solution and want a fully custom one (could be some sort of home-grown framework, more aligned with their goals). React allows that, being a library. Meanwhile, an actual framework-to-framework move can occur due to many factors like mismanagement of priorities or changes in HR situation (maybe they do not have success finding good Angular people cheaply, or they are already using Svelte somewhere and can reuse resources from another team).
- _ZeD_ 3y ago>>> React is not a framework, it’s a tiny lib that renders stuff reactively. yeah, no. try for example to mix in a single page react components and jquery ui widgets
- strogonoff 3y agoI did that with React, but you can do that with many frameworks, even Angular probably if you’re careful. You need to understand what makes a framework a framework. onion2k’s comment does a decent job of explaining that, take a look. React has no guardrails and does not force any particular structure. That’s why there’s a plethora of frameworks built on top of it.
- onion2k 3y agoI would include React in the framework camp. It isn't technically a framework but it goes far enough that it pushes you to write code in a specific way. If you approach it like a library you often find yourself writing code that doesn't work well with React, which is a common source of janky websites. If you approach it more like a framework, and make sure you follow 'the React way' you'll almost always end up with a better app. To that end it might be better to think about it like a framework.
- KronisLV 3y ago> I would include React in the framework camp. It isn't technically a framework but it goes far enough that it pushes you to write code in a specific way. My litmus test to decide whether I'd personally classify something as a framework or library is to see what it's compared against and how people talk about it, as well as how they actually use it in a given scenario. For example, people typically consider using either Angular, React or Vue for a project. Then, they talk about it very much like it is "an Angular project" or "a React project" because most of their code is limited to working within the confines of those (life cycles, state management, routing, patterns). Does the fact that you could swap out one React statement management solution for another actually matter in that case for the distinction? It would... if anyone actually ever did that. Most people stick to whatever is the recommended option. Same for the ability to run a whole Vue app under a specific div in a greater legacy site - in that case it would be treated more as a library... except that happens very rarely. Then again, I don't really care about how strongly people care about these things, in my eyes one day the same codebase could be treated as a framework (a SPA in Vue with all of the mainstream packaged like router and Pinia, with hundreds of components and thousands of dev hours) and another as a lightweight library to be embedded into something else.
- onion2k 3y agoI imagine because the framework isn't working for the way they want to build things. That's a good reason to switch. Teams should pick the tech that aligns best with the way they want to work. If they're switching for user-facing reasons it's likely that they're using just the framework poorly. Changing your own code is usually a much more effective way to get a perf boost than changing an underlying library.
- KingOfCoders 3y agoYes, but I was not interested in general reasons, but reasons with that theory "A framework is a way of aligning how you approach writing things. " in mind.
- solatic 3y agoTake your pick: resume-driven development, Make Your Day Job Exciting Again, or thinking that switching frameworks will magically solve all your technical debt and inherent complexity
- KingOfCoders 3y ago"Not much JavaScript was written." There was no Javascript.
- sakjur 3y agoI think that part refers to the web around 2000. JavaScript was definitely around and being used in a limited extent similar to what the article describes at that point.
- KingOfCoders 3y agoI talks about the simplest servers. We wrote those apps ~1993 and there was no Javascript. Then JS arrived for gimmicks (like display the time of day on a page) and later on was used to drive applications.
- deleted 3y ago[deleted]
- MrJohz 3y agoAs someone who has been developing frontend applications since the jQuery era, it would have been nice to see more explanation of why each new innovation happened. There's some of that for things like GraphQL, but to me the biggest and most interesting changes were the move from backend-driven rendering to frontend-driven rendering, and the move from DOM-as-state to rendering the DOM from state. Those ideas were hugely important, and both affected the design of modern frameworks a lot. Also more recently, the increasing push for moving everything - from CSS declarations to server-side actions - into components. This gets a brief mention, but again, it's one of the ideas that best explains recent trends in frontend development (and many historical trends as well).
- yen223 3y ago> to me the biggest and most interesting changes were the move from backend-driven rendering to frontend-driven rendering, and the move from DOM-as-state to rendering the DOM from state I think a lot of this can be attributed the rise of internet-connected smartphones and mobile app development. This led to a scenario where you had to have a separate backend API anyway to service the iOS or Android app frontends, so it was easy to justify doing an react- or angular-driven SPA for the web. Plus the new mobile form factor demanded more front-end engineering work, so it made technical sense to have the frontend be completely separate from the backend. This also explains the shift away from DOM-as-state, since you couldn't really drive mobile apps just from HTML, at least back then.
- teaearlgraycold 3y agoYes, but all of the React web apps that don’t have a companion mobile app aren’t just cargo culting (but there is a lot of that in the industry). Managing UI state the React way is easier for anything non-trivial. Sure, for forms the web has you covered. But that’s about as far as things go. I remember seeing the small amount of React code required for a typeahead search for the first time and realizing how much more I could now do. The problem is that we have opened ourselves up to all sorts of new troubles by taking on that power. I still wouldn’t go back. But I will complain when some rookie dev makes me download 10MiB of JS to look at a blog.
- ramzez 3y agoIt’s the last paragraph which says it’s all.
- WoodenChair 3y agoIn 2014 I wrote a "History of Web Programming" that's a good accompaniment to this article since it goes into some more detail on some of the older technologies: https://www.observationalhazard.com/2018/06/history-of-web-programming.html https://www.observationalhazard.com/2018/06/history-of-web-p...
- WA 3y agoI feel old when an article explains that a server can generate HTML and the browser renders the HTML and that this can be done quite efficiently for every interaction with a user. It’s strange to me that one can be a webdev without understanding that you do not need JS for a web app, although it does improve the UI in some areas. It feels even stranger that the term server-side rendering became a thing, since the server doesn’t render anything, but just generates HTML and sends it over the wire. And I’m only 39.
- aleksiy123 3y agoI believe generating the HTML is what the term render means in this case.
- n3storm 3y agoNo it is not. Same as videogames generate scenes and videocards render those scenes. Render is the final step presented to user. Users do not see HTML, they see text, boxes with background colors, buttons, those are html elements rendered for visual consuption.
- mewpmewp2 3y agoIn the whole React ecosystem render is used as a keyword to produce HTML/DOM abstractions though. For example class based components having the render function. The rendering you mention never happened anywhere in the React JS code. Browser did the rendering internally.
- DeathArrow 3y ago>the whole React ecosystem Web is much more than the React "ecosystem".
- mewpmewp2 3y agoOther libs/frameworks also use the word render. E.g. https://vuejs.org/guide/extras/rendering-mechanism.html https://vuejs.org/guide/extras/rendering-mechanism.html
- patrickhogan1 3y ago“The only software that I like is one that I can easily understand and solves my problems. The amount of complexity I'm willing to tolerate is proportional to the size of the problem being solved.“ Ryan Dahl - creator of nodejs
- huygens6363 3y agoProceeds to assist with the most unimaginably complex system known to man to solve fancy forms and partial refreshes.
- Sammi 3y agoCompared to what? Ruby? Python? .net? Java? Maybe Go can claim to be simpler. But there are many runtimes that are popular and equally complex as nodejs.
- huygens6363 3y agoCompared to not doing fancy forms and partial refreshes? I know, I’ll let myself out.
- z3t4 3y agoNode.js is a server framework for quickly building small systems like server daemons with good performance and security. It's interesting how much over-engineered it has become (blaming JavaScript) considering that it's now mainly a compiler target for web frameworks.
- MrVandemar 3y agoI do web design like it's 1999. I write the HTML. I upload the HTML. Works for me. But that was a good article, it explains the rather odd and frankly underwhelming direction the web went in while I was out of it.
- 4ndrewl 3y agoThere's probably a couple of things missing from the early days - Flash - we quite often built components in flash to provide app-like experiences - the Browser Wars - how difficult it was sometimes just to reliably target a DOM element across browsers But the most startling thing that's changed since the late-90s is the 'tooling industry' and just how complex the tooling has become, for arguably marginal benefit to the users of the web.
- n3storm 3y agoI would love to found mentioned "mootools" and "960.gs" in the article.
- jonwinstanley 3y agoHaha I remember mootools being pretty big when plucky upstart JQuery appeared
- n3storm 3y agoat least the name was honest about library weight XD
- gerardnico 3y agoIt does matter. When you write a gui, you want to think in a tree of component. Ie React. If you want to print, you think in document (html, …). That’s also a tree by the way. Html does not have any composability. They try hard to inject that in it (web component, jquery plugin, …) React (ie virtual dom) is a beauty in this regard and if you don’t use it, you would have a hard time creating any gui with a certain level of difficulty.
- dacryn 3y agoWe were creating many complicated yet great user experience frontends before React was even born, using server side template engines. React makes development at scale of these things easier, and makes a website really a website (clicks are just triggering javascript instead of the classic post/get cycle that fetches new html). But it is completely unnecessary to build any level of GUI
- brabel 3y agoPeople did, and do, create guis with very high complexity using desktop technologies, I can assure you we don't need React for that.
- throwaway2990 3y ago> React (ie virtual dom) is a beauty in this regard and if you don’t use it, you would have a hard time creating any gui with a certain level of difficulty Anyone who didn’t grow up building stuff prior to 2010 would have difficulty. we don’t need react in 2024. And it’s only making things worse now. Not better.
- strken 3y agoI don't agree that you need React or a vdom for composability. I remember a lot of server-side libraries with an API something like html( body( div( p("hello world"), class: "blah" ) ) ) where the tree was built using function calls. In such a system, HTML was often represented by an AST (or just a wrapper around a string!) and you could compose HTML together just by creating and calling a function. This is what JSX/TSX are doing under the hood: they're transpiled to a call to React.createElement. You don't actually need them, though.
- todotask 3y agoI would say it does matter to the end user when they are in an area with poor network connectivity. The Astro web framework provides a good balance between interactivity and content-driven experiences. Being able to reuse components saves time, reduces the carbon footprint and conserving more joule of energy on million of devices. One of which I believe Reddit have recently make the switch. You can see the impact we can make. A programmer's focus isn't just limited to following a straight line from start to finish and receiving their paycheck. Only poor soul like me are still out of job.
- Kiro 3y agoWhat's up with the space before question marks? It's really distracting.
- bloak 3y agoThat's French-style punctuation. It doesn't distract me too much. According to LinkedIn the author is in Egypt but has the same (Arabic) name (modulo spelling) as a famous French footballer (and headbutter).
- p4bl0 3y agoThat's how it works in many languages. French being one for example (an unbreakable space before all double punctuation such as '?', '!', ':', ';', etc.). The author probably just isn't a native English speaker :).
- politelemon 3y agoThanks for sharing that, I learn something new every day !
- Dachande663 3y agoThe jump from back-end to SPA and showing the example as yourdomain.com/any-thimg is a big give away. Remember Twitter et al with yourdomain.com/#/any-thing because the history API wasn’t a thing yet and the turmoil it caused when people realised this broke so much of the “new” web.
- jasonwatkinspdx 3y agoWho here is old enough they first learned webdev from this? https://philip.greenspun.com/panda/ https://philip.greenspun.com/panda/
- jonwinstanley 3y agoIn my little corner of the universe people building small to medium sized web apps are dropping JS frameworks and going back to doing things server side with Rails or Laravel. HotWire/LiveWire are then used for instant interactivity. Is anyone else seeing people making that change?
- steveobot 3y agoAll the reasons the author lists is primarily why I've been preferring using web components to add interactivity to web pages only when the components need them. Nice thing about web components is that it's browser-native so it doesn't require any framework code to ship with it, and if you do prefer a framework, most modern frameworks have wrappers that work with web components. We ended up building (yet another) framework dedicated to rendering web components (https://rootjs.dev https://rootjs.dev). It uses JSX for rendering HTML on the server-side, but no JS code is rendered to the browser at all by default. Web components usage is auto-detected and automatically injected into the page as a dependency, which makes for really good developer ergonomics.
- koonsolo 3y agoAlthough I like the article, I don't agree with the following statement in front-end: > People rarely pick “the best tool for the job”. They say that. But what they mean is “the tool I’m familiar with the most”. Front-end developers are the most eager to pick up any new (or hyped up) technology. Going from webpack to vite, going from npm to yarn, going from node to deno. Plus, I work with React developers, and most would also experiment with svelte etc. They absolutely love to learn and use new technology. At least that's my experience.
- DeathArrow 3y agoWhat's wrong with websites? Not everything needs to be a web application.
- gebna 3y agoI'm the writer. I do not know how it blew up on HN but I thank OP for sharing and thank you all for reading.