Tons of people making Python comparisons regarding indentation here. I disagree. If you make an indentation error in Python, you will usually notice it right away. On the one hand because the logic is off or you’re referencing stuff that’s not in scope, on the other because if you are a sane person, you use a formatter and a linter when writing code.

The places you can make these error are also very limited. At most at the very beginning and very end of a block. I can remember a single indentation error I only caught during debugging and that’s it. 99% of the time your linter will catch them.

YAML is much worse in that regard, because you are not programming, you are structuring data. There is a high chance nothing will immediately go wrong. Items have default values, high-level languages might hide mistakes, badly trained programmers might be quick to cast stuff and don’t question it, and most of the time tools can’t help you either, because they cannot know you meant to create a different structure.

That said, while I much prefer TOML for being significantly simpler, I can’t say YAML doesn’t get the job done. It’s also very readable as long as you don’t go crazy with nesting. What’s annoying about it is the amount of very subtle mistakes it allows you to make. I get super anxious when writing YAML.

Sounds reasonable enough. I think in most of Europe that’s about when kids finish elementary school.

I have used Google, DDG, Bing and Ecosia (which is basically Bing) at this point and ingl, none of them really stands out for its results. If anything, I think DDG and Bing beat Google.

Google might be the first company to create a monopoly out money and apathy. The apathy of users who don’t care about their search engine enough to even change the default.

If you gonna rant, please make it at least comprehensible. You went from “JS is flawed” to “everyone is wrong these days” within three paragraphs like wth.

I also highly disagree with your premise that people think ‘simple is bad’. Things that are complicated are usually complicated for a reason. C++ for example is complicated, because it grew over decades. Rust is complicated, because it tries to be secure, capture mistakes at compile time, while allowing for concurrency and memory management, and at the same time be very efficient and give the programmer much control. It’s hard if not impossible to achieve all these goals in a language without making it complicated.

Go on the other hand is not complicated, because Google engineers saw C++ and wanted to make something less complicated - and thus they created a simpler language. This is an example that goes directly against your argument, together with many other modern languages and frameworks that were created for reasons like this. But notably and more importantly, the most popular languages are simple. Python, JS/TS, Java - These languages are all relatively easy to use.

I won’t pretend that I get you bit about WASM since I have little experience with it, but as far as I understand it is primarily a vehicle allowing to use programming languages for the web that weren’t designed for it. And as far as I’m aware you can do quite sophisticated things with it, so where exactly is the problem? Putting guardrails in place is rarely a bad thing, because they are easy to remove but hard to establish retroactively.

I think TOML found a pleasant compromise there

I have yet to draw the comparison in person (only have a 165Hz), but I mean, every time you double the FPS, the benefit of doubling them again halves. Going from 120 to 240 to 480 Hz is going from 8 to 4 to 2 ms in terms of frametime.

A 4 ms difference in delay might be somewhat noticeable, if you have a very well running game and amazing reflexes. Anything beyond 240 is marketing bs / e-sport ‘I need every ms I can get’.

Remember that blind test on LTT where no one, including an esporty player, could reliably differentiate between 120 und 240 Hz?

I know it’s not exactly the most thorough experiment ever, but it’s all I needed to know.

That are 40 TOPS, no? I mean, why use standard nomenclature when you can have a big number I guess.

Any yeah, that’s a lot of OPS for a ‘+’.

Firefox enhanced tracking protection is pretty based here if you ask me

Heh, we the best. Now excuse me while I use my amazing brainpower to watch questionable anime and get more depressed 🫥

Too bad that just in time for this fuckup, AMD stopped chasing halo SKUs again. Just comically bad timing.

I don’t even get why they care. Can’t you just inform users once, then drop support and still collect their data?

I think fish is simply fantastic. Not only is it significantly more readable than most other shell languages, it was also recently rewritten in Rust (still in testing I think), which gives me a lot of confidence when it comes to your typical vulnerabilities.

I mean sure, a Rust vulnerability the reason we’re talking, but let’s not forget how valuable memory and thread safety are.

This hurts my brain. We have nice shell languages now, can we just lock down and phase out the rest please? I don’t even want to know the hidden cost of running Bash or sh scripts tbh. Both are languages where you can do something not right enough, because everything just has to be obnoxious.

Idk man, I just like electromagnetic waves

Every time I take a look at collections of user created themes for anything, I am reminded why design is a profession.

Not trying to shame anyone, I’ve been an enjoyer of custom themes ever since I started using Linux, but you need to have at the very least a little contrast in your theme. That’s kinda where this conversation begins :D

It allows for more fine grained access control and to implement afterthoughts.

Think having some private function that can break things if called improperly, but also allow you to avoid significant overhead when calling it the correct way. For example you could be avoiding input validation in a public wrapper for that function. If your friendly class already does it, or cannot produce invalid inputs, there is no need for that.

You could also implement logging after the fact, because your friendly logger object to read private members.

Arguably it’s a questionable design decision tho, as you could do all of this in other ways and it basically breaks any guarantees private would usually give you.

I hated YAML at first glance, but it kinda grew on me

Very insightful, thank you! And very shitty behaviour by Seagate. Proprietary and undocumented device status, amazing.

pRAM can actually be faster than DRAM in terms of latency. Main problems are cost, density and power consumption (to varying degrees, depending on the concrete technology)