I have written non trivial projects with ramda and I like it a lot. You have to use your judgement with readability. Some of the advanced functions are a little hard to grok at first, but most of the library is pretty straight forward.
I've contributed to large codebases that have static typing (C++ and TypeScript) and dynamic typing (JavaScript) and I've come to the conclusion over the years that static typing isn't really worth it as long as you have the discipline to write tests for your code. The most basic unit tests cover type checking concerns. Refactoring might require a bit more search/replace but I don't see how that is a big deal. Tests make refactoring safer than with just types. Tests act as good documentation of how you expect your code to behave and what expected inputs/outputs there are. You just don't get autocomplete which is a pretty overrated feature imo.
You could do the same process if you used dynamic typing and good test coverage. Just make your change and keep fixing tests until everything is green.
I went to a Clojure meetup one time and they all went on about how using Datomic in production is a nightmare and it's generally an over-engineered product that isn't worth the trouble in the end. Do most people who have dealt with Datomic in production feel this way?
This is unfortunately not uncommon. I feel like most of my coworkers at most companies Ive worked for don't use vim. One killer app of vim for me is macros. You can record a string of commands and map doing that to a letter. This makes certain mundane changes you have to do sometimes in software a breeze. For example, I had some code where someone was using string literals everywhere when they should have defined an enum. The convention we use for this kind of thing is to use UPPER_SNAKE_CASE and the strings were in camelCase. I was able to define two macros that let me improve this code in a few seconds. If I wasn't using vim I'd probably just leave that code as it was because it would have been so much effort.
How do you define object-oriented programming? From my perspective the very core of it is stateful objects with encapsulation and methods on those objects that pretty much always are not pure. If you just start treating objects like collections of functions, I don't really see how that's OOP. As far as I remember, it has been a little bit since I've used OOP everyday, pretty much every facet of the paradigm is centered around mutating state. You can certainly commingle OOP and functional code, but they simply aren't compatible paradigms.
What are you talking about? if you're async operation fails then your callback should always still be called but just with an error message in the second parameter typically. And what are you doing still giving call backs to async functions? Why are you not using promises?
The problem here is that this conversation is made complicated by the fact that plain objects in JavaScript are not what is really being talked about when people say the term OOP. So to clarify, stateful classes would be what I am talking about when I use that term. The foundation of OOP is based on tying state with functions in what are deemed "Objects". This implicitly makes all methods in an Object that depend on or modify an Object's internal state impure functions. And the purpose of most Objects methods are for the purposes of doing those things. Basically if you use stateful classes that encapsulate state and modify their own internal state with functions you are not doing functional programming. These two paradigms are in fact at odds and not compatible.
I have a very hard time believing that this stuff has to do with anything other than having the discipline to have a proper sleep schedule. It's possible to adjust your sleep schedule. People do it all the time when they change timezones. I didn't read the article, I'll go read it and update if I change my mind..
It's not about typing speed. It's more about comfort and accuracy. Also the cognitive load is really not a thing once you're used to it. Maybe you should learn to accept that some people might be more mentally flexible or skilled than you are rather than assuming people are lying to themselves.
Well, I think that any keypress that requires you to move your wrists in any way is weird basically. How do you reach 5, 6, or 7 on your number row for example? what about 1 or ` or esc? I like making it so that I can reach all of these buttons without moving my wrists and with the "correct" fingers.
It's not for me. I like fewer keys because I find that it's easier/more comfortable to use layers rather than have to do a weird reach for some key I need.
It certainly doesn't help with transitioning to alternative layouts. I found my touch typing improved dramatically when I started using ortholinear and vertical stagger keyboards that force you to really use the "right" fingers