5 ms·

Electron 30.0.0

84 points by aragonite 3y ago

gtirloni 3y ago
> Electron 30.0.0 has been released! It includes upgrades to Chromium 124.0.6367.49 Chromium 124 broke support for Wayland. I've had to downgrade to 123 to get it working again. Does it mean all apps upgrading to Electron 30 will also break? https://issues.chromium.org/issues/329678163 https://issues.chromium.org/issues/329678163
- viraptor 3y ago
  Does electron explicitly use Wayland ozone? The default setting still uses x11 and wouldn't be affected.
- c-hendricks 3y ago
  Huh, I wonder if this is why YouTube videos are just white rectangles on my VM. I had to just turn off hardware acceleration in chromium's settings.
- thelastparadise 3y ago
  Huh, so this must be why chromium has been showing as a 100% transparent box with 90's style mouse cursor glitching the past while.
dsign 3y 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 3y ago
  Was Delphi really that bad?
  - dsign 2y ago
    I 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 3y ago
  your 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 3y ago
    Are people using frameworks to avoid writing event handlers?? I use them to avoid having to manually sync UI state with data structures.
    - blueprint 2y ago
      it'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 ago
        With 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.

84 points by aragonite 3y ago

> Electron 30.0.0 has been released! It includes upgrades to Chromium 124.0.6367.49 Chromium 124 broke support for Wayland. I've had to downgrade to 123 to get it working again. Does it mean all apps upgrading to Electron 30 will also break? https://issues.chromium.org/issues/329678163 https://issues.chromium.org/issues/329678163

viraptor 3y ago
Does electron explicitly use Wayland ozone? The default setting still uses x11 and wouldn't be affected.
c-hendricks 3y ago
Huh, I wonder if this is why YouTube videos are just white rectangles on my VM. I had to just turn off hardware acceleration in chromium's settings.
thelastparadise 3y ago
Huh, so this must be why chromium has been showing as a 100% transparent box with 90's style mouse cursor glitching the past while.

dsign 3y 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 3y ago
Was Delphi really that bad?
- dsign 2y ago
  I 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 3y ago
your 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 3y ago
  Are people using frameworks to avoid writing event handlers?? I use them to avoid having to manually sync UI state with data structures.
  - blueprint 2y ago
    it'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 ago
      With 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.