kartoffelsaft
joined 2 years ago
I believe the reason it happened, in short, is that Take2 (the publisher) were really obsessed with the release being a surprise, at the cost of far too much.
For one, this meant that basically every job listing for the game never described what the game you'd even work on was. Most of the devs they got were juniors who:
- were willing to sign more restrictive contracts without the confidence to push back
- did not necessarily know much about the game, or even the genre (supposedly, besides Nate, only 1 dev was an active KSP1 player and another was aware of the game but never really played)
- this game was their first sizeable project
For two, it meant that a lot of management roles were taken up by people from Take2 to enforce the secrecy (who also saw KSP as having franchise potential, but that's a rant for another day). Few of them intimately understood what makes us dorky nerds enthusiastic about KSP.
This is also part of the reason they avoided talking to the KSP1 devs; they were afraid of some of them even hinting that a sequel was in the works. As to why they continued to not talk to them after announcing the game I'm not sure. Perhaps they were afraid they'd tell the uncomfortable truth that the game was making the same development mistakes as KSP1 and more.
But then I'll never sleep
Ok this may sound insane but trangle cut sandwiches definitely taste different than square cut. 3 holed donuts obviously won't but at least with sandwitches it changes how much of the crust vs everything else you taste.
My understanding is that leaves contain some compound(s) that, when wet and under the extremely high pressures that train wheels provide, becomes one of the most effective lubricants we know about. In other words, the brakes literally won't do anything because you'll slip-n-slide your way at the same speed you were going before.
TOEM is usually the game that I suggest for this sort of genre. I got it from someone who had an extra key from a humble bundle, and in hindsight I wish I bought it because they deserve the money.
Yeah honestly I wish more products had laws like this. Or, actually, the rule should be you can't sell it at a higher price within a certain time frame, because that's a better indicator of scalping.
I've been wanting to buy one of the B580 GPU's intel released, but as soon as there's stock it immediately gets bought out and resold on amazon at a 150$ markup. I can't think of any other rule that would effectively stop this behavior.
Were you trying to set firefox's volume? I've encountered that when I forgot I set the volume of a youtube video from in the video player. For whatever reason Firefox implements that functionality by repeatedly overwriting it's own volume in pulseaudio/pipewire.
As someone who's used both, I'd have a strong preference for Odin over Rust if it were at a stable 1.0 release. As it stands now (or, at least, when I used it), Odin is very much in flux. Spend enough time with the language, and you'll either find a bug with the compiler or the semantics will change after you update.
That said, it would be my favorite without those problems. It is a really simple language in a good way. There's no fancy language features that are just syntax sugar (well except maybe context, but I find that to be actually convenient). You can understand everything in an afternoon if you are already familiar with programming in other languages. Rust is pretty much the opposite in all of these reguards.
Rust also has the benefit of being pretty recognizable at this point, so if you say your project is in Rust then people will know what that means, unlike Odin. More "resume-able" in a way.
So, in short:
- Odin if you're doing it as a hobby
- Rust if you want something "real"