5 ms·
Not directly related, but compared with the event hell that UI development was twenty years ago, something like Vue.js (or React, but I haven’t used React) is a
by dsign 2y ago
Not directly related, but compared with the event hell that UI development was twenty years ago, something like Vue.js (or React, but I haven’t used React) is a pleasure to work with. So it kind of makes sense to have something like electronjs that bridges blood-and-sweat-and-tears Javascript framework achievements with the world of desktop development.
- throw-the-towel 2y agoWas Delphi really that bad?
- dsign 2y agoI preferred the native Windows API[^1] from the point of view of organization. In theory, you could use it to design the data flow in your application in whichever way you wanted. And yes, the operating word is "design", meaning that you needed to be decent at architecting software. And this was before .Net and before many C++ facilities that would make life easier (e.g., std::shared_ptr, or even boost::shared_ptr), when making a large scale application in C/C++ required some serious chops I was too young to have. [^1]: https://learn.microsoft.com/en-us/windows/win32/winmsg/using-messages-and-message-queues https://learn.microsoft.com/en-us/windows/win32/winmsg/using...
- blueprint 2y agoyour only problem with events is you dont know how to write code that remains simple react and view frameworks arent the solution to that problem. react isnt even reactive - you still have to deal with event -> repaint. react only tried to obscure that into a constraint language instead while actually hamstringing you and pushing the complexity elsewhere events are here to stay and that's a good thing. these reactive frameworks borne out of an attempt to avoid events or complexity don't eliminate events or complexity - they make everything into an event or a necessarily complex structure in their attempt at pathological avoidance. the solution is factoring and proper honesty in your semantic names. but most people would rather blame their (very ample) tools than their skill or laziness or apathy. i will say async/await is a big help for humans but synchronous code vs asynch as you may know is not the problem at hand here.
- eternityforest 2y agoAre people using frameworks to avoid writing event handlers?? I use them to avoid having to manually sync UI state with data structures.
- blueprint 2y agoit's the same thing. and you still have to manually sync to the exact same degree using these frameworks or not. state setting is part of the von neumann architecture itself so it appears directly in all programming languages you use. so the problem you say you're using them to solve isn't the problem.
- eternityforest 2y agoWith Vue, I add an element to a list. With vanilla JS, I would have to add the item to the list, then get the parent element, then create a div containing a bunch of hardcoded stuff, give it an id, keep track of that id, insert the item, then when I remove the item I would have to remove the item from the list. That could double the amount of cod e needed in most stuff I do.
- blueprint 2y agoVue is vanilla JS - it is a construct of vanilla JS - so it is not what I'm talking about when we talk about generations of languages etc. You still interact with it procedurally or imperatively. Overall, Vue is honest. React is decidedly not.
- eternityforest 2y agoI don't have any direct experience with React, but it does seem to be overwhelmingly popular. I assume the devs making insanely complicated stuff at fortune 500
- blueprint 2y ago