3 ms·

This is a pompously written puff piece. Moving logic to the client is the right choice for an application, and the wrong choice for mostly non-interactive cont

This is a pompously written puff piece. Moving logic to the client is the right choice for an application, and the wrong choice for mostly non-interactive content. Know what you're building and choose the right tools/use the right techniques. Javascript has been (and kind of continues to be) a mess, but thankfully you can compile almost anything to WebASM these days, and 95% of people have browsers that support WebASM, so if you want to build your app in Rust with QT have at it.

Waterluvian 4y ago
Is there an example of QT via WASM? That would be quite the sight.
- CuriouslyC 4y ago
  https://www.qt.io/qt-examples-for-webassembly https://www.qt.io/qt-examples-for-webassembly
  - slightlyoff 4y ago
    Hard pass: https://www.webpagetest.org/video/compare.php?tests=230205_BiDcRF_2WD-r%3A1-c%3A0&thumbSize=200&ival=100&end=full https://www.webpagetest.org/video/compare.php?tests=230205_B...
  - BuckyBeaver 4y ago
    Holy crap is that a broken mess. They should take that down.
CharlieDigital 4y ago
> Know what you're building and choose the right tools/use the right techniques. I feel that this is the author's point: in the modern era, the "right tool" is React (in the worst possible way and often because of ignorance). As the saying goes: when all you have is a hammer, every problem looks like a nail.
jimbob45 4y ago
JavaScript is a mess but HTML is a catastrophe. I don’t understand how JS gets so much flak when most of its shortcomings are actually shortcomings of HTML interaction.
deleted 4y ago
[deleted]
mixedCase 4y ago
> Moving logic to the client is the right choice for an application, and the wrong choice for mostly non-interactive content Well then we're fucked. Juniors and a good chunk of intermediate level devs do not understand where one solution ends and another begins, let alone how they work or their trade-offs, so if we want things to not suck ass in the real world (where there aren't enough senior devs who actually know and care) we'll have to figure this one out. My gut says that it starts with a solution similar to Qwik, but I haven't thought about the DX implications deeply enough.
BuckyBeaver 4y ago
Is Rust with Qt a thing?

Waterluvian 4y ago

Is there an example of QT via WASM? That would be quite the sight.

CuriouslyC 4y ago
https://www.qt.io/qt-examples-for-webassembly https://www.qt.io/qt-examples-for-webassembly
- slightlyoff 4y ago
  Hard pass: https://www.webpagetest.org/video/compare.php?tests=230205_BiDcRF_2WD-r%3A1-c%3A0&thumbSize=200&ival=100&end=full https://www.webpagetest.org/video/compare.php?tests=230205_B...
- BuckyBeaver 4y ago
  Holy crap is that a broken mess. They should take that down.

CharlieDigital 4y ago

> Know what you're building and choose the right tools/use the right techniques. I feel that this is the author's point: in the modern era, the "right tool" is React (in the worst possible way and often because of ignorance). As the saying goes: when all you have is a hammer, every problem looks like a nail.

jimbob45 4y ago

JavaScript is a mess but HTML is a catastrophe. I don’t understand how JS gets so much flak when most of its shortcomings are actually shortcomings of HTML interaction.

deleted 4y ago

[deleted]

mixedCase 4y ago

> Moving logic to the client is the right choice for an application, and the wrong choice for mostly non-interactive content Well then we're fucked. Juniors and a good chunk of intermediate level devs do not understand where one solution ends and another begins, let alone how they work or their trade-offs, so if we want things to not suck ass in the real world (where there aren't enough senior devs who actually know and care) we'll have to figure this one out. My gut says that it starts with a solution similar to Qwik, but I haven't thought about the DX implications deeply enough.

BuckyBeaver 4y ago

Is Rust with Qt a thing?