the linux foundation

for people ootl on D like me, this seems to explain the problems: https://dpldocs.info/this-week-in-arsd/Blog.Posted_2024_01_01.html

it’s tied to packagekit, so tumbleweed should work ootb. opensuse’s immutable distro is less likely to be possible though, as well as anything else like that

only sort of.

this is the original document defining markdown, and you’ll notice it doesn’t really specify a lot of the things that have compatibility issues across different markdown processors, along with allowing arbitrary html which really depends on where you’re showing it. There’s a list of ambiguous syntax here.

CommonMark is as close to a standard as we have.

I second the formbot voron 0.2 kit, it was my first printer and it was a great experience. I have had a lot of heat creep issues with the dragon hf hotend though, I’d probably recommend the standard one instead. Other than that it’s been much less required tinkering than I was led to believe. It generally just works.

tailscale also just has a button to buy/enable mullvad as an exit node. if you’re just looking for a commercial vpn for privacy it works well.

is there compositor support? is there a way to get kde to rotate my monitor to a specific degree via cli?

keep in mind I have no idea if there are real use cases for diagonal monitors, I just duct taped an accelerometer to the back of my monitor and can only get it to rotate in 90 degree increments with kscreendoctor and thought it would be funny if the picture was just always upright

wayland doesn’t support diagonal monitors

not sure for what purpose you want a tablet, but I had a fujitsu 2 in 1 in college that was pretty solid for linux support. no problems with pen drivers or anything. the screen swiveled around and it folded down into a tablet. it was pretty bulky compared to an android tablet or similar, but it worked well for taking noes and had a full keyboard when I wanted it

one more for using nix, but for language tooling I generally prefer a nix shell and installing per project dependencies there. then updates don’t break random projects and you know all the dependencies of a given project

it felt to me like coffeescript solved problems that people had, then js got equivalent features. arguably that could happen to ts as well

Brother laser.

I’ve been using vscode in firefox via tunnel to my main machine on my android tablet and it’s been working well enough

I’ve found it to be less strict than I’d prefer. Things like whether parameters are aligned or indented, whether or not the first one is on its own line, what statements are indented in fluent calls that have blocks, etc.

A lot of other formatters (prettier, anything for python, etc) force something consistent in those cases, whereas it seems like the dotnet formatter prefers to leave things as they were.

I’d love for it to be more opinionated and heavy handed if anyone has suggestions

I refuse to believe that people use a php style guide. I have yet to open a php file in the course of any job that doesn’t mix tabs and spaces arbitrarily on top of numerous other horrors.

Luckily it’s not often that I have to, so sample size may play in a bit…

I’ve found nixos is perfect for me since I like how precisely I can configure it.

Oddly enough, I’ve had a decent chunk of my only barely technical friend group switch to it for the opposite reason. They all just copypaste snippets of config between each other, and if something breaks they just go back a revision. I doubt any of them spend much time configuring anything. It really is the perfect idiot proof distro and I don’t normally see people talking about that side of it

Voron doesn’t sell anything, you either have to source all the materials yourself or buy a kit. I bought a kit from formbot when I built my V0 and have been pretty happy with it. They also sell V2.4 kits and have a warehouse in Czech

there’s a plugin for it here. It works well but it’s kind of at odds with the rest of blender’s tools and normal workflow

probably since later people could look at the partial image, see that pink wasn’t a very likely color, and check their math until the result looked more correct

I’d personally rather something like regal in clj or rx in emacs. Instead of strings that my formatter and autocomplete don’t know anything about and that I have to add to my build pipeline, I get native types that I can manipulate the same way I do other code, in editor or programmatically.