ruduhudi

Scaleway has a great managed kubernetes offering. They host the control plane and all you pay are the instances starting at 30-something € per instance-month.

I bet it‘ll start changing people‘s docs and sending emails without being asked to do so and then they have to dial it back.

No Server Components though, they are the pinnacle of too clever to be a good idea.

I actually like React's virtual DOM approach. It might not be the fastest possible solution, not the most elegant syntax, not particularly concise. but I can at least understand what it does and how data flows. I learned the hard way that with reactive programming (whether you call it observables, runes, signals, whatever) you can lose that understanding and it's a huge pain when that happens.

In this case that‘s actually a security vulnerability, I‘ve also seen a case where it built an api with auth but added a route where anyone could just PUT a new API key into it. Sometimes its own code review catches these, sometimes it does not.

Oh good example

Claude recently tried to replace a html sanitizer with a custom regex that perfectly fit all our tests as well as the spec I wrote

I have the freedom to work with AI tools as much as I as I want and kind of lead the team in the direction I see fit.

It’s a lot of fun for exploring ideas. I’ve built things very fast that I would not have done at all otherwise. I have rewritten a huge chunk of semi-outdated docs into something useful with a couple of Prompts in a day. Claude does all the annoying dependency update breaks the build kinds of things. And the reviews are extremely useful and a perfect combination with human review as they catch things extremely well that humans are bad at catching.

But in the production codebase changes must be made with much more consideration. Claude tends to perform well ob some tasks but for other I end up wasting time because I just don’t know up front how the feature must look so I cannot write a spec at the level of precision that claude needs and changing code manually is more efficient for this kind of discovery for me than dealing with large chunks of constantly changing code.

And then there’s the fact that claude produces things that work and do the thing described in the prompt extremely well but they are always also wring in sone way. When I let AI build a large chunk of code and actually go through the code there’s always a mess somewhere that ai review doesn’t see because it looks completely plausible but contains some horrible security issue or complete inconsistency with the rest of the codebase or, you know, that custom yaml parser nobody asked for and that you don’t want your day job to depend on.

I made this little tool to run claude code sessions in podman containers.

And just like svelte this is elegant exactly until you realize that it is not possible to correctly track all the dependencies and just like svelte you realize that a mix of explicit and implicit reactivity is really hard to debug and then you seitch to explicit reactivity and then you are just as complex as any other reactivity based framework

This is by far the best solution. Super simple and covers all those issues.

Deno does this.

They ended up adding dependency files later on to make it possible to keep package versions in sync without changing every file on every version change.

Please don‘t feel bad to ask questions!

With async IO you can do stuff concurrently without doing it in parallel which is a desirable thing for many workloads. With only threads you‘d need sync primitives all over the place.

Sooooo we're an agency specialized in Next.js stuff.

We're essentially a bunch of passionate engineers but none of us care for ops work including myself, I really want to focus on the code, not on the deployments.

Vercel actually kind of saves us money because the apps we work on are mostly internal tools that don't have millions of requests per minute and developer time is expensive. If vercel saves us one hour of engineering work per month compared to aws it's already cheaper and it definitely saves more than one.

This website is not readable on my phone at all.

Thanks to the odd scroll container i cannot zoom to a view where i do not have to side-scroll anymore.

Isn‘t that mostly a question of the wattage the appliance needs? Here in Germany we have a Max of 3000W on the regular plugs which is why, for example, stoves need special plugs. Not sure about water heaters though

Throttling stuff is another valid use case. I‘ve used a pub/sub for sending e-mail for a newsletter because we couldn‘t send too many of them at once so the consumer would run in a fixed interval and always pick up a fixed number of messages.

Can we please talk about how much reactive programming sucks for UIs? I miss all the people who switched from angular to react for a reason in these discussions... I'd bet none of those are going to move to svelte.

Torras Screen Protector for my phone. Saved me a huge ton of regret after a blurry night.

Web development is complex and has always been. 15 years ago you'd deal with complex hacks to work around the table based layout mess, the horrible browser APIs, javascript's prototype inheritance, Apache configuration and, god forbid, networks of .htaccess files.

10 years ago you'd deal with communicating stuff between language borders, what interaction to handle in javascript, what in ruby/php/perl/whatever and how to interact between the languages.

Now you deal with build processes, transpilers, bundle size optimization, framework configuration and broken react state updates.

It's intrinsically complex, deal with it.

Regulated industry here, we can't use it if we can't self-host it.

Love it when I'm on a design system's website and it's broken on mobile.

https://postimg.cc/N509Z8Kr

Location: Hamburg, Germany

Remote: Yes

Willing to relocate: No

Technologies: react, elm, PHP, Rust

Résumé/CV: cv.michelsmola.de/en

E-Mail: b (at) michelsmola.de

This is really just a Makefile in yaml without lots of the features and the milions of support articles.

Gitlab offers free private docker registry with your non-commercial projects and it's fairly easy to build and deploy containers using their CI when hosting the Dockerfiles there.

This is a long discussion and I hope this has not come up yet:

You can avoid the double constructor problem by using a rust-style constructor pattern:

class Foo { static int from(Foo *that) { that = new Foo(); that.x = 3; return Status::SUCCESS; } int x; }

Or you just read HN directly. what they call their feed is just a selection of relevant HN posts.

Add nextcloud for sync. There's a nextcloud notes app on f-droid.

dnt.abine.com

I think he is absolutely right about his dystopian view on smart contracts managing stuff but forgets about that one trusted party we're trying to avoid the most here, that costs us the most money and that we need the least in real life: Banks. That's what we neet the blockchain for.