7 ms·

Qt runs like shit compared to Electron, and its license prices are way too expensive. Moreover it's C++ so a deprecated, unsafe, un-cool and uninteresting dying

Qt runs like shit compared to Electron, and its license prices are way too expensive. Moreover it's C++ so a deprecated, unsafe, un-cool and uninteresting dying language no one wants to write anymore.

sudosysgen 5y ago
Really? Make a fully featured modern DE/WM/Compostor in electron that fits into 128MB of RAM and runs at 60fps on a Pentium III in daily usage then with a suite of apps. Or better yet, make a web engine from scratch, that is, write the rendering engine, compositing engine and so on using Electron primitives. Because both of these work very well when using Qt as a base, see LXQt and KHTML.
- nyanpasu64 5y ago
  Correction: LXQt uses Openbox (not Qt) for windowing, and offers a choice between no compositor (by default) or one like picom (not Qt) or KWin (Qt Quick, JS-based, I wish it wasn't JS-based but it's too late to change that).
  - sudosysgen 5y ago
    Qt Quick is not based on JS. JS is merely an option for Qt Quick.
- npigrounet 5y ago
  You do know very well that all of this is going to happen someday. Everything will be re-written in JS just because it's possible. And numbers will show that those solutions beat C++ in speed and resource usage, like VSCode does.
  - pjmlp 5y ago
    While using a runtime written in C++.....
    - npigrounet 5y ago
      In a few years or so, the runtime itself will be in JS. It's unavoidable, this is the way things are.
      - pjmlp 5y ago
        Until JavaScript has the language features to be able to bootstrap itself, that won't happen.
        gpderetta 5y ago
        As long as JS is jitted/interpreted at runtime, I don't even know how that would work!!
  - sudosysgen 5y ago
    What does VS Code beat in speed and resource usage? Be fair and compare it to other software with only colourization, Git support and extension support. JS can get close to C++ in speed but the same program in JS will always need more memory.
    - npigrounet 5y ago
      I doubt that. C++ programs have always tons and tons of memory leaks.
      - sudosysgen 5y ago
        Which you can fix if you're competent. If we're looking at bad programs, JS programs are famous for importing 15MB+ of code for simple functions.
pjmlp 5y ago
That must be why WinUI is written in C++, Metal uses C++ shaders, or CUDA hardware is designed according to C++ semantics, then.
- gpderetta 5y ago
  As per parent post, C++ it is not cool and hip anymore, so it won't keep CADT programmers interested long enough to get the work done.
  - pjmlp 5y ago
    Well, 99% of most programming languages fit that as well.
    - gpderetta 5y ago
      That's why according to the parent, everything is going to be rewritten in JS very soon! /rollseyes
- npigrounet 5y ago
  Let's just wait for JS bindings for all these things and let's see what competent people will use. You already know the answer, do you? Yes, it'll be the JS bindings.
  - pjmlp 5y ago
    Someone has to write those bindings, and they won't live forever.

sudosysgen 5y ago

Really? Make a fully featured modern DE/WM/Compostor in electron that fits into 128MB of RAM and runs at 60fps on a Pentium III in daily usage then with a suite of apps. Or better yet, make a web engine from scratch, that is, write the rendering engine, compositing engine and so on using Electron primitives. Because both of these work very well when using Qt as a base, see LXQt and KHTML.

nyanpasu64 5y ago
Correction: LXQt uses Openbox (not Qt) for windowing, and offers a choice between no compositor (by default) or one like picom (not Qt) or KWin (Qt Quick, JS-based, I wish it wasn't JS-based but it's too late to change that).
- sudosysgen 5y ago
  Qt Quick is not based on JS. JS is merely an option for Qt Quick.
npigrounet 5y ago
You do know very well that all of this is going to happen someday. Everything will be re-written in JS just because it's possible. And numbers will show that those solutions beat C++ in speed and resource usage, like VSCode does.
- pjmlp 5y ago
  While using a runtime written in C++.....
  - npigrounet 5y ago
    In a few years or so, the runtime itself will be in JS. It's unavoidable, this is the way things are.
    - pjmlp 5y ago
      Until JavaScript has the language features to be able to bootstrap itself, that won't happen.
      - gpderetta 5y ago
        As long as JS is jitted/interpreted at runtime, I don't even know how that would work!!
- sudosysgen 5y ago
  What does VS Code beat in speed and resource usage? Be fair and compare it to other software with only colourization, Git support and extension support. JS can get close to C++ in speed but the same program in JS will always need more memory.
  - npigrounet 5y ago
    I doubt that. C++ programs have always tons and tons of memory leaks.
    - sudosysgen 5y ago
      Which you can fix if you're competent. If we're looking at bad programs, JS programs are famous for importing 15MB+ of code for simple functions.

pjmlp 5y ago

That must be why WinUI is written in C++, Metal uses C++ shaders, or CUDA hardware is designed according to C++ semantics, then.

gpderetta 5y ago
As per parent post, C++ it is not cool and hip anymore, so it won't keep CADT programmers interested long enough to get the work done.
- pjmlp 5y ago
  Well, 99% of most programming languages fit that as well.
  - gpderetta 5y ago
    That's why according to the parent, everything is going to be rewritten in JS very soon! /rollseyes
npigrounet 5y ago
Let's just wait for JS bindings for all these things and let's see what competent people will use. You already know the answer, do you? Yes, it'll be the JS bindings.
- pjmlp 5y ago
  Someone has to write those bindings, and they won't live forever.