3 ms·

Next step - get rid of Node/JS and use plain old Qt natively, e.g. with C++.

• horsawlarway 7y ago
  Next step - just go use windows forms. Ammirite guys?!?!?! Who doesn't love outdated frameworks that artificially limit my options and dev resources!
  • pjmlp 7y ago
    Oh how I wish some frameworks would be half as capable as Windows Forms and the third party vendors eco-system. To talk about outdated frameworks, first provide tooling at the same feature level.
    • johndubchak 7y ago
      MSFT did get their tooling right. That's what developers liked early on and became somewhat dependent on was their tools.
      • pjmlp 7y ago
        I rather be dependent on vendors' tooling and enjoy productivity than dealing with lower grade tooling for the greater good or whatever. Be it Borland, Microsoft, Google, Apple, Oracle, OutSystems, Adobe, Qt, ...
• excursionist 7y ago
  That would kinda defeat the purpose of this 'Node-GUI' project. [EDIT] This project literally brings Node/JS/CSS on top of Qt - Node-GUI without Node/JS is, you guessed it - Qt.
  • pjmlp 7y ago
    Qt already supports JavaScript out of the box, no need for node.
    • ebg13 7y ago
      But what will I do without left-pad?
      • pjmlp 7y ago
        Use padStart().
    • nocman 7y ago
      Yes, but it may be important to some folks to have the node runtime available for an application they would like to be desktop based. I agree, though, that it would be important to decide if the built-in Javascript support fills the need before considering a solution like NodeGUI.
• joezydeco 7y ago
  Shhhhhh. That's blasphemy here.