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”.
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”.
clap and bevy are big offenders there. It’s really hard to learn how to use them due to this.
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#.
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.
What’s the error bar on that statement of yours?
I’d instantly reject such an approach. Find a better way to do things.
Rust had the same issue with tokio vs. async-std. I don’t think this was ever resolved explicitly, async-std just silently died over time.
My company is just doing a kanban board with weekly meetings to discuss the progress and what tickets will be worked on next. The major problem we ran into was when management asked “So, when is the release going to be? When are you done with that project?” about one month before we actually released. I simply had no answer at that point, because that’s not something these tickets with no estimates and no velocity tracking can provide.
The gleam name is also already taken by some OpenGL bindings on crates.io.
Bevy UI is so far off from what I need that I didn’t even bother. I started integrating Flutter instead.
As someone who has tried doing multithreaded design with Arc/Mutex, this is a complete nightmare. You constantly get into deadlocks and performance is abysmal, because Mutex is serializing access (so it’s not really async or multithreaded any more).
NVIDIA has been struggling in recent years to find use cases for their graphics cards. That’s why they’re pushing towards raytracing, because rasterization has hit its limit and people no longer need to upgrade their GPU for that (they tried pushing towards 8k resolution, but that’s complete BS for screens outside of cinemas). However, most people don’t care about having better reflections and indirect lighting in their games, so they’re struggling to get anywhere in the gaming market. Now NVIDIA is moving into other markets for their cards that don’t involve gamers, and they’re just left as an afterthought.
I don’t think that this will ever change again. Games like DOTA, Fortnite and Minecraft are hugely popular, and they don’t need raytracing at all.
I personally tried going towards fluid simulations for games, because those also need a ton of GPU resources if calculated at runtime (that was the topic of my Master’s thesis). However, there have barely been any games featuring dynamic water. It’s apparently not interesting enough to design games around.
The others are probably still busy installing the fax-to-toot gateways.
If you’re talking SQL, it would be SELECT * FROM posts ORDER BY dateposted LIMIT 100
.
The most expensive part is probably “not blocked by the user”, which X recently got rid of.
Such an algorithm has to run server-side, since it needs access to the full database of content.
It would be possible to allow users to upload their own algorithms (for example via Web Assembly), but I don’t know about any service that allows for that.
Tesla should mill the car from one solid block of steel.
You only have to cry once a day to power your contact lenses!
Since the antitrust laws don’t exist any more, it’s legal, yes. If you don’t want that, you have to switch to Linux.
My experience has been that good documentation is mostly something done if somebody gets paid for the work. People working on stuff in their spare time just don’t care enough to document their project.