596 karma · joined March 11, 2015
Edit: oh my, you also made Insomnia, that I used when Postman was on the enshittification path...
Edit: and even today. Generate textures for blocky assets? Sure. But full pokémon models that wouldn't need a ton of rework? Nope.
> I spend more time trying to resolve TypeScript complaints than I do adding code
Those complaints from the compiler are the main feature of any statically typed language! In TypeScript, they're here to tell you that something is potentially wrong with your code, and it might break in runtime.
"I spend more time trying to resolve [typing errors] than I do adding code" is something you'll hear from anyone that is not used to statically typed languages. _Any_ language, not just TypeScript. And it's an issue that quickly goes away by itself once you learn the language.
> Our team has lost hours on TypeScript exceptions in staging and production builds (but oddly not offline/local) where some external type was missing or incompatible, another one being that the local environment passes linting but CI doesn't, it shouldn't be so hard
That one is probably a simple configuration issue, not TypeScript's fault.
> Having to rewrite correctly and infallible JavaScript so that it was friendly enough for TypeScript to understand
This one I can get behind, but I'd put it in the same bag as the first point. I'm sometimes tempted to use things like non-null assertions (like in the example with the .filter().map()) but I'd say that 99.9% of the time the compiler is right, and it's safer to right one more line than a `!`. But you don't do it to make TypeScript happy, you do it to rule out a potential edge case, and avoid a runtime crash.
Off-topic, but please PLEASE put the publish date on your (technical) articles. When I'm looking for documentation and open an article without a publish date, I almost always discard it immediately. I'm not going to risk wasting my time learning outdated knowledge.
The first paragraph speaks for itself. The whole "involuntary" part of "incel" implies that your celibacy - the fact that people don't want you as a partner - is totally out of your control. Incels are the epitome of "nice guys".
Though I really like it, the finishes are really not great compared to a Nintendo Switch. The plastic feels cheap, the case creaks a bit, one of the triggers squeaks, the buttons clicks are super loud, and well, a speaker broke. There are also a few small software issues that are definitely not deal-breakers, but quickly add up as annoyances.
I still find it's a good device, it does what I expected it to do (sometimes even better), but for the price, I expected something a bit more robust.
I have several frontend side projects and they all use TypeScript. The static types makes it way easier to write & refactor even if you're working alone. I have also more confidence in my code and spend less time following JS trails to track stupid runtime bugs. Older projects are easier to pick up again.
Any project that goes beyond a few trivial files will benefit from Typescript.
Context is key, it depends on who that someone is.
I don't know if it's been backed up by real data, but services like Steam and Spotify tend to confirm this intuition.