Crimsonland is a great game, only horde game I've ever played actually. Sucks that they didn't get the credit for inventing the genre

View this comment - View article - View full comments

I also wanted to ask for a piece-wise linear fitting, where the slope is changed since steam deck. It's clealy changed the speed of adoption.

View this comment - View article - View full comments

Will worlds generated prior to the new biome get the new biome after the November update? It'd suck to have to generate a new world.

View this comment - View article - View full comments

Quoting: BlackBloodRumI don't think Steam Deck 2 is any time soon, remember we're working on Valve Time here

We keep making the same jokes, but Valve's obviously changed. They are quick now, and things can get a version 3.

But yeah, for sure SD2 needs to take a while. Like the other consoles, having something fixed to target is a bonus for developers, and you don't have something fixed to target if there's a new version every year.

I'd expect something like a new version every 5 years.

Compare consoles with phones for example. Long after PS4, PS5 comes and most people upgrade. However, every year your phone gets an iteration, but you spend a few years with your phone without changing. So with consoles, you get generations of games and something developers can target. With phones, there is no such thing.

View this comment - View article - View full comments

Quoting: BlackBloodRum[2] Don't deck and drive, let someone else take the wheel.

Letting someone else take the deck is not an option

View this comment - View article - View full comments

Quoting: EikeI'm also happy with my Nvidia and probably would buy one again.

Quoting: ShabbyXInternally (to the Vulkan workgroup), I can also attest that Nvidia is always on top of things, more so than any other vendor I'd say.

You've got internal insights there?

Yes, I'm (a small) part of the WG. Those extensions Liam reports as "Collabora did for Zink", usually it's me who did them for ANGLE, lol.

That reminds me, I should finally fix my handle in the spec, at some point I realized it's meant to be my github handle, but never got around to it.

View this comment - View article - View full comments

It's fashionable these days to bash Nvidia and love AMD, but you gotta hand it to them, they are always the first to support every extension. Internally (to the Vulkan workgroup), I can also attest that Nvidia is always on top of things, more so than any other vendor I'd say.

View this comment - View article - View full comments

I just made a reservation the other day and it said Q4. My plans to make it a Christmas gift for my wife is now ruined.

Click here to sign a petition to make Valve slow down production!

View this comment - View article - View full comments

While this was obviously a bug in their algorithm, said algorithm is also preventing brainwash videos from turning your child into a terrorist, racist etc.

Would you have rathered such an algorithm not exist? People should bear in mind the terrible complexity that such an algorithm entails. Can *you* code such an algorithm? If not, you can't expect it all to work flawlessly.

View this comment - View article - View full comments

Quoting: Guest

Quoting: ShabbyXThis is absolutely not true. 16KB is 4 pages of memory, saving that on every .so is huge! It's not just that you have the memroy laying around, there are other costs too. There's the cost of loading the objects from disk, maintaing the struct page entries in the kernel etc.

Everything has worked fine so far even with this extra cost, so I doubt the (real world) effect is huge. What kind of improvement this change makes for desktop use case?

Quoting: ShabbyXThere is a reason Linux is _fast_. With your approach, Linux would have been bloatware like the rest of them.

How come Linux is the fastest kernel there is when it absolutely follows that "bloatware" practice?

1. As others mentioned, little things add up. Linux is fast because every little performance improvement is applied. After all, large company X saves a lot of money for improving things by 0.01% simply because the multpilier is so large for them. You enjoy a fast kernel on desktop thanks to that.

2. Two reasons. One is that a good chunk of the ABI people use is POSIX, which is standardized. Linux is not free to change it, no matter how many complaints they may have about it.

But more importantly, it's because Linux actually doesn't follow the bloatware practice. Linux's ABI most definitely changes in backwards incompatible ways. It just happens to change mostly in actively developed areas where users are also developers of the feature and they adapt to new changes.

Linux's motto is not *never change the ABI*, but *never break userspace*. The difference is that if a change breaks ABI but not userspace (like, no active users of it, or userspace happens to not break), then the change goes through perfectly fine.

---

To be clear, I'm not defending glibc. They were wrong to make a backwards incompatible change without incrementing the major version. I'm only saying that "win32 is stable, so it must be good" is a terrible argument.

View this comment - View article - View full comments