git checkout -b main
git branch -D master
git config --global init.defaultBranch main

You don’t have to deal with shit if you don’t want to.

Probably?

This is the kind of thing that a LOT of companies outsource. Mostly for ill.

Bad developers just do whatever. It doesn’t matter if they wrote the code themselves or if a tool wrote it for them. They aren’t going to be more or less detail oriented whether it is an LLM, a doxygen plugin, or their own fingers that made the code.

Which is the problem when people make claims like that. It is nonsense and anyone who has ACTUALLY worked with early career staff can tell you… those kids aren’t writing much better code than chatgpt and there is a reason so many of them have embraced it.

But it also fundamentally changes the conversation. It stops being “We should heavily limit the use of generative AI in coding because it prevents people from developing the skills they need to evaluate code” and instead “We need generative AI to be better”.

It was the exact same thing with “AI can’t draw hands”. Everyone and their mother insisted on that. Most people never thought about why basically all cartoons are four fingered hands and so forth. So, when the “studio ghibli filter” was made? It took off like hotcakes because “Now AI can can do hands!” and there was no thought towards the actual implications of generative AI.

Shit code review is not code review. If you just rubber stamp everything or outsource it to someone who will, you aren’t doing code review.

Aside from that:

LLM generated code is more likely to have subtle errors that a human would be very unlikely to make in otherwise mundane code.

Citation requested

My current least favorite thing is LLM generated unit tests that don’t actually test what they say they do.

If I had a nickle for every single time I had to explain to someone that their unit test doesn’t do anything or that they literally just copied the output and checked against it (and that they are dealing with floating points so that is actually really stupid)… I’d probably go buy some Five Guys for lunch.

Its like saying that the problem is that you are using robots to assemble cybertrucks rather than people. The problem isn’t who is super glueing sharp jagged metal together. The problem is that your product is fundamentally shite and should never have reached production in the first place. And you need to REALLY work through your design flows and so forth.

You will never have resources to “test absolutely everything”. It is ALWAYS about building out personas and deriving tests from those.

What this tells us is that one of two things happened:

1. This was not tested at all
2. The testing harness resets the environment after every check (e.g. “does process close when killed”) rather than involving a manual reset (i.e. “close and re-open task manager”)

The latter is a lot more common than you would think since it makes it much easier to automate these harnesses rather than having a human at a VM. But… this is what happens when you don’t step through the entire workflow.

That is the reality.

The problem isn’t “vibe coding” (anyone who has ever managed early career staff will be able to attest that… the bar is REAL fucking low). The problem is a complete lack of testing or any sort of “investment” in caring if production breaks.

A lot of it is general apathy induced by… gestures around. But it very much goes beyond just the obnoxious rise in brain drains over “vibe coding”. Personally speaking, I am THIS fucking close to driving over to my company’s head of IT’s house and burning it down with him in it (For legal purposes, this is a joke) as that entire team continues to think “We’ll just wait until people tell us what is broken” is at all fucking acceptable.

But pretty much any SDLC is going to be built around code review. And code review is how you handle developers of different skill and sanity levels. Whether they are old hats who have been in the basement since before you were born, youngins who can’t stop talking about Rust, or chatbots.

I mean, at a high level it is very much the concept of ICE from Gibson et al back in the day.

Intrusion Countermeasures Electronics. The idea that you have code that is constantly changing and updating based upon external stimuli. A particularly talented hacker, or AI, can potentially bypass it but it is a very system/mental intensive process and the stronger the ICE, the stronger the tools need to be.

In the context of AI on both sides? Higher quality models backed by big ass expensive rigs on one side should work for anything short of a state level actor… if your models are good (big ol’ “if” that).

Which then gets into the idea of Black ICE that is actively antagonistic towards those who are detected as attempting to bypass it. In the books it would fry brains. In the modern day it isn’t overly dissimilar from how so many VPN controlled IPs are just outright blocked from services and there is always the risk of getting banned because your wifi coffee maker is part of a botnet.

But it is also not hard to imagine a world where a counter-DDOS or hack is run. Or a message is sent to the guy in the basement of the datacenter to go unplug that rack and provide the contact information of whoever was using it.

not everyone plays every bit of content in every game, local compilation still happens pretty regularly.

Yes. Which is why I emphasized that this mostly comes into play on the first boot of a game and would go away VERY rapidly if you ran multiple collections.

It is not limited to the first launch but it is most noticeable on it.

The shared precompiled shaders are a great solution for a bunch of stuttering, and they are only available on Linux because they actually require the compatibility layers.

Funny enough, MS have been talking about (and implementing?) that for their xbox store games or whatever. Which is actually a REALLY good approach if you ask me.

The fact is: from the data we have so far, it looks like Bazzite is a better experience on a handheld Microsoft co-developed when compared to Windows.

No, we don’t. Which is my point.

Again, I would love to see a rigorous methodology that argues this (and if I am not familiar with Cyber Dopamine’s game, please, someone link me to their methodology). But I have a scientific background: I can cherry pick whatever you pay me to cherry pick.

And, quite honestly? If the performance is mostly noise outside of that first boot after a major patch? That might be awesome if I am paying 80 bucks to play a 4 hour CoD campaign once. That is less than meaningless if I am looking at something like Crusader Kings 3 where I will log hundreds of hours before the next one.

Which gets back to… what is the point of looking at benchmarks? Is it to feel happy that your team won? Okay. You do you. Or is it to make informed decisions.

And as someone who would really prefer Linux (Proton or otherwise) to be a first class citizen? Actively misleading people is just going to hurt in even the medium run.

… Also, Wine is not an emulator, but I think you know that. ;)

My inner pedant thinks that it is worth actually looking at the definition of an emulator rather than the title of software. But mostly it is just a good way to weed out the people who were never going to engage in a good faith discussion :)

But they also have nothing to do with moment to moment performance. And I would argue that people, generally, aren’t pulling out a steam deck or a 1000 USD xbox to play a quick hand of Balatro while in line at the bank. I love that waking up my bazzite box under my TV actually takes less time than the nvidia shield I watch youtube on. I am not going to pretend that there is a meaningful difference between a 20 second boot and a 2 minute boot if I am sitting down to get angry at Silksong again. Same with my Steam Deck where I usually push the power button and then put the case back in my bag on a plane or off to the side while I get cozy at home.

Its similar to the initial OS install. I will never stop being enraged when I have to deal with cortana and all that bullshit to install windows on a box. I positively love that most Linux distros are like 3 clicks and then a two minute wait if I am not doing weird partition shenanigans. But that is more a plus to the OS and not a reason I would upend my digital existence.

Whereas this article is very specifically about moment to moment framerate.

I don’t know Cyber Dopamine’s credentials and don’t care enough to look.

But this has come up a lot in the past. And most of the time the difference between the OSes (assuming you turn off the most blatant of things) is noise that would disappear if your sample size was large enough and is comparable to the kinds of variations you see when all software is fixed but you have two different CPUs of the same model from the same batch but with slight manufacturing variance. Gamers Nexus and Level1Tech have both discussed this to varying degrees when going over their testing methodologies.

But if you are just doing the first run or two? THAT is where the very noticeable differences come in. Because shader precaching is a thing. At a super high level, it is the idea that every computer is unique and there are tweakable “knobs” that can improve performance when rendering things. Shader Precaching generally refers to testing and setting those knobs ahead of time to maximize performance. That is a VERY incorrect summary but it gets the point across.

Some games have an obnoxious 1-10 minute wait the first time you boot it up because they are, in the background, running through all of that to build that precache. Others say “fuck it, we’ll do it live” and you have a performance hit the first time you load an area or asset… that can be REALLY substantial on that first boot when EVERYTHING is being loaded for the first time.

But, because Linux tends to run games through (time to piss more people off) an emulator like Wine/Proton, it is already generally doing a translation layer even before the shader math. So that is why Steam will often push “good enough” defaults to linux clients every day and there is a setting to even optimize those for your system in the background while you whack it to your favorite onlyfans account.

But… that also gives Linux a pretty big advantage on that first boot on games that are doing it live. Because… we aren’t doing it live.

It might have been phoronix that actually did a deep dive on this? But the various blogsites love to either run their own numbers or find a youtuber who did, not take this into account, and get those juicy clicks.

Yeah

As funny as this is, it is more likely that people are leaving food in the back of their shitified SUVs and the seal is loose enough that the raccoons can smell it and want it.

Honestly? I would suggest using one of the frigging “vibe coder” IDEs over Eclipse at this point.

I would also accept Wordpad.

It is NEVER time to go back to the hell that is Eclipse.

Go to frigging notepad or kedit before Eclipse.

A good mindset is “How can I pleasure my partner more”. A bad mindset, and what you are describing, is “Why won’t my partner orgasm the way I want to”.

If you want to actually read and understand there is a big difference between “I want them to cum the way I want them to cum” and “what can I do to better interface with my partner”, cool.

If you just want to keep trying to rephrase things until people pat you on the head for expressing the kind of mindset said stand-up was ridiculing? I mean… you do you. Possibly with a vibrator.

And absolutely none of that is getting frustrated that your partner uses a vibrator instead of your fingers (or in addition to them).

If you are having actual conversations and the answer is always “I need to use my hitachi” then… maybe you two aren’t a good couple. From my experience? If someone actually knows what works for them and is confident in explaining that, they are also very open to trying new things. It just might not be what you want. That isn’t to say it is possible they ONLY want to do what they want to do but… that is very much not the sentiment being expressed in the meme from some lady’s stand-up.

But the wishing in itself should not be condemned.

No. It very much should be.

A good mindset is “How can I pleasure my partner more”. A bad mindset, and what you are describing, is “Why won’t my partner orgasm the way I want to”.

The former is… a partnership. It is knowing what does and doesn’t work and communicating and adjusting.

The latter is getting angry that someone… is a someone. You know what you want to do and they don’t want to do it so that makes you angry. And that is really shitty.

Don’t get me wrong. Everyone has intrusive thoughts. The key is to realize “huh. That is really shitty. Let’s work towards not having those thoughts and never fucking tell anyone about them”.

The reality is that it is generally harder for people with a vagina to achieve orgasm than for those with a penis. There are very much evolutionary reasons for that and… let’s not talk about that because it is dark as fuck.

In a perfect world? Two (or more) partners will always climax at the same time and everything will be wonderful. But that just isn’t reasonable. Maybe its been a while and one partner finishes faster. Maybe its stressful at work and you thought it would work but it just isn’t. And maybe you just kind of want the borderline sensory overload that sex toys tend to be capable of.

The reality is that partners should work towards making sure everyone orgasms as much as they want to. If that involves external stimulation with a vibrator while you have vaginal sex? Go for it. If that involves finishing someone off with a handy? Go for it. And so forth.

And if you feel that not being able to make your partner cum the way you want to is a problem? Grow the fuck up. Everyone is different and everyone responds to some stimuli better than others and that can change from week to week. If your partner really likes a vibrator? Awesome, work with that. Integrate it into the fun. Rather than get angry that they don’t want you to fingerbang them instead.

Fair enough. I was mostly just thinking back to when I was researching luggage tags and the general guidance was “airtags have the best coverage in the US and some Western European countries. For East Asia, it is generally fine but a lot more hit and miss as most countries vastly prefer Samsung Androids”. And my experience in Japan and Korea lined up with that where my luggage had ridiculously high fidelity with a samsung tag or whatever they are called.

But the point still stands. If you have a high end phone that basically nobody around you will have, you’ll stand out.

Oh I 500% assume racism is a big part of this too.

Not familiar with Catalonia but I assume there are at least a few ethnic groups that are associated with “rich” and this is a way to group them in.

Which, funny enough, was also kind of the deal with Blackberries. Yeah, Dealers had them. Because Dealers like buying expensive shit (See also: really expensive Rolex in a neighborhood where everyone is on food stamps) AND because they were ridiculously ahead of their time tech wise. You know who else had them? Business and (proto-)tech folk. And cops LOVED to say that the kid who actually made something of themselves going back home to visit family must be a Dealer because they have the same phone all their co-workers do.

Which gets back to: As part of an investigation, it is good. It is one part of a potential puzzle. In the reality of ACAB… ACAB.

Those articles don’t really support the claim? At all?

https://www.androidauthority.com/google-pixel-organized-crime-preferred-phone-3573578/ is unsourced but, taking at face value, seems like what one would expect. People aren’t getting stopped at checkpoints and forced to divulge what OS their phone is running and being taken to a black site if they run GrapheneOS. But someone holding up a pixel in a sea of cheap motorolas DOES raise some eyebrows. Same as someone with a ridiculously expensive rolex walking around The Hood and so forth. And, presumably, people who have been arrested for other reasons raise even more eyebrows if their phone isn’t running a stock OS which…

Look, with a just police force (ha!), that actually is a very reasonable stance. Back in the day it was having a Blackberry. For a decade or so it was having two phones until people learned to not do anything personal on a work phone and that became kinda normal. There are activities that are generally associated with “weirdos” and “criminals” and I think even the GraphenOS devs would acknowledge their userbase fall firmly into the former. If you see someone with a Blackberry hanging out leaning against a 7-11? You maybe hang out across the street for an hour and keep an eye on them. Arrest someone and they have three burner phones in their pants pockets? Maybe you look a bit deeper.

That is actual investigative work. Of course, the problem is that it instead becomes “That gameboy looks like a drug dealer’s phone. We are going to stop and frisk you and maybe sexually assault you in the back of the cruiser if we are bored”.

I’m keyed in on a lot of “high level” protest discussion as well as what investigative journalists need to do for actual safety. And one of the biggest topics that regularly comes up is the idea of “the burner”. In theory, if you are crossing a questionable border or think you might be stopped, you bring a completely blank burner. If they hack into it, you are safe, right?

Wrong. Because you are now an anomaly. NOBODY has no social media and NOBODY has no documents on their laptop. So what are you hiding? Let’s beat it out of you.

Which is why general best practices are often considered to have a real device that you actually use everyday and take through those checkpoints and on the riskier protests. But you make damned sure there is nothing incriminating or sensitive on there. Optimally through having your “burner” be the one you do said activities on, but also through just removing it well before you get on the plane or get in the car.

And a lot of that applies to device choice too. That cool ass Linux Phone might seem like a great idea but now you stand out from the crowd quite a bit. Same with taking your top of the line iphone to Korea where Samsungs grow on trees and so forth.