tarblog

Do you have a source on this? Even one about the market in general? I wasn't aware of this practice before now.

Monomorphisation is the name of the technique of producing a different version of the code for each set of type parameters that are used in the program. C++ and Rust use monomorphisation instead of doing runtime checks because they're trading off slightly bigger binaries for greater speed.

By not doing runtime checks you get to skip that work at runtime, obviously, but you also get to enable other optimizations like inlining the monomorphised version.

The burden of proof that facebook can see months into the future would be on the poster. No evidence is needed to simply disbelieve this.

>We take the data we get and process it for later use

What data do you collect/use to make the music?

Do you have any science to back those claims up? What are you basing it on?

Do you have a suggestion for a replacement for "monad"? It's always been such an opaque term to me, even as I began to get a grasp of it.

Professional ethics of software engineering is definitely something we're going to have to grapple with more and more. Another aspect is being asked to use Dark Patterns in a UI or build a skinner box into a game or app. There's evidence that these things do harm to people and having a professional organization that could help stand up to such things could be part of a solution.

Tip: include the text "San Francisco" or "SF" instead of "s.f.", it makes searching for your post more obvious.

I think you're on the right track.

The way I remember it: the product was still overwhelmingly better than everything else. Missing copy&paste was an "oh well" compared to owning an iPhone in 2007.

You shouldn't expect quantum computers to bring a "free-lunch" speedup the way that clock-speed increases did for such a long time.

I would define the term "high-level language" to mean that it's possible to write programs in the language without needing to worry about the specific hardware that the program is running on.

I would consider systems programming to be things like writing operating systems, drivers, high-performance native applications (for many difference definitions of high-performance), and databases.

I consider rust to be a high-level language and I further consider it to be suitable for systems programming using my definitions.

However, I don't consider go to be suitable for a lot of systems programming tasks because it has a significant runtime system that includes a garbage collector. Just because they describe themselves as a "systems programming language" doesn't mean that I believe them (at least as far as I understand that term). That said, there are certain applications that work fine with GC, and in those cases it can be a very nice way to achieve memory safety without programmer burden.

You have a typo in "Francisco"

>has been in iOS since forever

Granular permissions have only been in iOS since version 6.0, which came out 3 years ago. The first version of iOS was 8 years ago. For a feature that's "as common sense as it gets" we sure got along fine without it for half a decade.