IceSentry

> I'm saying if they're breaking shit in patch release

You just assumed this, but this isn't true. Bevy uses semver like most of the rust ecosystem.

The warning is just telling people that the breaking changes will be frequent. It doesn't mean they will be in a patch release. I don't understand what's to be confused about here. Bevy never specified any custom release strategy because there isn't one, it's just semver like almost everything else in rust.

No, the statement says that there will be frequent breaking APIs, it doesn't make any claim about release strategy. Releasing breaking changes on every 0.minor release perfectly fits in this definition.

Making a quick judgement based on an assumption that's provably wrong isn't really the definition of a professional engineer.

Bevy and rust in general uses semver with a special case for 0.x releases. See https://doc.rust-lang.org/cargo/reference/semver.html

> Initial development releases starting with "0.y.z" can treat changes in "y" as a major release, and "z" as a minor release. "0.0.z" releases are always major changes. This is because Cargo uses the convention that only changes in the left-most non-zero component are considered incompatible.

The 0.x is essentially used as way to tell people to use at their own risk since it isn't considered stable yet. Using a library like this isn't asking for trouble if you know what you are dealing with and in the context of bevy it currently means a breaking change every 3 months with a blog post and migration guide.

It's more like every >3 months because the .1 release aren't breaking

I agree that it doesn't get much use, but I still think it's a good feature to have. I personally prefer having a project board integrated with everything else instead of using an external service.

Most will assume this, the correct question would be: Would most human react fast enough?

That event was done by Uber and if the human backup driver was paying attention, as they were supposed to because it was a test run, it wouldn't have happen. Yes the software was at fault of doing what you are saying, but the incident was a test run and the driver should have caught it and report to the engineer, not play on their phone and not pay attention.

The video is clearly sped up and it looks like it did wait at the stop sign in the first part, it just didn't wait long.

Maybe it's the area where you live, but where I live it would be weird to not have reusable bags with you. Pretty much everyone has them.

I live close to montreal and we have a lot of environmentally conscious people here.

Just because Microsoft has a lot of money doesn't mean they can just throw it around. That's not how the world works...

They failed, it wasn't extinguished. Their plan wasn't to fail.

If you already know java for the backend then just use that. Or if you want to learn something new pick one language. You don't need to learn all of them.

For the client side I would recommend vue, but react is also very popular.

Once you have chosen the backend/frontend technologies then you can start building. If you don't know anything about rest learn how your apecific framework does it. You don't need to learn rhe whole spec. At least not in the beginning.