farresito

Noctalia will soon release v5, which is a complete rewrite in C++, which makes it even more appealing if you care about the performance.

I would hope most people do. It's in pretty much every high school curriculum, isn't it?

> I'm wondering if this is something that hits new developers faster than more experienced ones?

Almost certainly, at least according to Ebbinghaus' forgetting curve.

> In some sense, the visionaries in this space are not thinking big enough. I want visions of mobility with a totally different size, look, speed, etc. autonomous Golf carts? tuktuks? A moving autonomous bicycle carrier? etc

If anything, it's the opposite: most people in this space (Elon, George Hotz, Demis, etc.) have been saying for a very long time that autonomous driving is just the first step, and that their objective is to build world models.

I'm not talking specifically about SpaceX, although historically the cost of their rockets have been much lower than NASA. I'm being much more general. The public sector doesn't have the same incentives that private companies have, whether it's rockets or any other technology. It's sad, but it's the truth.

NASA just splurges money. The private sector is far better when it comes to money.

This is the first time I read that someone uses an acronym for ragebait purposes. The acronym "RL" is very well known. Dwarkesh's podcast is mostly AI related, so it's not a surprise that he will freely use acronyms. I think your take is very cynical.

According to the FSRS author [1], it will adapt to two buttons.

[1] https://www.reddit.com/r/Anki/comments/16t2lva/comment/k2cor...

What was your experience like in school and university? Have you come across people who you thought were at a similar level intelectually as you?

Do you have any other family members with very high IQs?

I disagree with you. I think the impact of AI on society in the long term is going to be massive, and such investments are necessary. If we look at the past century, technology has had (in my opinion) and incredibly positive impact on society. You have to invest in the future.

As someone who is interested in getting more serious with Rust, could you explain the essence of how you should always approach organizing code in Rust as to minimize refactors as the code grows?

That's interesting. For me it takes 30 minutes, give or take, to start to feel sleepy, and I'm also a night owl :-)

Not OP, but I've been using melatonin every night, no exception, and it's been very helpful. I use a much lower dose (between 0.3mg and 0.5mg), and it's worked completely fine, so I would suggest that you start very low and only increase if you really need it.

Once we have AI-based language servers, which will, at some point in the future, be able to track entire repositories, I think maintaining projects will actually be far easier than right now.

> like what's it doing differently, is it just a matter of more training data or is there something more going on

Well, the model doesn't start with "GPT", so maybe they have come up with something better.

Damn, that looks like a big jump.

It's common (at least nowadays, in my experience) in English to omit the verb or part of it in headlines.

Entrust makes a ton of revenue from hardware-related products (for example, printing ID cards), so it is far from the end.

Could you expand a little bit on what the "robust requirements engineering process" was like on that one team?

I think that's what they are trying to achieve with Mojo.

What does the tech stack look like?

This is the answer. I have only read bits from this book, but it seems very good for what OP is looking for.

> Rust is not a user feature, it's an implementation detail

Sure, but keep in mind that in the case of open source software plenty of people will choose software written in their favorite language so that they can potentially contribute to it. Or simply because they feel more connected to something that is written in their favorite language. So I don't think it's completely irrelevant.

IMO, Go is a mediocre language with great tooling and a great company behind it, and it turns out ultimately if you don't have the latter, the former is irrelevant.

Writing good code doesn't necessarily take more effort than writing bad code; in fact, my experience tells me otherwise. Teams that write good code iterate faster.

This mentality is how you end up inheriting terrible codebases.

> The better way is to design it from the ground up with a bunch of instrumentation that keeps all of your invariants under close observation and that stops the moment anything is not according to your assumptions.

Any personal "war stories" you are willing to share explaining how you went about designing such a system? :-) Or any presentation of someone who did that?

> a couple hours is a lot

That's a worst case. Most of the time I don't touch anything.

> the problem is that I could never get it to look exactly like I wanted. There were always some minor GUI bugs that irked me to no end. Add to that, there were some weird inconsistencies because for a long time there were both GTK2 and GTK3 programs running at the same time and they didn't look quite normal.

I think that is the big issue with environments that allow for endless customization. People look for perfection, and when you have too much free time it's tempting.

That's a worst case. The vast majority of the time I don't touch anything. I was just trying to point out that once you have a stable config that works out for you, there is no need to constantly change it.