Hacker News: lukaslalinsky

New comment by lukaslalinsky in "Redis 8.8: New array data structure, rate limiter, performance improvements"

lukaslalinsky — Fri, 05 Jun 2026 13:59:21 +0000

With the amount of problems I had using Redis Sentinel, I really wish there was another way. On multiple occasions, with completely different deployments, it got itself into a non-repairable state where the only option was to drop it and setup the replicas manually. I was hoping someone would do a Patroni-like project for Redis, but I've not found it yet. I've moved all persistent data to PostgreSQL and use a number of Valkeys behind Envoy proxy as a cache.

New comment by lukaslalinsky in "Redis 8.8: New array data structure, rate limiter, performance improvements"

lukaslalinsky — Fri, 05 Jun 2026 13:55:44 +0000

I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.

New comment by lukaslalinsky in "Open Code Review – An AI-powered code review CLI tool"

lukaslalinsky — Fri, 05 Jun 2026 13:52:49 +0000

Well, I'm just an extremely happy user. I've honestly tried to find an alternative, and couldn't. I'm using it in the context of solo developer and it provides a huge value to me.

New comment by lukaslalinsky in "Changing How We Develop Ladybird"

lukaslalinsky — Fri, 05 Jun 2026 09:58:45 +0000

It's actually common, many companies develop their products this way. The source is available, you can see the VCS, but you can't participate in the development. That's why I see this as signal that it's going to turn into a company.

New comment by lukaslalinsky in "Changing how we develop Ladybird"

lukaslalinsky — Fri, 05 Jun 2026 09:43:14 +0000

What made open source great, is the fact that if you find a problem, you can patch it. It's what motivated me, anyway. Ladybird is not SQLite, it's under development and very likely will be forever. To me it looks like they are transitioning into a company, where this model makes sense.

New comment by lukaslalinsky in "Changing How We Develop Ladybird"

lukaslalinsky — Fri, 05 Jun 2026 09:39:22 +0000

Indeed, while there is communication that the situation with merging external pull requests should improve, the reality is that it's easier to land a patch in Linux, than in Zig.

New comment by lukaslalinsky in "Changing how we develop Ladybird"

lukaslalinsky — Fri, 05 Jun 2026 09:36:30 +0000

I wonder how can a new browser engine survive with the source available model. Like, why would anyone support this, unless they have business association with the Ladybird developers?

New comment by lukaslalinsky in "Open Code Review – An AI-powered code review CLI tool"

lukaslalinsky — Fri, 05 Jun 2026 04:34:34 +0000

I've tried many AI code review tools. Nothing comes close to the depth of CodeRabbit reviews. It's the only such tool that can find real logical bugs. I'd love to be able to get Claude Code to do similar quality of review, but I can't get it right, no matter how I try.

New comment by lukaslalinsky in "Please Do Not Vibe Fuck Up This Software"

lukaslalinsky — Sun, 31 May 2026 19:31:47 +0000

That's possible, but who are you to tell a person what they should and shouldn't do in their free time.

New comment by lukaslalinsky in "Please Do Not Vibe Fuck Up This Software"

lukaslalinsky — Sun, 31 May 2026 18:32:11 +0000

Just going away from computers for a few days should be enough, the mob will get tired soon.

New comment by lukaslalinsky in "Please Do Not Vibe Fuck Up This Software"

lukaslalinsky — Sun, 31 May 2026 16:24:55 +0000

Look, it's not that long time ago when we had the xz malware. The pattern is always the same. Maintainer of the project is doing X, people start to pressure them to do something else, maintainer gives up and opens the project up to other maintainers, and then many things can happen. If there is any lesson from the incident, open source maintainers should never allow the pressure to happen, ignore it if it's too strong, block people. Rsync has been maintained for a very long time. Bugs happen, even regression bugs happen. People don't get to dictate how should the volunteer do development.

New comment by lukaslalinsky in "Please Do Not Vibe Fuck Up This Software"

lukaslalinsky — Sun, 31 May 2026 13:44:10 +0000

The thing is, showing the annoyance to the volunteer, who is already doing their best, has two possible outcomes:

1) they stop volunteering

2) they will ignore you

In neither of that is your issue solved. So maybe it's better to deal with the frustration on your own and then file a bug report.

New comment by lukaslalinsky in "Please Do Not Vibe Fuck Up This Software"

lukaslalinsky — Sun, 31 May 2026 10:40:10 +0000

The result might be closing bug trackers for the core open source projects. Or make them invite only. Even fundamental projects like Linux or LLVM accept AI contributions.

New comment by lukaslalinsky in "Please Do Not Vibe Fuck Up This Software"

lukaslalinsky — Sun, 31 May 2026 10:09:20 +0000

That's up to the maintainer to decide, no? If they decide to use AI to write more tests, then they do it. It's not like they owe the public something. If the "public" wants to take the project over and maintain it, they can fork it, but it's a thankless job.

New comment by lukaslalinsky in "Zig ELF Linker Improvements Devlog"

lukaslalinsky — Sun, 31 May 2026 07:45:13 +0000

I've tried building your project, but hit problems due to dependency hash mismatches. Do you have a screenshot somewhere?

New comment by lukaslalinsky in "Zig: Build System Reworked"

lukaslalinsky — Sun, 31 May 2026 03:45:42 +0000

There are going to be builtins to control this. The compiler will not do it on its own.

New comment by lukaslalinsky in "Zig: Build System Reworked"

lukaslalinsky — Sat, 30 May 2026 20:21:20 +0000

It's not just I/O, it's also mutexes, condition variables, time, etc. It's not horrible, but it does add up, so calling it super efficient is a stretch.

New comment by lukaslalinsky in "Claude Opus 4.8"

lukaslalinsky — Thu, 28 May 2026 18:25:47 +0000

I've said it before, but I don't like Opus past version 4.5. It became unresponsive, thinking for too long without feedback, sometimes seemingly getting stuck. I guess it might be marginally better for some benchmarks, but when using it as coding assistant, the new models are worse. Even the new Sonnet versions do that. I'm slowly getting used to Haiku-level LLMs with the hope to run it locally at some point. It's less autonomous, but maybe that's for the best.

New comment by lukaslalinsky in "What color is your function? (2015)"

lukaslalinsky — Wed, 27 May 2026 12:36:29 +0000

My work was kind of similar to the `std.Io` plans, so when I learned about it, I started aligning the project to that interface. Now it's a full fledged implementation of the interface. It's actually the first async implementation of the interface, the one in stdlib is very far from finished.

There are many shortcomings in the API, especially missing timeouts everywhere. It was clearly designed by people working on the compiler and other local tools, and not much network services, but I think it's a great improvement in the Zig ecosystem and hopefully people can now write reusable libraries.

New comment by lukaslalinsky in "What color is your function? (2015)"

lukaslalinsky — Wed, 27 May 2026 12:34:04 +0000

But if you have stack growth, the way Go does it, then the stack you allocate is actual memory you use. You are just trading heap allocations for stack growth. I started to see the stack as a super fast allocator that is always available.