Its not really hard to tell.

1,000 more tests!? That reads coherent to you?

Pipe to dev/null. Fastest database i have ever used.

/dev/null is web scale

It is literally true. You don't need to run a type checker.

mypy is also written in a style conducive to speed ups when compiling with mypyc

Funny i know about Proust from The Sopranos.

If we're sharing I learned about him from the preeminent Proust scholar in the United States, while I watched Little Miss Sunshine.

Same

You don't you build solar and wind, which have different seasonal productions. Wind power is actually higher during winter. See: https://www.researchgate.net/figure/Estimated-normalized-mon...

And if you combine the graphs for solar and wind from this: https://aleasoft.com/european-solar-and-wind-energy-producti...

You can nicely see that they are complementary in terms of energy production.

Yeah Containers like Option<T> and Result<T> not having a proper subtyping relation to T is major flaw. I mean you are basically giving a stronger guarantee if you are returning T instead of T or an Error, yet you break every callsite.

I have been thinking about this in terms of a data oriented programming language like clojure, but having types/schemas. If you use Union Types for something like getting a value out of a map for a specific key, then if you knew the schema of a specific map you could reduce the return type from {T, Error} to just the type of the value T that you know is there.

Basically a sufficiently smart compiler with the necessary information could make you not have to deal with errors at all in certain cases. With Result/Option/Maybe this would not be possible. It would always infect the entire callstack and you would always have to deal with it.

Concurrency is not "single core parallelism". Concurrency describes tasks/threads of execution making independent progress of each other. Parallelism describes tasks/threads actually running at the same time.

>Concurrency is not "single core parallelism"

Of course it is. Concurrency gives the impression to the user that parallel processing is being done, even when it's not. That's why my parents old 386 could render a moving mouse cursor and a progress bar at the same time (usually).

Concurrency lets you do things "in parallel" even if you can't actually do them in parallel.

They are not missing the point. The previous post was simply wrong. The halting problem is semi-decidable. So you can potentially find out wether a program halts.

Besides missing the point, this is also pedantic and quite boring.