Mentioning Electron to solve Unicode is like thinking about a bulldozer when you need to unclog your toilet.
1,123 karma · joined February 12, 2020
Mentioning Electron to solve Unicode is like thinking about a bulldozer when you need to unclog your toilet.
> Why would you want to render text in a gaming engine in the first place ...
Just about every game needs text, including Unicode text. Every proper engine handles it.
Instead of randomly picking from the 4 sides, pick one from the set of legal moves.
- Bloat... Both are extremely heavy dependencies if you want "the real deal" vs a stripped down version that looks like Python or JavaScript.
- Performance too. Python is slow. JavaScript too, unless you use the modern JITs.
- Licensing perhaps?
- Lack of support for that use case?
- Painful interop? No idea.
I am confident if Godot sees usage as a GUI/app framework, they will take care of that.
A game engine can avoid redraws trivially if no relevant input/event has occurred.
Further, AFAIK some graphic APIs do support dirty rectangles too, but to be honest, for desktop/laptop GUI apps I doubt it matters compared to anything else going on in the system.
And GUIs runs perfectly fine on integrated GPUs, further reducing the cost.
Blender does this perfectly fine, for instance.
rust-analyzer is great and we have waiting for it a long, long time. But it is not an IDE. Neither is the MS C++ extension.
Usually a single line does it in all of them, either in the shell or in a config file.
I call FUD.
So does any of the main package managers for C++.
> had an easier time with it
That is an empty argument. Not to mention Rust is only now in 2020 starting to get actual IDE support.
For C++ there are at least 8 major production GUI IDEs available, plus a few TUI ones too, plus dozens and dozens of specialized tools around it.
Even without a package manager adding dependencies manually is quite easy for the vast majority of popular libraries. With a manager it is the same as cargo.
I assume you are talking about old, broken, unsupported, closed source, binary only libraries, but then it is not a meaningful comparison.
The question is the opposite: you have to prove to managers the benefit overcomes the risk of using a new language. Rust is still not nearly stable nor popular enough for many fields.
Go is a very different language with different goals and constraints, so the question does not really fit.
> Rust and Go are much simpler to learn
Go is a simple language, yes. Rust is a different beast with the same intrinsic complexity as C++.
> can do everything that C++
Not exactly true (for the moment). Rust is lacking on const generics, HKTs and other details.
> sane, simple and clean build systems/package managers
That is not a big argument for the kind of projects is used for.
And it is not true either, since nowadays there are several competing, modern package managers for C++ too (build2, Meson, Conan, modern CMake...).
> not to mention async/await concurrency
The async IO model has been available in many languages for many years, including C++. In the recent years several languages (including Rust and C++) are bringing syntax sugar to let the compiler create the state machines. But it is not the only way of doing async.
It is not a C++ idea anyway, older languages have had similar facilities.
Last year was the transition period to the new UI, new renderer and everything else. 2.80 was not polished at all.
Since then they got access to way more funds from major FAANGs (NVIDIA, AMD, Microsoft, Intel...) and announced and release the first LTS which are the ones intended to be used by commercial studios for long-term projects.
Now they need the time to use that money to hire and speed up things. Future looks very, very bright for Blender.
Basically you are saying code performance is nondeterministic across your user base and across time too?
I am glad WebGL is a thing for pages that need some 3D widgets where performance is not a big deal. But for general software or games? I will keep my native software.
I am really curious, specially given there are many other languages out there to move to vs js.
Other critical bits for commercial development in many industries (certs, standards, third-party support, official bindings...) are also completely lacking.
That is not something against Rust, it is just what happens until things get popular enough.
That said, there are many use cases where performance does not matter as long as it is not "too much", for different values of "too much" depending on context.
Putting them in the list but leaving out all console manufacturers and operating system devs? Strange.
I hope they keep the team smallish as always!
So what? I haven't said anything about that.
As a data point, Steam (as a store) was already there 15 years ago.
> And those stores (..) is what allows all these things in native apps
Stores don't change what a native application can or cannot do.
Browsers have "won" for other reasons: licensing control, unavoidable analytics, subscription mechanics... All that combined is a dream for a publisher.
And publishers were readily available too, like for any other physical item.
If something was wanted, it did not matter, it would sell and distribute itself. Take a look at things like Lotus, Office, Windows, Doom...
Citation needed.
20 years ago you could make a commercial app with a GUI in no time with things like Delphi or Visual Basic.
Now to do the same we have to learn several standards and languages and libs/frameworks and build tools and server admin tools and...
A project is added to a framework.