I continue to be baffled and amused by the complete meltdown of the typescript community over the actions of a single man on a single package. The only people who have legitimate gripes are those that had been actively contributing and whose work was erased. The rest of you are acting absurdly childish. The anger and vitriol being thrown at anyone who disagrees on how to write javascript would make me embarrassed if I was associated or involved in the ts community.
They not only removed typescript without implementing an alternative breaking many projects depending on that library but they did it without informing the open source community which means many people who invested their time in making PRs (there was 60+ open PRs) have to basically completely redo their work.
Yes, and the people directly contributing to the project have legitimate gripes. Although, the parable of dhh is if you get on an asshole scorpions back, don't be surprised if you get stung. Dudes been an unreasonable prick for nearly 20 years now.
My comments directed at the manufactured outrage from the tooling zealots incapable of having a mature conversation. Or even accept a difference of opinion. The number of comments that start with, "never heard of Turbo, but let me weigh in on why you're an idiot for not liking Typescript. " is very telling...
Nothing is actually going on with typescript. This guy who's a big name in programming for creating a lot of good things and having a lot of shitty opinions just removed typescript from one of their projects and some folks are desperate to make that be a big news.
They removed typescript because they saw no benefit in using it. Then a lot of folks who can't deal with typescript got excited because "hey someone is trashing that thing I hate".
He became a patron saint because he developed Rails, and he huffed too many of his own farts. His track record can be boiled down to thinking he knows what's best and the evidence is damning
huh. what was the rationale for removing it in the first place? seems like a waste to throw away a whole codebase worth of perfectly good type annotations
People seems to be riled up by this, but turbo is mostly used with ruby on rails, right? I'm not familiar with ruby on rails, does it actually support some form of static typing it type hints? From the blog post, the dev (which is also the ruby on rails creator) doesn't seem to be a fan of bolting static typing into dynamic typing language.
RoR is very... specific. Some love it because it comes with magic. Many hate it for the same reason.
You either knows the magic and love it, or you hate it with a passion. You never really know when (not if) your change will break the system because it's supposed to name in a very specific way that work by, again, magic.
In Ruby, the convention is usually that things are duck-typed (the actual types of your inputs don't matter as long as they implement whatever you're expecting of them, if not, we throw an exception). Type hinting could be possible, but it basically runs contrary to the idea.
Now, Ruby on Rails developers are expecting some kind of magic conversion happening at the interfaces. For example, ActiveRecord maps the database datatypes to Ruby classes and will perform automated conversions on, say, date/time values. But from the developer perspective it doesn't generally matter how this conversion actually happens, as long as there's something between the layers to do the thing.
It's also used quite a bit with Symfony framework (PHP) which is strongly typed. I use it for example at https://schedule.lemmings.world. A shame, really.
CI/CD is useful regardless of which language you’re using. Sooner or later some customer is going to yell at you because you didn’t discover the fatal error before deploying.
@magic_lobster_party@alphacyberranger@unsaid0415 CI/CD won't prevent that. I wonder what it is for. Not using the CPU on my laptop for tests? And why would I want to commit before knowing the tests pass?
Consumer just needs to write 4x as many unit tests to make up for lack static typing. Hopefully the library author has done the same or you probably shouldn't use that library.
I thought it was clear: they're implying JS is simpler/faster to write and deploy because transpilation is necessary when using TS (unless you use a modern runtime).
No. They want to add syntax which allows browsers to parse typed code, but it would just be ignored - the type checking would still have to be done by e.g. Typescript.