this post was submitted on 11 Feb 2024
14 points (85.0% liked)
Learn Programming
1615 readers
2 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is the way.
I have nothing useful to add, as I noped-out to become a full web developer, for exactly this reason.
If I desperately needed to call into C++ libraries, I would just build the whole thing in C++. And you're right, it won't look modern.
That said, it sounds like you're asking the person running your app to give you an unprecedented amount of trust in the modern age (running locally, unsandboxed, running code from unmanaged libraries, presumably outside an app store ecosystem).
If you have users, in that situation, I'm guessing you have a deeply compelling solution.
And if I were in those shoes, I would build it 100% in C++ and let my users live with it looking old school. They'll notice the appearance once or twice, then they'll notice all the more important functionality for a lot longer.
This is definately the way with microsoft. Use this new shiny framework... 18 months later. No Use this one its' much better, just rewrite all your code again! 18 months later....