grokkingStuff

why would you install latex with a docker image? Installation doesn't seem that hard.

Didn't see anything for Haskell so I'll do that. Good link in general would be https://www.linkedin.com/pulse/haskell-data-science-good-bad...

- Python is established for Data Science vs Haskell You could use Haskell for whatever models you need (although finding 10-20 people for that might be a challenge) and it would be really easy to refactor for any changes you might have but I dunno if data science is something you'd use Haskell for. Most data science applications I can think of are either scripts to inspect/clean data (Python works well) and the rest involve a lot of trial and error (Haskell errors aren't great).

- Haskell libraries are awesome You could use Haskell for whatever important libraries you use on a regular basis - it's incredibly easy to write APIs for different languages in Haskell (which is great if you switch languages for some particular use) and it's easy to refactor (which is important in a new company that's likely to change a lot). Also, it's a lot harder to write shitty core libraries in Haskell.

I'd honestly recommend sticking to whatever language you already have code in. If you already have python models built, stick to them!

As much as I like IRC, I don't get why the author hates slack so much. I dislike slack (probably because of the culture in Slack groups) but I do think that having a mobile app & ease of use is why Slack is okay. Not having to deal with different servers & terminology that look scary also helps (a lot) for most people using Slack.

Most people who use Slack haven't ever used IRC professionally (or at all) - I've shown IRC to people who love Slack and I usually get "Ugh, it looks so old fashioned and difficult to use" as a reaction. Looks matters a lot if you want people to use it - most IRC clients are old or have designs based on old clients.

Plenty of Slack clones out there that look decent that have similar business models. What would be awesome if there's an IRC server that looked and acted like Slack; nice features like:

- a website to log into like Slack (with benefits like modern web design and Github, Twitter, Facebook login). - an irc client that looks decent on website, desktop and phone clients (and doesn't run on electron). - having multiple channels for one company like Slack channels in a group. IRC currently requires you to register several channels (which is annoying).

------------

As for the difficulty in writing bots for Slack vs IRC, sure it's easier to write stuff for Slack because:

- most Slack bots/services are written by companies who want their third party services to be easily integrated into whatever team communication their client use.

- most custom bots are variation of some bots that someone else has written (anecdotal evidence but pretty sure it's true). I'm pretty sure it's not that different for irc.

- most people don't bother writing bots unless they're willing to play around with bots; difficulty isn't an issue when it comes to writing one and I haven't seen bot development treated as an actual task (it's more of a hack that works and isn't really touched again.)

------------

Honestly, this seems to be a case where the author neglects how real-life people work in favor of code "niceness" (for lack of a better term). There's a reason why most people use Microsoft products (and it isn't because they make great software.)