Man it’s not lightweight, but damn, if CSS and JS isn’t a really easy way to build cross platform UIs than other options like Qt. There’s a reason why electron is so popular.
One of my experiments, an overlay for a game using camera position API to draw a 3d scene over the game, rendering things as if they were in the game (with some limitations) uses electron and three.js
It’s pretty fast, uses about 100-150mb ram, and works pretty well. A similar overlay using same approach but written in C and opengl take ~200+ mb and a c# one 150-250 mb. The c# one has more features overall so it’s not a complete comparison, but then my overlay can do things the other can’t too.
So was all this bloat inevitable as hardware got better, or is there a way to go back? It feels like a ripoff that our computers are 1000x better but they’re maybe 10x faster once all the shitty software is taken into consideration.
Better education. Don’t scare people who’re learning programming away from the lower-level stuff, especially as people are even getting scared to use type declarations, not just the pointers (of which I was fearmongered with in college, as they told me Java is the future).
Better portable APIs. Thanks to WebAssembly, one could easily have both something portable in a web browser and as a native desktop app, except instead we get browsers running said applications. I had some thinking about such a project, but then I remembered my iota project (a D-native replacement of SDL/SFML/GLFW, but without bloat by including standard library features), and then stopped thinking about it immediately, since a much smaller project already causes me too much headache. (Someone has a handy guide on win32 API? I have issues on getting certain messages produced, like input language change, and I don’t know if I glimpsed over some functions that enable them and just weren’t included in the documentation of the input language change event codes.)
You know, I haven’t worked on a super big project, but I feel like every time I’ve gotten a type error in a static language it’s pointed to something wrong with my underlying reasoning.
In the short run, yes. In the long run, this just makes a bunch of coders that are now afraid of type declarations, because they were scared away from it with the “what if you have to choose?” tagline, thus making turning back to the proper way of doing things harder.
Just from context, I’m guessing it means that you might type things one way and then need to use them another way later, and dynamically typed languages are sold as not having that problem.
I was thinking about this a bit. Does that mean you can develop a piece of software much more cheaply now? I have a fear that companies writing software get a 10% discount from writing bloat, while clients wind up using 10,000% the resources and are just so used to it they don’t complain.
Don’t worry, texteditor.com is also available as an app on Windows, macOS and Linux thanks to Electron.
It only needs 300 megabytes and you can style it with CSS.
It also only takes a single gigabyte of RAM per file being edited, Isn’t that fantastic?
Oh I love electron
Man it’s not lightweight, but damn, if CSS and JS isn’t a really easy way to build cross platform UIs than other options like Qt. There’s a reason why electron is so popular.
Shhhh, don’t tell anyone
Oh no, I love electron. That’s not a dig on it, it’s just very much a resource hog.
It doesn’t have to be.
One of my experiments, an overlay for a game using camera position API to draw a 3d scene over the game, rendering things as if they were in the game (with some limitations) uses electron and three.js
It’s pretty fast, uses about 100-150mb ram, and works pretty well. A similar overlay using same approach but written in C and opengl take ~200+ mb and a c# one 150-250 mb. The c# one has more features overall so it’s not a complete comparison, but then my overlay can do things the other can’t too.
So was all this bloat inevitable as hardware got better, or is there a way to go back? It feels like a ripoff that our computers are 1000x better but they’re maybe 10x faster once all the shitty software is taken into consideration.
I have a few suggestions:
You know, I haven’t worked on a super big project, but I feel like every time I’ve gotten a type error in a static language it’s pointed to something wrong with my underlying reasoning.
nope. The bloat is there mainly because it makes the job easier for the devs.
In the short run, yes. In the long run, this just makes a bunch of coders that are now afraid of type declarations, because they were scared away from it with the “what if you have to choose?” tagline, thus making turning back to the proper way of doing things harder.
Can you talk more about this? I’ve never heard that tagline and can’t figure out what it’s supposed to mean.
Just from context, I’m guessing it means that you might type things one way and then need to use them another way later, and dynamically typed languages are sold as not having that problem.
I was thinking about this a bit. Does that mean you can develop a piece of software much more cheaply now? I have a fear that companies writing software get a 10% discount from writing bloat, while clients wind up using 10,000% the resources and are just so used to it they don’t complain.
It’s not really inevitable, it’s just a consequence that develops can get away with being lazy because the hardware can cope with it.
Of course! And it definitely does not try to pry all info about the user that it can and definitely the company behind would not use that in any way.
And then youll only need a near 16gb of ram to text a text file.
That’s a very lightweight one. Stakeholders say it needs to be at least 600mb.
I like that you can just install it straight from the Windows Store, no need to even bother opening Edge to download it.
who dare speak of the runes?
SPEZ!!! I love spez! He’s so nice he did r/place again! Also, windows store?? I only know apt
Why is your profile picture the hyprland logo lmao
And the app is just a chromium browser without the ability of typing in your own URL.