rigelbm

As a Kagi long time user, and a Linux die-hard, I don't get the obsession with having everything being open source.

This will sound overly critic (sorry before hand), but what do you want the source code for?

Do you read the source code of every open source applications you use? Do you compile all of them to make sure there are no shenanigans? If you do, congratulations, you are a member of a very niche group of people, that I'm not sure companies will be targeting.

I pay Kagi because I don't want to be the product (via no-privacy ad businesses). Not because I hate ads per-se (although I really dislike them), but because ads-funding incentives are contrary to make their products better. I like to know that Kagi's only incentive is to make their products better, so that I will keep paying for them.

I more than welcome that now expanding to browsers. I would get absolutely 0 value from it being open source, and so would most users I would guess, including probably you, even if you are fundamentally against closed source software, which you have the right to be of course.

Meanwhile Europe still doesn't have a cloud hyperscaler, so most of these €200B will end up in the coffers of Amazon, Google and Microsoft, the real winners.

Error handling is really not an issue that needs fixing in Golang. That being said, I wish Golang had an assert key word as a shortcut to "if cond { panic }". A lot of those "if err != nil" in the wild should really just be assertions.

You answered your own question. I don't want my great-grand-children to be the first to have a great Linux Desktop. Ideally, I would like to have it now. Unfortunately, as things go in capitalism, the easiest way to accelerate development of something is with money.

Sincerely,

The Gatekeeper.

Imagine you did have an idea, put a lot of effort building it, just so that some random person takes a dump on your work. It wouldn't be nice, would it?

Unnecessarily harsh and misses the point that this is a new VCS that brings valid new ideas to table. As with any new thing, if it's not for you, it's not for you.

SBArbeit, ignore this kind of comment. Not because it's not valid feedback, but because it isn't worth it.

The proposed ToC looks amazing, and I can't wait to get my hands in this book. One thing that seems omitted though, which can have significant impact in performance, is I/O. That would have been a nice add-on.

Critically missing from the text are the definitions of "external" vs "internal" bootstrapping. The author left us all guessing, and by the look of the comments here, no one has figured it out yet, me included.

> This is a solved problem.

Hosting a gigantic monorepo for 25K concurrent users is so far from a solved problem.

Nice product. It's always good to see more choices in the authz space.

I think Ory (Kratos) is a critical omission in the comparissons page, given the Ory suite seems to be one of the top alternatives currently for OSS authz/authn.

Hopefully the omission is fixed soon.

I stopped at "Good Programmers". Seriously though, it would have been perfectly fine to phrase it as "Exploring the correlation between Code Style and Competitive Programming Performance". Everyone knows that competitive programming has constraints (e.g. small time limit, throwaway one-off deliverable, no collaboration) that favours a style of coding that you wouldn't normally find, for example, on a business setting.

It's not clear whether this paper was accepted at the conference, but if it was, it is a testament to the low bar of the examining board. I like to follow the "if you don't have anything nice to say, don't say anything" mantra, but this paper deserves an exception.