3 ms·

> I'm developing a Notion alternative in Qt C++ ...which is not native to the platform, so you're in a way proving my point. Unless I become professional writ

> I'm developing a Notion alternative in Qt C++ ...which is not native to the platform, so you're in a way proving my point. Unless I become professional writer, or develop an OCD about typing latency - standard browser and Electron apps (looking at you VSCode and Logseq) are good enough for my use cases. And don't misunderstand me, there's absolutely a place for native applications - when performance matters. Millions of CRUDs on app store are not one them.

rubymamis 3y ago
> ...which is not native to the platform "The Qt Rendering Hardware Interface (RHI) translates 3D graphics call from Qt applications to the available graphics APIs on the target platform."[1] [1] https://doc.qt.io/qt-6/topics-graphics.html https://doc.qt.io/qt-6/topics-graphics.html
- wiseowise 3y ago
  That’s irrelevant, they’re not using native widgets.
  - rubymamis 3y ago
    It's not because it means a Qt app can match a native application in performance (actually, my note-taking app is way faster than Apple's Notes). In terms of styling, yes, the styling of Qt Quick Controls is not quite good as to resemble native widgets, and I had to do a lot of work to get my own styles right. At least on macOS, I believe my app looks and behave like a native app (with 2 exceptions that I aim to solve soon).
    - wiseowise 3y ago
      > Qt app can match a native application in performance Correct. That doesn’t make it a native application, still.
      - rubymamis 3y ago
        In the Qt world, we say native-like.
scarface_74 3y ago
So that’s the argument for PWAs? They suck just like Electron apps but they are good enough?
- wiseowise 3y ago
  Press “parent” button twice to hear reasons for web applications. Your “suck” doesn’t mean anything to me. There are benefits and drawbacks to every approach. Benefits and potential of web applications and browser far outweigh current and future drawbacks for me.

rubymamis 3y ago

> ...which is not native to the platform "The Qt Rendering Hardware Interface (RHI) translates 3D graphics call from Qt applications to the available graphics APIs on the target platform."[1] [1] https://doc.qt.io/qt-6/topics-graphics.html https://doc.qt.io/qt-6/topics-graphics.html

wiseowise 3y ago
That’s irrelevant, they’re not using native widgets.
- rubymamis 3y ago
  It's not because it means a Qt app can match a native application in performance (actually, my note-taking app is way faster than Apple's Notes). In terms of styling, yes, the styling of Qt Quick Controls is not quite good as to resemble native widgets, and I had to do a lot of work to get my own styles right. At least on macOS, I believe my app looks and behave like a native app (with 2 exceptions that I aim to solve soon).
  - wiseowise 3y ago
    > Qt app can match a native application in performance Correct. That doesn’t make it a native application, still.
    - rubymamis 3y ago
      In the Qt world, we say native-like.

scarface_74 3y ago

So that’s the argument for PWAs? They suck just like Electron apps but they are good enough?

wiseowise 3y ago
Press “parent” button twice to hear reasons for web applications. Your “suck” doesn’t mean anything to me. There are benefits and drawbacks to every approach. Benefits and potential of web applications and browser far outweigh current and future drawbacks for me.