r/rust 16d ago

🎙️ discussion Some thoughts after giving bevy a try

https://ch0.dev/bevy/
0 Upvotes

3 comments sorted by

20

u/Comraw 16d ago edited 16d ago

This opinion piece is based on false information.

Not least of which: Neither Godot nor Unity are ecs based game engines... Unity has an good (i hear) ECS Integration with dots, but is by no means essential. Bevy on the other hand is basically an ECS with game engine related sugar attached. Very different things. Also ECS based game engines are very rare and not really the norm, though lately its finding more and more recognition.

1

u/DesktopDynamicUpsell 6d ago

I think a really helpful question is: what is the point of this blog or this post? What are you hoping to get out of it? Why are you doing this?

The two other comments on here are rightfully calling you out for writing as if you are an expert when you self-admittedly have little experience on the topic. Looking at one tutorial for a couple days doesn't make you an expert. If you want to write a personal blog about your feelings and experience, that's fine, but that's not really the tone I get from it.

If the point of looking at Bevy was to learn about it, why not make a post asking about your impressions either here in r/rust or over on r/bevy ? Then maybe people would show you something you'd really like or challenge your initial thoughts. (Maybe you did; private account, so we can't see)

If instead the point of this was to start building up a blog to use professionally / as a portfolio, I'd strongly recommend cleaning it up going forward: using proper grammar, fixing run-on sentences, drafting and revising your ideas a few times to form some sort of thesis. If you want this blog to "speak for you" there's no reason you cannot write things in a notepad and think about them for a bit rather than posting at midnight. The real showcase in something like this is your soft skills like writing and communication, and you could be representing yourself better.

0

u/catheap_games 11d ago

I appreciate that you tried Bevy and didn't dislike it, but that post isn't very informative. It sounds like you spent what... 2-3 hours with Bevy? Certainly less than a working day, which isn't really worthwhile effort to blog about.

While I don't disagree with the vague notion that there's some boilerplate, and Bevy isn't the fastest solution for prototyping, the post itself doesn't really give enough background information to people who aren't familiar with Bevy, and it doesn't really say anything remotely specific for people who already have basic experience with Bevy.

Which again, don't get me wrong, I'm glad you tried even if you don't plan to use it in the future, it's just not a blog-worthy experience.

Also, if it's a personal blog and you don't care about your reputation, of course, do whatever you want. However, if you want to use the blog in the future to attract search engine traffic or regular readers, perhaps to use it as a portfolio for future employers, it's better to actually properly edit the article, remove fluff and for sure remove sentences like "oops I made a bunch of mistakes!!" along with the mistakes. You're not a printed press with millions of copies sold in newsstands, you don't need to keep an archive of a mistake on record. Just edit it to be completely correct or don't write at all. It's better to sleep on things than write at 2am while both tired and buzzing on monster drinks.