just a silly turn of phrase meaning: you should know that this is what you signed up for

so, it’s the same.

saying “Linux does dynamic linking and Window does static linking” is both false and a mischaracterization. Windows absolutely does dynamic linking with its Dynamically Linked Libraries (.dll). how dependencies are linked is up to the developer and whatever hardware constraints. one reason i like Rust is that it prefers static linking, and a lot of tool chains are moving in that direction. the reason Linux distros push people toward their internal package management tools (eg apt) is to have tighter control over dynamic linking.

and we’re also glossing over scoop and chocolatey and winget and Docker.

but that’s where you get to stuff like flatpack and snap and Nix that try to contain the dynamic dependencies.

i don’t think downloading exes hoping that Windows has stuffed enough DLLs into the OS and just running them is a better solution.

super fair. i am a Linux guy normally. i’m just being honest. i wish there was a better more open alternative.

if you want to go with the Linux alternative it’s going to cost. get at least 32GB of RAM and at least a 4090 to run the kind of models you’re asking for. it’s the way she goes

it’s Ubuntu dawg. you get what you pay for.

honestly it’s hard to beat Macs these days in this space for two reasons:

• unified memory means that you don’t have to load up on RAM just to load the model and then also shell out for a video card with barely enough VRAM to fit a basic language model
• their supply chain is solid and has mostly avoided the constraints that other OEMs and parts manufacturers are struggling with

pricing is tough. sure, crypto is on its way out, but GPUs are still the platform of choice for most neural net workloads (outside of SoCs like Apple M-series). i built a PC in late 2024, and it’s easily worth twice what i paid for it.

i guess it would be nice, but packages being a few months out of date is pretty normal for Ubuntu, in my experience. i’m not sure what their testing process is like, but part of using something like Ubuntu is stability guarantees. if they felt like the couldn’t do that for newer versions for whatever reason (resource constraints, lack of downstream interest from stakeholders, etc) they’re not necessarily obligated to.

there’s a world of options. this is an LTS distro. use Arch or Nix or whatever if you want the latest packages. i actually switched to NixOS because the CUDA drivers were too new on Arch, and i wanted a better way to pin versions.

or i dunno keep publicly complaining about it until someone does the work for you

i mean, still. using any CLI tool for the vast majority of people is a nonstarter

anyone who says installing Arch is easy is hiding an extensive computer background. i struggled to install it the first time for sure. then it ran like a champ for like 8 years. solid distro with few compromises imo.

it’s one of those cases where if you have to ask, you should probably just use systemd. anything else is outdated or a passion project based on some idealism, which i’m all for, but if you’re worried about gaming performance as a primary concern i’d put it out of your mind. for example, i’m an obsessive tinkerer that uses NixOS and Arch before that and i use nushell and Neovim and Hyprland, but i use systemd cuz i don’t see a reason not to. it’s well supported and stable.

i’ve been a big fan of Jujutsu (jj) since adopting it a few weeks ago. things i used to avoid with git like proper rebasing and focused commits become so much easier, in addition to the benefits of conflicts being easier to handle. the learning curve i thought was going to be grueling only took a couple days to get used to, and honestly interop with GitHub and my team’s particular workflow were the hard parts. so not only is it useful, powerful, and becoming more important to my workflow all the time, it’s a joy to use compared to git.

i guess honorable mention to zoxide, which has basically replaced cd for me since it does everything cd does but also keeps a small db of your most commonly visited directories so you can just do z Downloads or z my_project or whatever from any directory

deleted by creator

first, i’m biased. i’m a home row kind of guy. i live in the terminal.

Which of the preferences you mentioned discounts this project?

i’ll be direct: light weight dependencies. i understand why you’d use Electron to build a UI, but does an API tester need a UI as a first class feature? i think something like hurl shows it’s not necessary. i get that maybe it’s an accessibility problem (juniors and Java devs being afraid of the command line etc), but UIs are not composable. i could run hurl (or curl for that matter) via bash or nushell or Elisp or Rust or Powershell or JavaScript or GitHub Actions or as a k8s postDeploy… and, not to draw the ire of Lemmy armchair zealots, they’re not easily usable by agents. an 8B model on my Macbook could figure out hurl, no MCP or crazy preprompting required.

plus: user adoption. this is the self hosted community, so maybe not everyone here has the same concern, but i can’t just commit a bunch of exotic files to my shared repositories. Bruno was a tough adoption, even though it seems obvious to version control this stuff and it was the only real option at the time. now i’m tired of Bruno cuz it goes out of date cuz it’s not easily scriptable with our internal auth services because it runs everything in its bespoke UI. if they haven’t made a button for it, you can’t do it. that’s the problem with UI dev tools.

no shade, i understand some people would be totally lost if their IDE didn’t have a big green run button.

i’ve been looking for a silver bullet in this space. hurl[1] seems promising as well. i feel like Bruno has always been jank, and going 1.0 didn’t help. at work i’ve stuck to vibe coding my API test code with a stack of TOML configs, that way i get to reuse/test my client code as well.

what i want is something version controllable with lightweight dependencies that i can automate easily. i’m afraid that discounts this project. not going to ask my team to download Yet Another Electron API client UI. i’m hesitant to introduce hurl, which can at least be scripted.

1: https://hurl.dev/

lots of good reasons to spin up containers for development is my point, especially for an embedded system with exotic system dependencies (compared to Node.js, for example).

Home Assistant is a “simple app” that i have to open ports for.

does that mean they have a good reason? maybe not.

really? i mean, people have done it for friggin vanilla ass Node.js servers. Android projects can have weird dependencies that a container might help solve (NDK etc).

i’m not saying that it’s my preferred way to build, but that wasn’t the question.

generally yeah. the problem is that the barrier to entry used to be higher so fewer people knew how to write code to integrate with the project before coding agents. now anyone who can install Claude Code has a seat at that table

sometimes syntax changes are part of the decision to do a rewrite. these are user interfaces at the end of the day. i’m not saying you’re wrong about any particular case, but it’s like saying “why make Instagram when Facebook exists” or “why make Scala when Java exists” etc. i like a good fresh look at how we use and instrument and teach our development tooling.

also, when i was 18 and would tell IT professionals i was getting a computer science degree, the #1 response was, “get ready to spend the rest of your life learning new things.” and i’ve found that to largely be true

yeah i get that.

generally most modern UIs are moving away from those reactive patterns (React, Svelte, etc) just cuz the composition can be optimized (Kotlin compiler plugin, shadow-DOM, etc), and a lot of people—myself included—find that declarative design easier to reason about. and yeah i guess i outed myself as an Android dev, but i can’t in good conscience recommend the node based Android XML UI lol (although that’s a different SDK).

anyway, not to yuck your yum. i played around with JavaFX back in the day but never made anything to speak of. i’ll have to check out more of your blog!

JavaFX with Kotlin

mad lad.

what makes you snub Compose UI?