geekingfrog

Why do people need to know about this magical thing? Isn't that enough if you solve a problem? Interested people will look for solution and find your magical thing, no need to add to the general cancerous spam of "hey, I'm sure you're going to find that thing awesome, even if you don't need it"

It's addressed in the article. Basically, you can mimick that with a generational GC as long as the youg generation space is large enough to hold all objects from a request.

String: Linked list of Char. Nice for teaching, horrible in every other aspects. Text and lazy Text: modern strings, with unicode handling and so on. ByteString and lazy ByteString: these are actually arrays of bytes. Used to represent binary data. Because haskell is lazy by default, and sometimes you want strictness (mostly for performances), there are two variants of Text and ByteString, and going from one flavor to the other requires manual conversion.

Great post. How much knowledge and experience of haskell did you have before starting this project?

Except that the wealthy don't pay that much taxes in the first place.

Does readable MUMPS even exist?

xpinstall.signatures.required should be the setting you're looking for.

what? off topic

After living in China for a few years, I understood something: the only thing chinese government cares about is its longevity. The whole system is designed to keep the party in the control seat. Economic growth was a way, now that's is slowing down, the party is finding other ways, but it would be a mistake to think chinese economy is more important than power for the party.

Looks nice, but the pie chart is really not a good choice. It's not clear at all which choice is the winner when some are close (among other things). Add an option to change to a bar chart or something else, or change the default please.

Be careful about spending resources on collecting useless data though.

One very useful advice when it comes to 'what to memorize' is trying to always watch yourself using vim. If you happen to do something repetitive, ask yourself: is there a better way to do it? How to automate it? And then, commit this new tip to memory. This way, you actually only memorize what is directly useful. This tip has served me very well.

It's a very good book. It explains a lot of 'why' and inner working of good practices.

It's also fairly comprehensive, ranging from - some evilness (type inference with ==, eval and its performance toll) - functions and higher order functions - objects and prototypes. Some good explanations of the all prototype and constructor thing - array, dictionnary and some things to know about their prototypes - api design and concurrency

It's 200 pages full of content, I recommend it.