As seen from my apartment in Reykjavík Iceland: https://ss.solberg.is/89N0qS7T

That’s beautiful. But you get aurora even sans G4, true? Was this more intense and spectacular?

Yes - not seen it this red though.

Keep in mind that a lot of vibe-coded software is flying under the radar because it’s being built to replace SaaS and bring workflows in-house. We often judge success by public launches or ARR, but the real "killer app" for this methodology right now is internal tooling for small teams. For example, instead of spending developer bandwidth integrating Salesforce into first-party data, teams are increasingly just vibe-coding a bespoke CRM or CMS as an appendage to their existing database. It’s complex software (state, auth, heavy logic), but it will never be on Product Hunt because it's purely for internal utility. The success metric here isn't "did we get 10k users," it's "did we avoid a $50k contract and weeks of integration hell."

I agree with your assessment, as a full stack dev with CS degree that just kinda waltzed into Salesforce for the last 5 years. Claude is more capable at delivering the customizability that Salesforce tried to offer with it's "clicks not code" approach. the only thing these CRMs have going for them is enterprise entrenchment.

I also work at Stripe and will be recommending that we migrate our CPQ off of Salesforce for various reasons (agent force is butt, platform limits are silly in 2025 - 6 meg max heap size for a backend transaction?????).

Yes this is like anyone sucessfully used their microwave over has anyone started a 1000 location fast food chain. At scale there are more microwaves than maccas.

True. I’m vibe coding and I realize I can combine a bunch of saas into 1 mega app.

Greatest feeling ever

I recommend https://remedajs.com/ - they're always making the types more accurate too. Like groupby has nonempty lists.

The types look great on remeda, but one thing that looks intriguing about SuperUtilsPlus is the focus on being tree-shakeable. Lodash's lack of tree-shake-ability is a drawback to using lodash on the frontend.

edit: the types on remeda look great though! If I were doing a backend-only NodeJS project, I'd be super tempted to test it out.

Just import what you use for lodash?, the theres not need for a treeshake situation?

Link to your wife's work?

libsql (from turso) is also working on this - the more the merrier

I just use cloudflare tunnels (cloudflared) - don't have to install any certificates, it's all handled by cloudflare. Yes, it exposes globally, but that's often convenient to share a link to my dev with colleagues. And it has been fast enough. Downside is that you need internet connectivity.

No - please check out Hono https://github.com/honojs/hono

The presence of alternatives doesn't mean something isn't the "de facto".

In all the times I've evaluated all of the alternatives to Express, this is the first time I'm ever heard of hono

Hono is the new hotness. It can run across , deno, bun, cf workers, etc etc it’s not locked to node

Hono Weekly Downloads: 46,831

Express Weekly Downloads: 29,109,573

Come on, man.

I believe this is not an appropriate comparison. Hono is a relatively recent project when compared to the age of Express.js.

Very different. Svelte has magic event bindings and compiles `.svelte` files. Their learning material is interactive and worth going through just to see some new ideas.

It certainly feels like that, but there’s actually a lot more magic happening under the hood with React.

You can open the compiled svelte output and follow through the entire code path for updates in a few minutes.

For what it's worth there's a good library to load markdown with Svelte components mixed in. Here's how I'm loading it: https://github.com/jokull/blog/blob/master/src/lib/getPosts....

SvelteKit is a very complete and well designed solution. Routing, data loading, forms, SSR, caching, dealing with environment variables - all very nice. The only "drawback" is Svelte - I just don't like the data binding thing and prefer working with React components and hooks. Maybe that's just because I've spent so much time in React/Next. Well written React code is actually quite easy to debug, reason about and debug. I find it super annoying to refactor Svelte code because every time I want to extract some code into a component it can't be a function in the same file before it becomes a whole new file. It has to be a file. Also haven't found anything nearly as nice as Framer Motion and Radix in Svelte land.

With all the love in the world, that's probably down to the sunk-cost fallacy. You've invested a chunk of time into understanding the idiosyncrasies and non-standard methodologies that React has pushed at you over the years.

Svelte's pattern for data binding (with the exception of the $: reactivity) is exceptionally idiomatic and as close to standard web as 2-way reactivity will ever be. Easy to get to grips with as a newbie and a breath of fresh air for someone with years of fe experience under their belt.

Svelte embodies the KISS principle and long may that last.

See, that's what a lot of people say about Ruby.

But some weird people like me enjoy JavaScript despite its downsides and find Ruby terrible.

Maybe its irrational but familiarity sometimes wins over level of idiomacy.

Everything in React is just a function, so there is expectation of how it works. The data binding in Svelte is a bit magical and not always clear if there are race conditions, but I'm a Svelte noob trying to port my existing app to it.