svvcfb1212

Yes - I do it regularly. Blink SSH to get to my workstation at home + tmux + [console editor of choice]. Works great when I'm somewhere I don't want to carry my laptop to, have a cellular connection, and find a few minutes where I feel like doing some work. For context, this is day-job work in high performance computing. The only awkward part is when I'm editing papers, although I've been happy with working copy (for git) + local tex editor/compilers on the iPad. Not ideal for producing final copy, but good for editing and drafting.

Ada, not ADA. It’s named after Ada Lovelace, not an abbreviation.

It is so interesting how people in tech jump to baseless conclusions about others' behavior that differs from their own...

Personally, I shifted to Ubuntu since it removed headaches re: getting a system running out of the box. By the time i shifted in ~2011 I had already transitioned through SLS -> Slackware -> RedHat -> Debian over the 1993-2011 period. After 18 years, Ubuntu brought relief in that I didn't have to deal with fiddling with things to get a system up and running. At that point the fun-factor of fiddling with the system had worn off and I was mostly concerned with getting work done, which Ubuntu addressed. Last time I tried Debian (~4 years ago?), it felt like it had caught up in terms of the out-of-the-box experience, which was nice.

> For most games worrying about allowing modders to easily edit code is premature optimization.

I was involved in a game project that died extremely quickly a few years ago. The project lead made every decision re: architecture, tooling, etc. somehow involve worrying about modding. As a result, we ended up with nothing to show since everything got derailed by a bizarre obsession by one person with modding before we even had anything to mod. I believe that person doesn't take lead roles on projects any longer...

...and this is how we get unnecessarily bloated software with ungodly dependency chains and complex build systems.

Sometimes a purpose-built module that addresses the need and maintains simplicity is preferable over complexity in the interest of some future potential feature that nobody has asked for yet, and may never ask for.

That’s not entirely fair. While it is true that it doesn’t cover the latest and greatest package management tools or libraries, it does have a nice coverage of the core language that is still perfectly valid. It is written for a different target audience than RWO I think - when it was written, most of the people who used Ocaml were PL developers and researchers, so it focuses on the language from that perspective.

I wouldn’t disregard it simply due to its age - that is a bad habit I see all too often (“Old = bad!”). Just to make sure before posting this, I went to some random parts of the book and pasted example code into a utop REPL for the latest Ocaml version and it worked fine. So it’s not like the code has bit rotted. It’s still worth a read if someone is interested in languages. It is not worth reading if you are looking for a tutorial on spinning up some form of web app or server app that uses all the shiny things people are currently excited about.