hawk_

Yes but try putting that on your CV.

Ok a related note, how does it compare to SeaStar?

That's totally something a bot would say to blend in ;-)

May be the ones that are dead are from poor imitation of more successful bots that are operating in our midst whose comments aren't dead?

For those discussions with the LLM do you just use Gemini chat or chat GPT etc... i.e. the chat interface?

For sure no two groups want the same subset but is there no "standard way" to opt in / out in the ecosystem? It's strange that there are large orgs like Google enforcing style guidelines but manual code reviews are required to enforce it. (or may be my understanding of that's enforced is wrong)

Is there a way to pass compiler switches to disable specific C++ features? Or other static analysis tools that break the build upon using prohibited features?

I can't imagine those examples you picked implemented in Erlang performing anywhere close to the Zig/C++ ones. So the "ad-hoc subset" there is by design.

Is Lyme disease much of a problem in Europe though?

Deceleration requirements are going to be harder than acceleration, one would think so how would you apply full brakes with the same motor?

When should one use D2 vs graphviz?

> if a Contributor Distributes

Doesn't this only apply to contributors and dev users?

Yep the JVM structured concurrency implementation is amazing. One thing I got wondering especially when reading this post on HN though is if stackless coroutines could (have) fit the JVM in some way to get even better performance for those who may care.

> If this was done the classical C way, you would always have to stack-save a number of registers

I see, so you're saying that GCC can be coaxed into gathering only the relevant registers to stack and unstack not blindly do all of them?

This is amazing to me that you can do this in Zig code directly as opposed to messing with the compiler.

What do you mean by "buttering the cost of switches", can you elaborate? (I am trying to learn about this topic)

In poker, like in trading, the key is knowing when you have an edge and being aggressive but also knowing when you have a losing have and cut your losses. It's the balance that makes a good player/trader.

That's nice. Do you have some tips/tricks based on your experience that you can share?

> the DB was a "pure overhead" software that aims to minimise memory consumption that's needed for a co-located resource heavy application)

Thanks pron for the reply. This describes it the best. To minimize resource consumption in a "pure overhead" software. It's currently written in Java and we are planning a rewrite in a systems PL.

Who is that single customer? I'd have thought by now there would be more.

Would you say writing something like a database (storage and query engine) from scratch is better done in Rust or Zig?

What has worked out very well in practice is hyper-threading. So you take instructions from two threads and if one of them is waiting on a branch the units of the CPU don't go unused.

Not clamp per se, but there are enough tiny snippets which can have off by one or other issues not relevant to when you think about the problem description.

This is the gap that LLMs have been filling quite well now in my experience. There are these little isolated tasks that are described easily in natural language for which the idiomatic code snippet can be created and importantly modified by LLMs as needed. No need to pull in pesky dependencies. Though when to switch over to a full blown dependency is still a judgement call.

Oh yes I didn't mean F# is the only one. Just that the other ones I am likely to work with i.e. C++, Java and Python don't have it.

I miss the F# pipe operator (https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...) in other languages. It's so natural to think of function transform pipelines. In other languages you have to keep going to the left and prepend function names, and to the right to add additional args, parens etc ...

I don't think there's a need to consume it, this looks like a topical application.

Which you then spit out like chewed up gum.

But why not chew on hair directly?

How do you use Rust without lifetimes?