HNHacker News
TopNewBestAskShowJobs

surajrmal

2,078 karma · joined October 31, 2017

submissionscomments
surajrmal··on VisualJJ – Jujutsu in Visual Studio Code
Even if you're not authoring changes as much, change management is likely still to be a very useful activity for a long while. Also note that not everyone is using AI today, and many that do only use it as glorified auto complete. It will take many more years for it's adoption to put us in a situation like your describing, why halt progress in the meantime? My personal productivity increased greatly by switching to jj, perhaps more than adding Gemini CLI to my workflow. I can more confidently work on several changes in parallel while waiting on things like code review. This was possible before but rebasing it and dealing with merge conflicts tended to limit me from doing it beyond a handful of commits. Now I can have 20+ outstanding commits (largely with no interdependencies) and not feel like I'm paying much management overhead while doing so. I can also get them reviewed in parallel more easily.
surajrmal··on VisualJJ – Jujutsu in Visual Studio Code
Even breaking changes in a library can cause massive pain. AI constantly wants to the use the old pattern it was trained on. Up until a few months ago it would always prefer using the 2021 edition of rust rather than 2024 for instance. Overall though I don't think this is insurmountable, but it definitely adds an impediment which will overall motivate people to do things non optimally for the foreseeable future. Luckily, not everyone is bound by AI today. I just write my own commits messages instead of letting the AI do it. jj is popular enough that I'm sure it'll learn how to use it in the next year (especially Gemini because Google is using jj internally and would probably train it on it as a result)
surajrmal··on VisualJJ – Jujutsu in Visual Studio Code
I love jjui, but I feel like it's also the reason I still use him over vscode. If you already use vscode, doesn't using a vscode extension make more sense?
surajrmal··on VisualJJ – Jujutsu in Visual Studio Code
While the primary maintainer is a Google employee, the majority of commits and committers are not. It's decidedly not a Google project.
surajrmal··on Apple Platform Security (Jan 2026) [pdf]
The way I look at it is that there is certain software that other entities aren't willing to let you run without assurances that it won't be tampered with. You don't necessarily have a right to be able to use that software if you cannot provide it suitable accomodations. It's your choice whether or not you want to run it or not, anything else is simply entitlement. This may seem annoying if it's your bank, but ultimately it's their choice to make. The current approach makes certain things painful, like trying to customize your os, but that's a problem worth solving rather than just ignoring. More software will start relying on this over time. At the end of the day trust is a hard problem to solve.
surajrmal··on Apple Platform Security (Jan 2026) [pdf]
You were not going to be able to use those apps anyways, so what does it matter to you? I, and I suspect many, agree with the purpose of attestation. The problems around it are strictly around establishing good ways to teach apps who they should trust, not around attestation itself. By putting your head in the sand, you'll never improve the situation.
surajrmal··on Rust at Scale: An Added Layer of Security for WhatsApp
If you build the standard library as a shared library it will be 4+MiB. The portion of that which you end up using is variable but there are ways to accomplish large usage without a great deal if code. I can get a 1.5 MiB binary down to 500KiB by dynamically linking the shared library. It's a net fun because I have many such binaries so it saves size in aggregate. It really does come down to what subset you use though.
surajrmal··on Rust at Scale: An Added Layer of Security for WhatsApp
I agree, but if you use more of the std library it will contribute more to the final image. I can write a 100 line rust file that ends up being 1MiB (even after lto) because I maximize as much code from the standard library as possible. This is not a knock on rust, but your statements can be a misleading as well. In practice most folks ignore the majority of the standard library so only a few hundred kib of std library end up in their binary.
surajrmal··on Rust at Scale: An Added Layer of Security for WhatsApp
PR makes it sound like it only benefits the company. It benefits the broader rust community as well. Where was it established that the article must provide you some technical knowledge to learn? I sure didn't go into reading it with the expectation it would.
surajrmal··on Lennart Poettering, Christian Brauner founded a new company
Sure, but devices that do that are not running a Linux distro off the shelf. They are creating something custom with the minimal amount of dependencies possible.
surajrmal··on Rust at Scale: An Added Layer of Security for WhatsApp
They didn't but keep in mind that the app is currently 170MiB. The standard library shouldn't have added more than a few hundred kilobytes. They already likely pay similar costs for c++, but it's more worthwhile as they have a lot more c++ code total.

Also note that if you statically link to the rust std library, lto will excise the majority of it anyways, no need to rebuild it.

surajrmal··on Lennart Poettering, Christian Brauner founded a new company
Do you have a way to tell the software to trust your kernel? If so, yes. Things like the web show how we can achieve distributed trust.
surajrmal··on Lennart Poettering, Christian Brauner founded a new company
I don't think this is generally true. If you are running Linux in your stack, your device probably is investing in 1GiB+ RAM and 2GiB+ of flash storage. systemd et al are not a problem at that point. Running a UI will end up being considerably more costly.
surajrmal··on Lennart Poettering, Christian Brauner founded a new company
I agree but it's difficult to argue against it. There is just so much you get for free by starting with a Linux distro as your base. Developing against alternatives is very expensive and developing something new is even more expensive. The best we can hope for is that someone with deep pockets invests in good alternatives that everyone can benefit from.
surajrmal··on Lennart Poettering, Christian Brauner founded a new company
Linux has been majority developed by large tech companies for the last 20+ years. If not for them, it would not be anywhere close to where it is today. You may not like this fact, but it's not really a new development nor something that can be described as infiltration. At the end of the day, maintaining software without being paid to do so is not generally sustainable.
surajrmal··on Rust at Scale: An Added Layer of Security for WhatsApp
The point of articles like this is to help build credibility for rust adoption. Rust is still not very widely adopted industry wide, and a lot of smaller players only use established technologies that bigger firms have shown works well. Rust is not inevitable, and articles like this are necessary for its future industry adoption.
surajrmal··on Rust at Scale: An Added Layer of Security for WhatsApp
The size is not fixed. It changes based on how much of the standard library you use. Dynamically linking the standard library is also a valid option in many cases.
surajrmal··on Porting 100k lines from TypeScript to Rust using Claude Code in a month
I recently did a c++ to rust port with Gemini and it was basically a straight line port like I wanted. Nearly 10k lines of code too. It needed to change a bit of structure to get it compiling, but that's only because rust found bugs at compile time. I attribute this success to the fact my team writes c++ stylistically close to what is idiomatic rust, and that generally the languages are quite similar. I will likely do another pass in the future to turn the callback driven async into async await syntax, but off the bat it largely avoided doing so when it would change code structure.
surajrmal··on RIP Low-Code 2014-2025
Working together to make something is actually fun though. Seeing something you helped build be useful for others can be fulfilling. I'm not suggesting you should only live to work, but there are aspects of work that make life more enjoyable. I dread becoming a full-time consumer (aka retirement).
surajrmal··on The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
Binary comparability extends beyond the vide that runs in your process. These days a lot of functionality occurs by way of IPC which has a variety of wire protocols depending on the interface. For instance there is dbus, Wayland protocols, varlink, etc. Both the wire protocol, and the APIs built on top need to retain backwards comparability to ensure Binary compatibility. Otherwise you're not going to be able to run on various different Linux based platforms arbitrarily. And unlike the kernel, these userspace surfaces do not take backwards compatibility nearly as important. It's also much more difficult to target a subset of these APIs that are available on systems that are only 5 years old. I would argue API endpoints on the web have less risk here (although those break all the time as well)
surajrmal··on The browser is the sandbox
I'm not sure new windows APIs use COM as people remember it. Nowadays they are written against WinRT, which is arguably an evolution of COM.
surajrmal··on The browser is the sandbox
The Linux API surface is massive. And the fact it's written on C leaves lots of room for vulnerabilities. I don't think you need to reach for a VM, but without a slimmer kernel interface, it's difficult to trust the kernel to actually uphold its required duties in the face of adversaries. This is why folks push heavily for microkernels. Chrome needs to work incredibly hard to provide reliable sandboxing as a result.
surajrmal··on The browser is the sandbox
Android sandboxing works in spite of the underlying security model, not because of it. It's also really selinux that does a lot of heavy lifting.
surajrmal··on Gathering Linux Syscall Numbers in a C Table
Fun fact, those numbers are also not consistent per architecture. Any similarly named syscalls can have very different abi on different architectures.
surajrmal··on Porsche sold more electrified cars in Europe in 2025 than pure gas-powered cars
It definitely worked in the past with Japanese cars.
surajrmal··on Porsche sold more electrified cars in Europe in 2025 than pure gas-powered cars
EVs are sold as a luxury product in the US. ICE cars are familiar, convenient (no need to figure out how to install a home charger), and otter cheaper (lower initial cost, service is cheaper, value maintains for much longer, etc). I bought electric, but I recognize it's a privilege to be able to do so.

If competitively priced EVs hit the market, consumers would buy them in much bigger numbers. Manufacturers want to use EVs as a way to redefine themselves and make more money and seemingly the industry is colluding to keep them premium with a shorter shelf life.

surajrmal··on Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss
Since when does an electron app count as native? You can install the webapp and that seems to feel basically equivalent.
surajrmal··on Singularity Rootkit: SELinux bypass and netlink filter (ss/conntrack hidden)
It doesn't.
surajrmal··on OpenBSD-current now runs as guest under Apple Hypervisor
Try asking your favorite llm. They will even guide you with a small curriculum.
surajrmal··on OpenBSD-current now runs as guest under Apple Hypervisor
This is the set of assignments they do at the university of Illinois (a top 10 computer engineering school): https://courses.grainger.illinois.edu/ece391/fa2025/assignme...

It looks roughly the same as when I took 15 years ago, except they switched to riscv from x86. Honestly, what you're describing sounds too difficult for a first assignment. Implementing irq handlers or syscalls on an existing codebase is far more realistic, plausible, and useful.

← PreviousPage 10 of 34Next →