Did it work? How do you know that? A consumer of your package sends a int when your package expects a string.
What now?
Comment on Some people just wake up and choose violence
unsaid0415@szmer.info 9 months ago
I recently made a small pure JS package at my company. It just fucking worked, can you believe it? No setting up compilation and CI/CD for build + release. Just put it in the repo and publish manually, and it just worked, it’s ridiculous
jmk1ng@programming.dev 9 months ago
sik0fewl@kbin.social 9 months ago
Consumer just needs to write 4x as many unit tests to make up for lack static typing. Hopefully the library author has done the same or you probably shouldn't use that library.
marcos@lemmy.world 9 months ago
4x as many unit tests
Well… the people fighting against TS are simply not testing things thoroughly. So they are not writing those tests.
Some times that’s even perfectly ok. But you don’t want to build things over a complex library that has this attitude.
(Except for svelte. It’s meaningless for svelte, as TS was always a really bad fit for it.)
Stumblinbear@pawb.social 9 months ago
It’s ok, just do what my company does and write no tests at all!
jet@hackertalks.com 9 months ago
Hey man it passed the CICD. Not my problem
nulluser@programming.dev 9 months ago
Theoretically, they’ll test and notice that doesn’t work and fix their code before they deploy it to production.
Quill7513@slrpnk.net 9 months ago
Where can you point to other developers evidence that the code in git matches the code you deployed? Deploying locally built packages to prod is an automatically fireable offense because its not auditable
nulluser@programming.dev 9 months ago
WTF are you talking about? All I’m saying is that if you write code (that in the context of this discussion passes arguments to a method you didn’t write, that may not be the type the author of the method expected someone to pass, but really, that’s completely beside the point), you should, oh, I don’t know, maybe test that it actually works, and maybe even (gasp) write some automated tests so that if anything changes that breaks the expected behavior, the team immediately knows about it and can make appropriate changes to fix it. You don’t need a strongly typed language to do any of that. You just need to do your job.
Ranman@lemmy.world 9 months ago
[deleted]Pyroglyph@lemmy.world 9 months ago
I thought it was clear: they’re implying JS is simpler/faster to write and deploy because transpilation is necessary when using TS (unless you use a modern runtime).
magic_lobster_party@kbin.social 9 months ago
CI/CD is useful regardless of which language you’re useful. Sooner or later some customer is going to yell at you because you didn’t discover the fatal error before deploying.