dimgl

> Go has an ad-hoc, informally specified, bug-ridden, slow implementation of half of a decent type system.

It's not lost on me that this is a widely used aphorism. The problem is that it's not true in any way shape or form.

I'm really surprised by this visceral reaction to not choosing Rust. Go is a great language and I'd choose it for a majority of projects over Rust just based off of the simplicity of the language and the ability to spin up developers on it quickly. Microsoft is a big corporation.

Why _not_ use Go?

C# needs an interpreter (.NET runtime) while Go compiles down to a binary. And the toolchain allows you to compile for other architectures fairly easily.

So that could be a fundamental reason why.

This is wild, I had no idea it even had this.

I don't understand this comment. Without caching, you'd be at the mercy of the geolocation company. I've deployed a service that does exactly this.

I'm really surprised that the pendulum has swung so far in the other direction that people are recommending not to use Redis.

Sure, don't introduce a data store into your stack unless you need it. But if you had to introduce one, Redis still seems like one of the best to introduce? It has fantastic data structures (like sorted sets, hash maps), great performance, robust key expiry, low communication overhead, low runtime overhead... I mean, the list goes on.

Ah, you know, now that I think of it, Apple Music has this pretty bad bug where after a couple of hours of playing music my playlist will stop playing and nothing I do will make the playlist usable again. This never happened in iTunes.

? How is this possible? I have zero issues on my Macbook, while Linux is consistently a PITA for me.

Can you explain how this mirrors what happened in Germany?

> Content marketing is dead.

I mean... good? The quality of search results has gotten increasingly worse over time...

Is this even the same company that created Terraform? HashiCorp's trajectory has been baffling...

Great, my account actually just got hit with this. Are we absolutely sure this is solved?

Thank the lord I didn't have anything all that important, and I was in front of my computer to change my password immediately.

As far as I can tell, no one signed into my account. Pretty embarrassing vulnerability tbh...

It's just you. It's extremely impressive. He likely set himself up for life with this + learned an unbelievable amount. And this is, in and of itself, a business. He has merch, a conference, a social media presence, etc.

Is it possible that they simply have a good product?

Can't that be solved with regular workflow tools and prompts? Is that what an agent is, essentially?

Or is an agent a collection of prompts with a limited set of available tools?

I should have clarified that yes, I used Alpine with htmx.

This sounds like a Remix problem more than a React problem. I really enjoyed the ideas behind Remix actually! In fact, I found that having both server and client code in a single file (a-la Next.js) made me super productive. And nowadays I bet it pairs well with LLMs due to having the full vertical slice available in the agent's context.

I really wanted that framework to take off.

But that community is straight toxic... I have not seen a more toxic community than the React Router community. It's one of the reasons I stopped using Remix. React Router 7 is actually pretty cool; I recently built a prototype on it and was surprised by how well it worked. But I know I'll eventually need some kind of support and feedback, and I can't imagine engaging with those devs/that community again...

I really have not liked htmx at all. Anything dynamic with it is a big, big pain...

Stores really turned me off in Svelte 4 so I was eager to start using Svelte 5. I've been using Sveltekit and Svelte 5 for a new project and I have to say... React's productivity is still unmatched, even if the Sveltekit and Svelte tech is technically better.

A couple of things that I found really annoying: all pages being named `+page.server.ts` or `+page.svelte` or a variation of that makes it hard to easily search for code. The tooling for Svelte is also separate from `tsc` and ESLint, making it tricker to both integrate into CI and use in dev.

And then there's just weird incompatibility stuff with the previous version. For instance, most Svelte packages still use stores, like SuperForms, so you have to contend with two versions of the world, making writing code really confusing at times. Plus, Svelte HMR is still kinda early AFAICT, so it will clobber your state when a Svelte module reloads.

I _really_ want to like Svelte. It's significantly faster to render and I like the ideas behind it. But React's productivity is unmatched.

I’m not sure anyone is convinced this will empower individuals. On the contrary: if we get this tech “right” enough, the inequality gap will become an inequality chasm… There is no financial incentive to pay humans when a machine is a fraction of the cost.

What are “parrot people”? And what do you mean by “doomers are probably wrong?”

I'm currently using a 32B Qwen model for summarization and it's pretty good.

Income inequality will soon become euphemism

Deepseek is not the only reason. I cancelled my OpenAI subscription because I've replaced it wholesale with Anthropic.

> I hate nearly every single thing about the MacOS UX. The dock is awful, and so many insane defaults all over the place. Hiding scrollbars is a bug, not a feature. Pointer acceleration is a bug, not a feature. The scroll wheel operating in reverse is a bug, not a feature.

I disagree with every single thing you've said here. And I'd be willing to bet most Apple users do too.

That being said, I do think there's some charm in simple, "outdated" UIs.

It's astroturf.

I've been using it. Completely overhyped trash. Does well in benchmarks and fails in real-world scenarios.

This implies that "hydration" exists exactly how it exists today in SSR. That's not the only way to hydrate a frontend client.

You could, for instance, as part of a server payload send back a JavaScript object full of state and the frontend will read from it and render accordingly. But that would require not using a framework and building it yourself, which I think developers nowadays aren't keen on doing.

I was doing with this Knockout back when I was using ASP.NET MVC! I'm surprised it's not a more common pattern.

How bad is the job market right now? Is it as bad as everyone says it is? Makes me pretty scared for the future, tbh.