michielderhaeg

You can make your allocations faster if you don't have to worry about deallocation. Could be a performance thing.

> Too much stress? I bet if you paid people so much money that they could work for 10 years and then either retire to a lower paying job, or retire entirely, people would deal with it.

Don't underestimate just how high-stress these jobs are and what it does to you. People quit these kinds of jobs for 2 reasons

  1) They can't deal with the stress mentally, or don't want to.

  2) They were not smart enough to choose option 1 and their body just physically gives up and they are no longer capable of performing their job as an ATC.

I know someone who is now legally handicapped because her lungs don't function properly anymore due to the stress and was forced to retire early.

I do agree that the pace is reasonable. Both with opaque pointers and the new pass manager API there was a quite a long transition period where both were supported before the old system was deprecated/removed. But with every new non-patch release, some part of the public API is changed and we have to adapt.

I think the bitcode parsers (binary and textual) are quite backwards compatible. Old bitcode IR will be upgraded transparently. So you might not have to keep up.

This reminds me of when I was still in university. During our compilers course we used the "Modern Compiler Implementation in Java" book. Because I was really into FP at the time, I instead used the "Modern Compiler Implementation in ML" version of this book (which was the original, the Java and C versions were made to make it more accessible). We noticed during the course that my version was missing a whole chapter on visitors, likely because ML's pattern matching made this kind off trivial.

One of the other students made a similar remark, that software design patterns are sometimes failures of the language when they have no concise way of expressing these kinds of concepts.

Flask is FOSS, maybe it is not too difficult to add support for this yourselves.

If I switch to the light theme and back again, the diagrams become white and readable.

The only downside is, I believe, the electricity bill. The reason to use a rpi is that it has enough computational power to do many useful self-hosting tasks while consuming only a fraction of the power of a beefy computer.

There are many places in the world where this is not a thing. I live in a densely populated country where it it simply not possible to get that far away from any city. If you drive 50km in any direction anywhere in the country, you would've encountered quite a few cities. I would have to cross several borders to get to a place without light pollution.

This is what the Glasgow Haskell Compiler runtime does. If you run a Haskell application, you'll see it has uses 1TB of virtual memory.

This way you never have to talk to the kernel if you need more memory.

Can you explain the privacy argument to me? Bitcoin is a massive public ledger, I have a local copy of literally every transaction ever made. How is that better for privacy?

Don't quote me on this, but I think most String operations are compiled to StringBuilder operations automatically.

What if your code is browser specific and uses the javascript based API? You'll need to run it in the browser to debug it right?