News for hackers. Stuff that matters.

JB_5000

Hey - small Aussie team here. It's 1am and we just open sourced ContextUI.

It's a local-first desktop app for building and running visual AI workflows. TSX-based UI modules, full filesystem/CLI/GPU access, works offline with no cloud required.

Workflows can be published to the Exchange - others install and run them locally with deps resolved automatically.

Agents can create workflows and immediately test/run them in the same runtime.

Desktop app is Apache 2.0. ~300 users, ~230 workflows published.

Tell us what's awesome and what's terrible

AI isn't killing SaaS – it's killing single-purpose SaaS

Over the last year I keep seeing “SaaS is dead” takes. I don’t think that’s what’s happening.What seems under pressure isn’t SaaS as a model. It’s narrow SaaS built around a single capability that AI can now reproduce cheaply.If your product is basically a thin wrapper over a model, or differentiated mainly by features rather than workflow integration, the moat feels weaker now. AI compresses...

( Read More... | 9 comments | 3 points | on HN )

Would you choose the Microsoft stack today if starting greenfield?

Serious question.Outside government or heavily regulated enterprise, what is Microsoft’s core value prop in 2026?It feels like a lot of adoption is inherited — contracts, compliance, enterprise trust, existing org gravity. Not necessarily technical preference.If you were starting from scratch today with no legacy, no E5 contracts, no sunk cost — how many teams would actually choose the full MS...

( Read More... | 25 comments | 5 points | on HN )
Ubuntu. Its great. So much cleaner and userfrienly then Microsoft. Definitely don't need to be a dev to work in Ubuntu anymore. Honestly, I don't know how microsoft is holding its base.
Re:Making Sense of the AI Era on Monday February 23, 2026 @06:12PM (#47130403)
ai doesnt replace engineering. it compresses execution. abstraction always moves up. assembly to compilers to frameworks to cloud. same pattern.

real risk isnt ai taking jobs. its people becoming prompt approvers who dont understand systems or failure modes.

fundamentals still win.

Re:Show HN: loopmaster Beta – Code Music on Monday February 23, 2026 @06:11PM (#47130382)
cool idea and nice execution. highlights how far browser-native tools have come. curious how deep the DSP actually goes though — is this more a creative sketchpad or something you could realistically build full tracks with long term.
good breakdown of the tradeoffs but it kinda stops at critique. explains why age verification becomes invasive but doesnt really propose what a workable alternative looks like. feels like we need concrete models or architectures not just pointing out the trap.
Re:Most web utility sites are going to die soon on Monday February 23, 2026 @12:37AM (#47118515)
i think everything is shifting, not dying.

local-first tools make sense and new patterns/protocols will emerge from that. but convenience always wins, so web utilities won’t disappear — they’ll just evolve.

Re:Show HN: AI-Native Architecture Series (Open-Source) on Monday February 23, 2026 @12:36AM (#47118509)
actually respect this.

feels like more solo builders are realising agents arent about intelligence, they’re about constraints — DSLs, deterministic layers, boring hybrid architectures.

you stop writing code and start designing guardrails. curious how this scales though.

Re:AI is locking people out. At Scale on Sunday February 22, 2026 @03:59AM (#47109501)
AI can also be a massive democratiser. Lowering the barrier to building means more people can create accessible tools, not just large teams.
GPU simulation isn’t just speed, it changes what’s possible to design. Whoever iterates fastest wins, not whoever starts smartest.
Re:Study: Self-generated Agent Skills are useless on Monday February 16, 2026 @11:37PM (#47043756)
Interesting benchmark, but worth noting the methodology: skills are generated before the task, with no feedback loop. In practice, useful skills tend to emerge from doing — you attempt, observe what failed, then codify what worked. Generate → execute → observe → refine. The paper tests cold generation, which is a different (and less realistic) setup.