You can fix you code 10 times you will fix it.

I also use Haiku daily and it's OK. One app is trading simulation algorithm in TypeScript (it implemented bayesian optimisation for me, optimised algorithm to use worker threads). Another one is CRUD app (NextJS, now switched to Vue).

Are you saying Haiku is better than Sonnet for some coding use? I've used Sonnet 4.5 for python and basic web development (pure JS, CCS & HTML) and had assumed Haiku wouldn't be very good for coding.

I'm saying Haiku isn't that bad, it's good enough for my needs, and it's the cheapest one. Maybe it's because I'm giving it small, well defined tasks.

I'm using Sonnet with a free account.

Doesn't (honest question) the operating system kernel prevent data races in memory accesses at the level of system calls like brk? I wonder at what level the operating system handles such things?

I mean, aren't system calls thread-safe?

As a general rule, not all system calls are thread safe.

What do you think, there are milions of people or companies running NetBSD on 486 to protect the planet from e-waste? How many times have you replaced your phone with a newer model in the last 10 years?

> How many times have you replaced your phone with a newer model in the last 10 years

Once, after accident.

Maybe in the future, if the language has very good AI support, security guarantees of the language won't be as important, as it (ai) will find potential bugs well enough. This may be the case with Zig, as the language is simple and consistent, and the lack of macros will make it easier for LLMs to understand the code.

AI is not remotely capable enough to be trusted with that. Perhaps in the future it will be, but I'm not betting on it with the lack of improvement we have seen thus far.

For me it is natural that since the desktop environment is the most important part of the desktop operating system, it should have its own distribution.

For some background, it is now a single guy paid by Microsoft to work on implementing async direct I/O for PostgreSQL (github.com/anarazel)

Maybe such operators for basic linear algebra (for arrays of numbers) should be just built into the language instead of overloading operations. I'm not sure if such a proposal doesn't already exists.

There is a specialized `@Vector` builtin for SIMD operations like this.

let name = $state('blastonico')

I know some people didn't like this change. I think it works well to help make it clear and obvious to reactive vs non reaction changes.