mcdermott

Borges is the master of the short story, but I think that he may need to share that title with Guy de Maupassant. I'm currently reading both of their collected works of fiction, alternating between them with each story and enjoying the experience.

C# (the default .Net lang) has so much ceremony, boilerplate/scaffolding and IDE dependence (IDE programmers) and OOP overhead that it requires 5x more lines of code than the same app in Python or Go. Every time my interest peaks, I take a look leave with the same feeling that it's a dated/bloated OOP relic and would take all the joy out of programming. I've also noticed that most C# programmers don't usually know another language (other than a little JS) and seem totally dependent on Visual Studio; if all they had was a text editor they'd be lost. That's not a good place to be.

Perl 6 was a huge mistake; it's a different language and should have never had the same name. I support renaming it so we can all forget about it and have Perl 7 be a direct, mostly backwards compatible descendant of Perl 5 with feature enhancements. This whole Perl 6 nonsense was the reason I jumped to Python many years ago.

Python has "jumped the shark" for me. Python is no longer Pythonic (the "import this", zen of python easter egg should be removed). It's lost it way and is TIMTOWTDI now, heading for that Perl 6 brass ring. Golang is now the Pythonic language.

Chef (and configuration management in general) is an anti-pattern for a cloud native approach.

The soup of the Chef ecosystem has always seemed hard to understand (and teach new team members): Chef, Chef-solo/zero, rubocup, test kitchen, food critic, berkshelf automate, delivery druck, inspec, infa, etc...

With containers and immutable infrastructure there just isn't the need anymore. They obviously realized this and created Habitat as a response, but after trying it a few times, I don't see why I'd use it over plain old Docker + K8s.

If you still need configuration management, Ansible is more flexible, is easier to learn/teach (no need to learn Ruby), agentless, no need to run a sever and can also do some orchestration.

I've been toying with Nim over the past few months and really like it and hope its adoption picks up post 1.0. I've been using Python for 10+ several years and Go for the past two years and returning to them after a good Nim coding session always feels a little depressing. My favorite feature is the Uniform Function Call Syntax (UFCS).