They mention their company numerous times over, sure doesn’t seem like a personal blog. It seems like a company discovering something that has been documented over and over again.
Article written like it’s someone that just discovered types even though a majority of the programming world said to use types for decades…
Also I completely disagree with the assertion that you should write everything including backend in typescript in order to share types. You should be using a schema and generating your types if you are writing large systems. That way any service that uses your APIs can generate the types as well and isn’t locked in to your language.
And please dear lord stop writing backend code in JavaScript or typescript or any scripting language.
Other than that, yes, use types. They literally do exactly what every proponent of types has said they do for years. Turns out it’s a huge benefit!
None of the complexity of GitHub actions would be solved with any other configuration language. It needs to be a full scripting language at minimum. The problems with GHA have nothing to do with yaml.
I’ve had the invisible window issue, today for the first time, but not the other issues you’ve listed. iOS 18 on the other hand, holy fucking shit has it been a nightmare.
Ruby and Python are both scripting languages and have been since being invented. Static type annotations are a dumb thing to add to a language like Python and Ruby, they’re not static languages. If you want static typing you should be using a different language. The syntax is most definitely not worse, and that’s not an opinion, Python’s for comprehensions are nightmares of readability, and hardly make sense 5 minutes after you write them. Ruby prioritizes readability over everything else.
Speed is almost exactly the same, with Ruby winning on many benchmarks. The only people saying Python wins are Python programmers. There was a post on the clojure community the other day comparing specific instances and while clojure was winning them all, Ruby was in second on most of them.
Python only looks better from the outside. I spent years coding in both at the exact same time at the same company. The only two things Python wins on is number of packages, and even that is a dumb metric (looking at you npm), and Click, which is an absolutely fantastic CLI framework.
I haven’t heard that in 15 years. The main reason to use Ruby is that it’s a better Python. The tooling is 10x better, it has all the same language features and more, it has easily enough packages to handle any situation you want, and it doesn’t have all the bike shedding that Python has.
You shouldn’t be writing applications in a scripting language anyway. They’re for scripting, it’s in the name.
Less about grammar and more about using the wrong word due to similarities, like loose vs lose. I think esl speakers in general have great grammar, but it also depends on their main language structure. For example certain root language speakers like Hindi or French tend to have great grammar until something comes up like “are you going to the park?” where they might say “you are going to the park?” Or something like “I am knowing the answer” instead of “I know the answer”. Same with Germanic language speakers with ordering, like “I to the store went”. I honestly don’t see these often, and they’re very easily recognizable as ESL language patterns, which is why I called them out as exempt. Because learning another language is hard. But if you speak English natively there’s no reason you should be misusing “lose vs loose”. They’re not even pronounced the same!
It’s mind numbing. I understand ESL speakers having trouble, and I understand being tired and messing stuff up in comments, but if you’re making a post you should be double and triple checking everything you wrote. It’s ridiculous.
The first two or three examples are really bad but the rest are quite good.