Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "typescript"
-
The brief history of Facebook open source:
- FB releases React under an oppressive licence that tells "woopsie, can't sue FB if you use React"
- a lot of money goes into making React popular to gain leverage from mass adoption
- VMware bans React in their company
- FB releases Flux to bring state management. It flops. Replaced by what some Russian student wrote in several evenings (Redux)
- Preact is released. It's faster than React, and it has MIT licence. Vue beats React in GitHub stars.
- Under mass pressure, FB changes React's licence to MIT. Initial plan to gain leverage fails spectacularly.
- FB releases Flow Types. It flops. Replaced by TypeScript.
- FB releases their own app market for React Native. It flops.
- FB releases Relay. It flops. Replaced by Apollo.
- FB tries to push React.Suspense for the whole JS landscape to obey and comply to how it works. Community says "Fuck You".
- FB releases react-native-web. It flops.
- Web Components are out in all browsers, adopted as a standard. React doesn't support them.
- Google releases Lit, a virtual DOM framework on top of Web Components to fuck with React. It's a massive success.
- React 18 is out. Still no Web Components support.
- (you are here)17 -
It hasn't even been two weeks since quitting the clowns and I've:
- recorded and edited a new React TypeScript course
- released a new SaaS product (in alpha)
- cleaned up and optimized the home page of an existing SaaS app
- started a mobile app version of said SaaS app
- started working with an agency to drive more traffic to same said SaaS app including guest posts and content creation.
I guess I always had it in me but needed to be broken by the rate race system one final time before venturing out on my own.
Refreshing.10 -
What do you call it when you type a script? A TypeScript. Then you spill coffee on it...
now it's a JavaScript.5 -
In the Ruhr area (Germany) we have some very old, very strange words with strange meanings. One of those words is ‚Prutscher‘.
A Prutscher refers to a person who does things but never gets a good result, due to lack of knowledge or simple carelessness. Most of the time, Prutschers are people who are interested in certain subjects and often work in the related jobs, but who lack the motivation to properly train themselves, learn what there is to learn and to always keep up with their technologies .
Here are a few examples I've stumbled upon so far in my career:
- Developers in their 60's who read a book about PHP 25 years ago and decided to become a software developer. Since then haven't read anything about it. Who then now build huge spaghetti monoliths for large companies, in which they prefix every function, every variable and constant with their initials and, of course, use Hungarian notation.
- People who read half a fucking tutorial about <insert any fancy js framework here> and start blogging/tweeting about it
- Senior web developers who need to be told what the fuck CORS is and who can't even recognize CORS related errors in their browser console.
- People who have done nothing else for 18 years than building websites for companies on Wordpress 1.x and writing few lines of PHP and Javascript from time to time. Those who are now applying as a frontend dev due to the difficult economic situation and are surprised that they are not accepted due to a lack of experience.
- Developers who are the only ones working on Windows in the team and ask their Linux colleagues for help when Windows starts bitchin.
- People who have been coding for 30 years, have worked with ~42 languages and don't know the difference between compiled and interpreted languages in the job interview.
- Chief developers at a large newsletter-publisher who think it's a good idea to build your own CMS (due to a lack of good existing ones, of course).
- Developers who have been writing PHP applications for multinational corporations for 25 years and cannot explain how PHP is executed. They don't even know what the fucking OPcache is, let alone fpm. FML
- People who call themselves professional developers but never ever heard of DRY, KISS, boy-scout rule, 12-Factor App, SOLID, Clean Code, Design Patterns, ...
- Senior developers wondering why the bash script won't run on their fucking Windows machine.
- Developers who consider Typescript to be a hindrance and see no value in it.
- Developers using ftp for deployments in 2022
- Senior Javascript Developer applying for a job and for whom Integer is a primitive data type in JS.
- Developers who prefer to code without frameworks and libraries because they are only an unnecessary burden/overhead and you can quickly code everything up yourself.
- Developers who think configuring their server(s) manually is a good idea.
You fucking Prutscher. What you have already cost me in terms of work and nerves. I can't even put it into words how deeply I despise you. I have more respect for the chewing gum that has been stuck in my damn trash can for the past 3 years than I do for you guys. You are the disgrace of our profession. I will haunt you in your dreams and prefix every fucking synapse of your brain with MY initials.
As a well-known german band once sang in a very fitting song: I wouldn't even piss on you if you were on fire.
If you recognized yourself in one of the examples here: FUCK YOU!38 -
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 behind28 -
I met a programmer in an online dating app some months ago. She worked with golang, and things were going nicely with us talking a bit.
Then I mentioned that I currently work with Typescript and NodeJS and she stopped responding 😞
Should have posted this as story, since this is not actually a joke.12 -
BE GONE CLOWN!!!! MAY YOU BE CAST BACK UNTO THE DEPTHS FROM WHICH YOU HAVE SPRUNG!!!!!
🪄✨
👻👹👺
🤡
can't wait to be absolutely fuck you rich while the clowns continue to fumble around in the sandbox for the next 5 years 🪣⛏️😂😂😂
all those years, crouched over a laptop, learning React, then TypeScript, then PostgreSQL, then .NET, then React Hooks, then Redux Toolkit, then Golang, then GraphQL, and even RabbitMQ and gRPC mixed in... more and more and more............ IT'S TIME TO SPREAD MY WINGS AND FUCKING FLY BABY!!!!!
why work for clueless clowns when your own technical know-how is literally 1000x (or perhaps infinitely) theirs? Was I an idiot? Yes, I was! Way too nice and I bought into the hype fake idiot brain culture, but now I've finally woken up. Time to ascend to the stars by myself.
Cheers devRant, this 🤡 is finally going to transform into a 👨🚀🚀
You may not hear from me for a while sadly, but I'll be sure you guys get the first shoutout - see you on 🪐rant one knows limit saturn tag really going to break devrant tag limit no mars emoji manifesto clown no done with clown3 -
Fucking React Scripts, "yOu hAvE mUlTiPlE VErSiOnS oF bAbEL-JeSt, Use nPm Ls Jest To TrACk It Down"
Ok you dumb fucks:
npm ls babel-jest
react-typescript@1.0.0 /Users/chris/Downloads/8sleu4
└─┬ react-scripts@4.0.3
├── babel-jest@26.6.3
└─┬ jest-circus@26.6.0
└─┬ jest-runner@26.6.3
└─┬ jest-config@26.6.3
└── babel-jest@26.6.3
OH LOOK THEY ARE BOTH IDENTICALLY 26.6.3 STOP BUILDING AN OPINIONATED PILE OF GARBAGE IN YOUR COCONUT TREE FUCKED UP FALSE PARADISE YOU CALL SILICON VALLEY!!!!!!! I'VE NEVER SEEN SUCH A BUNCH OF GARBAGE!!!! I'D PREFER A TOOL WRITTEN BY KINDERGARTNERS IN CRAYON!!!!! AAAAAAAAAAAAAAAA
EVERY
SINGLE
TIME
REACT SCRIPTS
BREAKS2 -
I've been working on a proof of concept for my thesis for a few days and the async query calls drove me nuts for quite a while. I finally managed to deliver all query results asynchronously while still very much relying on a strong architectural design pattern. I am filled with caffeine, joy and a sense of pride and accomplishment.rant late night coding caffeine async await query proof of concept javascript boilerplate database typescript1
-
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. I3 -
I miss when my job was just about coding, I could spend entire workdays writing C# or TypeScript while listening rock or metal with few meetings in between, being very passionate in programming and computers sometimes I found was I doing so engaging which I spent more than my 8 hours workday on company's code base trying to improve it and my older coworkers were very happy with my code.
Then a "promotion" happened, I went to work directly with a client, a huge enterprise which is working on renovating his internal software and here the fun stopped. Long useless meetings are a regular occurrence, there are absurdly long procedures to do everything (for example since CI/CD is leaky we have to do dozens of workaround to get a microservice deployed) and having very little written documentation this gives an huge advantage to people which actually enjoy to spend their entire workdays on a MS Teams call over "lone programmers" like me which actually feel significant fatigue in doing that (alone sometimes I was able to log 12+ hours of programming daily between work and personal projects while after 3 hours of PP I feel drained) since the information passes in meetings/pair programming and I dread both.
I feel which my passion is still there, I still enjoy coding, tinkering with Linux and BSD, broadening my knowledge with technical books and having passionate conversation about tech but I dread my job, sometimes I try to look at it under a more optimistic eyes but most of the times I just end disappointed.3 -
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.5 -
What the hell is the point of using typescript if you are going to put any everywhere? Fucking useless.3
-
I was applying for a job that I really wanted, and were told to code an assignment. I sat for 2-3 days coding an e commerce app in react which was super fun and challenging, I think I made a pretty decent app. but after I handed it in and a couple of weeks later I got back that I didn’t make it further in to the process. The feedback showed that I missed some essential stuff and I mixed typescript and JavaScript even though it was supposed to be in typescript (I’m new to TS) :(
I feel so disappointed, I probably had too many things going on while doing this that I didn’t had time to review it properly before sending it in. Oh well, at least I have a nice job now (but underpaid)9 -
Hey guys, I published a package to generate typescript types from your BE specs that uses OpenAPI schema. Would love to have some feedback/improvement.
https://github.com/devTeaa/...4 -
It's rant time again. I was working on a project which exports data to a zipped csv and uploads it to s3. I asked colleagues to review it, I guess that was a mistake.
Well, two of my lesser known colleague reviewed it and one of the complaints they had is that it wasn't typescript. Well yes good thing you have EYES, i'm not comfortable with typescript yet so I made it in nodejs (which is absolutely fine)
The other guy said that I could stream to the zip file and which I didn't know was possible so I said that's impossible right? (I didn't know some zip algorithms work on streams). And he kept brushing over it and taking about why I should use streams and why. I obviously have used streams before and if had read my code he could see that my code streamed everything to the filesystem and afterwards to s3. He continued to behave like I was a literall child who just used nodejs for 2 seconds. (I'm probably half his age so fair enough). He also assumed that my code would store everything in memory which also isn't true if he had read my code...
Never got an answer out of him and had to google myself and research how zlib works while he was sending me obvious examples how streams work. Which annoyed me because I asked him a very simple question.
Now the worst part, we had a dev meeting and both colleagues started talking about how they want that solutions are checked and talked about beforehand while talking about my project as if it was a failure. But it literally wasn't lol, i use streams for everything except the zipping part myself because I didn't know that was possible.
I was super motivated for this project but fuck this shit, I'm not sure why it annoys me so much. I wanted good feedback not people assuming because I'm young I can't fucking read documentation and also hate that they brought it up specifically pointing to my project, could be a general thing. Fuck me.3 -
Fucking A.I. resume filter bots.
As if tech interviews weren't hard enough, I have to fill my resume with keywords to get past a bot! Every damn application and cover letter has to be unique.
And when I get past a bot, a hiring manager replies with "Sorry, you seem to have more experience with Typescript than JavaScript, and we can't take that risk."
It's the same.damn.language.
Yes, I spend my spare time with C and Python. Why does that say "unsuitable candidate" instead of "versatile"??!!
$#*%!?&@ tech industry.
Take your "Good luck with your future endeavors" and stuff it up your ass.1 -
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.3
-
Literally anything that comes out from Anders Hejlsberg, always liked what the dude brings to others. I fucking loved his work on the Pascal Programming language, back then it was all over the place in Mexico. I can only imagine that in the U.S it was just as big since a lot of mfkers in here are still pushing Delphi from what they found with Turbo Pascal.
His work on the C# programming language is absolutely incredible and C# is one of the best languages in my book. And I fucking adore TypeScript, so literally, everything this dude puts out, I pay attention, listen to and learn. As far a language designers go, him and Rich Hickey are my top favorite mfkers in the field, but Anders it to me a personal idol.
I also happen to really fucking like C# and Clojure man, like come on those two are just legit good languages.8 -
LMFAO
nice one dude. i'm gonna approve this one time just to show you i'm a good boss.
....of course not.5 -
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*t2 -
Here I am for three months trying to implement TypeScript in this project that was a dump when I picked it up.
And then some morons get assigned to the project and just start adding @ts-nocheck everywhere?
Like, WHAT THE ACTUAL FUCK?
And then you wonder why the project is bug-ridden??
FUCK THESE PEOPLE THAT CALL THEMSELVES JAVASCRIPT ENGINEERS!! NO WONDER JS GETS SUCH BAD PRESS WITH ALL THESE CLUELESS IDIOTS TO WHOM STATIC TYPING IS JUST AN OBSTACLE TO THEM CHURNING OUT LINE AFTER LINE OF "CODE"3 -
How the fuck does TypeScript still not have service worker support? Seriously, it's just a typings file. People have written that typings file. They would just have to include it in the lib collection shipped with the compiler. Yeah, it would have DOM calls intermixed with the SW api, but frankly, having the typings for a set of calls you can't use is infinitely better than missing them for a set of calls you can.
The relevant issue is 5 years old btw.7 -
yeah we use isomorphic async hydrated SSR pseudo-rendering with edge-server chunked ES module CSS-in-JS-in-CSS ESNext TypeScript interop through GraphQL in react-native-web transpilation to react-dom in NextJS isomorphic rendering context React hooks5
-
Hello guys. Today I bring you my personal top 3 programming languages
🥇 Go
🥈 TypeScript
🥉 Java
🏅Honorable mention: Free Pascal
Thanks for reading9 -
I have been working on this software for 3 years now. The code base was a working prototype made by my boss before I came, not more, not less. Php + Angular. Have been refactoring a lot, backend is backed with hundreds of tests now, frontend still lacks a lot. Still a lot of programm structures are still the same weird ones my boss once created in a rush between two meetings while learning Angular to get the prototype finished. Now it's used in production which makes hard to refactor, because we have to maintain backwards compatibility. Neither the parts I added or refactored completely are satisfying, because they are built on this structures, because i never got any feedback for anything I decided and because I changed my own paradigms over time.
So I am all alone on this project. All genuinly new projects are assigned to the new team members (i was the first one, no we are five plus my boss) because I wont have time, have to maintain the old one. So I never can do something new which is quite frustrating.
I did a little side tool, the only thing I invented and did completely by myself in our repertoire - and now some stakeholder shows big interest onto this. Instead of giving me the task to make a real project from this my boss wants to give it to them to develop it. Why? Because I need more time for the main application.
Also the more the software is used the more bug tickets and feature requests come. I was crying for help for months but the others had appareantly more important stuff to do.
This might be true to some extend. Yesterday we had some kind of crisis meeting and my boss wanted again to assing pur junior to help me, who has a shit load of other things to do and is a student. I insisted that this would not be enough, and one of the fulltime devs has to get involved because the thing is our core application and I am only part time btw. So my boss said we wont decide today but one of them should do it. They should have some time to figure out who which is understandable but it's not that I didn't keep saying this for months. Now they are all like whimp whimp when I have to do php i will quit. The new projects are all typescript, with node backend if any. But alas, one of them even said yesterday he doesn't want to do js anymore. Okay... but... this is our tech stack then get another job allready?
And I should do the same probably. But then again I feel very sorry for my boss who helped me in very dark times of corona and more. If both of us leave, the project he worked on for decade (including convincing poeole, collect money..) might be suddenly at it's end while he is so exited about it's access today...
I also get insecure if it's really that they hate php so much or that they don't want to work with me personally because maybe I am a bad team Player or what?
I experienced the same at my old workplace, got left alone with big parts of the project because they didn't want to do php and js in this case and it ended up five devs doing the python backend and me doing the frontend and the php cms part all alone. Then I quit and now everything seems to happen again.
And then again I think I am only fucked up so hard by this stuff because I do not really like being a developer at all. I only do it for the money and because I am good at it (at least i think so. Nobody ever bothers to ever to read my code and give me feedback, because you know, php and js). So I guess I would hate any other job in the field maybe likewise?
This job *is* convinient, salary, office
position, flexibility could not be better. At the end of the day it's not that stressfull. And i don't have any second of freetime (due to family) or energy i could offer a new and more demanding employer, can't work over time or even take a fulltime position, can't home office, can't earn less, can't travel very long to the office and especially can't go back to school to learn something completely new. Some of these constraints are softwe then other naturally but still my posibilities at the Moment are very limited. That might change in about five years if the family situation changed. So it would most likely be reasonable to stay until then at my current job? And bear being alone with this app, don't getting involved on any new project, don't learn anything new, don't invent anything.
There was one potential way out, they considered offering me PHD position to the upcoming ml part of the project... But I learned that I would attend to a bunch of classes at university first, which i would like to, but I don't think i have the time.
I feel trapped somehow. I also feel very lonely in the Office because those fucktards keep saying in home office.
Man, I don't want to go to work today.6 -
I started my first job in programming on Tuesday. I made a VPC using CDK in Typescript. Today, I deployed to production for the first time. Never felt so proud of myself. 😊4
-
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???8 -
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. -
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)16 -
So, I've had a personal project going for a couple of years now. It's one of those "I think this could be the billion-dollar idea" things. But I suffer from the typical "it's not PERFECT, so let's start again!" mentality, and the "hmm, I'm not sure I like that technology choice, so let's start again!" mentality.
Or, at least, I DID until 3-4 months ago.
I made the decision that I was going to charge ahead with it even if I started having second thoughts along the way. But, at the same time, I made the decision that I was going to rely on as little external technology as possible. Simplicity was going to be the key guiding light and if I couldn't truly justify bringing a given technology into the mix, it'd stay out.
That means that when I built the front end, I would go with plain HTML/CSS/JS... you know, just like I did 20+ years ago... and when I built the back end, I'd minimize the libraries I used as much as possible (though I allowed myself a bit more flexibility on the back end because that seems to be where there's less issues generally). Similarly, any choice I made I wanted to have little to no additional tooling required.
So, given this is a webapp with a Node back-end, I had some decisions to make.
On the back end, I decided to go with Express. Previously, I had written all the server code myself from "first principles", so I effectively built my own version of Express in other words. And you know what? It worked fine! It wasn't particularly hard, the code wasn't especially bad, and it worked. So, I considered re-using that code from the previous iteration, but I ultimately decided that Express brings enough value - more specifically all the middleware available for it - to justify going with it. I also stuck with NeDB for my data storage needs since that was aces all along (though I did switch to nedb-promises instead of writing my own async/await wrapper around it as I had previously done).
What I DIDN'T do though is go with TypeScript. In previous versions, I had. And, hey, it worked fine. TS of course brings some value, but having to have a compile step in it goes against my "as little additional tooling as possible" mantra, and the value it brings I find to be dubious when there's just one developer. As it stands, my "tooling" amounts to a few very simple JS scripts run with NPM. It's very simple, and that was my big goal: simplicity.
On the front end, I of course had to choose a framework first. React is fine, Angular is horrid, Vue, Svelte, others are okay. But I didn't want to bother with any of that because I dislike the level of abstraction they bring. But I also didn't want to be building my own widget library. I've done that before and it takes a lot of time and effort to do it well. So, after looking at many different options, I settled on Webix. I'm a fan of that library because it has a JS-centric approach. There's no JSX-like intermediate format, no build step involved, it's just straight, simple JS, and it's powerful and looks pretty good. Perfect for my needs. For one specific capability I did allow myself to bring in AnimeJS and ThreeJS. That's it though, no other dependencies (well, at first, I was using Axios because it was comfortable, but I've since migrated to plain old fetch). And no Webpack, no bundling at all, in fact. I dynamically load resources, which effectively is code-splitting, and I have some NPM scripts to do minification for a production build, but otherwise the code that runs in the browser is what I actually wrote, unlike using a framework.
So, what's the point of this whole rant?
The point is that I've made more progress in these last few months than I did the previous several years, and the experience has been SO much better!
All the tools and dependencies we tend to use these days, by and large, I think get in the way. Oh, to be sure, they have their own benefits, I'm not denying that... but I'm not at all convinced those benefits outweighs the time lost configuring this tool or that, fixing breakages caused by dependency updates, dealing with obtuse errors spit out by code I didn't write, going from the code in the browser to the actual source code to get anywhere when debugging, parsing crappy documentation, and just generally having the project be so much more complex and difficult to reason about. It's cognitive overload.
I've been doing this professionaly for a LONG time, I've seen so many fads come and go. The one thing I think we've lost along the way is the idea that simplicity leads to the best outcomes, and simplicity doesn't automatically mean you write less code, doesn't mean you cede responsibility for various things to third parties. Those things aren't automatically bad, but they CAN be, and I think more than we realize. We get wrapped up in "what everyone else is doing", we don't stop to question the "best practices", we just blindly follow.
I'm done with that, and my project is better for it! -
Hello there. I'm a junior frontend developer, and I'm starting to think that IT is not for me.
Okay, first things first. This story/rant might be a bit longer than I previously thought, but whatever... :p
I started working in frontend about a year ago.
Now the problem is, that I'm absolutely rubbish with coding, and I'm starting to think that it might have something to do with my personality. While I loved (and still do) doing HTML and CSS, and maybe some JS as well, when it comes to working with frameworks, build tools, TypeScript, and all this *****, I just want to stand up and carefully smash the keyboard through the display. I can't stand the constant cryptic error messages and gazillions of config files, and don't even get me started with TypeScript. This is not how I imagined what programming is like - I know it's my fault, I was a bit naive. I still love making simpler things in HTML/CSS/JS and playing around with Linux, but I lost my will to do any of these even in my spare time. I don't have the patience to feel incompetent all the time with the promise that in a few years, doing this rubbish 8 hours a day, I will get better at it. Some colleagues even talked about it being like Lego and getting into the "flow": yeah... not in my case. There's nothing creative in this, it all feels like a factory line where I have to do the line work but also configure the machines as well...
The funny thing is, I made about the same amount of money working in less prestigious jobs. Sure I didn't like any of them, they were tiring and boring as hell, but at least they were not stressful and frustrating. I'm seriously considering moving to Western Europe and working as a bicycle delivery guy in the Alps, a postman, a waiter, or literally anything else that has something to do with the real world, and leave programming to the actual software engineers (who I deeply respect by the way).
I'll probably add more to this, but I need to go now and meditate a bit. :D11 -
javascript is garbage
typescript despite best intentions, regardless of how well it's executed, is still garbage as it's some sort of band aid on top of javascript, and javascript is garbage
Before you ask, yes I'm garbage at front end development5 -
Dear php. You weren't my first one. But you were my first serious one. The first i made money with. We had a great time together until ajax came. Do you remember? I did more and more with js later but you still where my main. You even exposed your source code to me. Time changed. They started to hate you. And yes, they where right in some points. But they never saw your good sides. I saw them. I stood with you. But i was froced to wrote backends in typescript, in Java. And you know what: i didn't feel so bad. For gods sake, I fucking enjoyed it, php!
When did we become so alienated? When did I staet to write my dayly heller scripts in bash instead of you?
Yes, you improved. Hack came, than php7, php8. You archived a lot. You finally brought types. There was a time when I thought everything that stood between us will be overcome. That we will be together forever.
But recently i had this conversation on DevRant with nmeri and did some research afterwards. And I learned, maybe you will never have generics. It just don't work out, php, I am sorry. It's not your fault, it's mine. But i dont think i can live without a proper type system for the rest of my life. Not after i taszed those other languages.
I don't know when it will happen. When i switch projects this summer maybe. Maybe next year, when i start a new job. Who knows. But it will happen: you won't be my main anymore at one point. Maybe we can stay friends but i want you to know, that i am open for something new in my life. Something with generics.4 -
i don't wanna say it, but I'm going to say it
1, 2...
3
FUCK RUST.
Took me 30 minutes to prototype this shit in concise, safe and idiomatic Bash.
Took me 4 hours to rewrite it in idiomatic Rust. Did it work just as well? BIG FUCKING NO.
Rewriting it in a crazy-girlfriend-like annoyingly strict nominal Typescript, took me 1 hour.
IT WAS fucking DELICIOUS doing it.
Did it work just as well, BIG FUCKING YES!
Fuck you Rust. F U C K YOU
--- still love you tho22 -
Here's a fucking challenge:
Generate an MD5 hash in React Native!
crypto - NOPE deprecated, react native throws when you try to import it anyway
react-native-crypto - NOPE, needs to make use of a shim that recursively edits node_modules... hmmmm yeah you think thats a good thing to have?
react-native-fast-crypto - NOPE, no TypeScript types, no documentation in general, only supports sha512?! WTF
garbage fucking idiot tooling stupid dumbass stupid splat splat barf splat22 -
If you feel it’s time to change I have a great job offer for you…
proceeds with offer with maximum wage that is half what you earn and by the way you need to know React, TypeScript, NextJS, Redux, NodeJS, ES6, Webpack, RESTful i GraphQL API
Nice to have is Python and Go
Girl you need to decide if it’s great offer or technology mishmash.
Hell no, glad you didn’t mentioned young and dynamic team cause I clearly see some dynamic technology stack there.
Company helps people find medical treatment clearly forgot about treatment on their stack.
Someone needs to tell them their tech leads are complete morons but since you’re not looking for head of technology it won’t be me lol. -
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.8
-
Rust's DX is incredible. I previously published a couple packages to NPM and every step of the way i had to fight with NPM, Webpack, Rollup, Typescript and the mass of third party plugins for all of these that wired them together. Here it's literally just
cargo publish5 -
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!4 -
RAAAAAAH fuck fuck fucking shit!!! Fuck jest Typescript "on the fly" compilation esModuleInterop typeroots, missing definitions jest ts-ignore and xtest everywhere, manual npm linking with different pkg mgrs & pub to a private registry, building docker images locally and doing tag management across git, docker & kubernetes then cross fingers that prod which has 0 common setup with local & test somehow works, open architecture "tickets" and wait months before they resolve, then repeat ad infinitum. How the fuck can I be productive when I need to be all over the place all the time and deal with these meta-code shenanigans. I just wanna code, damned3
-
I just released my first NPM package that is actually functional and used in a private project (https://npmjs.com/package/@lbfalvy/...) and I have to say, the quality of debug tooling for Node is abysmal. I spent 4 hours just on Webpack's "Field browser doesn't contain a valid alias configuration" error which simply means "package not found", and then getting Rollup to output a working compiled javascript _and_ a d.ts was its own day-long ordeal.4
-
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.10
-
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.7 -
Working at a different company for a few weeks before getting back to my usual work.
I'm using everything I hate: ReactJS, factories, style through JS, Jira, Teams, TDD...
The only good thing is I'm using TypeScript...1 -
Fucking mongo, fucking nested documents in nested documents that need to be filtered. I'm either really fucking dumb, the query is hard or both.8
-
Junior Software Developer Job( $37k-$42k USD)
-1 year experience
- J2EE, Javascript, HTML, XML, SQL
- object oriented design and implementation
- management of relational and non-relational such as Oracle, PostGreSQL and Cassandra
- Lifecycle and Agile methods
- Familiarity with the Eclipse development environment and with tools such as Hibernate, JMS, ,TomCat/Gemini/Jetty, OSGi.
• UNIX skills, including Bash or other scripting language
• Experience installing and configuring software packages
• ActiveMQ troubleshooting/knowledge
• Experience in scientific data processing and analytical science in general
• Automated testing tools and procedures, including JUnit testing, Selenium, etc.
• Experience in interfacing with scientific instrumentation, potentially over IP networks
• Familiarity with modern web development, user interface and other ever-evolving front-end
technologies, such as React, TypeScript, Material, Jest, etc.
I am betting they don't get many people applying.9 -
Best
typescript - I needed to learn it for a project and I like it, I know java and javascript and it is something in between of those two that makes writing enterprise web applications easier, it’s nice that you can debug it directly in chrome, it makes things easier
Worst
docker, Dockerfiles - devops tools - amount of shell commands inside them and mangled && to make everything running in one file layer makes those unreadable mess that you need to think twice to understand, there is no debugger for it, you do everything with try and see what happens, there is actually no real dev toolset for devops and that sucks, since you got builder images that makes things more mangled than before, it’s clearly missing some external officially approved scripting language or at least
FUNCTION and
WITH LAYER and indentation / parentheses syntax and they still trying to make it flat, why are you doing that ?
as a result next to Dockerfile cause you can’t import multiple ones you get bunch bash scripts with mangled syntax and other crap that is glued together to make a monster - and this runs most of current software on this planet2 -
Situation: I have a love hate relationship with python due to the lack of types as I have in more established languages such as C#, Java and shit even TypeScript
Situation (cont): A rather large codebase that i have developed for multiple processes at work run on Python.
I don't hate it, I just don't absolutely love it, there is a lot of things to like about Python, but man I do have some conflicts with it, I have been facing out to use other solutions that feel scripty, such as the newer versions of C# with .net, but I would say that about 80% of our codebase runs on Python, the rest is PHP.
I am somewhat traditional in the way my programs run, I started with C++ and Java, then for whatever reason (I blame codecademy at the time) switched over to Ruby and Javascript, mostly Javascript. I do not remember how I found Python, I do remember learning it with an online tutorial, shit was easy to get started with.
My codebase running on Python is huge, and they do a lot from automation scripts, to data gathering and database management, never had I been bitten with the "oh noes is so slow" bug since my code is not Google level big, for everything else Python seems rather fast imho
I dunno, big time love hate relationship9 -
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 typescript11 -
Fucking hell. Typescript is configured to require explicit typing of everything "because sometimes it does weird conversions". But because temporary variables can have weird types used just there (like arrays of various objects), there is a lot of variables typed as any.
That's bad on its own, but whatever. The real kicker is that eslint is set to throw warnings whenever it sees any, "so that people don't just put any on everything". I guess that was a failure...
I asked around and it turns out that TS and eslint were configured by two teams independently that merged when the project was new young, and it sort of stayed that way. No one from the original team is even working in the co panu anymore, yet this clusterfuck still lingers on, and even spreads to every new project that team starts8 -
CAN 👏 PEOPLE 👏 STOP 👏 ADDING 👏 `/// <reference lib="dom">` 👏 TO 👏 NODE.JS 👏 PACKAGES
It's a Node.JS package, for fuck's sake. But for SOME reason, sometimes to get around the lack of `URL` and `URLSearchParams` in @types/node, people keep including the *entire* DOM typings in their definition files/TypeScript files!
Sometimes I upgrade my deps in a Node.JS project and find that DOM typings have been added, causing errors when trying to use the global `URL`/`URLSearchParams` (I've shimmed these so that these (Node.JS versions) are in the global namespace). Then you have to search in all your dependencies for which one is including the DOM definitions.1 -
Thanks I hate it, I hate the fact that typescript will still transpile this. Not an exact copy of the code I'm working with, but close enough. Also this code targets es3, but we generate tsconfigs that say es5 (which don't actually get used) which leads me to believe that we generate them soley for the benefit of ides, and because if they said es3 the ide would show even more errors7
-
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?8 -
For fuck's sake Microsoft, why on Earth do you announce a half-done feature? Was this an idea from marketing? Upper management? I am fairly certain that nobody who actually writes code for a living would have ever approved releasing a rushed feature to a TYPE SYSTEM.7
-
I just started a new job where in my onboarding, I’m supposed to learn typescript and react. I am also supposed to gain some knowledge of databases. Since I am so new, I don’t really have any meetings. I see my manager maybe 2x a day. I’ve been using my time at work to learn these technologies.
I learn best by doing projects. I recently built a bot that scrapes media off of one site and posts it on another site. I was thinking I could create a react front end in typescript for the bit. I would also add a database to my project (the model for the front end) which contains the post history of the bot.
Would that be appropriate for work? I thought it would be good project to help me learn react. However, I am new to the “corporate” world and I feel like my manager won’t want me to waste company time on my side project.
The only other responsibilities I have are reviewing the source code and watching some onboarding videos6 -
WHO THE FUCK THINKS
THIS SHIT
TS:
```
const a = function(callback: (err:any,data:string) => void):void{
callback(null,'balls');
}
a(function(err:any,data:string){
console.log(err,data)
})
```
IS BETTER THAN THIS
ES6:
```
const a = function(callback){
callback(null,'balls');
}
a(function(err,data){
console.log(err,data)
})
```
kys10 -
[LANGUAGE DESIGN]
What are some interesting / unique approaches you've seen to representing generics in syntax? The only one I know is the Java/C#/Typescript way of using a separate set of parentheses and either specifying all of them or none, and I've already experimented a bit with passing them as regular arguments which works great with autocurry but every syntax option for inference adds visual noise.9 -
I've been working with Node and Typescript for a while now, and I wrote a wide array of very general utility functions. Examples include:
- Array.filter but you also get the residue array, it can also leave holes in both arrays if you want to join them later
- Array zipping and unzipping to and from tuples (especially valuable when you're manipulating the prop set with Object.entries() in a HOC
- Array maximum selection, with an optional mapper
- Cancelable promises, lazy promises, a promise that resolves when a given function on an object is called (excellent for DOM events), a timeout promise.
- A typed event with both immediate and microtask listeners depending on whether you need state guarantees (this idea I took from a Github gist and upgraded it)
I want to put them on NPM so I don't have to write them and their tests again, and so that if I ever think of an improvement it's easier to propagate it. Do you think I should release them as tiny individual packages which would be nice from a versioning standpoint, or should I make them into a compilation which would be a lot less work for me (and therefore would probably result in better documentation and more tests)?4 -
Looking at vacancies and the JS build tools asked (Babel, Gulp) and then visiting their websites I notice that I don't understand what they are going on about.
"Leverage gulp and the flexibility of JavaScript to automate slow, repetitive workflows and compose them into efficient build pipelines."
What the actual corpo fuck?
The "get started" page expects you already know npm, typescript, and when you look at their pages, well... Where does the circlejerk end and the actual Javascript start?
I've been out of the corporate loop for a few years, seems it's all about build tools these days. I need to get out of this industry pronto.3 -
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!15
-
It's probably no news that I love Typescript's versatile and powerful generics. Today I found what is probably the most brilliant use of these tools to solve a real problem. This package exports one generic type which takes one generic argument, reads it like a JSON schema and returns the Typescript type for it:
https://github.com/YuJianrong/...7 -
I got contacted by an other company and I am so unsure whether to accept their offer or stay at my current job.
For now I spend 2 years at my current company. The culture is great and everyone gets treated very well.
The bad part is, that it is located in a part of Germany I really can't stand and to this day fully remote is not an option.
Additionally lots of stuff is really frustrating in my daily work, e.g. colleagues that experiment with critical parts if our infrastructure, resulting in every developer who made the mistake to update the local development stack being unable to work for half a day or so.
This and the fact, that our techstack sucks hard. (mostly bad php for backend and server-rendered HTML and a weird mix of Typescript, Javascript, Vue and some old bits of deprecated angular for frontend). This company has it's own product (a web platform) and no real deadlines in the sense of "something bad happens, when your team won't achieve the project in the originally proposed time"
Company number two seems to work with a wide variety of technologies for very different projects (it's a consulting compan), would pay me ~28% more than my currently raised pay and allows for full remote.
When I try to look objectively on the facts everything points to accepting their offer, but on the other hand there is this weird feeling of this being a joice that would come to soon...
How do you make such decisions? I already talked to a great colleague of mine, who thinks it might not be a bad idea to stay at the company for an additional year or 2, because I haven't yet reached the point where there is not enough to learn here anymore, which I agree on, but this company seems to offer everything I want.
I feel overwhelmed with this situation :D that's why I would like to know how you people try to tackle such a situation8 -
Anyone living in the Netherlands? I planning to move to Amsterdam in a year from now. I obviously would like to find a job here first. Is there a job platform besides LinkedIn that people use often and have success with?
I’m a senior engineer mostly working with Typescript, Python, AWS, IBM and Google clouds, DevOps, infrastructure.
EU citizen.5 -
everything is going as planned! :)
Learned Rust Lang. i loved it (that doesn't mean i am done learning na? No! never stop)
new language i could do game memory hacking in without worrying about C++ memory leaks or issues. it also compiles to assembly! another of my favorite languages!
(i use rust for game development and other stuff)
i am not leaving C / C++ though that would be harsh!,
i abandoned javascript for react and typescript.
to be honest the developer just made javascript and left us with a [object Object]
finished learning the android java api so im basically set anything i want to make i can just go on my pc, listen to music and write it out in a couple of days.
well phazor what are you going to do now?!
i will code till i am old.
i will leave my mark like a shid that made its skid in the bowl :)5 -
Ha, Microsoft closes my easily reproducible issue with their Monaco editor as 'resolved':
> posted "resolution" is totally wrong, it's not even in the TypeScript typings of their own library or anywhere in the documentation
jesus christ today is not my day
seems like everyone already started chugging the Christmas eggnog, maybe I'd just give up and start do the same2 -
Dev goals for 2022? Best and worst DX in the past?
Wish to prioritize customers with useful business goals who are open to sustainable web dev, usability and accessibility.
Want to use even more CSS and find a way to use new features like parent selectors without sacrificing compatibility.
Continue learning and using Symfony, but also continue with my full-stack side project using JS or even better TypeScript for the backend also for the backend.
Best developer experience: getting new customers for my own business after leaving a company last winter.
Worst developer experiences:
Corporate customers with large budgets and design agencies seem to fancy all the antipatterns I thought bad and obsolete, like carousel content, animations everywhere, and autoplay videos on the home page. Poorly written, poorly thought, and sometimes contradictory, requirements. Customers and agencies changing their mind halfway through a project.
"Agile" daily meetings, not giving devops necessary repository permissions, and making Webpack mandatory for no real reason.2 -
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.1 -
Just created a Cloudflare worker that sends messages to the backend over PubSub. Feeling pretty bad-ass right now.3
-
honest question: if I know ReactJS, Golang, Python, Typescript, and a bit of Postgres and living in Costa Rica, what sort of freelance services could I promote on the net?
I used to freelance on sites like PeoplePerHour, doing projects of 1 month in 3 weeks or less, but I would like to do that again in my own website under my own terms, sort of speak.
any recommendations?2 -
Ever since I started learning about React with Typescript my respect for design patterns that restrict how state can change has grown massively. On the web, nothing happens when you say it should happen; everything always takes a while to execute and there is always a transactional period between validating an action with client-side state and receiving the result from the server, and if you want to account for that everything becomes infinitely more complex and you eventually end up with mutexes.5
-
I love Typescript's challenges. Today I had to make a generic interface that replaces every property in its parameter with either itself, a promise of itself or a different property keyed `obtain${key}` which is a function returning either the value or a promise of it. Not a very difficult challenge, but it was very satisfying to solve.
If anyone has the patience to attempt it I'm very curious what more experienced type theorists than myself come up with.1 -
Where have i been? the answer is Yes. im still alive, caught rona 3 times never been better.
as a OKAY not pro developer i can create what i want.
and if you're wondering. Yes i have deleted my rants.
i use typescript. i will not go back to js.
RUST IS SUPERIOR TO C++
(i still use C++ because i am a mad cheater in android games this is gonna probably come to a halt soon i haven't been on my mobile a while)
all i literally had to do was sit at a computer for hours. stick to one language and just build projects on my own i stopped coding on mobile after one of my unstable projects had got access to my devices files. oh and last but not least tampermonkey sucks and my favorite game moo moo.io and sploop.io is full of macroers, cheaters and now nobody wants to play legitly in the game. i forgot this website and decided to take things slowly. time goes fast when your mind really be dazed.5 -
Immutability is nice and all, but there are languages and tasks where it really doesn't work as well as it should.
-
I contimnue to just hate javascript, especially react. just fucking go die. You can't fix a shit sandwich by wrapping it in fucking typescript. Gah, fucking hate this crap.1
-
What the fuck is this syntax in a typescript file, I'm having trouble finding documentation if anybody can enlighten or link me
const [, updateThing] = useMutation(UpdateThingMutation);
The [, throws me off
i fucking hate front end22 -
Interview question i had:
- how does jwt work under the hood, where is it stored, what 3 parts is it made of, who creates jwt, how does the server know what information the jwt token has (how can it say oh you're Joe you can login now)
- what is the difference between observable and promise in typescript, how does observable work, what is a stream, what is the difference between fetching data through an observable and fetching data with promise and when should we use one over the other, what does .next() funcrion do in observable under the hood
Answer me these questions without googling8 -
Why the fuck why are tslint and prettier are always sucking their dicks and fuck each others asses.
Do you know this moment when you think:.... 🤔 They have millions of downloads, why do I bother formatting my code so much. Mabye all this people are smarter and saving so much time.
Then you set up eslint and prettier adjusting 10000k rules just to find eslint and prettier five minutes later in one file fucking their asses again how to indent on save😠😱7 -
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.4
-
Why on Earth is React.Component.state public? This doesn't make any sense. It has no significance, but it just feels so, so stupid.2
-
stateofjs survey reminds me of all that's wrong with JavaScript: too many frameworks each of which has to reinvent the wheel and depend on too many node_modules child dependencies, most don't support TypeScript properly (ever tried to convert a node-express-mongoose tutorial to TS?), there is still no proper type support in JS core language, and browser features get added in form of overly complex APIs instead of handy DOM methods.
Instead the community gets excited about micro-improvements like optional chaining which has been possible in other languages for decades.
At least there is something like TypeScript, but I don't like its syntax either, it's overly verbose and adds too much "Java feeling" to JavaScript in my opinion.
Also there is too much JS in web development, as CSS and HTML seem to have missed adding enough native functionality that works reliable cross browser to build websites in a descriptive way without misunderstanding web dev for application engineering.
After all, I'd rather have frontend PHP than more JavaScript everywhere.
Anyway, at least the survey has the option to choose how satisfied or unsatisfied people are about certain aspects of JS. But I already suspect that most respondents will seem to be very happy and eager to learn the latest hype train frameworks or stick to their beloved React in the future.5 -
Any backend devs here working with TypeScript? What are the best framework choices right now? I've been looking at Nest.js, but there seems to be a steep learning curve that might hamper onboarding of my (literally fresh graduate) new hires. There's also Ts.ED, which seems like the fat has been trimmed from it.
I know people will recommend something like, just using express / koa / hapi but I don't think we have the time to work with something super lightweight 😬😬😬. And besides, opinionated frameworks will speed things up for now (we have a lot of crap we want to do this incoming 2022)12 -
I don’t know if I’m fucking stupid but ESLint is so unbelievably hard to setup. Too many fucking plug-ins, configs and rules. All I want is my Airbnb config on my React Typescript project and nothing else. I can’t even fucking get that sorted. Not to mention the hundreds of Medium tutorials that all do things just slightly differently to the point that I can’t mix and match a config.2
-
Design team loves to use any in their components. I just love having to dig through multiple nested components to find out what i should put as input or console loging to found out the outputs. Whats the point of using typescript at that point. It costs nothing to write a single interface..1
-
devRanters!
Do any of you find that you can type the solution faster than GitHub Copilot recommends?
That's how you know you're senior 😏
Also, on a serious note, does it only support JavaScript / TypeScript? Didn't really take time to investigate.
I thought there was also a feature you could tell it what to code and it would try to write a solution. Haven't really seen how to do that yet.7 -
I never thought in my life that I would say this sentence one day - but:
Today I switched back to VS Code because it uses less memory than IntelliJ.
Context: Only temporary, very resource hungry dev environment, TypeScript, IntelliJ used >4.5 GB of ram and started lagging.5 -
i have no idea what im doing
javascript, jsx, typescript, react have some of the ugliest and redundant syntax i have ever seen
what are people's favorite reference material for them
do people recommend the official documentation, was surprised react looked better than expected for its docs6 -
I spent the whole damn day trying to setup grpc-web, but this protocol is documented so damn poorly!
You manage to set grpc up for one language and it’s all cool, then you stupidly think that you are free to reuse the compiler you used for the nodejs version for your frontend part but nope! Our web module is now deprecated, please use this module instead!
“Ah yes just clone the repo and check out (…) and you can also check this link whic is in no way highlighted in the middle of a wall of text (…)”
*checking the other page*
Ah yes you need to install a package available only on your unix machine (great! Screw the devs in my team who use windows I guess, they’ll be happy to hear this!) and don’t forget to clone this repo to build your own plugin! And by that I ofc mean to compile it on your own!
- compiler error
After digging for an hour you find a requirement in an obscure issue opened and closed cause “ah yes we have a dependency not stated anywhere” *close issue and never add it to the project*
Fine, fine I can survive this bs
- another compiler error, no solution found after 2 hours
Honestly? Why the fuck do I need to compile this stuff? Just give me a damn npm package I can use? Goddamn it’s just transpiling, you don’t need access to my OS! (Aside for fs to save the files, and which btw is accessible via nodejs)
Now, I COULD download the latest realease as a precompiled, but… honestly?
I give up, I’ll do some shitty rest apis cause the customer’s not paying me enough for even THINKING to go trough this shit again when they’ll ask an iOS app. Or having colleagues asking me to help them understand how to do it.
Side note: also add typescript support to the web-code-generation ffs! Why does node have it and web don’t?5 -
typescript is shit.
I have never seen such a stupid bug in other languages.
https://stackblitz.com/edit/...
Apparently, there is no way to do type narrowing in a nested object without using enum12 -
The Node and its magic tricks never cease to surprise me.
I created several new components and tried to compile them for verification. Then this big fat error popped up.
I commented out all the newly created code (didn't remove any files, just did ^A^/). Recompiled. This big fat error again.
Undid modifications I made to the files that existed there before. Recompiled. This big fat error again.
Moved the newly created files outside of the project scope (mv app/<...>/featureX/ ../bkup/). Recompiled. SUCCESS.
Moved all of those files back (mv ../bkup/featureX app/<...>/). Recompiled. SUCCESS.
wtf...2 -
My two main grudges against Typescript:
1) Union types can't be passed as arguments if there is a variant for every element of the union
2) No tuple polymorphism, i.e. [T, U] isn't assignable to [T]. This is not a mistake because the length of the arrays differs and therefore they may be interpreted in a different way, but IMO there should be a tuple type which is actually an array but length is unavailable and it supports polymorphism. This sounds stupid, but since function parameter lists work well with tuples it would actually enable a lot of functional tricks that are currently inaccessible.7 -
The world would be better if the TypeScript guys knew what they could create with less complexity in any other language. Of course, if they are interested in learning. There are SPA applications out there that have more lines than Doom 3.7
-
Hello, fellow developers, i am having a question in mind that confusing me about my career choices.
At first i joined a company as a full stack developer with 6 months experience in MERN, MySql etc.
Now i have completed nearly 1 year in this company but they are always assigning me to full DevOps CI/ CD projects. And i agree i am learning a lot of new things and completed the given works too.
BUT , the question is , should i completely shift as devops engineer or software developer? What might be a better career in long term?
Ps: in CI/CD i did almost all works in Typescript using CDK and sometimes a little bit in python (not good in python but learning)10 -
Babel fails about 10% of the time, but if I re-run it it works. What the fuck did I even get myself into, and why aren't elements of a modern javascript toolchain completely deterministic? (webpack, babel, typescript, react)1
-
Found next to a TypeScript definition set of 16 overloads, written for all combinations of 4 bivariants.1
-
Found a great book called Grokking Deep Learning from Andrew Trask. The hole point in to make your own Deep Learning framework from scratch. Using python, but I think I'm going to try to go at it using Typescript. Lets see how that goes.1
-
!rant
Go's tuple-style returns. ❤️
What's an exception? I don't even know what those are anymore. 😄
I've started using this pattern in JavaScript / TypeScript too.
also... supabase anyone? ❤️5 -
ima keep this very fucking simple: If you support TypeScript, you are a mother fucking asshole and I hope you BURN IN HELL.11
-
I'm in love with F#, the tooling can be a little buggy if you're used to TypeScript or Java but before learning it I've never been able to solve a real life problem with less than 10 lines of code7
-
Why building a library of React component should be this hard: I'm sick of Webpack, Babel, Typescript and all the shit which is duct taped together to build some damn widgets.4
-
Typescript is my new favorite and my grudge is the stupid scoping of type assertions. I have an async function that checks whether a variable is set and awaits a change event if it's undefined. This function is working javascript but invalid according to typescript, because it relies on the exact type changing while the function is running. I had to convert it to a mess of promises to bypass this because (and this is the best) the callback-based syntax of identical meaning will reset all type assertions, even locals that are never written after the callback's creation.8
-
I'd like to learn about functional programming. What books, courses, tutorials or articles would you suggest? I have a good understanding of abstract algebra and I felt the need to learn it because my Typescript is a mess and I visibly don't know what I'm doing.1
-
[typescript] Should I use a promise to represent an event that can occur at most once, may never occur but can never fail? If not, what else should I use? Callbacks?5
-
Some senior just pushed some half assed typescript code generator that generates stupid types that make everyone's life difficult.
Who need transparent type inference? Just use type guard everywhere.
Can't reason with the particular individual.
Please release me from my misery.
In house built == shitty version of original open source library. -
Our company has the opportunity to start moving towards a more microservices architecture approach.
There is so much technical debt that needs to be paid back, this opportunity is a godsend!
Now, of course, the whole "programming language debate" comes into play at this point.
To provide some context, we've reached the point where we need to be able to scale, and at the same time where speed and performance are also important. I would argue that scale is of more importance at this stage.
Our "dev manager" (who is really only in that position since he's the oldest, like scribbling on a notepad and the sound of his own voice) wants to use Rust, as this is a peformant language. He wants to write the service once and forget about it. (Not sure that's how programming works, but anyhoo). He's also inclined to want to prematurely optimize solutions before they're even in production.
I want to use Typescript/NodeJS as I, along with most on the team are familiar with it, to the point that we use it on a daily basis in production. Now I'm not oblivious to the fact that Rust is superior to Typescript/NodeJS, but the latter does at least scale well. Also, our team is small - like 5 people small - so we're limited in that aspect as well.
I'm with Kent Beck on this one...
1. Make it work
2. Make it right
3. Make it fast
We're currently only at step 1, moving onto step 2 now!7 -
I tried building a project with nextjs. I dont like it. Angular is still better. Nextjs might be more lightweight but i dont care. Theres way too much shit i need to write and theres no boilerplate code like there is in angular. Also in angular components can be grouped in 1 directory and from there you group its services interceptors guards scss typescript html etc. In nextjs all of that shit is thrown in /pages and /components while styles go to /styles. Reasonable, but what happens when the application is large as shit? Thats why angular will always win long term2
-
I have a readonly object property foo on a typescript class. When I create an instance bar by calling the constructor, bar.foo doesn't compare equal to this.foo as seen from within bar several async calls later. What could I have possibly fucked up?5
-
Good developers timebox themselves to 15 minutes before asking a question
How do I learn react, jsx, typescript, graphql in 15 minutes to solve my problem or figure out good questions to ask
fml , what are good career alternatives5 -
What’s the easiest way to implement a chat feature in my app so that 2 users can talk to each other. Looking to probably use a third part service because I don’t want to have to deal with security and other stuff that I might easily mess up on. Full stack Typescript btw.4
-
Git gud with TypeScript, do some mobile or some web dev. Also find a full time remote job so don't have to work in a office the rest of my life
-
Being lazy sometimes and writing type definitions after I’m done developing something rather than before (hence wasting time as doing that work is meant to help with the development process in the first place...)
-
My team and me nearly finished a big new feature for our website.
I am a junior dev and this was the first big thing I was in charge of and now that I see how it unfold I feel really bad.
It consists of php backend (integrated into a 20 years old monolith) and vue frontend (punctually jumpstarted by a clusterfuck of typescript files included into php rendered html) and especially the frontend part looks so bad.
Vue is relatively young in our project and almost nobody has a clue about it. I learned so much about vue in the process, but the result is a behemoth of awfulness that grew over several months.
I have a really strong desire rewrite the whole mess, but I will never be officially allowed because it works and practically all the flaws in our code base are subject to the classic
"well, someday, somebody probably has to do something about that, but for now let's start this shiny new feature"
So for now I think about doing it secretly and pass it to my buddy to review it. I guess chances are high that not even the colleagues in my team (apart from my buddy) are going to notice, since they aren't as interested into vue as I am and don't have the overview over this features code as I do, but on the other hand it feels like something I could get in trouble for and apart from the cursed code base my company is great.
Have you ever bin that disgusted by your own production code before it was even one year old?3 -
today the backend dev told me that he was trying to setup typescript for the company for so long and the company resisted him but he was super proud of his achievement of getting typescript into the project and i told him. sorry I agree with the company, you're stupid
i didn't tell him he was stupid ofcourse but i told him why i thought it was an unnecessary dep
i asked him are you doing a lot of number crunching? he said no
and i told him, most of the data you're going to recieve is in a string format or in json strings
very rarely are you going to get number data
and you can easily coerce the data into whatever you want37 -
Yk Javascript is both the best and worst langauge. Best language because it can be on the browser, mobile devices and on the server. Its the worst language because of its weak typing and no runtime typesafety along with several other weird stuff, it also may not be the best choice for utilizing multiple cores on the cpu but thats rarely an issue i need to address.
Ive been using typescript + zod validation library to address weak typing and no runtime typesafety and it feels good plus i work with serverless mostly so i dont need to worry about cpu issues. I just wish i was using something that wasnt being transpiled. -
Just built out my first app using Cloudflare Workers, Typescript, and DurableObjects. Holy shit, this is nice stuff.
It's taken little to no time to build out:
* JSON API written in Typescript
* JWT verification against my OAuth backend (SAML support too)
* CI Automated Deployments including unit tests
* DurableObject support
* 3rd party HTTP calls + caching (built in to the framework!) to reduce network latency and hiccups.
* Cron-like tasks on each stored object so they can awaken the app on a schedule and update themselves as necessary
* Rapid deployment to new environments
The local testing with coordinated "miniflare" is dreamy too. -
I’ve been jumping on techs for a web application I wrote in Next.js and Mongo (mongoose) using Typescript.
The problem- I hate looking at codebase. Partly due to mongoose has a bug which makes type intelisense slow.
Moving forward, I’ve been creating different projects of the backend, in plain node typescript, in nest, in graphql but my inner self wasn’t satisfied.
Last night I deleted all the projects and decided not to change anything and continue working on the garbage code I’ve written a year ago.1 -
You know what sucks? Android having only 2 languages for their android app documentation why can't it at least support rust or typescript or other languages, im sick of all of this "fun" stuff
if you would choose the android documentation language what would you pick? ;o
my jetbrains ide is currently crying in a corner...13 -
ProCoders ,first of all, is a team of talented software engineers who love what they do. ProCoders are an IT staff augmentation firm with more than 80 engineers on board who can manage any project. As a professional offshore software development team, our team can find the superior software engineers for your startup. Our company are experts in CSS, Node.js, Flutter, JavaScript, HTML, React Native, Ionic, TypeScript, Angular, PHP, Vue.js, Symfony, Ruby, React, Laravel, Ruby on Rails etc.2
-
I want to know if I should use java for interview questions,but I’m a bit iffy because I’ve only done a OOP course last semester using java and I haven’t used java in any real world projects or at work. The language I primarily use is typescript/JavaScript. I also know python, but the same thing goes for that as well. What should I pick? I need a wise answer. 🙂6