Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

KSP2 is spamming the Windows Registry until the game stops working

forum.kerbalspaceprogram.com

Post reply on HN
Print view View original

41–50 of 306 posts

Re: KSP2 is spamming the Windows Registry until the game stops working

#41

Post by recursive »

duped wrote: post #40
recursive wrote: post #34

Earlier quoted context omitted.

I still haven't seen a non-handwavy method for orchestrating a transaction across microservices. That means I still can't use them. Although I don't think I ever wanted to particularly.

You wouldn't ever design a microservice architecture that required transactions across them. Every microservice owns its own data.

Maybe it's just the domain, but I guess it means the scope of my microservice is just the whole damn thing anyway. I guess I was doing microservices the whole time.

Re: KSP2 is spamming the Windows Registry until the game stops working

#42

Post by dclowd9901 »

foobarian wrote: post #25
kortex wrote: post #8

It feels like the Windows Registry is one of those well-intentioned ideas that ended up being a tremendous mess in actual implementation. "Let's use a central database to store things that the OS, drivers, and UI need to access" somehow became "half assed KV dumping ground for every process and their dog to litter with whatever while acting as a singular bottleneck". See also: https://news.ycombinator.com/item?id=322…

They are global variables. Worth working very hard to block in any project. Separate microservices are the most effective way I saw so far to stop people in a large org from making shortcuts via global contexts. I feel bad for our frontend devs dealing with a tide of global constructs in our React codebase.

Global objects in react are almost universally an anti pattern. The only way to do them right is through a context, ensuring the state lives in the context. But most people hate writing the scaffolding, so a non reactive, non FP singleton gets to work and fails at integrating correctly with the react ecosphere.

Re: KSP2 is spamming the Windows Registry until the game stops working

#43

Post by zamadatix »

comprambler wrote: post #23

Everyone seems to love shitting on KSP2, when the same people forget what KSP1 was like in Alpha. No science, shitty graphics, excessively wobbly rockets, inconsistent orbits, (other than graphics) seems familiar? It took a looooong time for KSP1 to get where it is now, it will also take awhile for KSP2 to be as polished. Chill out.

Being an original Alpha owner, prior to Steam even, I think many people forget it was ~$10 and that came without any overpromising by the development studio.

The two releases are nothing alike and if KSP 2 intended to use the same release model it should have either been dirt cheap or not released for many years. As it stands now it comes off as a massive grift and deserves the hate.

Re: KSP2 is spamming the Windows Registry until the game stops working

#44

Post by garba_dlm »

SketchySeaBeast wrote: post #3

KSP2 is really becoming the premier example of "Nearly perfect labour of love's legacy ruined after being bought by a larger company." More on topic: I have no idea why one would want to use the registry to store this information.

the oh-so subtle difference between two almost equivalent but in-the-end completely different intentions of:

making games (and also a bit on money on the side)

making money (and having to make some video games so the money will come)

Re: KSP2 is spamming the Windows Registry until the game stops working

#45

Post by ye-olde-sysrq »

comprambler wrote: post #23

Everyone seems to love shitting on KSP2, when the same people forget what KSP1 was like in Alpha. No science, shitty graphics, excessively wobbly rockets, inconsistent orbits, (other than graphics) seems familiar? It took a looooong time for KSP1 to get where it is now, it will also take awhile for KSP2 to be as polished. Chill out.

KSP1 was made by a bunch of scrappy lovable indie devs making their first game (iirc Squad's team was a marketing company prior to this?) in a LCOL area funded by dreams and whatever $10 early access sales they made on steam, with no-one to tell them what to do.

KSP2 is made by TTWO, who is a publicly traded AAA studio of notable fame and decades of legacy and domain expertise.

If Squad sold KSP1's IP to TTWO and then went and made "KSP2" under a new name with their squad-sale money, that would be a different story. But even with that goodwill, I would still not be believing in the current KSP2 ever being a success story.

Re: KSP2 is spamming the Windows Registry until the game stops working

#46

Post by sco1 »

comprambler wrote: post #23

Everyone seems to love shitting on KSP2, when the same people forget what KSP1 was like in Alpha. No science, shitty graphics, excessively wobbly rockets, inconsistent orbits, (other than graphics) seems familiar? It took a looooong time for KSP1 to get where it is now, it will also take awhile for KSP2 to be as polished. Chill out.

Seems like the developers forgot too, since we have 10+ years of lessons learned and here we are starting from the same place making the same mistakes all over again.

Re: KSP2 is spamming the Windows Registry until the game stops working

#47

Post by SketchySeaBeast »

brucethemoose2 wrote: post #26
SketchySeaBeast wrote: post #3

KSP2 is really becoming the premier example of "Nearly perfect labour of love's legacy ruined after being bought by a larger company." More on topic: I have no idea why one would want to use the registry to store this information.

> Nearly perfect labour of love I wouldn't go that far. Its not KSP2, but KSP1 has plenty of jank and bugs.

It has jank, but I don't know anyone who stopped playing because of it.

Re: KSP2 is spamming the Windows Registry until the game stops working

#48

Post by digging »

Noughmad wrote: post #14
Pannoniae wrote: post #6

Not surprised at all; KSP as a franchise is in the enshittification stage where they aim to invest the minimum amount of money and maximise returns. This is just simply inexcusable software engineering and quality control. Bit tangential but I'd like to remind everyone that this is the game where the lead designer (?) said that wobbly rockets and physics bugs are adding to the fun of the game, and they are implemente…

Well, I still believe it's going to be good eventually. Like KSP1, for example, or No Man's Sky. There certainly have both the resources and a guaranteed player base to make that happen. That said, I cannot be sure of that, so I will not buy it until it is actually good.

> KSP1, for example, or No Man's Sky

Those are two very different examples, though. NMS was improved heavily but in many ways never approached the features and qualities that people were expecting. KSP2 feels more like NMS than KSP1 in that regard - people have expectations. They've been sold a specific vision which doesn't look like the game. Further, unless it's great... why not just keep playing KSP1 with extensive modding?

Re: KSP2 is spamming the Windows Registry until the game stops working

#49

Post by SketchySeaBeast »

mattsan wrote: post #31
TylerE wrote: post #15

Earlier quoted context omitted.

I knew it was going to be a disaster as soon it became obvious that it was a continuation of the old code base, which has a lot of fundamental issues.

This is the first time I'm hearing it uses the old code base - do you have a source? I thought in the initial marketing they were big on saying it's a full rewrite.

You'd think if they were using the old code base they'd have more of the old features.
Post reply on HN