Is that a big deal? That's easy to avoid if you don't pre-order games and just wait for the day 1 reviews. Even if you did end up with a shitty situation, Steam lets you refund the games with minimal hassle.
On the other hand, there are players who'd rather have the game earlier (like me) than a few months later, despite its launch issues.
The alternative approach -- Baldur's Gate 3 being in Early Access forever -- is fine too, but damned if that wasn't a long wait.
Maybe the compromise is bigger companies being willing to release in Early Access more often. That shouldn't be limited to just indie companies, but any publisher that wants early and broad public feedback.
Especially for a city-builder game (where there isn't really a campaign or spoilers), I don't see why not...
large companies don't have much incentive to use EA. The usual incentive for EA is to make a game cheaper for early users and to get important playtesting done.a big game with a big ad budget, QA testing studio, and internal playteting doesn't need to worry about that.
Well, in this case, they were a 30 dev company that knew the performance was going to be so bad, they had to release a warning a week before the game came out. Seems like Early Access may have been appropriate, and maybe saves the review score too.
I thought it would go without saying, but devs don't control the release schedule. The best best solution is to simply optimize before release but they clearly weren't given that choice.
Publishers care a lot less about review scores, and never cared strongly about user reviews. They were so polarized to begin with that Steam changed it from numeric actors to up/down (or meh). It's a long running game and scores can improve.
With the possible exception of darwin, all the major operating systems are fairly careful about maintaining backwards compatibility. They've certainly been making noises about cutting support for a long time, but it's not surprising that they were very deliberate about doing it for real.
There is a difference between ongoing support and security fixes support. Oracle database dropped support itanium on Linux since version 11. I suggest others did this as well. Of course companies wanted to extend their HW lifetime as much as possible and switch from everyday production use to some secondary functions. But having this power hungry monsters online is a waste of money on my mind.
It took extra long because for various reasons it was the officially blessed architecture (specifically, HP-UX on Itanium) for running Oracle databases, leading to HP suing Oracle when the latter bought Sun and essentially declared HP-UX is to soon be EOL'd
They don'w own this bitcoin wallet of course. They need receipt to attribute payment to them and get comission. They verify transaction and get into the loop.
Basically, having infinite budget you can send any gift you can imagine to your friend via Amazon at day-1 and cancel irrelevant orders at day-0 except correct one to make your friend happy at his BD, which is day+1. Make better future correcting your past decisions based on today information. Now the question is: how to get enough money?
> Even worse, the more concepts and abstractions you apply to your code the better programmer you are!
I had an Android programmer, who was eager to write clean code following GOF patterns, OP and the rest of the fancy things senior developers usually do.
Ended up Android team with 3 devs required 3x time to develop same feature compared to single iOS engineer.
It's often said that Design Patterns are workarounds for limitations in the expressiveness in a language: for example, the Singleton pattern is only useful in languages where you can't pass a reference to an interface implemented entirely by static methods - or the Visitor Pattern is the workaround for a language not supporting Double-Dispatch - method call chaining is a workaround for not having a pipe operator, and so on.
You said you're targeting Android, that implies you were using Java, which has its reputation for both a rigidly inflexible language-design team and its ecosystem having more design-patterns than a set of fabrics swatches - that's not a coincidence.
But for iOS, they'd be using Swift, right? Swift's designers clearly decided they didn't want to be like Java: take the best bits of C# and other well-designed languages and don't be afraid to iterate on the design, even if it means introducing breaking-changes - but the result is a highly-expressive language that, as you've demonstrated, allows just 1 Swift person to do the equivalent of 3 Java people. Swift is an actual pleasure to use, but using Java today makes me weary.
(To be clear: Java was a fantastic language when it was introduced, but it simply hasn't kept-up with the times to its own detriment, it feels like its falling behind more-and-more at time goes on - but that's going to be the fate of every programming language eventually, imo).
Well they weren’t a good senior developer then. Part of the art is knowing when to use the patterns. An incredibly im protest differentiation as it’s so so easy for someone a bit green behind the ears to see this and think that any sort of architectural thinking is useless.
> Well they weren’t a good senior developer then.
He wasn't. He was a mid grade dev, but it does not important, because even sr devs can fall in love with overcomplications.
Reminds me of Go. At the beginning you make only simple moves. As one learns the game more complicated patterns emerge. Watching master games the lines again are simple and clear - in hindsight.
