Earlier quoted context omitted.
RAD never really died, we just stopped calling it that. But open Visual Studio today, and create a new Windows XAML app, then open the form designer. You can still drag a button from the toolbox, move it around, then double-click it to wire up an event handler - exactly like it was in VB6. In fact, it's quite possible to ignore all the modern stuff like data bindings entirely, and just manually read and update all wi…
A typical Delphi app might have done that, but a selling point of Delphi was that it had data binding. Connect the TDB* vies to a TDataSource, and it would show the values of a database, without requiring manual updates.
Second-Guessing the Modern Web
431–440 of 467 posts
Re: Second-Guessing the Modern Web
#432Web development clearly has a problem. I don't know enough to say what we have to do about it but I look at the current state and my face curls up in disgust
Re: Second-Guessing the Modern Web
#433Earlier quoted context omitted.
Just look around your government systems. They have had decades to fix themselves but are they fixed yet? Are they faster, less bloatier, less user hostile and privacy invasive?
Let’s hope the public sector isn’t the model that the software industry is following.
Re: Second-Guessing the Modern Web
#434Earlier quoted context omitted.
I'd say majority of programmer-hours, because anything else is a metric that's too unreliable / easy to fudge. "Individual products" is an arbitrary marketing distinction (e.g. a company I worked for could create and sell new products by tweaking few lines in a config file; every customer would get their own mix and match of software pieces). And neither investments nor revenue are directly correlated with the amount…
Using web technologies is not the same as doing crud web apps. Games for example are a very different kind of programming. And even if network admin and factory automation apps have web front-ends, that's still a minuscule part of the code.
Re: Second-Guessing the Modern Web
#435Earlier quoted context omitted.
> loads 50x-100x faster And takes less time to develop in the first place! These frameworks just seem like pure overhead to me.
You end up dupe your layout page everywhere and have a hard time update all of them if designer changed their mind. Or you could use some template system to do that… but if you need to use template, why not use react(or something like that) anyway?
You write your website in XML and the browser renders it using the template
Re: Second-Guessing the Modern Web
#436Earlier quoted context omitted.
It literally does, unless you have the form POST or GET to an API directly + a redirect from the API. You have to override the submit functionality which is built-in by the browser. You have to maintain state of what the user inputs, which the browser handles for you. You have to reset inputs, which the browser handles for you (button type=reset). And a ton of people forget to actually validate on the server because…
It's sad how convoluted something as simple as form submission has become with "modern" Javascript frameworks. I'm not sure if it is React's fault, or the way most people use it, but it does seem to degrade into a mess of over-complexity. (I've been working on web sites since CGI scripts were a thing.)
Re: Second-Guessing the Modern Web
#437Earlier quoted context omitted.
Let the page refresh, what's wrong with going to `/orders/{order_id}` page to get information about the order? It is REST-ful and static Exactly. As a bonus, you automatically get the behaviour associated with a link that browsers already implement: people can bookmark a link for later use, open it in a new window, etc. All of which would need extra effort (and thus also easily break) if it was just a clickable eleme…
Not sure why you think SPAs can't have unique URLs or real links.
Re: Second-Guessing the Modern Web
#438Earlier quoted context omitted.
You still have to debug those - if you set the wrong state/etc, things will break like before. All react does is remove the need to modify the DOM directly when you want to modify things.
But setting the wrong state is someting that happens far less and is much more traceable, because the encapsulation of state changes into a single place massively reduces the side effects (and global state) that were the cause of 90% of those bugs in the bad old days.
Which is wrong, React doesn't address that in any way, shape or form.
Re: Second-Guessing the Modern Web
#439Earlier quoted context omitted.
Very few SPAs give proper user feedback. There could be any number of silent errors in the background. Badly built apps that ignore errors and don't work well for users are certainly not limited to SPAs, and blaming SPA tech for that seems a bit unreasonable.
For "classical" websites, it was not possible to screw it up . The feeback was always there - clear, unmistakable, universal across sites. Boom, "No Internet", site's gone. Press "back" to get the previous state and click again/resubmit later. And it was nice that you could actually do that - use the "back" button to revert to the last correct state even without an Internet connection. Can't do that with almost any S…
Re: Second-Guessing the Modern Web
#440Earlier quoted context omitted.
Check out the sibling comments. Complex does not mean hard to use. My car is complex, but it's pretty easy to get a driver's license. Gatekeeping refers to making it seem like it's too hard to get into and therefore not worth trying for beginners/non-technical folk.
So by "gatekeeping", you mean that you think it just seems harder to get into, but actually isn't harder to get into? What do you think makes it falsely seem harder to get into for beginners, when it isn't really?
Writing such "more complicated" blog posts makes one look more talented?
I don't know