4 ms·
So let me just check that I understand this correctly. A whole bunch of problems that were "solved" (or at least, had fairly good solutions) in the context of
by PaulDavisThe1st 7y ago
So let me just check that I understand this correctly.
A whole bunch of problems that were "solved" (or at least, had fairly good solutions) in the context of desktop GUI toolkits have resurfaced in the context of application development confined to the web browser.
Almost none of the previous "solutions" are usable, because of the specifics of the theoretically portable "browser platform" for which all this development is taking place.
So instead, an entirely new set of frameworks are slowly being developed to solve the same set of problems that desktop developers worked on 20+ years ago, and are slowly converging on similar approaches?
Is that too cynical, or just about right?
- rsynnott 7y agoYeah, no, that seems to be about the size of it.
- heleninboodler 7y agoI'd say it's pretty correct, but I'm not sure I'd agree with what I think your conclusion might be. If you want user interface toolkits based on 20 year old paradigms in your browser, just build your app on something like YUI. :) "Make it like the desktop" was the initial wave of web developers' first instinct, and it wasn't great.
- cactus2093 7y agoGenuinely curious, as someone who wasn't building desktop apps 20 years ago, what are the toolkits you're referring to? When I google "cross-platform desktop frameworks", the entire first page of results are all about the modern toolkits like Electron, Photon, ReactNativeEverywhere, etc. So it seems like your complaint is many years too late at this point. Maybe there were solutions to this 20 years ago, but if I'm starting from scratch today trying to build a cross-platform app, what I'm looking for are frameworks that are mature, well documented with lots of tutorials on how to do basic things, and have a large community around them for getting help on e.g. stackoverflow. It doesn't really matter what has been around longer, if the newcomers have surpassed it on these fronts.
- int_19h 7y agoQt would be an example of a desktop UI framework that was around 20 years ago, and is still popular today. It's also far more mature and stable than Electron etc, and better documented. I don't know whether there are more Electron apps these days around than Qt apps, but it's certainly neither outdated nor obscure.
- PaulDavisThe1st 7y agoQt is already mentioned. GTK+ was also around 20 years ago (actually quite a lot more than that). For people dealing with media stuff, these days there's also JUCE though that is a relative newcomer. There was also FLTK, which I think it still around. Oh, and WxWidgets which was a very thin wrapper around the native GUI API on all 3 major platforms.
- cameldrv 7y agoQt, Wx, GTK, Tk for starters.
- yawaramin 7y agoThere was Delphi ... https://www.embarcadero.com/products/delphi https://www.embarcadero.com/products/delphi
- rendall 7y agoHow do these older frameworks (Qt, etc) approach state management?
- PaulDavisThe1st 7y agoWell, first of all, the problem in its most basic sense doesn't even really exist for many places where you would use "Qt, etc". You wouldn't be reacting with a remote server or if you are you have a stateful connection with the remote server. That's true whether the "remote server" is just a database server or something more specific. But going somewhat deeper (and based on reading all the defenses of "React, etc" in the comments thus far), the fundamental difference is that if you were using a desktop GUI toolkit, you would almost certainly assume that there's essentially zero cost (or almost neglible cost) to the communication between the data (model) and the GUI. This is (one of the things) that is so different for web development, where everybody is struggling to optimize away roundtrips back to the data (server), because it actually costs. Put differently, whatever protocols might be implemented inside a desktop GUI to talk to a not-in-memory data source, the protocols are almost certainly designed for precisely that purpose. Whether its a vendor-supplied connection to an SQL database, an application-specific serialization/deserialization protocol, some IP-based message passing protocol ... whatever, it will all have been designed for the express purpose that it is being used for (more or less). HTTP? Ahem. Granted, web app development has augmented HTTP in various ways (most dramatically would probably be websockets/webrtc). But fundamentally, the state management issue in a web app originates with the fundamentally stateless communication protocol being used between the app and the data sources/servers it is dependent on.
- andrewstuart 7y agoI don't think this is correct. I don't believe the concept of one way data flow was in the old desktop app approach was it? Nor was the idea of "props" i.e. a consistent mechanism for pushing parameters down to subcomponents through a consistent and flexible interface. Nor was the idea of the render function - giving components a consistent function used to display itself. Also gigantic leaps are being made in the area of simple componentisation - we are now down to very pure functions that handle a very constrained task. State management in ReactJS especially with hooks is giving much more simple and clean mechanisms for handling cross cutting. Old desktop applications, because they did not have a core application "cycle/flow" and were not arranged as a tree of components, had a tendency to end up as a spaghetti mess of complex highly coupled interactions with the whole thing risking collapsing under its own weight of complex interactions. Modern frameworks like ReactJS address these things by reducing complexity, increasing modularity via components, giving applications a general structure which is a hierarchy of components, giving all applications a consistent model for data flow, forcing a simpler mechanism for data sharing via the one way data flow rather than the more highly coupled two way data binding, and lately, emphasising the power and simplicity of plain functions over classes, objects and inheritance. Surely there's other innovations too I haven't thought of. Characterising modern web development frameworks as somehow only now catching up to 20 year old desktop development does not seem correct to me. Such an idea does perpetuate the myth though that the JavaScript world is full of dumbos badly trying to reproduce what all the smart "real developers" did a long time ago.
- PaulDavisThe1st 7y agoTo be honest, most web apps remind me much more of the old "software development tools" that used to come (still come?) with databases from 20-30 years ago. Web apps seem much closer to the database read/edit interfaces from that time (though much, much prettier and generally more sophisticated): there's a simple model (which does include one way data flow) - there's a data store somewhere, and the task at hand is some combination of: 1. present that to the user. 2. allow the user to enter new data. 3. allow the user to modify the data. Oracle and others before and after them had a rich set of tools to develop primarily terminal-based applications for these purposes, which began to get "graphical" sometime around the end of the 1980s. These days, I suspect almost nobody uses that toolchain, and instead does the exact same tasks (again, much prettier, more visuals, more interactivity) via the browser. Desktop applications started moving away from this model as "creation" apps started to emerge, probably starting with "desktop publishing" and moving on to include graphics in general, audio and video. By the time you get to Photoshop, for example, considering the task to be moving data either from or between a data store and a user interface doesn't really get you very far (though it's still an important aspect). It is not true that old desktop applications did not have a tree of components. That's a core aspect of every desktop GUI toolkit that i'm familiar with. One thing that the desktop GUI toolkits didn't do very well was that tended not to support the original conception of MVC (not the current one found on the web). For example, when you interacted with some widget, it would change its visual state before anything took place in the "model". My vague impression of quite a few of the web component models is that they at least avoid this some of the time - the user interacts with them, and they (mostly) only change their appearance to display a change in the model.
- erikpukinskis 7y agoAll technology goes through two somewhat independent cycles, continuously: 1) The bloat cycle 2) The disruption cycle The bloat cycle is where you have a “platform” that does more and more until it has a lot of features that most users don’t need. Eventually the cost of supporting those random features gets too high and there is pressure on people to hack together an alternative micro-platform that does some arbitrary subset of things. If that subset is actually a superset of “must-have features” for a large number of users the micro-platform becomes a new platform and the cycle repeats. The disruption cycle is when there is a singular feature that is prohibitive to add to the framework, because of past decisions. Businesses working on the platform will just work around the hole, or fill the hole in a hacky way. This creates pressure for someone to create a new platform that solves that one unsolved problem. It can leave many solved problems unsolved and still ascend to dominance under conditions famously described in “The Innovator’s Dilemma”. This would be something like “multiple users work on the same surface” or “works the same-ish on literally all the OS’es” features of the web. These cycles might seem pointless, but they’re not because you end up in a different place than where you started. You get some fundamental simplifications and new features each time you go around. Ideally as a user you want to time your entry into the cycle so you don’t have to deal with the regression phase.
- wwright 7y agoIMO, this same pattern is followed by a lot of other things: - corporations - governments - TV shows - music - all human relationships Sometimes you want to be with the group, other times you think it’s easier to be without the group. It’s part of being human.
- jrochkind1 7y agowell said and insightful I think! I think these cycles are just results of human social behavior around software platform technology; whether they have a point or are pointless -- they can be either. Sometimes it's two steps back one step forward, other times the reverse.
- kerkeslager 7y agoIt's so frustrating. React/JSX, and maybe Immer, is actually really good--it's revolutionized the way I write frontends. But I'm wary of bringing these tools into products, because I know that then I'll be having to constantly fight to not bring in whatever global state management nonsense people on my team discover first. If you stick around long enough you see global state systems collapse under their own weight into trashpiles of unintelligible code, but for the first quarter or so, it seems really simple to just pull the whole application into global state.
- austincheney 7y ago> Almost none of the previous "solutions" are usable, because No, it’s because developers are shamed and generally unemployable for writing code that doesn’t make use of a colossal super framework.