In recent years, TypeScript has emerged as a popular choice for many developers due to its extra layer of static typing. However, this article will explore the reasons why you should reconsider using TypeScript and shift back to pure JavaScript. We aim to spark thought-provoking discussions and encourage users to share their opinions in the comments section.
React.js was written with Javascript
Simplicity and Flexibility:
JavaScript, being a dynamically typed language, offers a greater degree of flexibility by allowing developers to write code more intuitively without the overhead of type annotations. By reverting to JavaScript, developers can embrace the simplicity of the language, focusing solely on achieving desired outcomes rather than wrestling with complex type systems.
Rapid Prototyping:
One of the major drawbacks of TypeScript is its learning curve and initial setup time. JavaScript, on the other hand, provides an ideal environment for rapid prototyping, enabling developers to quickly iterate and experiment with different ideas. Returning to JavaScript would empower developers to hack together ideas faster and get immediate feedback.
Larger Talent Pool:
TypeScript, being a relatively new addition to the JavaScript ecosystem, limits the available talent pool of developers. By embracing JavaScript, you open up opportunities to collaborate with a larger community of developers who are proficient in the language. This advantage not only facilitates better knowledge sharing but also enhances the potential for finding skilled team members and contributors.
Reduced Code Complexity:
Although TypeScript promotes type safety and catches potential errors during compile-time, this additional layer of complexity can make the codebase harder to understand and maintain. In contrast, JavaScript's dynamic nature allows for more concise and readable code, reducing overall complexity and improving collaboration within development teams.
Vibrant Ecosystem:
JavaScript boasts an extensive ecosystem of libraries, frameworks, and tools carefully crafted over the years. While TypeScript does support JavaScript libraries, not all of them have TypeScript type definitions readily available. By transitioning back to JavaScript, developers gain access to a vast array of battle-tested resources and community-driven solutions.
We hope this article has ignited a conversation, and we eagerly await your thoughts and comments on this topic ?
Join us @ IDURAR : JS Open Source project
Latest comments (40)
Look at this dev.to/desone/why-typescript-vs-ja...
I have read your article carefully. In my personal opinion, one should strive to use both JavaScript and TypeScript well. Moreover, as a project grows, TypeScript becomes absolutely necessary, I believe. In my company, when we developed a massive commercial real estate solution, we built the server using JavaScript. We worked hard with jsdoc to handle a complex database schema. Eventually, we implemented a system quite similar to the Nest framework, but the lack of types was truly a terrible experience. When we migrated that project to TypeScript and Nest, we felt a real sense of liberation.
I read this article and I'm intrigued by the author's arguments for going back to JavaScript from TypeScript. I've been using TypeScript for a while now, and I definitely agree that it can be a bit verbose and can add some overhead to development.
However, I also think that the benefits of TypeScript outweigh the costs. TypeScript can help to catch errors early on, which can save time and frustration in the long run. It can also make code more maintainable and easier to collaborate on. I think it's important to weigh the pros and cons of TypeScript before making a decision about whether or not to use it.
Interesting!
i use chatgpt in telegram free bot in this link
As @szagi3891 says, your points are weak. — Here's why.
This goes for any dynamically-typed programming language; this isn't special to JavaScript.
Also, there are reasons why you wouldn't want to just be flexible.
Well, if said developer is versed well enough in JavaScript, they should be able to get the hand ov TypeScript almost instantly.
Literally, as much or as little TS as you want can be typed or untyped, so certain, TypeScript-specifc, features can be introduced to the programmer, and integrated into their code, slowly, in a way that gives them room to breathe.
Not really.
Consider my last point, again; since as little or as much ov the code can typed, we can make the TypeScript as similar or dissimilar to JavaScript as we'd like — however, simplifying the code will just water down any benefits TypeScript is trying to give you.
And?
There doesn't need to be type-definitions just for TypeScript — one can get by perfectly fine by just using the JavaScript types' names — not to mention that using
classes in JavaScript and TypeScript is virtually identical.I agree with most of your arguments; simplicity and flexibility of JS vs TS, could be that there is a larger talent pool for JS than TS. I do not agree 100% about the learning curve if the leaner has good base on different OOP languages (apart of JS) and do not agree about that the initial setup time is larger for TS than JS, depend of what are you building, for complex projects the set up time is very similar (Unless you are saying that you can not write TS on a web-console from your browser). About that JS is better for prototyping, hacking, and do PoCs I agree. But for complex projects, that has lot of components and parts, and lot of developers involved, TS is a winner, reduces the errors and misinterpretations when you are using a component that wrote another one.
Also I must admit that for the last 7 years I was developing at services at the backend and could be that the point of view of a fronted dev could be more JS oriented.
I feel once you start using TS, its pretty difficult to go back to a non-type world. It nourishes discipline in coding which is the best part.
Agree, the only way returning back to JS after TS is when you are forced to work on legacy projects
After learning TS I had never created a project with JS :)
I think mentioning React as an example here is a bit ironic. While it's true that it has been written in pure JS, they have also created Flow, which is quite similar to TypeScript, and React PropTypes. So I assume they clearly saw a strong demand for types.
I can see from your perspective that JS may seem like a better choice when limiting the context of the argument between TS and JS. Unfortunately, the context is significantly larger than your argument considers.
I would love to hear your thoughts on how JS is a better choice at scale. Or for different project types. I know there have been successful projects built without TS, so I'm not just looking for examples of people who didn't use it. But instead, I would like to hear your thoughts and perspective.
For example, one problem I consistently run into without TS is identifying data structures. If I'm trying to reuse someone else's function or component, figuring out the required structure of an object is unnecessarily complicated and often requires a lot of time investigating. This can be solved with the addition of JSDocs, but since you did not include that in your argument, I assume you are not using it...but if you are, there is also a learning curve to proper JSDoc format, so it's more of a tradeoff. Do you have thoughts on how JS makes this sort of thing easier without the need for other tools?
Additionally, I know there have been several large projects recently dropping the use of TS (Svelte for example), but before making a sweeping declaration that "if these teams are dropping it, so should everyone" we must first consider the reason why they are doing so. Many of the example projects people bring up in this regard are packages and libraries meant to be used within applications. Building a package/library is vastly different than building an application. They have different requirements, considerations, skillsets, serve different needs, and have different audiences. Could you share your thoughts on why TS should not be used for any project, rather than it being used as a tool for specific jobs for which it's best suited?
I look forward to hearing your thoughts here!