I switched to Bazzite and I’m really liking it.

I have had a few issues with old SDR software that didn’t work.

All in all, I’m very happy with the change and have absolutely no plan to return.

I’m so grumpy, I bought three 8bitdo Ultimate controllers and only one keeps a stable connection even using it’s USB dongle on the steamdock. smh. I then tried a different PC with Bazzite, same deal. Like wtf why won’t they work

I hope to buy a new steam controller but I’ll return it the same day if that shit doesn’t connect

I highly recommend if you’re going to get the 8bitdo ultimate try getting one and just return the ones that don’t work.

wow a Unison comment on the wild! What kind of stuff have you done with it?

Absolutely agree. I know much more about operating systems and software that the average person, and I’ve only been able to handle a number of Bazzite issues with Kagi Assistant. Trying to find how to fix something on forums and regular search is extremely time intensive.

Of course keep in mind that if you’re messing around with your OS you might just screw something up and have to reinstall, but so far I’ve not had anything even close to that. Bazzite seems to be pretty hard to break.

Really for me, Linux only became fun once I started using chat tools to help me learn how to make it do everything I wanted. And I’ve been using Linux off and on for work and at home for twenty years. It’s just sometimes really arcane, and the differences between opensuse, Ubuntu, fedora, and mint made it feel like I never could learn how to fix things.

Sometimes things are harder than I want or just aren’t working right out of the box. But then sometimes I’m able to do things that are actually impossible on other operating systems. So it’s really a trade-off. Also it’s getting better every single day. There was an issue I had last month with a controller, I messed around for 30 minutes but couldn’t get it to work. I tried it last week and it just worked. So don’t lose hope entirely.

Same thing I said the other post, be sure it’s a device with removable battery or a battery bypass so it doesn’t turn into a spicy pillow and catch fire

I’ve been using Bazzite for like a year now and it’s great. I legitimately love using it and so far it plays all the games I like and it’s much more stable than Ubuntu was

My friend is giving away some free copies of his book for learning vim, it’s been super helpful for me. First come first serve

https://leanpub.com/deliberatevim/c/p1cPq3Bb9

Whoa whoa, what do you want to do, crash the entire US stock market over here?! Our whole economy is propped up by the story that AI is the future and will replace all jobs forever. We’ve got MS paying OpenAI paying Nvidia, and that’s making the line go up.

So let’s be cool with throwing around “numbers” that “prove” the emperor has no clothes. Because, like, we gotta pretend he does at least until the next thing that needs every video card ever.

I used my old standby QMK and just wrote the config with cursor/vim.

Here’s a cool picture of my soldering job, I didn’t test it until the end, and it all worked first try!

I’m sure someone will be like “um akchuly” to my explanation. But for me it’s good enough to think if it that way.

I’ve worked in Haskell and F# for a decade, and added some of the original code to the Unison compiler, so I’m at least passingly familiar with the subject. Enough that I’ve had to explain it to new hires a bunch of times to get them to to speed. I find it easier to learn something when I’m given a practical use for it and how it solves that problem.

In practical terms, it’s most commonly a code pattern where any function that interacts with something outside your code (database, filesystem, external API) is “given permission” so all the external interactions are accounted for. You have to pass around something like a permission to allow a function to interact with anything external. Kind of like dependency injection on steroids.

This allows the compiler to enhance the code in ways it otherwise couldn’t. It also prevents many kinds of bugs. However, it’s quite a bit of extra hassle, so it’s frustrating if you’re not used to it. The way you pass around the “permission” is unusual, so it gives a lot of people a headache at first.

This is also used for internal permissions like grabbing the first element of an array. You only get permission if the array has at least one thing inside. If it’s empty, you can’t get permission. As such there’s a lot of code around checking for permission. Languages like Haskell or Unison have a lot of tricks that make it much easier than you’d think, but you still have to account for it. That’s where you see all the weird functions in Haskell like fmap and >>=. It’s helpers to make it easier to pass around those “permissions”.

What’s the point you ask? There’s all kinds of powerful performance optimizations when you know a certain block of code never touches the outside world. You can split execution between different CPU cores, etc. This is still in it’s infancy, but new languages like Unison are breaking incredible ground here. As this is developed further it will be much easier to build software that uses up multiple cores or even multiple machines in distributed swarms without having to build microservice hell. It’ll all just be one program, but it runs across as many machines as needed. Monads are just one of the first features that needed to exist to allow these later features.

There’s a whole math background to it, but I’m much more a “get things done” engineer than a “show me the original math that inspired this language feature” engineer, so I think if it more practically. Same way I explain functions as a way to group a bunch of related actions, and not as an implementation of a lambda calculus. I think people who start talking about burritos and endofunctors are just hazing.

I’m guessing it’s the lube slightly leaking out. I mean I wouldn’t eat it. It’s probably not going to short circuit anything and damage the board. It would be a foolish choice to fill keys with conductive lubricant.

Wow that’s good news, I’ll have to give it a shot

Am I going to have a bad time trying to switch to Wayland? I just use discord, Spotify, steam, some basic steam games, Krita, and emacs

I suppose this is a hot take, but I’d never intentionally select a closed source paid database or programming language. Your data is the most valuable thing you have. The idea that you’d lock yourself into a contract with a third party is extremely risky.

For example, I’ve never seen a product on Oracle that didn’t want to migrate off, but every one has tightly coupled everything Oracle so it’s nearly impossible. Why start with Oracle in the first place? Just stay away from paid databases, they are always the wrong decision. It’s a tax on people who think they need something special, when at most they just need to hire experts in an open source database. It’ll be much much cheaper to just hire talent.

Meanwhile I’ve done two major database shifts in my career, and you are correct, keeping to ANSI standard SQL is extremely important. If you’re on a project that isn’t disciplined about that, chances are they are undisciplined about so many other things the whole project is a mess that’ll be gone in ten years anyway. I know so few projects that have survived more than fifteen years without calls for a “rewrite”. Those few projects have been extremely disciplined about 50% of all effort is tech debt repayment, open source everything, and continuous modernization.

I don’t think it’s going away until ECMA supports native types. Until then it’s the best game in town.

If a team decides to move away from it, it’s only few hours work to entirely remove. So even if it’s going away, it’s risk free until then.

But I cannot imagine why any team would elect to remove Typescript without moving to something else similar. Unless it’s just a personal preference by the developers who aren’t willing to learn it. It removes so many issues and bugs. It makes refactoring possible again. I think teams that want to remove all types are nostalgic, like a woodworker who wants to use hand tools instead of power tools. It’s perfectly fine, and for some jobs it’s better. But it’s not the most efficient use of a team to build a house.

Fantastic meme, I’m dying over here

You definitely described it perfectly: total chaos.

Titles are just “how valuable you are to that team”.

Every team has different needs, so a senior engineer in one team might be a junior on another team that has a totally different set of needs. There is also no standardized titles, so it mostly is just “whatever they want to call it”.

But you can’t see the code that runs those services, stores your settings, deploys your code, etc. Services are still a liability if they go away and your project depends on it