I just checked again, and apparently they finally added some documentation since I last checked. The section about the macro stuff just used to say “look at the examples”.
anlumo
That’s not how research & development works. Nobody asks for a specific person there. Stuff just doesn’t get done.
I’d rejoin for double the wage I previously had. Need to build up an emergency fund for this precarious position.
It’s the confidence with which he sprouts his nonsense. People flock to confident personalities, because they must know a lot of things (presumably).
Apple used to be that way, but they too got caught in the enshittification cycle.
It’s just too easy to build up a brand and then sell cheap shit for big money.
Ist das klug? Damit würde die AfD noch mehr von Russland abhängig werden.
clap and bevy are big offenders there. It's really hard to learn how to use them due to this.
There’s the saying that software development is one of the few crafts where the craftspeople also create the tools for themselves.
OP is talking about a different kind of skill issue than the article. The article is about skill issues in writing Rust code, while OP is about skill issues in choosing the right technology for the right task.
Not picking Rust for code that has to be prototyped quickly and iterated a lot is kinda obvious. The solution would be to use Rust for the core engine where the requirements are clear and something else (lua? Python?) for the gameplay code. Even the engine the author wants to switch to does the same with with the divide between C++ and C#.
Es ist der freie Markt! Angebot und Nachfrage.
Bevy's ECS is tied up with Rust's trait system, therefore it's impossible to use a different language.
Bevy has added runtime-defined systems and components to enable scripting integration in recent updates.
The LGPL is inherently incompatible with anything on Apple's App Store, so if there’s a chance that I might want to publish it there I can’t touch anything-GPL.