Readit News logoReadit News
gorjusborg commented on Why we built Lightpanda in Zig   lightpanda.io/blog/posts/... · Posted by u/ashvardanian
azaras · 9 days ago
What are you developing in?
gorjusborg · 9 days ago
Depends on the problem at hand.

Zig where I used to use C/Rust (but admittedly I spent the least time here).

Go where I used to use Java.

Bun/Node for typescript/javascript, where each is appropriate, but I favor Bun for standalone application programming and local scripting.

gorjusborg commented on Why we built Lightpanda in Zig   lightpanda.io/blog/posts/... · Posted by u/ashvardanian
gorjusborg · 9 days ago
Years ago, when I initially picked up Rust, I loved it. It does a lot of things right. At the same time, though, I knew there was a possibility of it going wrong in two opposite directions:

1. Developers balked at being required to take on the cognitive load required to allow GC-less memory management

2. Developers wore their ability to take on that cognitive load as a badge of honor, despite it not being in their best interest

I eventually came to the decision to stop developing in Rust, despite its popularity. It is really cool that its creators pulled it off. It was quite an achievement, given how different it was when it came out. I think that if I had to implement a critical library I would consider using Rust for it, but as a general programming language I want something that allows me to focus my mental facilities on the complexities of the actual problem domain, and I felt that it was too often too difficult to do that with Rust.

gorjusborg commented on Why we built Lightpanda in Zig   lightpanda.io/blog/posts/... · Posted by u/ashvardanian
websiteapi · 10 days ago
has there ever been a project that became popular and/or successful because of its programming language? does it really matter to the end user what language it's in if it works well?
gorjusborg · 10 days ago
There's a big part of me that agrees with your implied conclusion, that it shouldn't matter.

On the other hand, I've found that core decisions like language ecosystem choice can be a good leading indicator of other seemingly unrelated decisions.

When I see someone choose a tool that I think is extremely well suited for a purpose, it makes me curious to see what else we agree on.

The Oven team, the ones who created the Bun runtime, is a good example for me. I think Zig is probably the best compromise out there right now, for my sensibilities. The Oven folks, who chose to use Zig to implement Bun, _also_ made a lot of product decisions I really agree with.

gorjusborg commented on UniFi 5G   blog.ui.com/article/intro... · Posted by u/janandonly
a3w · 10 days ago
Ah, this is a Ubiquity product. That explains it.

Why did AVM or Netgear Orbi not get this treatment for "works", though?

gorjusborg · 10 days ago
No experience with AVM, but Ubiquiti gear is at least a class above Netgear equipment.
gorjusborg commented on Human hair grows through 'pulling' not pushing, study shows   phys.org/news/2025-12-hum... · Posted by u/pseudolus
adrr · 11 days ago
How did this explain in-grown hairs?
gorjusborg · 11 days ago
Pulling doesn't have to happen at the surface?
gorjusborg commented on Zig quits GitHub, says Microsoft's AI obsession has ruined the service   theregister.com/2025/12/0... · Posted by u/Brajeshwar
kakwa_ · 12 days ago
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?

gorjusborg · 12 days ago
I don't enough experience w/ Buildbot or Travis to comment on those, but Jenkins?

I get that it got the job done and was standard at one point, but every single Jenkins instance I've seen in the wild is a steaming pile of ... unpatched, unloved, liability. I've come to understand that it isn't necessarily Jenkins at fault, it's teams 'running' their own infrastructure as an afterthought, coupled with the risk of borking the setup at the 'wrong time', which is always. From my experience this pattern seems nearly universal.

Github actions definitely has its warts and missing features, but I'll take managed build services over Jenkins every time.

gorjusborg commented on Anthropic acquires Bun   bun.com/blog/bun-joins-an... · Posted by u/ryanvogel
btown · 12 days ago
Yea - if you want a paranoidly-sandboxed, instant-start, high-concurrency environment, not just on beefy servers but on resource-constrained/client devices as well, you need experts in V8 integration shenanigans.

Cloudflare Workers had Kenton Varda, who had been looking at lightweight serverless architecture at Sandstorm years ago. Anthropic needs this too, for all the reasons above. Makes all the sense in the world.

gorjusborg · 12 days ago
Bun isn't based on V8, it's JavaScriptCore, but your point still stands.
gorjusborg commented on Installing Java in 2025, and Version Managers   blog.hakanserce.com/post/... · Posted by u/hakanserce
genzer · 17 days ago
Ever since I found `asdf`, I threw away jenv, nvm, fmn and rvm.
gorjusborg · 16 days ago
Same here, having a different version manager per language ecosystem got tiring due to the small differences.

I used asdf for a while but moved to mise-en-place (mise). Same reasons though, one tool manager for all the tools.

gorjusborg commented on CornHub   cornhub.website/... · Posted by u/andy99
gorjusborg · 23 days ago
I was hoping to see some corn smut.
gorjusborg commented on Git 3.0 Defaults to "main" Branch Instead of "master   phoronix.com/news/Git-2.5... · Posted by u/birdculture
ripbozo · 24 days ago
I don't understand why there was such manufactured outrage over master branches, but not master recordings.
gorjusborg · 23 days ago
I think the idea that there was outrage about branch naming is manufactured.

It was more that the naming was potentially offensive and cost next to nothing to change.

The people griping about it are the ones outraged.

u/gorjusborg

KarmaCake day2811January 28, 2016View Original