lambda_garden

Couldn't this be injected into the runtime so that no code changes are required?

Perhaps really performance critical stuff could have a "notrace" annotation.

Java 21 is colorblind - but the colors still exist

I have a genuine question about Loom / virtual threads / etc.

In languages with async-await syntax, I like that it is explicit what is sync and what is async. I also like how the "bind" points within an async expression make it clear where the syncronization happens. It seems to me that Java 21 makes all of this implicit, which is a step backward in this respect.

Similar to how types enforce valid usage (a foundational idea in Java), I feel that an Async<T> should not be implicitly a T.

Are people concerned about this at all?

Have the Java designers addressed this?

This is not equivalent to (say) a single Postgres database where we get shared state with transactions between all users - or have I missed something?

> LLaMA, with up to 65B params, opened against Meta's wishes

They sure didn't try very hard to secure it. I wonder if it was their strategy all along.

The issues I raised were pretty concrete, and not merely "this symbol is better than that symbol"

Why are people so enthused about Python syntax?

Some problems off the top of my head:

- The lack of new variable declaration keyword makes scopes less explicit. nonlocal is not simpler in the large than `let x = ...`

- The lack of multi-line lambdas is very limiting for anyone coming from JS, C#, Rust, Kotlin... heck even Java

- The ternary operator (... if ... else ...) is needlessly different for other mainstream languages

The brittleness of this kind of thing is a real application for LLMs

Could be getting ahead of the next iPhone announcement

Indeed. A question we should be asking is what the Swedish government should have done if faced by mass non-compliance

Trouble with that is invoking main and declaring main are too similar. I prefer this:

    let main () =
      printf "hello"
      0

But why not test? If we don't expect compatibility to break, then it will be little extra effort surely?

They use Haskell in any case [0]

[0] https://jacobin.com/2022/05/jacobin-is-looking-for-a-program...