TypeScript can be great, but in practice I have seen teams lean on it as a way of taming data models that are overly complex and changing at rates that strain the ability of developers to keep up. Sometimes it might more sense to control complexity and extreme rates of change directly instead of moderating their impacts by using TypeScript like a blind person's cane.
If you write a web language as a primary part of your job, you might not be an engineer.
In all seriousness though, I hate having to add a bunch of tooling to my dev process so that I get to write extra syntax to avoid warnings about valid code in the language as it is actually interpreted by the VM. It’s bureaucratic bs, so yeah, I avoid roles heavy on TS.
JS has a type system already. Its rules are laid out in easy to read specs. Maybe ”engineers” should learn how JS works instead of placing “safety” features in the way of their half baked understanding of the code and how it interacts with external data from the DOM, http requests and so on.
If you write a systems language as a primary part of your job, you might not be an engineer.
In all seriousness though, I hate having to add a bunch of tooling to my dev process so that I get to write extra syntax to avoid warnings about valid code in the language as it is actually interpreted by the CPU. It’s bureaucratic bs, so yeah, I avoid roles heavy on C.
Assembly has a type system already. Its rules are laid out in easy to read specs. Maybe ”engineers” should learn how Assembly works instead of placing “safety” features in the way of their half baked understanding of the code and how it interacts with external data from the terminal, disks and so on.
Typescript is about reducing and almost eliminating runtime errors. We rarely have any errors show up on our error monitoring tools because of Typescript.
Type systems don't deal with variables. Type systems deal with interactions between values. Maybe those values are inline, maybe they are stored in variables.
You don't imply anything from an assignment other than the variable now has or is pointing to the new value. This is the same in every programming language. The only difference is that some programming languages gatekeep what you can assign to a variable based on types.
TS is fine. Some people overengineer it absurdly. But in decent quantities is fine.
I have recently used NextJS, after not using it for a few years. It feels like it has jumped the shark. Meh new features bur requires redoing many things.
Pretty much every issue with Typescript is actually an issue with Javascript. Typescript is purely an improvement.
It looks like "ai generated" is the problem.
Is this a bigger problem than Microsoft Front Page(or other WYSIWYG) generated code? How would you compare this Upwork contractor quality code?
Frontpage code is isolated in a single file, a single page in your website.
AI code is often reused, because it's code and you are supposed to export/import it. Hence the damage spreads instead of being contained.
Sounds like AI is the problem, which I agree, LLMs in most peoples hands outputs garbage.
Luckily I’m working in a codebase with “human” issues, which I’m responsible for refactoring
Related:
Next.js, Just Why? (2023)
https://news.ycombinator.com/item?id=41803327
TypeScript is the best thing that ever happened to js and to web dev in general to date.
JS infra and tooling is the worst thing that is still happening to web dev.
Both are slowly getting better and better. I see no objective reason to stay narcissistic about it in 2024.
Bad code is a universal problem, not a feature of a specific language.
Next.js projects I've seen became semi disposable after a year.
how many new codebases could you have worked with that are AI generated?
TypeScript can be great, but in practice I have seen teams lean on it as a way of taming data models that are overly complex and changing at rates that strain the ability of developers to keep up. Sometimes it might more sense to control complexity and extreme rates of change directly instead of moderating their impacts by using TypeScript like a blind person's cane.
If typescript is an instant turn off for you, you might not be an engineer.
What is an "engineer" to you?
[dead]
If you write a web language as a primary part of your job, you might not be an engineer.
In all seriousness though, I hate having to add a bunch of tooling to my dev process so that I get to write extra syntax to avoid warnings about valid code in the language as it is actually interpreted by the VM. It’s bureaucratic bs, so yeah, I avoid roles heavy on TS.
JS has a type system already. Its rules are laid out in easy to read specs. Maybe ”engineers” should learn how JS works instead of placing “safety” features in the way of their half baked understanding of the code and how it interacts with external data from the DOM, http requests and so on.
If you write a systems language as a primary part of your job, you might not be an engineer.
In all seriousness though, I hate having to add a bunch of tooling to my dev process so that I get to write extra syntax to avoid warnings about valid code in the language as it is actually interpreted by the CPU. It’s bureaucratic bs, so yeah, I avoid roles heavy on C.
Assembly has a type system already. Its rules are laid out in easy to read specs. Maybe ”engineers” should learn how Assembly works instead of placing “safety” features in the way of their half baked understanding of the code and how it interacts with external data from the terminal, disks and so on.
Typescript is about reducing and almost eliminating runtime errors. We rarely have any errors show up on our error monitoring tools because of Typescript.
TS does not have a VM. So you’re starting off on the wrong foot. And JS does not have a type system at all.
Also, you shouldn’t gatekeep who is/isn’t an engineer.
JS has a dynamic type system. You may not like it, that doesn't mean it doesn't have one.
Otherwise, no programming language would have a type system except for Idris, for exactly the same reason.
Maybe I’m misunderstanding, could you give me an example?
Do you mean the fact that it can imply a variables type from assignment?
Edit: I’m plainly wrong, mishmashing words.
Yes JavaScript has a dynamic type system
Type systems don't deal with variables. Type systems deal with interactions between values. Maybe those values are inline, maybe they are stored in variables.
You don't imply anything from an assignment other than the variable now has or is pointing to the new value. This is the same in every programming language. The only difference is that some programming languages gatekeep what you can assign to a variable based on types.
TS is fine. Some people overengineer it absurdly. But in decent quantities is fine.
I have recently used NextJS, after not using it for a few years. It feels like it has jumped the shark. Meh new features bur requires redoing many things.