this feels like a breaking change akin to macOS changing the Command key to bringing up a start menu because it confuses Windows users. platforms have differences, and this one is actually so tiny and inconsequential it feels like any ameliorated confusion will be offset by confusion of people that rely on it and use it. is this really the barrier to adoption?

other commenters have hinted at this, but the main point of most of the good advice is this: don’t use the system Python install (ie the one from apt) for development. uv is my go to, but the idea behind *conda, pyenv, asdf, etc is the same. the underlying OS shouldn’t be an issue; you should be able to ship the code between OSs and build just fine, ideally.

nice. simple and modular i like. i deal with far too many “one stop shops” at work to bring that home

we use Jenkins + a bespoke wrapper at work. thats left a bad taste in my mouth enough to avoid Jenkins altogether

this is my experience as well. we have a bespoke wrapper around Jenkins, and the more we can test locally the less time we have to spend waiting for the system to fail. it’s one of the reasons i’ve adopted just to script things locally as if it was CI.

heck yeah this is the review i was looking for 💯

you’re right. i just expected it to be an increase 😅

i honestly didn’t look that close, obviously haha

but yeah, i’ve been kinda looking for a reason to de-Microsoft my stuff

good lead. it’s just the one project for now, and to my surprise it’s actually a dependency for the ollama-rs project, so i feel somewhat obligated to keep it stable.

yes, according to this morning’s email

three, maybe four things:

1. as mentioned: Obsidian. i pay for Sync cuz i like the product and want them to succeed and want reliable offsite backups and conflict resolution. use a ton of links and tags. i’ve been into using DataView to make tables of IoT devices, services, todo items, etc based on tags and other YAML frontmatter.
2. chezmoi. manages my dotfiles so my machines are consistent. i have scripts that are heavily commented that show how to access MQTT, how to read and parse logs from journald, how to inspect my network, etc. i do think of them as code as documentation, even if they’re also just convenient.
3. NixOS. this has been my code as config as documentation silver bullet. i use it as a replacement for Docker, k8s, Ansible, etc as it contains definitions for my machines and all the services and configuration they run, including any package dependencies and user configurations. no more statting an assortment of files to figure out the state of the system. it’s in flake.nix
4. honorable mention to git and whatever git hosting provider is not on your network. track your work over time, and you’ll thank yourself when things go wrong.

some things are resistant to documentation and have a lot of stateful components (HomeAssitant is my biggest problem child from an infra perspective), but mainly being in that graph mindset of “how would i find a path here if i forgot where this was” helps a lot

in addition to what others have said, i’d say a lot of civil infrastructure—hospitals, clinics, government facilities, etc—are locked in either because of bad politics or weird vendor lock in. my dad ran his own dental clinic, and he had to run a Windows server because it was required by his software vendor that did everything from appointment reminders, to the web portal, to billing, to showing which of your teeth were missing, to integrating with scanners or other equipment. it was shit software that looked like Windows 3.1 well into the 2020s, but it did the job and 24hr support was reliable. just an anecdote, but as a software engineer i was fascinated by it.

definitely. Qualcomm provides the SoC and drivers for what comes on that package, but you’ll want to add a battery controller, power controls, and other embedded systems onto the motherboard to make it act like a real system. it’s also a way different boot process in my experience than a normal x86 platform. the difference between ARM and x86 isn’t just the instruction set. plus at this level nothing is ever plug and play.

as for how Valve was able to ship an ARM device, they stuck to the normal kinds of IO a mobile device with a SD8gen3 would have and already have a great OS for fast iteration that they have tight controls over.

i’m excited for this XElite line, but i can see how it’s not in Qualcomm’s best interest to spend their engineering labor on porting to desktop Linux, not with Microsoft and Dell etc already having bids on that time. as long as Qualcomm is upstreaming and not actively blocking open source development, i don’t understand the kind of resentment i see for them. because they work with Google? i see them becoming more open as they become more prolific outside of embedded systems and Android. i see it as an exposure problem.

i don’t understand. don’t they operate in one of the largest Linux platforms around, Android? if you mean they don’t support your desktop wifi chipset or publish modules for their SoCs, then i guess that’s fair to say. but i think a deeper integration with Linux can only be a good thing. i guess my perspective on Qualcomm is colored by the fact that i worked with them briefly on an embedded project, have seen their docs, and have booted their dev kits into a full Ubuntu environment.

sucks

(but also maybe yay for Linux on ARM?)

nah nushell does all that and more. i think fish is a good alt for someone who knows enough bash to know that scripting it sucks. if you want autocomplete and plugins n stuff it’s probably the most ergonomic POSIX-like shell out there.

it started just dropping in to mess with some data. now it’s my daily driver, and i have a trove of scripts that are my docs as code for systems like systemd or stuff that is specific to work

i made the transition from fish to nushell and can confirm all this stupid JSON data and YAML config was the reason

i mean… sure. some neat tricks in here i wasn’t aware of, but asking my mom to open the terminal… i mean it’s not rocket science but that doesn’t make it accessible. all the scripting and stuff that you’re talking; that stuff comes in the Jellyfin box. honestly, it might be worth it to have both if you have users that aren’t comfortable in the terminal

ok i’m not saying do this

i recently setup an API proxy, C&C server, Grafana and Prometheus, and Discord bot. now i can send pings via Grafana or with a simple request (provided it’s authed via VPN or proxy) and have my Discord bot use a local LLM on my network to deliver the alert to a Discord channel in the voice of Ultron.