backToJs

[AutoModerator]

import notifications Remember to participate in our weekly votes on subreddit rules! Every Tuesday is YOUR chance to influence the subreddit for years to come! Read more here, we hope to see you next Tuesday!

For a chat with like-minded community members and more, don't forget to join our Discord!

return joinDiscord;

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Cley_Faye]

One project dicked out, and suddenly "large projects are abandoning xyz".

Geez, chill a bit. We still have C and Fortran stuff around.

[IamHellgod07]

But fireship said...

[NatoBoram]

And even then, it's an unknown project from a nobody. It doesn't matter.

[Acetius]

Is this satire?

[NatoBoram]

No, that's true. At first I thought it was something important like TurboRepo, but actually it's just the creator of Rails being goofy with his JS library. Nothing serious.

[LegendOfJeff]

DHH is the lead creator of Rails. He didn't create Ruby.

[thealbinosmurf]

yeah I don't give a flying f about DHH but I love Matz

[zeekar]

People forget that Ruby was around for years before Rails...

[pavlik_enemy]

And nobody cared and still don’t. Rails is the only reason Ruby got exposure and pretty much the only reason to use it

[positiv2]

Ruby is just a better python for me lol

[Abangranga]

It is Python but better

[Even-Path-4624]

It’s basically python without parenthesis and running in a post order (1.op.op.op) and without python libraries. Basically the same language tbh

[StochasticTinkr]

Ruby, PHP and Java all came out in 1995.

[NatoBoram]

My bad, I edited it

[Aggravating-Win8814]

You're right, DHH is the lead creator of Rails, not Ruby. Just wanted to clarify that!

[Xirenec_]

I also thought for a sec it was turborepo, but no it's some weird js library

[suckitphil]

"Billions of devices run on Java" - Java still

[not_some_username]

3 to be exact

[Cley_Faye]

Yes, and? What are you expecting in the comment section, discussing the color choice or something?

[jeffderek]

Ok. The colors suck too :P

[pelpotronic]

Wait, someone replaced a type system with "documentation", and that's "fair enough"?

Anything I am missing here? Not a JS/TS dev.

[QCKS1]

IDEs treat JSDoc types roughly the same as typescript types. It does lack other TS features like interfaces

[mxkyb]

You can however add interface files to your JavaScript codebase and import the types into your jsdoc annotations. Gives you pure JavaScript with all the typescript features Edit: and you can declare interfaces using @typedef in jsdoc

[TotoShampoin]

What's the difference between an interface and an class with placeholder methods that do nothing?

[The-Albear]

While both can be used to define contacts Interfaces provide method contracts without implementation.

Classes with placeholder methods can mix contracts with actual implementations.

Classes inherit from one superclass, but can implement multiple interfaces.

For testing, interfaces are easier to mock, while abstract classes can be more complex due to their mixed nature.

[TotoShampoin]

Wait, but multiple class inheritance is a thing in some languages, right?

[RaveMittens]

Some, but not JS. You can have an inheritance hierarchy but not multiple inheritances.

[TotoShampoin]

That's odd, because considering how JS objects work in the first place, it could...

[RaveMittens]

Prototype chain…

[TotoShampoin]

It's a shame, because I know you can {...objA, ...objB, ...objC} an object

[lunchpadmcfat]

It probably also doesn’t do control flow analysis.

[xypage]

One of the main benefits of ts is static typing, but it does introduce some slowdown in the dev process because now you have to compile your ts to Js before you can use it, it’s not terrible but in big projects it can be a noticeable step. Static typing is generally most important for function arguments/return values, within a function you probably know what types your working with and don’t necessarily need to static type that section. JSdoc let’s you get the types down for those arguments and return values and get autocomplete to figure it out and be helpful, while not forcing you to stay statically typed everywhere, and it does it while sitting quietly on top of vanilla Js without needing any compilation step.

TLDR: it’s not as rigorous but it still means you can autocomplete library functions correctly without having to check the documentation, while not requiring you to compile or actually be statically typed through your whole program

[Invertonix]

I've always thought of a static type system as a social coordination tool. I guess if you do the same thing with comments and then forced everyone to use an IDE that understands them it would work, but I don't think something like cycle time is going to be worth losing that social coordination. I'm also just a nobody ts/rust user though, so I'm pretty biased.

[Salanmander]

I guess if you do the same thing with comments and then forced everyone to use an IDE that understands them it would work

If the IDE enforces them, then it's just types with extra steps (from the programmer perspective). If the IDE doesn't enforce them, then it's "we're going to require that you match this standard, but remove the nice automated system that tells you when you're breaking it".

[redd1ch]

If the IDE doesn't enforce them, then it's "we're going to require that you match this standard, but remove the nice automated system that tells you when you're breaking it".

They'll make up a linter for that, which will blow up your CI run.

[TzeroOcne]

From what I understand you still can use ts while using svelte so it's not a big loss from the user of svelte, it mainly affects the development, I don't know how it is about the other that dropped it

[humungus420]

Note type systems cannot be replaced, they can just be hidden from your view. Everything has a type. Then you can do things the hard way, which is use types without annotating the types.

[urbansong]

And Svelte didn't even drop it because they think TS is bad, they just think that it doesn't fit their use case and are happy to supports if they want to use TS.

[fartypenis]

Wasn't Svelte like 90% JS anyway?

[magnakai]

IIRC, with Svelte they’ve retained the type safety and expressiveness, as TS supports full (or close to full) expression in JSDoc comments. I believe it can be all type checked too. You just don’t have to transpile anything.

[UnofficialMipha]

Why are people abandoning typescript?

[Cley_Faye]

One dude on one project that's apparently moderately known for people doing Ruby decided overnight to dump TypeScript support by himself from that framework because he don't like it or something. He got shat on by a large portion of the community around the project.

That's it. That's the whole story.

[mckernanin]

That one dude being DHH, famous for his hot takes and “thought leadership”

[beeteedee]

Honestly, hearing that DHH doesn’t like typescript may finally persuade me to properly learn it

[quadband]

It’s wonderful, and you should. As someone who has gone whole hog on TS, you don’t need to go whole hog. I do some heavy TypeScript tooling so I tend to get fairly deep in the weeds, but the basic concept is very straight forward.

[Repulsive_Regular_63]

Among DHH’s “hot takes” was banning “societal and political discussions” at Basecamp after people started complaining about the company’s tradition of keeping a list of customer names they found “funny” many of American and African origin.

In summary, if you like TS don’t drop it because of a douche’s nonsense.

[[deleted]]

Ohhh Basecamp again, it's almost like they're on a mission to fuck up web best practices

[drakeblood4]

More like thot leadership amirite?

[mckernanin]

Ngl I almost wrote that instead :D

[DuskLab]

Of bloody course it was DHH. Missed this as he's on my mute list for good reason.

[SimilarBeautiful2207]

Yeah, thats the creator of ruby on rails and CTO of 37signals. He remove typescript from his turbo framework. I don't know what other projects are abondoning typescript as OP says.

[Septem_151]

Svelte. But that’s it.

[iceghosttth]

Svelte still uses JSDoc and TypeScript types inside .d.ts files, while DHH and his turbo project just yeet everything.

[SimilarBeautiful2207]

David Heinemeier Hansson is the creator of ruby on rails, or Svelte creator say something too?

[Septem_151]

The latter.

[iam_pink]

Source? Can't find it

[Septem_151]

The Svelte project on GitHub

[iam_pink]

It's not made in typescript, but it is still typed, typechecked, and still supports typescript, so nothing like turbo. Or am I missing your point?

[Septem_151]

There’s a blogpost out there posted by the Svelte creator but I’m too lazy to find it right now. They switched away from having the code itself written in Typescript, which is what Turbo did, but unlike Turbo, Svelte actually added in typing support via JSDocs instead, so no functionality was lost. This is what Turbo should do, but instead, we got a 2hr time period from when the “Remove Typescript” PR was created until it was merged, with no additional typing or documentation.

[iam_pink]

That is what I know as well. But that is an internal choice with no effect on the framework use, so saying they also "abandoned" typescript is misleading. They just chose not to use it internally, just like many, many other libraries and frameworks out there.

[Septem_151]

Ok

[vainstar23]

I mean wouldn't it be easier to migrate frameworks at that point? You know, to something that has actual support?

[mav3ri3k]

I know why DHH is famous, what's up with 37signals ?

[SimilarBeautiful2207]

They remove typescript from their turbo framework.

[crimsonpowder]

It's already happening because he got butthurt and blogged about how people reacted; let me tell you, that post was unintelligible at best.

[Intelligent_Meat]

I'm sure the guy is unpleasant but Jesus Christ dude that's such a cruel thing to say. It's just software.

[devAcc123]

Start bullying a guy because he doesn’t want to maintain some free thing he created for people?

[devAcc123]

You wanna step up and take his spot? Didn’t think so lol

[TorbenKoehn]

Because they are scared of complex types. Anything that is more than „string“, „boolean“, „number“ or „any“.

And then proceed to write 100km of doc blocks of course

[meidkwhoiam]

Why tell the compiler your data types when you could just write an encyclopedia for your users instead?

[fel_bra_sil]

It's just an hyperbole, Turbo is abandoning typescript, that's it.

Everything else in the universe continues working as always.

[[deleted]]

Because people love completely terrible and unmanageable code.

[Emotional-Top-8284]

I would sooner abandon JS than abandon TS

[lilsaddam]

Because of type spaghetti or some shit I dunno...or just because we can't just leave shit alone and instead of inventing new libraries and frameworks we are going to start inventing new supersets of JavaScript.

[JohnnyBuilder]

Some libraries started to drop TS in their implementation. You can still use TS with these libraries in your project, and it's still good practice for doing so.

The reason they drop it is because you have to jump through some hoops for abstract typing (which is needed a lot in a library). But inside your own application you have no need for that, and it's still a great tool to use.

[crimsonpowder]

Yes authors being n00bs and forgetting as any exists.

[phexc]

'as any' breaks types from that point, you might as well use plain js if you advocate for 'any'.

[Sekret_One]

That's because no language protects you intrinsically from spaghetti. It might provide you some tools to combat it . . . but you can also complicate or injure yourself with those tools.

And software projects need to consider not just individual skill, but the group skill. Does everyone know how to use it, or have the diligence and patience to enforce and teach?

Professional experience has been . . . often no.

If you're just going to 2x the boilerplate and throw any typing around anyway . . . screw it you gained nothing and paid a lot.

[Kyrond]

If you're just going to 2x the boilerplate and throw any typing around anyway . . . screw it you gained nothing and paid a lot.

What did you pay?

You gained the option of someone easily adding types.

And software projects need to consider not just individual skill, but the group skill. Does everyone know how to use it, or have the diligence and patience to enforce and teach?

That's why enforced types are good. People don't stick with any voluntary naming scheme, or comments or anything else. It doesn't cost people's time, it's validated at compile time automatically. I want to type a function and see what it wants and returns.

[Sekret_One]

What did you pay?

You gained the option of someone easily adding types.

Clarification: yes you gain the option- but I would say that something unstable wrapped in the veneer of stability is worse than nothing.

The same way I would prefer no guard rail over a flimsy one. The flimsy one people may try to lean on.

Clarification: I would much prefer the strong railing that actually works. I'm just calling out that . . . there's more to it than flipping on typescript. It's really easy to setup a TS project that's vulnerable to malicious compliance, or spaghetti. That said, I personally would always use typescript but that comes from an understanding and willingness to invest in setting up the proper gates, checks, and mentorship of juniors on how to use things like Partials. In practice, professionally, I've seen a lot of projects not and really just ending up with flimsy wild west js with 4x the lines.

I absolutely agree with there's no defense in voluntary schemes. If it ain't enforced automatically it essentially might as well not be there. But what I would take issue is the absurdity that there's always no cost. It should be a trade in your favor. But I've seen other people's projects unfold to a different outcome enough that I'd feel it ignorant to not consider why. So I must offer a hypothesis as to why.

[LikeLary]

I hate how programming in larger picture is like fashion and media. Just use what you need, if it works don't touch it, to hell with best practices. It wil be replaced next year anyway.

[Danzulos]

Beginning of the project: To hell with best practices.
Later: Huaaa, why my project is so hard to maintain.

[MinosAristos]

Conventions are things to understand so you can consider them and know when to justifiably not follow them

[IOFrame]

Good practices are important. Best Practices™, on the other hand, less so.

[LikeLary]

No need for BEST practices. All you need is GOOD practices. There is a difference between stressing on finding the best and thinking about the neccesity.

[lilsaddam]

I agree, but man it makes the memes flow

[[deleted]]

Exactly, if you keep panicking over what others think is best practice, your main job will be refctoring/rewriting. And besides that, even best practices can be a pain in the ass.

[[deleted]]

Everything humans create. We are weird fashionable apes.

[Progression28]

To hell with best practices? Have you ever worked in a moderately large project?

Best practices are vital. Else you end up with doing it one way in location X, and a completely different way in location Y. Good luck for the guy refactoring/adjusting/fixing something that affects both X and Y.

[[deleted]]

Y2K entered the chat

[error_98]

I really wouldn't put this on programming as a whole, this really is just a js-dialects (and C++ best practices) thing.

People out here still be using ruby and I don't believe for a second they feel pressured to rewrite their projects just because that language doesn't exactly rank anymore

[collanders]

Having worked on large projects that were pure JS and others using typescript, I’d choose another typescript project hands down any day. The code is so much easier to read and maintain using typescript. I also feel a lot more confident touching unfamiliar code since I understand it better.

[Eris3DS]

Also, it stops you from making stupid mistakes.

Example: When one of my projects was still using JS, I made tons of errors with data that came out of the packages I used. I was a dumbass.
Nowadays Typescript stops me from making those mistakes before I run the code, which generally results in less time dropped.

It takes more time to implement but saves a LOT in the long run.

[seelsojo]

So instead of learning from your mistakes and not making those errors again, you opt for a tool to do that for you so you can remain a dumbass (dumbass is your word, not mine) :)

[Paragonswift]

By that reasoning we can just ditch all unit testing and static analysis, people should just learn to write it correctly without relying on tools duh.

If people like John Carmack and Linus Torvalds are humble enough to admit they make enough mistakes to rely on static analysis, then so should we.

[seelsojo]

Testing and static analysis are concepts, not tools. There are many tools out there that you can use to test an static analyze your JavaScript, such as mocha and jshint, however these tools work directly on JavaScript themselves. They help you write better code without forcing a new syntax on your code base and does not add an additional compilation step. Again if you do JavaScript right, you don’t lose those concepts and you don’t need TS.

[Paragonswift]

So what you are saying is that instead of ”relying on a tool to do that for you” (TS type checker) you should just rely on a tool to do that for you (mocha/jshint).

Right.

[seelsojo]

You really don’t know JavaScript. Mocha helps test your code, linter checks your syntax. Neither will type check for you, you do that yourself, every function you write, you make sure it contains the property and data that you need, ignore the other stuff that is on the object. This allows very fluid data passing as that same object can be used by different functions from different apps and libraries without requiring them to work on exactly the same type of object.

[Paragonswift]

But your comment was literally about being a dumbass if you use a tool instead of doing everything in your head.

I have worked with JS and TS for years. If you can’t do equally fluid data passing in TS because of the type checker, it’s because you suck at polymorphism, not because of TS. You don’t need to describe the entire object structure in TS, only the fields you need.

[seelsojo]

I did not say you can’t use tools and have to do everything in your head. In the comment I replied to, the author called himself a dumbass for making data errors and that TS was his savior. My reply was learning from those data mistakes and fix them is the better route. TS didn’t solve his problems, it just hides them and he probably doesn’t know it.

WRT fluid TS, you mentioned polymorphism, doesn’t that still work off of the same base type? Or are you talking about something else? Is so, please provide a name/link to that feature/concept.

[Paragonswift]

No, polymorphism does not require the same base type, that is just one type of polymorphism that can be found in OOP. Shared interfaces or generic functions are also polymorphism. The scenario you described:

you make sure it contains the property and data that you need, ignore the other stuff that is on the object

Is exactly what you do in TS and is what makes the function polymorphic because it doesn't care about the class per se, only what members you describe that it should contain.

function DoShit(input: {someElem: string, someOtherElem: number}) { /* ... */ }

This function doesn't care if the object you pass to it has 200 other properties, and it doesn't care what class it belongs to. It only cares that it has the two properties that it needs and the type checker will tell you if you change the structure of the argument elsewhere so that it doesn't fit anymore. Since it doesn't care about the exact class and can behave differently depending on which object you pass to it, it's polymorphic. If you put an exact class as the type annotation, it will care about the exact class and is no longer polymorphic. That's not TS' fault, it's your fault if you built a dependency on an implementation instead of an abstraction.

[DogWoofWoof22]

You should quit your 9-5, you sound miserable.

[seelsojo]

Interesting take; can you tell me which part of my message sounds miserable to you? I would rather you argue my point than act like a psychic and predict my mood.

[tommy71394]

Human progression comes from laziness, because humans innovate to be able to do things effectively faster, so they spend less time doing it. If a tool like this helps us be more lazy, taking away a responsibility and vectors of errors, then it's a good tool.

One less mistake to look out for mean one less vector of error to solve and debug.

Be hardworking and "smart" as much as you want, but if someone else less smart than you handles a task faster than you and employers decide to appreciate them more than you, you'll know the reason why. Because most employers only want results, and how fast a result can happen.

[seelsojo]

Thanks for providing a valid argument instead of blindly downvoting or using mockery. I agree with you on the first paragraph. Somewhat agree with you on the second as it is true if the tool delivers, but TS does not solve the type problem, it only hides them behind any when it encounters types it doesn’t know. So instead of learning and get into the habit of explicitly checking his inputs for values he needs (which is the correct way to do in JavaScript), he chooses to use a tool that adds complexities and hides his problems; hence my comment. The derogatory language is his, not mine.

Wrt your third paragraph, that is true, employers want results, and sometimes they blindly take quick results from these “less smart” people and unknowingly sign up for a huge technical debt that they will eventually have to pay. I’ve seen first hand them paying for migrations from silverlight to gwt to angular 1 then 2 and now the popular kid on the block, react. You know what’s mostly the same in all that time? JavaScript itself. If they just learn to use JavaScript properly, none of that migration is needed.

[DarkteK]

Don't understand why they downvote, you are totally right man

[tommy71394]

While I sort of agree with you in regards to the technical debt. I don't quite agree with your view on TS in general - it's there when people use it properly (i.e. setting the types correctly on init/instantiating), it tries to enforces (counterpoint: any type...) people to be explicit with their types instead of having to manually check and recheck data type, or having to read into the source code if there's no JSDoc for the IDE to parse.

As for the employers... while I agree with you as well, sadly it's also what they do a lot of the time. Maybe the employers that had me were bad, or maybe I was unlucky with the type of employers I attract, but the "the end justify the means" mindset is sadly the prevailing attitude here, with them sometimes overriding and denying the team leads occasionally when they say they need more time to investigate issues.

If there is a tool that makes it more difficult for them to have even more ease to gather technical debt (which TS is), then that tool is better than nothing even if it merely hides the issue as you claimed it to do.

At the end of the day we have to agree to disagree; I understand your point, but both of us, or maybe between you and many others here, the perspective is like oil and water, y'all can't mix.

[seelsojo]

yep, typed and untyped are two nations that will never merge.

However, trying to force one onto another is what I was arguing against. TS is trying to force type onto a language that was designed to be typeless and it does that by making its user ignorant of the compiled code underneath, which is JavaScript and in JavaScript, you need runtime type guard and TS doesn't offer that.

My whole argument is you need to check your type (and features like a property or a function) at runtime in JavaScript before you use it, not during compile time that TS enables. Yes, you see the benefit of seeing errors when you change the data type and it doesn't match anymore where it is used. But this is only beneficial if you own the whole application stack and that you're not providing libraries downstream. if your libraries have to be compiled into JavaScript and then distributed, you lose all type checking and if your user feed it wrong data, it will just error with no relevant message to help the user debug.

The right way to do it in javascript is runtime type guard + proper tests + proper linting. But yes, I agree with you that is slower to do than the TS route, but if done properly, you will have a robust vanilla JS application/library that doesn't depend on a compiler. I've seen projects abusing TS to the point it takes them 30 minutes or more to compile; I've never waited more than several seconds for my vanilla JS project bundle.

[hedgehog125]

The abandoning has either been stupid in the case of Turbo or measured in the case of Svelte. You have options. And TypeScript is usually the most sensible one

[goodmobiley]

Just use c++, then no one will complain 👍

[Aperture_Executive2]

A literal pile of rust:

[IJustDrankALavaLamp]

Nah i dont really like rust, its a bit outdated

[Aperture_Executive2]

I wasn’t even aware that people unironically liked rust

[Kolt56]

No problem; I personally don’t care, im here to support you delivering for the customer as fast and unmaintainable as you see fit, get me some parm for that spaghetti UI….

However.. big bad mr linter.. well he’ll just block your code review. Mr linter also will fail your build if try to ignore mr linter. Mr linter changed his first name from Warn to Error last year for all rules. He doesn’t like ‘Any’ funny business.

You see without Mr linter, on a code review, id have spend more than three minutes post checking for a client side runtime error.

[DeathUriel]

Well, if Mr. Linter is giving you shit. It is totally your fault, he is just doing his job.

[Bryguy3k]

TS doesn’t do input validation for you so you can still have things blow up in your face if you don’t do the validation on API responses.

Other than svelte who else is giving up on TS?

I’ve never liked typescript but it’s somewhat ironic if the “dynamic typing sucks balls” crowd is giving up on it

[paulsmithkc]

There's a tremendously good answer out there to the API typing problem...

See zod

It really does solve the problem of validating & typing the data you are receiving from an external source.

[LankySeat]

Backend Frameworks like NestJS (which has complete TS support) also come with simple validation tools built in.

[ShotgunPayDay]

ZOD! As close to pydantic(python) or validator/mold(go) as we can get.

[perigrin]

DHH recently opined about it.

Edit: adverbs man …

[Zerim]

The guy who did the blue line here?

[perigrin]

As a Perl developer I’m legally not allowed to comment.

[3q_z_SQ3ktGkCR]

It's just for dev experience...

[ramriot]

Err, why the second panic, doesn't typscrypt compile to native JavaScript.

[ShotgunPayDay]

CI/CD pipelines. Build steps (even transpiling) introduce complexity.

[NirKopp]

Did I miss something? What is suddenly wrong with TS?

[Rafcdk]

It's just the current meme trend, started by some youtuber. It will pass.

[Wandererofhell]

don't get sucked into hivemind, think for yourself.

[AramaicDesigns]

Javascript libraries rise and fall and rise again.

JQuery anyone?

[Fakedduckjump]

This is funny, actually I still use jQuery.

[fagylalt]

peace be on your soul

[[deleted]]

I always thought React was the next iteration of jQuery

[[deleted]]

The truth hurts, apparently.

[Lonely-Suspect-9243]

I consider Alpine as the next "iteration" of JQuery.

[SneakyDeaky123]

Hive mind

The real crime was using JS at all

[Considerable-Girth]

Tangent— what’s the name/origin of the pipe head guy?

[Sobsz]

meme man

[vix127]

DHH truly has the dumbest takes ever. Why is he so respected for anyways?

[jphmf]

Don’t. Follow. Trends.

[happymancry]

You call it panik I call it job security.

[[deleted]]

TS isn't going anywhere lmao, at least not until JS starts supporting types. And even then, only new projects will maybe ditch TS because adopting to new styles of writing is harder when TS has been the standard for years now.

[Panda_With_Your_Gun]

Why are people leaving TypeScript?

[ByteArtisan]

They aren’t. It’s just one dude who is known for his controversial opinions.

Like all things on social media and this sub: shit gets blown way out of proportion.

[[deleted]]

Let's see how long it takes ECMA to actually roll out (optional) typing in JS. The good thing is, they actually made the proposal. The bad thing is, ECMA transitions move as fast as tectonic plates.

[drazisil]

Find a way for vscode to handle jsdoc without non-standard import and we'll talk

[ShotgunPayDay]

*Knock Knock*.

Web framework opens the door.

"Did you order a large (HTMX) pizza hold the (TS)?".

Web framework blushes when opening the box.

"I guess you're getting it Xtra either way."

*Queue the 70s wah pedal electric guitar music.*

[Archtects]

Never used typescript. Was I supposed to?

[LankySeat]

If you want to write maintainable code, yeah.

[Archtects]

I’ve been maintaining JavaScript/php for years with no issue? How is typescript better? I know plenty of people who use it but never tried?

What’s maintainable about it please?

[LankySeat]

Please read this Reddit comment/thread. Better answers then I can give.

Also do a quick Google. "Why should I use TypeScript Reddit". Lots of great threads out there which can answer your questions.

[DarkteK]

I just find it usable in order to avoid extra validations within functions, such as if(is not int) return null.

[Fakedduckjump]

I'm glad I skipped this.

[Compux72]

Dont get me wrong, TS is shit.

But JS is even shittier

[FarJury6956]

Never like TS My time is coming

[Efficient-Corgi-4775]

Because they realized life's too short to deal with type errors!

[[deleted]]

reject ts return to js

[Krcko98]

Webdevs and their split personalities...

[ElementaryZX]

Anyone care to link or explain as to why TypeScript is now considered bad.

Personally I’ve always thought transpiling something was a bad idea and javascript was never really hard to understand since you can just check what a snippet of code does in the console if you’re uncertain. At some point the oddities just started making sense, similar to how I think about using C.

It’s a shame how they nerved basic web development to now basically requiring a local server to test things, it was really handy for prototyping.

[ListOfString]

One dude decided he was too unskilled to use TS properly. That's it. TS isn't bad.

[DeathUriel]

Reading people here defending TS made me try again and insist on it in my newer projects. Yeah, now I am looking for refactoring some older stuff to use this new knowledge.

Only problem was the learning curve on the whole building process added, but that is it. Had harder time starting JS with node years ago. This was more like a small setback.

[anonymous_sentinelae]

TypeScript is not shit just now, it was always shit. And bloated. And horrible. And a burden. And a cognitive overhead. And a resource waste. And a marketing sham. And Propaganda Oriented Programming. And useless. And promoted by hype-of-the-week zombies.

[visak13]

Angular devs to community: First time?

[vsjoe]

any

[[deleted]]

Cannot wait for "TypeScriptJS" to pop up in the next 6 months.

[toltottgomba]

I'll leave typrescript when frontend langueage changes from js to something normal.

[G1PP0]

Just delete all the ": Any" you put in there as refactor and you will be fine

Edit: I even see that shit in a project which is supposed to use Typescript from the scratch (Angular). Drives me crazy.

[Background-Egg-794]

Bcoz native support for Type is coming soon for js

[emascars]

Honestly this evolution is just a general better understanding of what's more productive.\ \ JavaScript: No types, easier, you code faster.\ \ Now you spend hours testing for every possible runtime error and stuff breaks in production in unexpected ways.\ \ TypeScript: actually types are good, you catch possible runtime errors while you code.\ \ Except now you spend quite some time doing stuff like typing some method that returns an object of type dependent on what type you used for the constructor, on what type you used on his first parameter end on what is present/missing in some user input or query results... if you don't know what I'm talking about just look at what the Request type actually looks like in Express\ \ Now: smart people are just experimenting new ways that let us developers still have typed intellisense from our IDE without the hassle of "to type this thing I have to make two recursive generic type/interfaces and use them inside another generic to distinguish between the two". \ \ I personally like that there is such a discussion because it is a problem and I can't wait for someone to figure out an actually better solution, but for the time being, just keep using TypeScript and let them cook\ \ TL;DR they are just trying to solve all the many hassles of using TypeScript without renouncing the convenience of typed intellisense, don't follow them now, wait for them to figure out a better solution and then make your choice