lukaslalinsky

6 ms·

31.
by lukaslalinsky 4mo ago
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, bu
32.
by lukaslalinsky 4mo ago
That's possible, but who are you to tell a person what they should and shouldn't do in their free time.
33.
by lukaslalinsky 4mo ago
Just going away from computers for a few days should be enough, the mob will get tired soon.
34.
by lukaslalinsky 4mo ago
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 oth
35.
by lukaslalinsky 4mo ago
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 w
36.
by lukaslalinsky 4mo ago
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.
37.
by lukaslalinsky 4mo ago
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
38.
by lukaslalinsky 4mo ago
I've tried building your project, but hit problems due to dependency hash mismatches. Do you have a screenshot somewhere?
39.
by lukaslalinsky 4mo ago
There are going to be builtins to control this. The compiler will not do it on its own.
40.
by lukaslalinsky 4mo ago
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.
41.
by lukaslalinsky 5mo ago
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 us
42.
by lukaslalinsky 5mo ago
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
43.
by lukaslalinsky 5mo ago
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.
44.
by lukaslalinsky 5mo ago
I've spent the last year working on an async runtime for Zig and I really grew fond of stackful coroutines. Your just program your code as if everything was blocking. The main benefit is that you can use whatever library, it doesn&#x27
45.
by lukaslalinsky 5mo ago
On the other hand, it's easy to win an argument with it after it does something stupid, so that feels satisfying. :-)
46.
by lukaslalinsky 5mo ago
Except complaints that it's horrible, you mean?
47.
by lukaslalinsky 5mo ago
The disadvantage is that then you never learn how GIMP works and will forever frustrated it's not Photoshop. Sometimes it's better to take the hard way.
48.
by lukaslalinsky 5mo ago
I don't get it, I've been using Ubuntu from the very early days, that's probably 20 years now. And I really didn't encounter any serious problems. Over the years, I had one instance of driver update breaking wifi. That s
49.
by lukaslalinsky 5mo ago
If they can also vibe-code some modern Android app for Zulip using the unlimited tokens, I'd be happy.
50.
by lukaslalinsky 5mo ago
I still think the best process with Claude Code is: 1) ask it to gather context that you know is relevant 2) only then ask it to do whatever you want it to do. If you do it the other way around, it will over research, over think and general
51.
by lukaslalinsky 5mo ago
It works exactly the way I'd work. I have learned to navigate large codebases before LSPs existed. I used vim for many years and would grep to find the relevant files. When I first tried Claude Code last year, I was like WTF, it's
52.
by lukaslalinsky 5mo ago
People were doing async I/O before coroutines existed. They are using callbacks and their own networking.
53.
by lukaslalinsky 5mo ago
I always wondered what is the motivation behind Haiku. Is it a recreation of BeOS for the sake of recreating it, or is it practically usable for daily use?
54.
by lukaslalinsky 5mo ago
I really don't think so. Bun was using their own language, that forked from Zig 0.14. It's not like the communities interacted much. All of Bun's code was their own internal code, it was not part of the Zig ecosystem. I don&#
55.
by lukaslalinsky 5mo ago
They can't, because Bun is tied to a fork of Zig 0.14 which is not compatible with regular Zig compiler.
56.
by lukaslalinsky 5mo ago
Green threads are fine for large servers with memory overcommit. Even with static stack sizes, you get benefits over OS threads due to the simpler scheduling. But the post was about embedded and green threads really suck there. Only using a
57.
by lukaslalinsky 5mo ago
It was not for performance reasons, but for scaling up.
58.
by lukaslalinsky 5mo ago
Exactly, and Zig 0.16 is explicitly a release with known issues, just count the number of TODOs in the std.Io namespace.
59.
by lukaslalinsky 5mo ago
I've been using DeepSeek v4 pro as an alternative to Claude models and for the first time I can see it as a real replacement. With the other Chinese models, I was missing something, but DeepSeek seems good enough for the kind of develo
60.
by lukaslalinsky 5mo ago
I'm really thankful for Zed. I claim it's a better VI successor than vim/neovim. The fact that it comes with batteries included is a huge win. Multi buffer is super useful. I'd prefer if it was NOT written like a game en

More ›