News for hackers. Stuff that matters.

florentmsl

I think nowadays they are perfectly fine. Blazor Server had lots of disconnects because our customers typically don't have a stable Wi-Fi connection. Blazor WASM had next to no tooling. It was dotnet 5 or 6, so still very early on the WASM journey of dotnet, not much or no documentation and no AI to overcome initial hurdles.

tbh I sometimes miss React & TS too, for the frontend React is just straightforward, and TS is no bad language at all

To be honest, in retrospect I should have released the first version. But as an engineer, I got stuck fixing things and adding features because I thought, “otherwise no one will use it.” While adding features, I realized I needed to change the tech stack in order to move faster and add more functionality more efficiently. In the end, I’m happy with Rails, but I should have released years ago.

Show HN: I rewrote an inventory app 4 times over 5 years before releasing v1

https://upzonehq.com/

I’ve been building for 5 years.I rewrote it 4 times (Blazor Server -> Blazor WASM + Asp backend -> React + Node -> Ruby on Rails - Ruby and Rails are both awesome btw.) and kept telling myself I was “improving the architecture” when I was really avoiding release. I also spun up a few side projects in that period and shipped none of them.This is the first one I finally pushed live.It’s...

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

Show HN: Frost AI – Stop losing money on AI agents

https://www.frostai.dev/

Hi HN,Florent here, one of the founders of Frost AI. Before that, we tried to build an AI Agent for a friends business. We realized we'd have to build a whole system for usage tracking, per-user cost analysis, subscription management, and a customer billing portal. We had to spend more time on boilerplate billing code than on the AI itself. A single user in a weird loop could rack up a massive...

( Read More... | no comments | 2 points | on HN )