oic it’s using React Native. gotcha. of course the problem that everyone was worried about was which Javascript engine was running the task bar and totally not that the task bar was running Javascript in the first place

“unhackable” is a bit sensationalized here. the Xbox One is actually a security success story not because it is impossible to hack, but because it’s a rare example of a console that wasn’t hacked in its service lifetime. at the risk of giving praise to Microsoft, the architecture is actually really neat and informed the security features of subsequent Windows releases, ie a hypervisor with sandboxed sub containers (this is why they required TPMs).

(also i’m not agreeing with requiring a TPM for general purpose machines; they make sense on a bespoke hardware platform like a game console)

i bet this hack is nuts, but the blue team deserves some level of kudos

youtu.be/U7VwtOrwceo

i was expecting more a human review than an AI context dump, but whatever. i’m conflicted. i’ve been through my share of vim plugin manager migrations, including the recent big change to Lazy. i’m tired boss, and i’m worried about bloat. i hope this feature works out, but i’m gonna let it bake for a while.

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: hurl.dev

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

i personally have pushed back on every “infinite scrolling” feature request from product designers. first, you think you need it; you don’t. second, you think it’s just so nifty! it isn’t. oh it your content is dynamically generated? what was wrong with Reddit’s pager that launched that site into popularity?

it’s unnecessary complexity that hides information from the user, makes API calls (which are, spoilers, paginated) more complicated, can cause the obvious memory/resource consumption issues, and just generally disempowers the user. which i guess on a social media app is the point. but totally counter to the goals of a fleet management system lol

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?