2,777 karma · joined February 27, 2009
Contact me at mccracken.joel@gmail.com
If your reply to me seems unnecessarily combative, pedantic, or uncharitable, I will probably not reply. Its not worth talking with someone who appears to be intentionally misconstruing my words. Ain't nobody got time for that.
I'd put money on either the team not knowing Haskell when they started, or the "genius" was one of those completely impractical people who do type-level astronautics in Haskell.
For a company as large as github (and microsoft), I would expect support metrics (mean time to response, max time to response) to be known to management.
Eventually, for various reasons, Google decided that an open xmpp based system didn't work for them, and they closed it and extended it. This was effectively the end of xmpp as a distributed tech that many people use today.
Interesting, in a lot of ways SMTP is no longer an open system. It is extremely hard to operate a mail server in such a way that your valid emails get delivered correctly and not marked as spam. So for example in the name of fighting spam, it is extremely difficult to participate in this "open" system.
My main rationale for using XML for this is that
1. It was designed for it. (extensible markup!) 2. It has built-in considerations for things that could otherwise cause a more naive approach to have problems (for example, CDATA tag) 3. Other interesting features for this specific use case.
I don't love it, but it works OK. I might end up making a little less-verbose DSL which makes writing it a bit nicer, but actually converts to XML on a pass-through.
Anyway, shoot me an email if you want to compare notes on the topic. It seems like so many people are happy with markdown as an authoring format that its rare to meet people who see the problems.
Elixir is def cool but keep in mind that it is just much more normal of a language. You can probably learn it in a few weeks. Haskell is a much longer journey
It claims to not work on macos as a secondary monitor, but it does work for me, however the sides of the "screen" are invisible/cropped, so to use it I have to carefully arrange emacs and firefox inside the visible region.
The refresh rate isn't perfect, but its more than good enough for my usage (emacs, looking at docs)
It’s very hard. I’ve found most experienced Haskell devs still get it wrong at times. It’s one of the things that makes me think that we need to rethink the overall approach to laziness
I'll go try that tho!