scott01

In "Where Winds Meet" you can talk to NPCs

I played the demo and it blew my mind how cool the puzzles felt. I'll definitely get the full game later, though I doubt I'll invest 500 hours into it.

This was a response to a request for tips, suggesting oh-my-pi.

It already does: more taxes, HMRC's new analytics systems, selling government properties. Weakening encryption merely means you can't legally hide anything.

Obviously speculating, but if you make a really good humanoid robot, it'll be easier to create purpose-specific ones, as the tech is basically explored far enough. Plus, in China they don't just build factories, but create infrastructure / supply chain around them. Also, maybe they are trying to scale out automation, e.g. the Xiaomi factory that has mo workers, maybe they're betting on a universal-ish automation machine.

I’m a developer, daily driving Linux, and prefer GUI apps. Would’ve used Sublime Text if clangd plugin worked. Hence stuck with Emacs. Open Code GUI sucks compared to their TUI though.

I have to say, I prefer dongles lately. There are many inexpensive hifi dongles that sound great with in-ears. They’re also USB class-compliant audio devices and work everywhere. Obviously a preference, but as other commenters have mentioned, 3.5 jacks do break, and I’ve personally broken plenty.

Interesting, how did the fault happen for you? Was the PSU underpowered? I have a 850W unit, so you think it’ll be enough?

With this amount of VRAM, do you happen to be using a Strix Halo or a Mac?

In my experience, using chats merely as stack overflow replacement, e.g. for providing obscure API usage examples, is a huge time saver — otherwise I would’ve had to lurk around game engine sources, examples, comments, sometimes forum posts, etc. AI code reviews definitely help finding issues, especially when I work on something for more than a week and inevitably forgetting things.

This was a prelude to his argument for needing a set of moral standards.

This is an amazing and inspiring talk. Humanising and empathetic, especially when compared to the vast majority of other related content.

There’s a relevant book from No Starch, highly recommend. The author also has a series of blog posts on the topic.

https://nostarch.com/building-a-debugger

Thanks for this, I’m actually learning Rust (albeit slowly) atm, and still can’t wrap my head around how arena allocs would fit the borrow checker

From what I understood, their critique of RAII is twofold: coupling of allocation and initialisation, and enforcement of deallocation. The ease of use of smart pointers makes it tempting to allocate/free of temporary structures even within one single function. Given enough number of such occurrences, it kills performance by a thousand cuts. Also I remember they mentioned it’s not necessary to free memory if you’re about to close your program, because the OS will take the memory back. Obviously you need to gracefully deinitialise some things, like audio or other devices, but that’s beyond the discussion.

As on some references, Ryan Fleury did an episode on Wookash podcast on RAD debugger showing ECS like approach.

IMO, their RAII critique is a but nuanced, but because of their personality the discourse often gets polarising.

Edit: the sibling comment just proved my last point.

Projection. Your account posts mostly negative or passive aggressive comments.

Can you elaborate?

Yep, and I feel many commenters in this thread are comparing value propositions only in terms of specs. I’ve built a number of Mini-ITX cases, from 5L to 20L, and they are a pain to work with and maintain. In some cases it’s impossible to make a reasonable filtered airflow, so dust builds up very fast, and a teardown to do clean up is pretty annoying. Steam Machine looks very straightforward to maintain. And it’s also tiny and quiet.

I believe the tools like Resolve are built around VFX reference platform specs. I doubt anyone will standardise on the basis of a rolling distro where you can’t pin glibc version. https://vfxplatform.com

Honestly, I completely missed the quotes on the first read. I agree with the sentiment that crimes should be called out as crimes and not, e.g., ‘oopsies’.

For type erasure (it’s sometimes useful), custom allocators, I/O, for example.

I agree. His negativity has probably detracted quite a few people from him that otherwise are quite aligned. Still, his historical remark is rather peculiar.

As for the language, yes, sadly, it’s with us seemingly to stay. I code it professionally and I can’t find a single interesting, or even good, thing about it. Apart from wide adoption of course. Everything about it feels extremely badly designed from the user perspective (though it’s probably technically very impressive) with many details, that probably the sanest strategy is to use a small subset of the language. At least I don’t have to use STL at work, that’s something positive, I guess :)

Same. Also the “russophile” part sounds kinda racist.

I respectfully disagree — a lot of conveniences that C# provides produce GC trash which will cause frame spikes. I remember having had to add a non-allocation string.contains alternative at one project. Lambdas and linq also have this problem, or if a string is passed through native-c# boundary. Language itself is really nice though :)

I have email backups from a provider where filenames are extremely long.

I’m not as experienced as some people here, but in ~10 years, I’ve never needed to write code for anything other than x86 or arm. So I agree with the author on their priorities.

Obviously. I responded to the commenter with some context, but your comment doesn't bring anything to the discussion.