4 ms·
I don't know. It reads to me like they are rediscovering what e.g. Visual Basic and Delphi did in the nineties: UI component libraries. Particularly VB used to
by jillesvangurp 7y ago
I don't know. It reads to me like they are rediscovering what e.g. Visual Basic and Delphi did in the nineties: UI component libraries. Particularly VB used to have a pretty lively component ecosystem. Also, the web is littered with attempts to have reusable javascript components for things like menus, combo boxes, and other cruft people end up wanting in their web sites.
This article reads a bit like a blast from the past in that sense. I think if I dig a little I might be able to dig out some papers from the sixties and seventies advertising the virtues of functions, modules, and even components with very similar language as in this article.
There is some progress here of course. Internalizing CSS is a good thing. Having that as a separate thing to manage and align is just too painful to keep in a maintainable state. I think some people are still disagreeing with this but I've seen some examples of css increasingly being driven from javascript instead of shipping as a separately loaded and created artifact. Web components sort of formalize this in html/javascript and allow you to isolate components from each other, which is another good thing. Separation of concerns and isolation are good things.
Also good is the shift to typescript, a language with a bit stricter semantics than javascript and of course better typing. The article does not mention this but given the speed and confidence with which they did this, I suspect they'd be pretty happy Typescript users.
Other than that, I think React is mostly a variation of the same kinds of design patterns that have dominated UI development for the past decades. I did some Swing development in the nineties and I still think that was a pretty nice framework to deal with relative to the current madness that is modern web development. The web can still learn a few new tricks. I have good hopes for WASM bringing some more choice and options to the scene.
- pjmlp 7y agoI believe that once WASM matures a little bit more we will get that tooling back, alongside Flash's revenge.
- jillesvangurp 7y agoSure, you can use it for good and for evil. I expect this as well. Sadly, there seem to be a few annoying limitations that browser makers seem to be stuck on for the immediate future (e.g. garbage collection, simd, threads, and a few other things). Still, wasm is good enough for pretty sophisticated stuff. I was playing a version of doom 3 ported to wasm a few days ago; with decent frames per second even and quite playable: https://news.ycombinator.com/item?id=18817278 https://news.ycombinator.com/item?id=18817278
- agumonkey 7y agoThe 90s GUI world was also a bit different in aim. Shorter in scope. Basically winforms, buttons, menus, sliders. But I believe the web added some new usages (shape shifting widgets, merging, way more animation [for better or worse], more dimension also).
- pjmlp 7y agoAll of that available on WPF, introduced with .NET 3.5 on Windows Vista, about 10 years old now.
- agumonkey 7y agoFew points: I don't assume Microsoft was innovating at any point since the 90s, wasn't WPF a response to Mac OS X compositing layer ? Also I didn't mean to glorify the web. But I really think that it was the main driver of new mainstream desires in terms of UI (not to my taste). Even more than native iphone/ipad application no matter how sleek and sophisticated because of how few dev and users they had compared to web apps.
- pjmlp 7y agoNot at all, given that a composition engine and a full blown UI framework are not the same thing. And regarding innovation, CSS now has a grid layout thanks WPF engineers initial contribution.
- Liron 7y agoNo, componentization is only one of the major concepts of React. Declarative reactive re-rendering is key, as opposed to having to imperatively code the details of how UI parts transition from one state to the next. For example, iOS UI development had componentization, yet it was still necessary for them to launch SwiftUI this year to get on the React(ish) bandwagon.
- pjmlp 7y agoJust because they lacked data binding like on WPF/QML/JavaFX/QML.
- rimliu 7y agoCSS driven by JS is, imho, just a consequence of it not being treated seriously (the same goes for JS).