HNHacker News
TopNewBestAskShowJobs

kakwa_

1,465 karma · joined August 10, 2015

submissionscomments
kakwa_··on Just Use Go
After having way too strong opinions about this, and even if Go is my go to language, I've stopped caring for this kind of statements.

In the end, the language doesn't really matter and extremely rarely is the bottleneck.

Python, Java, Go, C#, PHP, Node, Ruby or Scala, for backend stuff, all these languages can do the work 99% of the time. They all have well developed ecosystems, and are sufficiently mainstream to easily find developers.

In the end, these languages are just variants of the same tool, and I find more interesting to just pick one and build something with it, rather than bickering endlessly about which one is better.

kakwa_··on Red Squares – GitHub outages as contributions
Well, it depends.

Managing and coordinating a bloated organization always has a cost and an overhead, from communication issues to technical inefficiencies.

And I also doubt the frontend/backend divide is so clear. I would bet quite a few developers are working on both.

kakwa_··on BYD overtakes Tesla and Kia as the best-selling EV brand in key overseas markets
It's not always the case, for example Japan has very low immigration.

And there is also the demographic disparity at play here.

The US is attracting migrants mainly from Latin America, that's a population basin of 650M people, roughly 2 times the US population.

In China's case, the surrounding countries susceptible to provide migrants is what? a third of China's population?

I'm not knowledgeable nearly enough about the area but I also feel there are also significant cultural and historical elements limiting large scale immigration (for example, the complex Sino-Vietnamese relations).

kakwa_··on Permacomputing Principles
Are these principles really about sustainability?

It seems to be far more geared toward promoting some sort of misplaced post-collapse resiliency.

In other words: solving some hypothetical issues on the other side of a catastrophe for a world we don't know anything about, and almost ignoring present and actual problems.

kakwa_··on When everyone has AI and the company still learns nothing
Pretty standard in highly regulated fields like aerospace, finance/banking or industry.

Sometimes for good reasons, like thorough validation need or operational constraints like spaced-out maintenance windows.

Sometimes for bad reasons, like a complete absence of unit tests and very old and brittle code bases requiring a lot of manual QA and several iterations for a version to be in a releasable state.

kakwa_··on YouTube, your RSS feeds are broken
For the home page, I would recommend the "UnTrap for Youtube" browser extension.
kakwa_··on Sierra Raises $950M at $15B Valuation
Your toaster is well... a toaster.

And even something as simple toaster might need some customer support. These things do fail quite often, sometimes dangerously.

Increase complexity even a little; or worse, deal with a service (phone, internet, subscriptions, etc) and you will need this safety net.

Nothing is 100% reliable in this world.

kakwa_··on A report on burnout in open source software communities (2025) [pdf]
I feel this report is missing something when it puts all OSS developers into the same bucket, and somewhat fails to define what an OSS developer actually is.

There is tons of variability depending on many factors like the project complexity, usage or visibility, or the size of the community around it or the audience/userbase.

Technically, I'm an OSS developer, some of my stuff is even packaged in Debian, with a whopping 17 installs according to the package popularity contest... And I cannot say this has burnt me. I get a few bugs reports and PRs here and there and that's all. And I feel most OSS work ends-up in this category, with this report painting a far too bleak picture discouraging people from contributing.

But some projects do become popular or critical pieces of infrastructure, or both. The hobby structure is indeed completely inadequate in such cases. Such projects should not be only held by a solo or a pair of developers coding at night and doing everything.

maybe, they should be offered the possibility to make it their day job, or to have some help from developers doing this as their day job?

kakwa_··on Good developers learn to program. Most courses teach a language
Honest question, is leetcode tests an actual failure from the recruiting company perspective?

Sure, it means that from time to time you will reject people like the Homebrew creator. And it also means the recruiting process now sucks for the applicant.

But in a context where it's extremely tricky to evaluate an applicant during the short span of an interview, it seems honestly like the least "arbitrary/trusting your vibes" recruiting method we have now which could be deployed at a large scale.

At least, you are getting people you know had the ability to remember this stuff, and also were willing to put in the effort to learn it.

kakwa_··on Functional programmers need to take a look at Zig
On the other hand, most pieces of software in this world are kind of mediocre code written by unmotivated employees within tight timelines.

In such context, I think Go might be a better or at least, more realistic, compromise in most cases.

kakwa_··on We need a federation of forges
I think the gain sits in the middle: if the giant server starts to get iffy (moderation, content, policy, technical issues), people can leave it somewhat easily and form or grow another decently sized server which will have enough reputation from day one.

We already have other decently sized GH alternatives such as Gitlab, Codeberg and various OSS forge instances (freedesktop, Fedora, Debian, etc) which could be federated and become a safe harbor if we were able to maintained project visibility and discoverability.

kakwa_··on GTFOBins
Concrete example:

A few years back, our support team needed to do some network capture with tcpdump. The quick and natural way to allow that was to add a sudo rule for it, with opened arguments (I know it's a bit risky, but tcp port and nic could change).

Looks good enough? Well no...

With tcpdump, you can specify a compress command with the "-z" option. But nothing prevents you from running a "special" compress command and completely take over the server:

> sudo tcpdump -i any -z '/home/despicable_me/evil_cmd.sh' -w /tmp/dontcare.pcap -G 1 -Z root

This seems trivial, but that the kind of stuff which are really easy to miss. Even if these days, security layers like apparmor mitigate this risk (causing a few headaches along the way), it's still relatively easy to mess it up.

kakwa_··on Asahi Linux Progress Linux 7.0
I feel like more money would not have helped that much. Maybe it would have enabled a few of the devs to work on it full time, but I doubt it would have brought more people into the project.

I would indeed love the EU to step in but not in the way you are probably thinking.

I would rather see such effort being made unnecessary through a law forcing the manufacturers to provide enough information/specification or even code for alternative/after-market OSes to be viable on the devices they produced.

And also, if possible, mandate a degree of standardization (looking at you Android phones and ARM SBCs) enabling commonality of efforts when supporting a device class.

kakwa_··on GitHub is having issues now
Syncing the code is the easy and trivial part and your CI job is only solving that. And in my opinion, it's not even that necessary for most projects.

The difficult part is all what's around the code:

* the tickets/PR (including the closed ones)

* the links referencing the project

* the CI setup

* for large projects, the committers permission setup

* if applicable, the push/commit/branch rules

All that will be deeply annoying to migrate on a per project basis, or might get lost.

But that's not even the worst on my opinion. Losing the go-to platform for finding software is (fediverse for software when?).

kakwa_··on Asahi Linux Progress Linux 7.0
I would have been happy if all that happened like 3 years ago.

Now, it's 5 years in, the Asahi effort is losing momentum. Core developers are going on to do other things, significant chunks (3922 commits) are still not merged upstream and no major distribution has an official build.

Sorry, but in my opinion, the project is at risk of becoming a dead and unmaintained branch.

Don't get me wrong, the Asahi team did an incredible job on this bloody difficult endeavor, but now is time to properly merge it and not let it go to waste.

kakwa_··on Asahi Linux Progress Linux 7.0
Well, after a while, the effort of maintaining and improving M-series kernel support should be directly be done by kernel maintainers, not within a fork with periodic merges (maybe some Asahi folks should become kernel maintainers).

Doing so would enabled mainstream distributions to provide maintainable M-series builds, with all that entails in terms of stability, enabling choice, maintenance or security fixes.

The whole fork + dedicated distribution made sense at the start of the project since it provided a playground for quickly iterating and experimenting (which is a no-no to do directly in the mainline kernel or in a major distribution).

But Asahi is still the only Linux on Silicon option after all these years, which is a bit worrisome. Asahi should have been a cool but temporary initiative.

At some point, the project will lose momentum and for its accomplishments to last, it should be merged into the general effort, i.e. drivers maintained directly in the Linux kernel, and the userland stuff made to be easily packaged and shipped by mainstream distributions.

kakwa_··on Asahi Linux Progress Linux 7.0
While I absolutely love the technical write-up from the Asahi team, and being absolutely impressed by their accomplishment, to the risk of being an overly negative contrarian, I remain a bit skeptical.

I'm concerned that after all these years, it's still a separate project and not an effort sustained directly within the kernel mainline and mainstream distributions like Ubuntu, Debian or Fedora.

These kinds of reverse engineering projects are extremely challenging. With skills & field knowledge, it's "easy" to get to "80%" and have something useful for you and the most dedicated users. But reaching the "95%" required for a polished & general public ready experience needs nearly as much effort, often on tedious and time consuming tidbits.

kakwa_··on I don't want your PRs anymore
> I usually find it easier to take their branch, do all of that work myself (attributing authorship to commits whenever appropriate), push it to the master branch and close the PR than puppeteering someone halfway across the globe through GitHub comments into doing all of that for me.

The PR system is great for reviewing changes within a dev team.

But, indeed, when its an external contribution, it kind of falls apart. It's unrealistic to expect from an external contributor, often a one time one, to know the ins and outs of a project (code standards, naming tastes, documentation, tests, ...)

I really like your workflow, and often did something similar in my projects (or merge in main, with subsequent fixes/realignments).

But I'm wondering if it could be smoothed out and normalized by Github/Gitlab/Forgeo, or maybe at the version control software level.

kakwa_··on US Bill Mandates On-Device Age Verification
That one is murky.

I would argue it falls more on a case like the Linux distributions one and the guy in South America is responsible.

Google, in my opinion, can be held accountable for Android because they deeply control the ecosystem (App Store, APIs, Services) and de-facto prevents significant modifications, specially when they deal with Android security framework & mechanisms (if you modify this stuff too deeply, the Apps could break).

But if a distribution cuts ties with that, then it's the author or the entity behind it who is responsible, and if it's deemed illegal, downloading his ROM should be blocked in the US.

In truth, if I were a defender of this law (which I'm not), I would not worry too much about it. This text is here to force mainstream OS vendors to provide an API for age verification. The micro-subset of people flashing custom roms onto their phone or recompiling a piece of OSS software with some flag disabled is in practice so small that it's not really an issue.

While I do agree that this law could be better written, properly categorizing in it the cases of MS, Apple, Google and maybe entities like Linux Distribution honestly is kind of a nightmare.

kakwa_··on US Bill Mandates On-Device Age Verification
IMHO, the law tries to target the last entity which has practical control over the OS design and implementation aka the final developer/integrator.

For example in the Linux world, it's the distributions.

Where it gets murky is with Android (and to a lesser extent Windows).

IMHO, the entities which should be responsible are Google and Microsoft.

But since vendors, specially in the Android world, can heavily tweak the OS, there is a case that it's more the device manufacturers like Samsung which are responsible.

The relevant interpretation in practice will usually happen naturally, and the most ambiguous stuff will be set by jurisprudence if necessary.

kakwa_··on We've raised $17M to build what comes after Git
More like an idea decently likely to be resold for more.

Good ideas are a decent subset, but you could also have a bit of "Greater Fool Theory" compliant ideas.

kakwa_··on Show HN: I built a Cargo-like build tool for C/C++
While I do get why CMake is a scripted build system, I cannot help but notice that other languages don't need it.

In Rust, you have Cargo.toml, in go, it's a rather simple go.mod.

And even in embedded C, you have platformio which manages to make due with a few .ini files.

I would honestly love to see the cpp folks actually standardizing a proper build system and dependency manager.

Today, just building a simple QT app is usually a daunting task, and other compiled ecosystems show us it doesn't have to be.

kakwa_··on Prediction: Microsoft will eventually ship a Windows-themed Linux distro
The graphic stack in NT is done in a microkernel fashion, it runs in kernel space but doesn't (generally) crash the whole OS in case of bugs.

There are a few interviews of Dave Cutler (NT's architect) around where he explains this far better than I am here.

Overall, you have classic needs and if you don't care about OSS (either for auditability, for customizability or for philosophical choice about open source), it's a workable option with its strength and weaknesses, just like the Linux kernel.

kakwa_··on When hardware goes end-of-life, companies need to open-source the software
That's not enough by a long shot.

There are already plenty of devices, from old phones to vacuum robots, where we have that or near enough.

Technically, we know how we could maintain/re-flash these devices.

Yet, we don't. Why? lack of standardization, specially the boot process in non-x86 platforms.

Having to maintain per device images is not really practical at scale.

kakwa_··on My Home Fibre Network Disintegrated
Well, not mass produced enough.

Common mass produced products manufacturers have incentives to not mess-up too badly: recalls or warranties on such scales are a nightmare.

With military contracts, its a paid maintenance opportunity.

kakwa_··on Debian's Git Transition
Just a few bits about that.

I would recommend looking into the chroot based build tools like pbuilder (.deb) and mock (.rpm).

It greatly simplifies the local setup, including targeting different distributions or even architectures (<3 binfmt).

But I tend to agree, these tools are not easy to remember, specially for the occasional use. And packaging a complex software can be a pain if you fall down the dependency rabbit hole while trying to honor distros' rules.

That's why I ended-up spending quite a bit of time tweaking this set of ugly Makefifes: https://kakwa.github.io/pakste/ and why I often relax things allowing network access during build and the bundling of dependencies, specially for Rust, Go or Node projects.

kakwa_··on GitHub Actions has a package manager, and it might be the worst
Fragile against upgrades, tons of unmaintained plugins, admin panel UX is a mess where you struggle to find the stuff your are looking for, half backed transition to nicer UI (Blue Ocean) that has been ongoing for years, too many ways to setup jobs and integrates with repos, poor resource management (disk space, CPU, RAM), sketchy security patterns inadvertently encouraged.

This stuff is a nightmare to manage, and with large code bases/products, you need a dedicated "devops" just to babysit the thing and avoid it becoming a liability for your devs.

I'm actually looking forward our migration to GHEC from on-prem just because Github Actions, as shitty as they are, are far less of an headache than Jenkins.

kakwa_··on Zig quits GitHub, says Microsoft's AI obsession has ruined the service
Maybe I have low standards given I've never touched what gitlab or CircleCi have to offer, but compared to my past experiences with Buildbot, Jenkins and Travis, it's miles ahead of these in my opinion.

Am I missing a truly better alternative or CI systems simply are all kind of a pita?

kakwa_··on The Mozilla Cycle, Part III: Mozilla Dies in Ignominy
Sometimes, I'm wondering if Mozilla did not get too much money.

With an order of magnitude less money, I think they would have been more focused on improving Firefox rather than trying to diversify with projects like Firefox OS, VPN services or AI.

Even today, given their ~$1.5B in the bank, at the cost of a really painful downsizing, the interests alone could probably pay for a Firefox development focused on standard adherence, performance, quality and privacy.

Mozilla is not a company trying to reinvent itself to survive. If it becomes irrelevant because the Browser becomes irrelevant in the future, that's fine in my book, the organization would have fulfill its mission.

But it is sad to see it become irrelevant because of mismanagement and lack of focus.

kakwa_··on What Killed Perl?
Perl was pretty much first in the wave of interpreted languages from the late 80ies and 90ies. It set the bar on what to expect from such ecosystems.

But being the first meant it got some oddities and the abstractions are not quite right imho.

A bit too Shell-esque, specially for arguments passing and the memory abstractions are a bit too leaky regarding memory management (reference management fills too C-esque for an interpreted language, and the whole $ % @ & dance is really confusing for an occasional and bad Perl dev like me). The "10 ways to do it" also hurts it. It lead to a lack of consistency & almost per developer coding coding styles. The meme was Perl is a "write only language".

But I would still be grateful of what it brought and how influential it was (I jock from time to time how Ruby is kind of the "true" Perl 6, it even has flip flops!).

In truth, these days, I feel the whole "interpreted languages" class is on the decline, at least on the server. There are a lot of really great native languages that have come up within the last few years, enabled in large part by LLVM. And this trend doesn't seem over yet.

Languages like Rust, Swift, Go, Zig or Odin are making the value proposition of interpreted languages (lower perf but faster iterations) less compelling by being convenient enough while retaining performance. In short, we can now "have the cake and eat it too".

But the millions of lines in production are also not going awywhere anytime soon. I bet even Perl will still be around somewhere (distro tooling, glue scripts, build infra, etc...) when I retire.

Anyway, thank you Perl, thank you Larry Wall, love your quotes.

https://en.wikiquote.org/wiki/Larry_Wall

← PreviousPage 2 of 19Next →