924 karma · joined May 18, 2011
> let f = map reverse
> f [[1,2,3], [6,7,8]]
EDIT: scratch the "let" example (thanks nandemo), tryhaskell.org doesn't support that. my bad!
My point remains: one of the main reasons of using HATEOAS is so that you can evolve your API without breaking clients. The other main benefit is so that your client can discover your protocol by simply following hypermedia controls.
I could have an endpoint example.com/users become example.com/subsite/users. It is precisely because the URL might change that you want to give the client URLs to the next possible actions.
What makes you think he's unhealthy? Because he has whiter complexion and he isn't bulky?
I'm just a beginner Haskeller, but this seems like a pretty bold (and false) claim. I've used Parsec for writing a Scheme (while reading the book), Shelly and Shake for build and test automation, and some statistics libraries for, well, statistics. They were all intuitive to use, and there was no "impenetrable morass of esoteric abstractions". I'm not sure what you're on about. Maybe provide examples?
I'm a bit off-topic, but you don't need to "compromise" your HTML with AngularJS, you can place "data-" in front of your attributes and you're HTML-compliant again :).
People build amazing sites in both languages... so you can't go wrong... it's just a matter of what you want to learn on the way. Good luck!
Isn't it strange to compare Python/Perl to C and say that one is better than the other? It's apples to oranges. You wouldn't use Python or Perl to build an OS, and you wouldn't use C to prototype a web app.
Can someone explain how Minix compares to Hurd? In terms of how far ahead both projects are, the differences in their architecture and visions?
The problem is probably: "Googling for some obscure mail archive to find I need to change “bop” to “boop” in /etc/something/config.ini. The amount of time that I had to spend doing this crap was growing instead of shrinking."
If you take the time and patience to understand your system and sift through man pages, configuration time will obviously shrink. If it's growing it's because you've never sat down to truly understand the cogs and screws of your system.
On the other hand, not everyone wants to read man pages, they'd rather something that "just works"... which Mac does way better than Ubuntu, unsurprisingly.
There's QNX for that: http://www.qnx.com/products/neutrino-rtos/secure-kernel.html It's used in industries such as automotive, nuclear, etc.
Perhaps you meant "future secure open-source Unix" ;) (QNX source was closed the day RIM announced the purchase)
It is obviously not meant to be taken literally. He is, though, wanted by the US, the Brits, the Swedes... Who would you say, off the top of your head, has a higher "wanted" status today?