veber-alex

Twenty years ago, Gentoo taught me Linux.

A friend and I wanted to play around with Linux, so we installed Mandrake[1] Linux on a school PC. We didn't know what we were doing, and the GUI (I think it was KDE3?) abstracted too much. It was also very unstable.

I don't remember how I got to know about Gentoo, but I then proceeded to install and reinstall Gentoo on my home PC (Athlon 64) about 20 times, and this was when you had to start from stage1, so you had to do a full bootstrap, kernel, and system compile; no binaries and no shortcuts. The scrolling gcc output on my screen was the coolest thing ever.

The Gentoo handbook was amazing. It taught you exactly how Linux works and how to install every component of the system.

After a while, I began contributing to the distro and even became a developer for a few months but had to quit due to real life.

I don't follow Gentoo today, but if it's still valuable as a tool to learn Linux, I can highly recommend it.

[1]: https://en.wikipedia.org/wiki/Mandriva_Linux

'a

10 years? are they going to contribute 1 line of a code a day or something?

I am pretty sure that developers motivated to contribute code benefits end users plenty.

I don't know why you went with hardware.

Most people don't want old software because they don't want old software.

They want latest features, fixes and performance improvements.

It's already supported in vLLM, SGLang and MLX.

Neither Bun nor Deno have any killer features.

Sure, they have some nice stuff that should also be added in Node, but nothing compelling enough to deal with ecosystem change and breakage.

Fake site.

You login with your credentials, the attacker logins to the real site.

You get an SMS with a one time code from the real site and input it to the fake site.

The attacker takes the code andc finishes the login to the real site.

Hmm, maybe npm needs to do the same thing the iPhone does now.

If you change your key you can't use it for like 12 hours or something?

AI based code review with escalation to a human

You are right. I don't understand.

How can any software developer work when they need to open and close 4 files per minute? I have never met or heard of anyone working like this.

If you think "build by atom team" and "not electron" are any kind of serious advantage for any peace of software than your are the one who lacks knowledge about software development.

To continue with your metaphor what he did is basically say "My salary is great because I make more than that other guy". That doesn't mean anything.

The comparison to Rust is meaningless.

Each project has different demands and requirements from their infrastructure.

For example, Rust compiles all open-source crates on a regular basis to test for regressions.

You can't just point to Rust and say, "Look at that guy."

If you want to justify the expenses of your infrastructure you need to explain where the money goes.

Strange.

I just opened the same project in Cursor and Zed and started typing around, and I can't tell any difference. I am usually very sensitive to this stuff; for example, I can detect when my Mac drops below 20% battery because ProMotion is disabled and the screen refresh rate drops to 60Hz.

I agree with you.

I tried Zed several times and I just don't see the point.

The main issues with VScode over something like the Jetbrains IDEs is that language servers are just not as powerful or as integrated to the IDE as the Jetbrains solution can be and Zed does nothing to solve it.

I don't think it being a native app offers much added value.

So...nothing.

VScode starts very quickly for an electron app. MS did a great job there.

Memory usage of the IDE doesn't matter much when your language servers can eat 10s of gigs of RAM.

oh 100%.

I am just annoyed that every time Zig developers publish some articles or even make some comments here on HN they always contain something negative about someone else.

Like even in this thread when someone said that Zig wastes too much money on infrastructure the first thing Andrew Kelly does is to show that Rust spends much more.

1000x seems low to me.

Rust is used in production by many companies out there.

crater runs are constantly running [1]. Every time there is a PR with any danger of causing a regression a crater run can be requested.

[1]: https://crater.rust-lang.org/

-1 time because it would have never have happened without AI

You are right, but it doesn't mean we can't complain about it :)

As a side note, I hate the `as` cast in Rust. It's so brittle and dangerous it doesn't even feel like a part of the language. It's like a JavaScript developer snuck in and added it without anyone noticing. I hope they get rid of it in an edition.

Knowing how the Zig developers operate it's 100% not a bug and it's exactly the case you described.

Why does the compiler decay the FileError and the global error set to an integer? If they were unique types, the if statement would not have compiled.

But why?

If I just need to check for 1 specific error and do something why do I need a switch?

In Rust you have both "match" (like switch) and "if let" which just pattern matches one variant but both are properly checked by the compiler to have only valid values.

I don't use mypy so I can't comment on it but at least from what I have seen pyright is deterministic in it's output and get output json.

Regarding the ~80k errors. Yeah, nothing to do here besides slowly grinding away and adding type annotations and fixes until it's resolved.

For the code example pyright gives some hint towards variance but yes it can be confusing.

https://pyright-play.net/?pyrightVersion=1.1.403&code=GYJw9g...

Yeah, I had to do a double take while reading the article because I missed the error completely while looking at the code.

The compiler doesn't know anything about threads.

The compiler knows the Future doesn't implement the Send trait because MutexGuard is not Send and it crosses await points.

Then, tokio the aysnc runtime requires that futures that it runs are Send because it can move them to another thread.

This is how Rust safety works. The internals of std, tokio and other low level libraries are unsafe but they expose interfaces that are impossible to misuse.

I find the Zig example to be shocking.

It's just so brittle. How can anyone think this is a good idea?

Here is some actual useful advice:

Use a type checker! Pyright can get you like 80% of Rust's type safety.