-
Because the example is so well prepared, I just tried it out and was somewhat surprised that it would not use more than 1 CPU.
To make it use 4 CPUs on my system I had to compile it with:
stack ghc --resolver lts-7.14 --install-ghc --package conduit-extra -- --make -threaded echo.hsAnd then run it with:
./echo +RTS -N4Then you can see that with every new connection and long input it will use more and more CPU.
-
-
How do both parties agree upon exchanging data such as binary data, dates, and so on, where there might be multiple valid textual representations? The benefit of a spec is that it constrains the design space on uninteresting problems like data interchange so you can focus on more important things.
-
Standard Microformats are a thing; I’d say this is an easier problem to solve in HTML than in json
-
-
Um, I do not believe the author of this post meant 3rd Amendment. This has nothing to do with quartering troops.
Relevant https://xkcd.com/496/
There’s some discussion in the blog’s comments about how the 3rd Amendment might be relevant, since requiring printers to print these dots has an effect similar to stationing an informant in someone’s home. Seems like a stretch to me though.
Yeah, that seems completely incongruous with any other reading of the 3rd Amendment.
The Third Amendment has only ever faced one serious court challenge. A prison in New York had on-site housing for the guards. The guards went on strike, and the state brought the National Guard in to control the prison….and housed the soldiers in the same housing.
The court found that that the state did violate the Third Amendment, but not itentionally, and that the case did not establish precedent.