rienbdj

This feels like a “sell the shovels” move. Social media is full of “this one prompt to get rich quick”. It’s the new “one weird trick”.

There are compile-to-yaml config languages

Tragedy of the commons. What stops a company taking on the strong junior engineers you just invested time and resources into?

Not many people are employed as computer scientists (they are mostly academics) compared to SWEs.

Can’t sustain six figure salaries because current prompts are wrong.

Cut juniors for AI

Save money

Invest in market share

Increase market cap

Hire the last remaining seniors at higher rates but only where needed

Great time to be a shareholder or staff level engineer. For everyone else, the ladder has been pulled.

Pretty good performance for low effort is a big win.

Build systems are a much harder problem, probably because mainstream languages are all edited the same way, but not built the same way.

The closest we have right now are build systems in the Bazel / Buck2 lineage.

The burden of proof is the other way

Training AI models to drive valuation reminds me of high frequency trading

Really cool nice job!

With more and more ecosystem libraries being written in Rust (and a Python wrapper) could this be a way to expand the Haskell ecosystem?

Reading what Stainless is/was - why was this a company and not an open source project?

Effective AI use (in my experience) has human doing the load bearing parts by hand (schemas, api spec, overall architecture, domain types) then AI fills in the blanks.

Bazel caches tend to have a size limit.

You need to trust your build execution machine anyway. They have your source code and you will be executing the artifacts that they produce!

The post talks a lot about performance, and indeed Python performance is poor. However, it’s not poor enough to matter in the early stages of most projects.

The larger issue is actually correctness IME. Rust offers a better static-type story than Python, sure. But I would consider Haskell or OCaml to get even further gains.

Bring back lightbox!

Does anyone know if Mojo is more suitable for functional programming that Python?

Things like optimizing away object allocations, pure function inlining, tail call optimization?

Translating library usage from C# to F# is pretty mechanical so not sure if specific docs are needed.

The larger issue is the C# community loves OOP so you often have to wrap these libraries into something more “FP” if that’s how you want to work.

Overall it’s far better than having nothing (looking at Haskell, OCaml as much as I enjoy them!)

It’s really hard to please everyone all of the time on this front.

This kind of thing is why Roc compiles to WASM but not JS.

C++ could use some do-notation

Question for Zig users:

Can comptime blow up compile times? Does it have arbitrary cutoffs like C++ template depth?

The issues with Go in that article only surfaced at Discord scale.

I would love a language that distinguishes functions (pure mathematical constructs) from procedures (imperative constructs that map in a predictable way to the instruction set).

This feels like the direction Algebraic Effects might take us.

I get what you are saying, but…

An exception is different to an Either result type. Exceptions short circuit execution and walk up the call tree to the nearest handler. They also have very different optimization in practice (eg in C++)

Under this strict definition you can’t even throw exceptions!

(Pure) expression orientation is the true marker of FP

Meta wants the models to be cheap and available because their strength is the context data and platform control.

When allocating engineering spend you need to predict impact. If you know how features of GitHub CLI are used and how you can do this more easily.

Interesting - I had not looked deep into this before.

Is suppose the difference is RDS has high 9s, whereas in the Litestream case the frequency of crashes is tied to your application code and deployment process. In practice this will take more work to reach the same uptime?

There are also atomic references when mutability is the best approach. This is forcing single writer but in the API rather than as a proof.