I am unfamiliar with this filesystem, and am curious about it. Could someone explain to me its benefits over btrfs?

What I like to tell people is that I am as good a programmer as I am for the simple reason that I began when I was about 8, which gave me a very early start on making all of the mistakes one can possibly make when learning how to code.

(It has been funny watching some of my coworkers learn a new coding technique and finding it to be so cool that they apply it everywhere regardless of whether it fits or not while I think to myself, "Ah, I remember when I went through that phase as a teenager!")

It's interesting to see how C++ has essentially become the testing ground for new features before they make their way into C.

That is conceptually how dynamic programming works, but in practice the way you build the cache is from the bottom up rather than from the top down. It's a bit like how you can implement computation of the Fibonacci sequence in a top-down manner using a recursive function with caching, but it is a lot more efficient to instead build it in a bottom-up manner.

Does it really make sense to have access to the entire C++ language to run on GPUs? Aren't basic constructs that you take for granted in a complicated general purpose language like C++ super-expensive on a GPU? For example, my understanding is that whenever a GPU runs into a branch, it has to essentially run that part of the code twice: once for each branch.

I completely agree with that assessment, but what is weird to me is that most people use frameworks so they don't actually touch any of the markup themselves.

That approach makes a lot of sense for amateur web sites, but less sense for professional web sites.

Wait... I just noticed this:

[XHTML] never took off on the web, in part because in a website context so much HTML is generated by templates and libraries that it’s all too easy to introduce a syntax error somewhere along the line; and unlike HTML, where a syntax error would still render something, the tiniest syntax error in XHTML means the whole thing gets thrown out by the browser and you get the Yellow Screen of Death.

This confuses me; don't you want to make sure you are always generating a syntactically valid document, rather than hoping that the browser will make something suitable up to work around your mistake?

In fairness, the actual title of the article is "What's Your Go-To Java Stack [emphasis mine]".

Thanks, it's actually kind of nice to hear someone who likes using PHP explaining in detail why they like it.

Nifty! Thanks for posting this.

So basically this idea is similar to how Rust does things, except that the compiler doesn't warn you when you are doing something unsafe? I think that is reasonable for a 2007 paper, but not necessarily today.

Thank you for taking your time to make sure 0.19 is stable before upgrading! I recently switched here from another instance because they upgraded while 0.19 was unstable and it broke a lot of things.

Q: Why the name "Fleece"?

A: It's a reference to the mythical Golden Fleece, the treasure sought by Jason [emphasis mine] and the Argonauts.

I see what you did there...