chundicus

For me it depends a lot on the context. JSON is often very human readable (as long as it's not too deeply nested), fairly well defined (compared to CSVs), and most languages and software have easy out of the box support for parsing and manipulating it.

If I were building a system that had to deal with large amounts of tabular data that isn't directly consumed by humans, JSON wouldn't be my first choice nor my last.

> Garbage collection tasks are postposed to when we're asleep, but they can only be put off for so long and there's a capacity for "stuff to consolidate later" that fills up

Do we have a strong reason to believe that? I know brain and sleep mechanisms are tricky topics with lots of unknowns, but I thought I had read research that showed sleeping brains likely perform a chemical analogue to "garbage collection".

Great tool! Nice way of condensing and displaying a lot of information. Doesn't look like 'intervals' is working though.

I'll have to use this to brush up on scales and see how it goes.

I can't shake the feelings that a trillion or a quadrillion parameters won't solve the fundamental shortcomings of ML models not being models of artificial intelligence. I guess there's no way of knowing until we reach AGI, but I've never heard a compelling argument for why pure ML would get us there. GPT3 seems more like an argument against that hypothesis (in my view) than for it. Even the best, most expensive models today are incredibly brittle for enterprise usecases that shouldn't necessarily require AGI.

I've always imagined AGI (perhaps naively) as being achieved by clever usage of ML, plus some utilization of classical/symbolic AI from pre-AI winter days, plus probably some unknown elements.

Data races is what I meant; good catch.

Likely a joy for Rust and a desire to try something ambitious that hasn't really been done.

Rust doesn't have the mature libraries that C# offers, but it isn't barren anymore either. It does offer nice assurances like entirely avoiding race conditions by default (when using safe Rust). Rust often leads to performant code, but it's hard to say if that's really a feature of the language or just a bias due to the kinds of people using it and the projects they work on.

If you're just looking to get into game development without any other goals in mind, then C# is a safer choice

This is such a silly but entertaining project. I love that it's the server for the website as well.

I would imagine money primarily. On top of that, the larger the room gets the more costly and ineffective this becomes.

Agreed. By "this" I actually (confusingly) was more so referring to the general negative feedback Cyberpunk has been receiving.

I hope this will encourage big studios to stop releasing broken games, but I doubt it will. The incentives are just so broken due to ease of patching, a need/desire for cash after a drawn out dev process, and a general disrespect for their customers.

I think releasing a "broken" game in the form of "early access" from smaller studios can be good in terms of iterative and community development, but also that can be abused too. These bigger studios really don't have as much of an excuse in my opinion.

The only solution I see is to stop pre-ordering games and don't reward studios that do this, but easier said than done.

Wow, that's pretty interesting.

I didn't know they didn't have time zones. Are people there just used to the fact 8am will look very different depending on which region your in?

Yeah people are "lazy" in that they don't want to spend precious few free hours of their weeks grinding out a gimmicky skill-set that is at best tangential to the actual work they would be doing.

I understand there is no simple solution to how to hire software engineers, but you should be able to recognize why a lot of us don't like the current status quo of interviewing (even if you thrive in it).

I still don't see how this has anything to do with decentralization, and frankly the way you're justifying it sounds like you wanted to use a clickbaity word that doesn't really apply here.

How does this help data ownership? How does this decentralize the 'power structure'? The ownership and power is still in the hands of the server. The benefits you highlight here are addressed by SSL. Is this trying to address the downsides of SSL? I can't see how it is/would.

It seems like 'frictionless monetization' is the only thing this really addresses, and even that I'm skeptical of.

I don't mean to be such a detractor, but you really need to reconsider what the purpose of this technology is and sell that purpose better. Because your current explanation makes no sense.