Rubbed me the wrong way too, dude is the exact opposite of AI. He IS clearly vibing in the photo however.

I haven’t bothered to actually search or troubleshoot yet, but since I’m here - have you had any problems with power management failing to automatically turn screens off when idle?

I don’t get consistent behavior there it seems (AKA it leaves them on when it shouldn’t), but that’s I think the only significant oddity I’ve found in the ~7 months or so I’ve been running Bazzite. And like I said I’ve done basically nothing yet to try to solve it, just wondering if you’ve seen it. I have the issue on a desktop and a laptop, using entirely different monitors (not even same brand) FWIW.

Yep I use KDE-flavored Bazzite and actually forgot GNOME was even offered! It works deliciously. Came over from Windows last winter finally and boy, the UI alone is just so much nicer.

Ouch! My dignity! Help!

As a (primarily) Python dev, I hope you use this and have a miserable time lol

Blech, this is my least favorite kind of testing. I’d much rather have some all-encompassing integration tests even if they’re confusing AF, than the “yep the language still works as advertised” nonsense that this approach often amounts to.

You’ve never sharked a genie? What a prude!

Just wanna add another Bazzite recommendation! If you’re on the fence and feeling like “but my games!” - Bazzite’s got your back. Shit works great.

For me it’s less about fear and more about having a limited budget of time and effort to spend on learning things, so CSS and front end generally gets deprioritized. But that’s cuz I’m a back end kinda dev in my soul, lol.

I’ve seen the good points you’ve made elsewhere in this thread - I would indeed react very poorly to willy-nilly back end changes and I think you’re right that people don’t give CSS and visual styling the same degree of professional respect when making changes. And that sucks.

Sounds like a certain lake troll is agitating to improve his lake-dwelling experience, if ya ask me.

So I think I was wrong, but you are too lmao.

10¹²⁰ is the number of valid game-trees, or valid ~80 move games.

The much smaller number I quoted above, though, IS the valid positions, I was thinking it was actually the trimmed down “truly valid” game-tree sequences.

Isn’t math fun? Limitless ways for us to be wrong!

valid chess positions is in the neighborhood of 10⁴⁰ to 10⁴⁴

Lol, big board you’re playing with…

I enjoy and appreciate nature in nearly all its forms. Even mosquitos just tryna live, they’re born required to bite somebody 🤷‍♂️

Fuck the Canada goose.

Fuck em as a group, fuck their whole flocks, fuck a flying V of Canada geese. Fuck em as an entire grand, branching lineage of this strange fractal miracle we call life, get rid of the Canada goose and our timeline returns to the more harmonious path it had been on before everything stopped making sense.

Canada is cool, fuck that goose tho.

Yeesh. For the privilege of yourself and your users working with a horrible buggy mess of half replaced, half duplicated (triplicated? worse?) apps and features.

And a near guarantee that in a 5 year timeframe, you see 1+ others who paid for that “data in my own jurisdiction” service somehow get fucked in ways they shouldn’t, be it leak or strongarm or whatever.

I’m not suggesting Windows is doomed or anything extreme, but they have cratered their credibility with anyone paying attention. Whole thing feels closer to poorly strung together malware than a serious OS to me.

Sounds like Copilot pulled their programming socks WAY UP that day

This is hilariously autistic sounding for a machine.

Auto PDF text extraction caught your eye too? Got a solution you like currently?

That’s a useful way to look at it, as verbose / extended documentation (amounts to exhaustive usage examples, if you’ve got thorough tests).

I don’t have a metric that’s quick to relate, but for me the…attractiveness or value in testing relates heavily to:

• Project lifecycle - longer and slower -> more tests
• Team size (really more like 1st derivative of team size…team “churn”?) - larger, changing faster -> more tests

Both of these are influenced by your description of tests as docs. Onboarding new engineers is way, way easier with thorough tests, for the reasons you’ve mentioned. Plus it reduces that “gun shy” factor about making changes in a new codebase.

But it’s not always better. I’ve been writing less (few, honestly) the last year or so, sadly.

This should be the standard :)

Maybe they’re hoping there’s an untapped market for that, which would involve strong margins and therefore help fund work on more run-of-the-mill hardware…?

Lots of assumptions I just made 😅