TypeScript is the condom for JavaScript.

Its typescript pal...

*codes in TypeScript*
*Only use type 'any'*

Typescript❤

How I feel when I need to switch back from a TypeScript to a plain JavaScript project.

fellow programmer: what did you write today?

Me:

TS humor

It's stuff like this that makes typescript the only way to write modern JavaScript.

4 all the JavaScript haterslovers:
Check out typescript.

I fell in love with it months ago.
😍

That moment you realise Typescript is not called Typescript because it has types but because of the immense amount of typing you have to do to get anything done...

What do you call it when you type a script? A TypeScript. Then you spill coffee on it...

now it's a JavaScript.

Typescript as a "Machine Learning" language wahhh???

Typescript be like

Any Typescript users here? I feel like it's not used as much as it should.

Completed Angular 2 course on codeschool, really liked improvements and simplicity of Angular over Angularjs. Decided to do quick start guide in official website. Oh my f**king god... I need to setup webpack, typescript linter, typings, polyfills etc angular2-cli is no better, crawling with errors... why... why can't one just start a project and work instead spending loads of timing configuring all of that... AND WHY WE CANT HAVE PROPER SUPPORT FOR LATEST FEATURES...

I don't even know what I am ranting about... I just wish to spend more time creating things than configuring for ages development environment.

Go home node.js you're drunk. You don't need 441% CPU just to compile typescript

You hired me to be a JavaScript developer. Just because you have stock inMicrosoft is not a good reason to try stuffing Typescript down my throat. Maybe you should have hired a Typescript developer!

Going back to JS after heavily using Typescript sucks so bad. :(

!rant

Other than typescript, what is the best language for back end development? PHP?

I cannot take this shit seriously.

I don't feel like reading the rest of it

Title: fuck typescript
1st line: well, actually I love typescript

Reason 47 to use typescript: keyof as a generic param allowing you to reference child properties

WHY DOES TYPESCRIPT EXIST OH MY FUCKING GOD WASN'T JAVASCRIPT ENOUGH

(just starting out on angular2 and i already hate it compared to jQuery)

Typescript be like

When someone does Typescript stuff using the "any" keyword

Hey, it's 2023.

If your component isn't written in TypeScript, I'm not using it :)

"TypeScript is overly complicated!!!" why, because it pointed out everything wrong in your JS code?

"TypeScript is not flexible!!!" why, because it makes you not rely on fragile "only possible in javascript" patterns?

"TypeScript isn't needed!!!" why, because you've never worked on a project with more than 100 lines of code where dependency management and clean code policies were implemented?

god just stop with the JavaScript purist BS, you aren't going to win this battle, and it's even worse because not only are you injuring everyone in the software community, you're injuring your own productivity and skillset

actually, you know what, fine. just use pure JS and HTML implementations. see you in 10 years when i'm retired and you are still running around in circles wondering why the world has left you behind

JavaScript is the ugly girl freshman year with glasses and acne. Typescript is the beautiful women she became senior year and won prom queen. Hate on JavaScript all you want because it was a language written in 2 weeks but the new releases with es6 and now typescript are a far cry from the js people were written back in the day. The times they are a changing -Bob Dylan.

It's interesting how much fun Javascript is, when you just ignore it and use Typescript instead. 😎

You've got to be a masochist to be a javascript/typescript developer.

Each time I come back to the npm-related parts of my project, the application won't start because of some dependencies nonsense. And I know for sure I left the project working perfectly last time.

Every time... every fucking time! Just leave the project unattended for a week and be sure you'll find it dead next time.

I mean I as a developer don't really have to do ANYTHING for my code to break.

How can people love javascript is a mystery to me.

Wanted to learn Angular 2, realised I'd have to learn TypeScript, System.js, and about 50,000 other frameworks before I could even do Hello World. Back to Angular 1 I guess.

Have a function that takes parameters and then performs a switch statement to determine what function to call next with those same parameters. One of those parameters is a Union type.

During CR, my reviewer said they’d like if instead of returning the function per case, I instead assigned a handler to the value of the function per case and then returned that handler at the end of the switch. Simple change, right? Only snafu, I’m casting one of the parameters on a per-case basis.

Somehow, through no fucking change of my own, TypeScript in its wisdom has decided that the type of that value by the time I call the next function is a fucking Intersection.

WHY THE FUCK DO YOU THINK IT’S AN INTERSECTION?! I’m fucking casting it per case! I’m ensuring it’s the right type for the next function called on a per case basis!

…. And that, my friends, is how I wasted a day with a stupid refactor that was ultimately just scrapped because no one could figure out how to make it work.

Goddamn fucking TypeScript. I

My new favourite languages:
Ruby
Rust
TypeScript

What's yours?

Have I ever mentioned how much TypeScript compensates for JavaScript's Lack of being statically typed?
It's. So. Much. Better.

if ( condition ) {
callback(data)
}
callback(error)

--is a lot different than--

if ( condition ) {
callback(data)
} else {
callback(error)
}

callbacks are not return statements 🤦‍♂️

I'm having such a blast writing code in TypeScript. Once you learn it you cannot go back to regular JavaScript.

Once understood javascript, it's not so bad. Particularly if used with Typescript

Learnt typescript, didn't knew that it's Microsoft

Why is Typescript such a snarky fuck?

a: number = 2;

tYpE Is TrIviAlLy InFeRReD fRoM NuMbeR lItERaL

Shut the fuck up you barely turing complete piece of digital refuse. Why does it bother you so much if I leave the fucking type on for clarity? This is almost as bad as my ex.

TypeScript and JavaScript

Friend learning typescript: JavaScript is easy, you do exactly opposite of what you did in java. Typescript is a half baked mess.

Started learning TypeScript and Angular2 today. Oh to be at the bottom rung again.

Well I guess it's official, I love TypeScript

JavaScript is a rollercoaster. From "Golly hello world is easy and I can make webpages now", to "wtf '1'+1 is '11' kill me now", to "it's not be that bad if you know how to use it", to discovering typescript and it starts feeling like a real language.

... until you can't build the project because you have too many types so you blow the memory limit in node. I can up the limit, but I can't guarantee that we won't blow past this in the future. Browsing issues on the ts repo reveals that this has been a thing for years.

Sticking with the rollercoaster analogy I'm now at "Burn it all to the ground".

I fucking hate TypeScript and Rust. I’d rather be working in C++

Been waiting for vue 3 to support typescript, even after it released the support isn’t that good. I’ll just hope it got better in the future

Typescript seems like such overkill, but then you need to refactor your code and hit a bunch of issues in production. I don't think I'll ever go without typescript again. Fuck dynamic typing, it doesn't scale

TypeScript...
An annoying "helpful" friend who points out your mistake even before you do it...

I've written two different real time audio resampling algos (called on source and called on target) using linear interpolation, both in typescript, both work on first try and both perform great. I feel like the omniscient god of web audio processing.

Typescript... Yay or nay?

You have a JavaScript application. You have to keep up with stupid devs that don't know TypeScript because you don't have the time to let them study it and they get demotivated when they can't do stuff so fine, you keep it JS. You use JSDoc to write the documentation. You miss using TypeScript so you start doing some @typedef's. Oh your linter gets it and starts behaving as a substitute of TypeScript. You get excited and write more and more @typedef's! ... until they get so complicated that you start documenting *that*...

Yesterday, we searched in our IT comunity Angular jobs. One of first jobs had these tags: angular, react, typescript and dart. How can programmer decide, when even the company can't decide what to use...

Thought I'd try out Asp.Net Core + React + Redux, at first I got shocked from the TypeScript shit I saw, but an hour later, I like what I'm seeing :P

Hey dear HR people and Headhunters - learn to write proper Joboffers - when someone is a JavaScript developer and even writes JavaScript for 10 years for a living doesnt mean he can or wants to write strict typed TypeScript out of the box using an library ecosystem and NOT a framework already written with TypeScript (React vs Angular)

Write TypeScript developers in the job offers when you search them: TypeScript !== JavaScript.

Today i spent one hour and half trying to understand why my ajax request was returning "undefined" instead of a json object. It turns out i had just to restart ionic because of some bug in the ts transpiler.

Fuck you typescript.

Java errors: if something is underlined in red in the IDE then it is a real error for sure

TypeScript errors: if something is underlined in red in the IDE then 50% of the time it is some 🤡 sh*t

Huh. Been using typescript for about a year. Had no idea it was made by Microsoft

Why I hate typescript. Bored during quarantine so thought I rant a little more about this.
1. Compilation time, typescript increases project compilation time from 1 second to 3-4 seconds, which is basically triple or quadruple the time if you don't know math.
2. You write a minimum of 30% more code.
3. Many libraries are not written in TS by default, which means you end up having to manually install a fuckton of @types/(pckg name) manually which is incredibly shit.
4. Typescript is an absolute pain in the ass when using dynamic libraries. Plus when it works, it usually ends up finding maybe 1-2 errors in your code MAX, completely not worth it.
5.JSDoc is 100 times better. (Still don't use it though).
6. I actually enjoy loosely typed languages, having your compiler being smart enough to tell what the type of your input is is much better than it assuming you're a fucking retard so it forces you to manually type everything.

P.S if you hate loosely typed languages, kindly resort to Angular, C#, Java or whatever and leave JS alone, cunt.

Today on "You're wasting your life by not writing typescript"

Union types

The value with redux, among other things, is incredible

Damn bro Vue 3 sucks actually. It's just a big function now with arguments like "`this` can be sometimes confusing when TypeScript is used." - hell no, my component was a class and this was the fucking class. nothing was confusing about this.

It's all a clusterfuck of magic now, I don't see why writing `ref(5)` or `return { all of your shit }` after `setup() { complete business logic inclusive functions here }` is better.

I was so looking forward to all the improvments, but why do we need these 3 apis with actually no difference, tried to be explained by the same image of colorful blocks in every single fucking article?

what happened to methods? am i seriously supposed to return them from a function? that just feels wrong.

I need to create a npm module for creating react-native app with MobX and TypeScript.
The whole setup is a nightmare.
create-react-native-typescript-mobx-app seems insane

What do you guys think about TypeScript? Does it worth time to learn the syntax? Also what is the relation between Angular 2 and TypeScript?

Typescript is pretty damn sexy

my frontend colleagues always keep amazing me with their create way of writing code:

```
const input = "a";

const result = {
"a": () => console.warn("A was selected"),
"b": undefined,
"c": () => console.log("hello")
}[input || "c"]?.();
```
Poor man's switch construct ... (facepalm)

typescript, I HATE you!

ME: Trying to extend Subject and override Subject.subscribe(PartialObserver<T>)

ME: export class MySubject<T> extends Subject<T> {
subscribe(obs?:PartialObserver<T>): Subscription {
return super.subscribe(obs);
}
}

ME: compile
TS: Compilation error! No such method to override!

ME: load the app -- ERROR

ME: recompile
TS: Compilation error! No such method to override!

ME: load the app -- works perfectly

:confusedjackie:

Make up your mind! So is that class compileable or not???
If not -- how the fuck does it work then???
If yes -- why the fuck do you yell in my face with all those errors???

I fucking give up. Typescript is not meant for complex projects. It's meant for simple projects that are big. There's no way forwards, no matter how much I try to simplify my types I simply can not get the typescript server to stop lagging out the moment I do anything complex. It can't fucking do it, it just can't. And that sucks really, really hard.

I'm so tired of finding the ceiling on everything. I had a bad smell for typescript when it came out... and I never should have expected any more than this.

JavaScript: You don't know what's going wrong.
TypeScript: You don't know how to make it right.

"I'm too freaking lazy to learn to write good JavaScript so I'm gonna build a top-language with types, and then a compiler so it transpiles TypeScript to JavaScript and runs my app on the interpreted language it was at first. I'm gonna save so much time" - 2017 people

One day after typescript , I ditch JavaScript on es5 totally and my college education on objective orient finally pays off ! !

I love functional programming but still insist that objective oriented is better for large project

First React project with ES6, already makes me want to switch to Typescript...

Typescript would be such a beautiful language if it wasn't for JS

Writing Node entirely in TypeScript. Mini MEAN stack front and back entirely in Typescript... What a beauty 😍

Joys of TypeScript.

(Notice the letter case of the first character of the type name.)

So today I told my boss “nodejs without typescript is like sex with strangers without a condom. Sure it’s fun and all... but then you get an std”

The state of JavaScript in 2024.
More frameworks, more minor syntax shortcuts to make code look more like emojis

?= := ?? .? =~ ;-P

but no native typing

so that devs can go on fighting about "JavaScript vs. TypeScript"

Hiii devRanters, I have a TypeScript question for you...
How do I dynamically import classes?

I have a class like this:
export default class Foo implements Bar {
...
....public getName(): string {
........return this.name;
....}
}

and then I have another file with this:
import(`./class-cmd/${file}`).then((command) => {
....winston.debug(command);
....winston.debug(command.getName());
});

the first command spits out something like this:
debug: default=class Foo {
....constructor() {
........this.name = "foo";
....}
....getName() {
........return this.name;
....}
}

and I would expect that the second command will work, however it throws this:
UnhandledPromiseRejectionWarning: TypeError: command.getName is not a function

Any idea what I might be doing wrong?

I definitely didn't need/want typescript in my life

I was working on a thing at work which routes http requests from one endpoint and port to several local services.
I was halfway done when I noticed I just wrote a primitive reverse proxy.

Anyway, I'm calling it GRID, Gateway for REST Interface Distribution.

It's capable of dynamically attaching new routes and services and removing those during runtime via inbuilt typescript compilation service.

Each "runtime module" defines several routes which may have a middleware function (express.js style), which gets executed before forwarding the request to the local service.

I don't know why, but I'm kinda proud of this one; Feels like I made something actually useful for once.

Gonna maybe add a webUI with the monaco editor to write typescript modules without needing VSCode...

Also I may implement a load balancing system for scalability.

It comes with a cli too.

Gonna put it on github and post it here once I'm done with v1.

Who was working for 20 minutes without TypeScript compiling and wondering why nothing was changing: this guy 🙋🏻‍♂️

My dev lead is a uniquely poor leader with an impressive ability to produce a large amount inflexible, temporarily functional code.

As we're in another pair programming session where I try to keep him from destroying over all type safety and architectural decisions to meet a self imposed demo deadline, he keeps trying to access properties of his state.

This state object is incorrectly typed with an anonymous type with incorrect properties.

Despite repeating calmly stating that the object is incorrectly typed, and that's why there are red underlines when he tries to access a property he knows is in there, he insists that that's not correct.

Finally, he knowingly says that he's figured it out and that he's been doing this for many years.

What was the solution you might ask? (state as any).myProperty;

Truly breathtaking mastery.

Just came across a function with a typo (this is in TypeScript) - let's call the function slightlyComplicaedName - see the typo? t is missing. Wanted to refactor the function name to fix the typo. Next thing I know, the project doesn't compile anymore. There was already a function called slightlyComplicatedName in that file and it was doing something completely different.

I get that naming is hard, but using typos to differentiate between functions seems too much :)

Best: VSCode, Typescript, Webpack
Worst: mov ax, bl

I fucking hate TypeScript

If you're part of the TypeScript cult, go fuck yourself too

Sometimes I wonder what the hell I'm up to

Well Done TypeScript! :D

Dear TypeScript, could you not have chosen any other extensions rather than .TS? Apparently telesync have been using .TS for IDK may be decades. But all you could go with was .TS?
Now Windows Explorer keeps on thinking .TS is a telesync file thus it keeps on trying to load a thumbnail for the files whenever a folder with .TS files are opened.

I knew AngularJS, just learnt Angular. Realized what typescript is and how amazing it is. I am a .Net guy so creating lambda functions in typescript made me excited lol. It's a little frustrating to write "imports" in every TS file though. Can now add ✔️Angular and ✔️typescript to my resume 😉. Starting with Vue.JS as soon as I am done playing with Angular.

Me, rueing typescript: "Dammit, Typescript!"

Typescript's cheeky response: Type 'string' is not assignable to type "Dammit"

ಠ_ಠ

I mostly work in Java as a backend developer, but lately I started a frontend side project in Angular. Man, Typescript and SASS are awesome! Totally love it :)

Typescript: All of your javascript code is valid typescript
Installs Typescript
runs typescript
Typescript: line x in function y has an error
Checking the function for error and the code is fine
After wasting an hour comment out all the linez in function y
Run typescript
Typescript: you have an error on line x which is commented in function y

ERROR IN A COMMENTED LINE :(

TypeScript should be its own language and not a “wrapper” for JS.

What does a Typescript developer tell Javascript developer ?

"You are not my Type"

I'm a node JS developer, but I basically don't use Typescript but with the whole buzz around the technology, I feel I'm doing something wrong by not using Typescript and refusing to learn it. What do you think?

10 hours later...

"FINALLY, I'M DONE SETTING UP TYPESCRIPT CONFIGURATION"

I was heavily inspired by typescript syntax, but the configuration is as complicated as webpack. Damn you frameworks

I am curious if this companies hiring requirement would be a red flag for you. They want at least one year of Typescript experience. Fine. They would not consider a person with 5 years of Javascript and zero Typescript experience.

I totally forgot how bad working with JavaScript is. After like a year of working with properly typed TypeScript base where navigation and documentation works very well, now I am in a world where IDE (IntelliJ IDEA) does very little, essentially it's just now a stupid editor. After few days I miss TypeScript already.

I honestly treat JavaScript as a binary executable format nowadays. It's an output format for me.

I choose you, TypeScript.

I implemented the equivalent of “?.” In typescript with a function callled safeRetrieve(descend into the field only if the object is not null).

We could not update typescript, so I just created this function and it made me used to use ‘keyof T’ as a parameter type… I still feel very satisfied after I use this approach with anything because it really feels like using typescript correctly!

TypeScript is like the bumper of the Victorinox Inox.
Protect the watch, but it looks horrible.

I started making a library to get to know TypeScript. 4 days into the commits and I don't know if I made the best choice or the worst choice. I MEAN WHY CLASSES!! JAVASCRIPT IS MORE A FUCNTIONAL PROGRAMMING LANGUAGE THAN AN IMPERATIVE PROGRAMMING LANGUAGE! I DONT WANT TO NEW UP! I DONT WANT THE DEVELOPERS TO NEW UP! WHERE ARE THE DESIGN PATTERNS! I CANT FUCKING FIND IT!!

We are starting a new project where we decieded to use node.js with express.js. It is quite exciting because we have previoisly use node.js only a little and me and my colleagues are eager to learn something new. As I was doing some research I came upon TypeScript. Do you guys think that it is worth spending more time learning TypeScript and use it in upcoming project?

Discussing with the boss:

boss: < How is it going? >
me: < I'm trying to rewrite this horrible javascript code with typescript >
boss: < But release cannot support typescript >
me: < I can compile typescript locally and then release >
boss: < You are not listening to me! we can not execute a script in typescript >
me: < In fact we will use a script in javascript >
boss: < So why are you rewriting it in typescript? >

And so the discussion continued for another 20 minutes...

There's plenty of literature about how to emulate classes and interfaces flawlessly in JS even without es6, but no, let's make a separate language using 20 extra keywords and several unnecessary concepts called TypeScript with its own compiler.

Typescript - made me think before I type.

Microsoft for creating typescript, and google for maintaining angular and forcing people to learn typescript before learning dog shit angular

What should a programming enthusiast be told, when he asks "Is learning TypeScript worth it?"

typescript and me is a love/hate relationship, almost toxic at times

Omfgggggggggggggggggggg
Fuck you typescript.

A whole day wasted working on react native pull to refresh bug, wondering why the fucking hell shit doesn't even appear when u try to pull. And so many other weird shit like touchable opacity not showing up.

Guess what was the problem? Fucking typescript importing shit from react-native-gesture-handler.

Btw I live and breathe typescript. I appreciate typescript everyday but for today fuck you typescript.

A tool widely use and been perceived as a superset of JavaScript does not have a FUCKING language specification, we have no single clue why certain things are done the way they are done. All we FUCKING do is guess.

Fuck typescript

I feel like it might be a tiny bit (not much) better among React developers, but I ended up within one of those enterprise Angular till death companies, and it seems like nobody would ever doubt their Typescript skills, yet nobody actually understands Typescript at all.

In theory, I love Typescript. But you can abuse it to a point where it's almost as painful to work with as normal JavaScript.

It's not that I'm a master of Typescript.
But while I feel like I'm the only one understanding the mental model behind Typescript and also get stuff like mapped types or why you might wanna replace your enums with as const assertions, the rest calls themselves Typescript developers in their CV, no doubt. But It's way to easy to write whatever Typescript, while it's not as easy to reel get the hang of it.

A TypeScript boolean/undefined Flag variable kept fucking up
true == true didnt hold true

checked the "typeof" in console and it's GOODDAMN STRING.
What's the point of TypeScript's "type safety" if a Boolean variable is holding a String type for whatever reason. URGHH I HATE JAVASCRIPT.

I just got told that a codebase written in javascript / typescript can't be built to last.

This is the type of rediculous stuff us Web Devs have to put up with.

TypeScript is basically Grammarly for JavaScript

I want to use Babel or Typescript for the first time. Because as I read it is the way to go, when compressing JavaScript and make it browser compatible. If that's false, please correct me.

There's a question I've got about this. Right now I am using a PHP router file dealing with requests and selecting the right .js file and compresses it. So I can write like modular JavaScript functions and include them when needed.

My question is, what do I have to change in my setup to switch to the mentioned technologies?

Angular 2 is really, really satisfying me. Such a very clean and smart way to organize web functionality! And es2015 + typescript is sooo nice to work with.

I just built a TypeScript microservice and got a heap out of memory fatal error. What the actual fuck? Micro my ass

Attempting a huge undertaking. I'm trying to convert a large JavaScript library, written in standard ES5 syntax, to Typescript with ES6 syntax. Turns out it's extremely difficult, but if I can finish this it will be 100% worth it

Every time I try to use TypeScript for something, everything I learned a month ago is deprecated. Tsconfig keeps changing. The way to get and set up definition files has changed like 5 times now. From downloading, all the way to referencing. Can we please just settle on something now?

Why developer of c# (Anders Hejlsberg) when developing (TypeScript) not implemented method overloading and interfaces' methods implementation with same names.

Fuck ESLint. Fucking JavaScript. Fuck Typescript. Fuck everything.

Do devranters think that Reason(ML) is too late to the game to compete against TypeScript...or can it ride React success to become more than a niche?

Personally I like it, but, like with F#, I don't enjoying the lack of resources every time I need to get something done.

Reading OpenSource lib that write in TypeScript is a nightmare

WTF:

export function concatMap<T, I, R>(
project: (value: T, index: number) => ObservableInput<I>,
resultSelector?: (outerValue: T, innerValue: I, outerIndex: number, innerIndex: number) => R
): OperatorFunction<T, I|R> {
return mergeMap(project, resultSelector, 1);
}

That is just fucking definition, no execution code inside

Dear Microsoft, you are the one who created VS Code, Typescript. How could you possibly screw these things up? VS Code intellisense is terribly slow while working with Typescript but works so well when working with flutter/dart or any other programming languages. Shouldn't you be the one doing the best? Shouldn't you be doing a better job at something that you created? How could you mess it up??

Typescript integration in Visual Studio SUCKS!! I waste so much time fucking trying to set up Angular 2 boilerplate that would take almost no time in VS Code or another editor because this bloated piece of garbage has to try and hack everything into MS build tasks and "Virtual Projects".

You would think that the company that created Typescript could figure out how to integrate it properly into their flagship IDE!!!

FUUUUCCCCCKKKKK!!

I have a recurring problem with Typescript where I can't search types for errors because all search engines are flooded with questions and articles about type checker errors.

Question: We are planning to transition our old ES5 codebase to modern ES6/ES7 and even typescript.

What would be the build tool you would recommend if we want to start supporting ES6/ES7 and even Typescript?

Webpack, Vite some other?

This is a vanilla Javascript Project with large codebase it's been built using custom build tools like UglifyJS and UglifyCSS and of after lots of begging it finally got the green light to move to a more modern build tool and start supporting a more standard JavaScript Features.

Mainly I want to move to TypeScript but transition would be slow so the build tool would need to support .ts and .js as well, that is traspile both the .ts and .js into one final production build.

What build tool would you recommend for that?

Migrating to TypeScript. Seems "fine" so far..

*PLEASE SEND HELP*

For fuck’s sake typescript !

My friend was asking can Html, Css , Typescript and C# be use in web/app development together....
PS. Who can answer this and vote...

TIL the only way to extend Monaco is to TypeScript

mfw

Strongly Typed TypeScript

May the developer Gods have mercy on me

Typescript 2 makes types non-nullable by default! 😎🎉👍

Frontend JS devs - did you take the plunge into Typescript?

I've done some reading and a simple intro course but I'm still on the fence, what pushed you over the edge to adopt it?

My colleagues want to forbid the usage of the shorthand constructor in TypeScript.

I feel strongly about this.

At least they find it annoying that I call the more verbose one "PHP-style constructor" :D

Started using typescript and other than the toxic wasteland that is NPM, I'm actually quite enjoying my time. Fuck javascript in the ass, typescript is like a nice dick pic to that ex who called to threaten your life for the third time that day. Different phone numbers every time too. Fuck JS.

As a Software Design junky, I just enjoy using TypeScript for more conventional C-style programming structures in JavaScript !

Typescript is like a condom that has sideways with passages to flow the stuff ! Which is basically a bloody condom with hole ! WTF 😑 .ts to .js !

You just want whole bloody damn Java to be implemented at client side ..😣 God bless us .. Hate u Angular ... I loved you like hell now u hokkin up with this hoe ...
Hail JavaScript !

Bro typescript is sooooooo gooood...
holy shit!
coming from a cpp/java background it feels like a fucking relief to know something like typescript exists and you dont have to blindly trust the dynamically typed crap

Someone explain typescript to me , I still don't get why we need it?

Why I don't use Angular?
Angular = TypeScript
TypeScript = MS
I will not support MS in any way.

MFW I worked longer than 8 hours because of a weird bug that turned out to be caused by lack of typing in a third-party library. Was supposed to be a number but I was giving it a string 🤦‍♀️Need more sleep.

The funniest part is the library was written in Typescript. HmmMMMMmm...

Throw a `parseInt` or warning for wrong type in there for me, fellow devs! Save consumers of your library a headache!!

“Typescript is bulletproof, I have no consistency at risk”

“…”

“guh”

WHY DOES TYPESCRIPT AND TSC HAVE TO RUIN MY LIFE?!?!?!?!?

well folks, i've truly seen it all. an impressive an informative post on all there is to know about TypeScript, about time, since it's only 2023 and I've been waiting for this for so long!

...

"note: the syntax" 😂

remember that at the end of the day, this guy is employed, and i am not...

in all seriousness though, it's mind boggling to me these companies that market themselves as software or developer companies (or "professional" developers themselves) STILL aren't building their web apps using TypeScript

inb4 javascript maximalists / purists - come back after you've built and had to maintain multiple 10K LOC webapps and tell me that typescript didn't help you

🤡🌎🤡🌎🤡🌎🤡🌎🤡🌎

Today I saw how the frontend devs on my team write Vue components + TypeScript. It's bad and it further proves that Vue=bad. Not even TypeScript can save it from being bad. Function defineComponent is ugly

What's your opinion on TypeScript? I'm having a hard time figuring out if it's worth using for a React side project

Typescript is amazing, but this little snippet

NaN === NaN // false

Drives me fucking crazy

I am currently using angular from 1.5 years. With angular 2 coming to production i was thinking of moving to it.

But i have some questions:
I am hesitating to move because it encourages typescript over javascript. It adds 1 more dependency to my code ( code will break after angular updates and also when typescript updates).

I do not have any such problem learning vuejs or reactjs.

So, which one do i choose.

I'll preface this by saying that TypeScript is a beautiful language.

But also UTTERLY INCOMPLETE.

Here's what I'm trying to do: give the compiler well-defined contextual type information for a decorator's argument (a lambda signature) and for the decorated class method, so the user would not have to toil and type every single argument.

But does that happen? No.

I'm honestly disappointed.

Fuck you eslint:

* Missing semicolon.eslintsemi

* Unnecessary semicolon.eslint@typescript-eslint/no-extra-semi

How do you feel about using TypeScript with React? I appreciate the benefits, but, as every snippet of React code everywhere on the web is vanilla JS,I just don't want the cognitive overhead.

Yes, I know TS is JS, but, if I'm not going to use the features, why bother? I'd want to strongly type props, state, etc.

What's the status of TypeScript support in the React ecosystem (eg Router, MUI, etc.)?

I'm kinda hoping Reason will get some traction as the type inference is much better, but, will that happen? Or is that going to fizzle so it's a choice between TS and JS?

Appreciate any thoughts on this---including those from anyone who's in the same boat.

Looking for views on TS in React ecosystem---no need to sell me on TS in general.

Anyone know how to go about unit testing an application that is made up of:
- Electron
- Node
- React
- Typescript

(React using Typescript of course).

Electron has its own framework (Spectron), people seem to use Mocha with Node, React has its own tools like React testing library (and testing UI components will probably end me) and Typescript seems to play best with Jest - but a special Typescript flavour of Jest called ts-jest is preferable because the only other option is having Babel and its Typescript support that doesn't type check.

I want to beg for the sweet release of death.

Typescript is a PIECE OF SHIT that adds 3 problems for every 1 it solves! Messing with so much shit from its linter and builder just so some OOP fools can code JS like *TAB* *TAB* *TAB* again!

I'm a Ruby on Rails developer. I love Rails because you can get so much done so quickly. I've built huge websites on Rails at the consultant shop where I work.

A couple of years ago we added a frontend guy to the team. We switched from doing full stack Rails to using Rails for API only with Vue with Typescript as the frontend. Since this transition took place, I am unable to get anything done on frontend. It takes a huge amount of effort to just add a new input box to a page. Our whole team is on the edge of getting laid off because we can't get things done in a timely fashion for clients and our products consistently run over time and over budget.

Here I'm trying to add an "Are you sure you want to delete this?" message to a form, and I'm on third hour trying to make Typescript happy. I want to assign a variable a value and I have to decipher errors like this "Type 'Ref<string>' is missing the following properties from type 'Vue<string, Record<string, any>, never, never, (event: string, ...args: any[]) => Vue<Record<string, any>, Record<string, any>, never, never, ...>>': $data, $props, $parent, $root, and 30 more." WTF?!?!

Am I just not smart enough for this? Why did programming suddenly become so hard for me? If I had to start off this way I wouldn't be a programmer because I wouldn't have been able to figure this out alone and it wouldn't have been any fun. Anyone else have the HATE for Typescript that I do?

Say what you want about Angular, but this framework made me like Typescript.

Am I just stupid, or is typescript just terribly overengineered?

Some new t-shirts would be great like Angular, TypeScript, Unity etc..

Elm vs Typescript & React & MobX start the fight *_*

Productivity Hack: I'm a java developer who decided to write a productivity app that integrates to-do, pomodoro and eisenhower matrix altogether with reports generation. this will also help me logging at work. I'm also using electron + angular2 + typescript, just because, well, I'm trying to learn new stuff.

Long story short, many many many many days later, i'm still waiting for that productivity boost. What is dis webpack? Wat u mean loaders? Wat promises? electron-prebuilt is now electron? Wat u mean npm and node should be updated? .....

Please send help

Should I move up to typescript from vanilla Js for mostly framework-web?

im gonna find the guy who invented typescript and throw him into a vat of butter

People trying to force using Typescript... I crie ebrytime :*(

Teamleader : just add TypeScript.
Me: Uhm okay?, someone has expirience with that?
Teamleader: No, just do it .

After 15h of trying adding TypeScript to the React / Redux App I ve to tell him that i couldnt do it.

So now I think that i am stupido as fucko..

I'm using typescript and run mocha acceptance tests. I was confused as to why my tests were failing on the Jenkins albeit they passed locally just fine.

I couldn't find the error. Just after making a pause, implementing something else, I realized what the problem was:

As I renamed a folder from `fixtures` to `tapes` my test run on the Jenkins suddenly claimed to not find the files in `fixtures`. Yet in my code base there was no occurrence of the string `fixtures` anymore and then it hit me like a brick wall:

I have old transpiled files in my outDir, the `dist` folder on the jenkins! Locally, I make sure to run `git clean -fd` once in a while, so I never was hit by it it locally. Yet my jenkins had really old files in the `dist` folder. And just running `rm dist/* && tsc` fixed the entire ordeal.

Well, JavaScript is so 2012 and typescript is the new shit, yet transpiling the code can leave to some quite strong headaches.

Node Js Typescript dependency management makes me want to hang myself

I'm new to angular but I'm using it with typescript and it's so horrible

So maybe stack overflow is better for this...but it's kind of ranty too so here goes.

Any react + typescript devs here? Cause I did something dumb. I ejected the project because I needed to build a custom express implementation...long story short, I can't run a webpack react dev server or use hot reload. Which is a PAIN! If I wanted to wait for a full TS and react static recompile after changing a css prop....I wouldn't be in the web game!!

Has anyone else had this and fixed it??

TypeScript types are fun. Problem is: the check is compile-time only.

I just wasted an hour not understanding that an integer passed from command line was actually getting transmitted as a string. The library, where that value landed as parameter, happily ignored the non-matching type and worked as if the value has not been set at all!

Dear library maintainer, please enforce your parameter types! Throw an error right into my face saying I shall not pass anything but an integer! Don't just continue to work to produce false output correctly. Thank you!

Dear TypeScript, I really want type checks on runtime.

Dear JavaScript: Why did you ever think loose types were a good idea? (And I say that as a PHP developer as well.)

I have the will of migration from Javascript to typescript but i don't know where and how.

When elements of an union are distinguished by a boolean, VSCode's Typescript plugin can only do type elimination if I branch by "== true" and not if I just branch by the boolean.
This is because Typescript treats booleans as an union of the constants "true" and "false", and compile-time elimination can only be done if I use syntax that makes sense with unions. Logical evaluation, for some reason, doesn't.
The fact that this issue can even appear is deeply concerning.

I dont know if i should learn typescript, i really like how it shows any error if you have done some mistake in the code in realtime. But it seems kinda hard and its not used that much at my office work. Should i start learning now or should i focus on strengthening my react skills for now? I work on react and javascript on daily basis.

I've heard "someone" saying, that typescript and c# are somewhat similar. Now I've never worked with c#, but I still doubt it. What do you, human of devRant, think?

TypeScript! Why you default compiler option "pretty" to false!? Why would anyone want this as false? This is such an amazing feature disabled out of the box! GNARF!

I USED TO GREP FOR ERROR TO GET ERROR HIGHLIGHTING!

:/

I didn't realize how mediocre autocompletion for python on vscode was until I started writing typescript on it. I think I'm gonna give PyCharm a try

I look at the "Discover Repositories" sidebar every time I log into github. I've found some really cool stuff that way.

But I'm really confused as to why I keep getting typescript-related repositories there.

I've never created a ts repository
I've never made a pull request that had ts in it.
I've never created an issue in any ts repositories.
I've never even written a single line of ts.
The only reason I can think of is that I was browsing the official typescript language wiki for a few minutes...
A COUPLE WEEKS AGO
Yet sometimes, all 3 repos in the side bar have typescript in the title.

TL;DR: github, please stop pushing typescript on me.

Does anyone have a good 'getting started documentation' for react redux with typescript. youtube videos and official documentation are mostly ES5.

You know the feeling when your mom come to visit and then start reorganize your stuff and complains about the way you choose to live ?

That how I feel when TypeScript come into my code and start reorganize my functions into Classes and bug me, all the time, about the types I must use to active there function

( thanks to Angular )

I can not wait for the day till JavaScript can be thrown into the fiery pits of hell and we can just use wasm or even have the browser just support typescript natively.

when some lib using Typescript they think that they can show in the top of the page function with the full fucking complex signature and that explain everything you need to know about what the function do and how to use it !

what about some simple basic signature, table of attribute name and meaning. and some good examples

like we have then on the old day ??

Day1: It is really awesome to give data types for the variable I am about to use in typescript

Day1(few hours later): Let me declare all variables with type 'any'

IT SHOULD NOT BE THIS FUCKING HARD TO COMPILE AN ELECTRON APP WITH TYPESCRIPT

What's the point of using TypeScript if you type all of your code with `any` or worst part is you don't provide any types!?

P.S
If you're anti-typescript or any static linting tool, I know this will not prevent any runtime errors, but this is part of the testing/code quality. My teammates do not care for quality, and I'm tired of it.

You know what?? Fuck typescript + mongoose