This doesn't tell us much and could simply be Typescript replacing some JavaScript as they say. Would be nice to see the actual figures. I suspect combined together they would show a steady figure.
JavaScript is effectively deprecated next to TypeScript. You’ll see some projects in the middle clutch to “type annotated” JavaScript but it’s not popular. Most JS is untyped and on its way out.
I dislike TypeScript, and I feel it's mostly fake. There are plenty of ways to accidentally bypass the "type system" and do stuff that should be illegal in a statically typed language but work because there's JavaScript underneath. I feel TypeScript adds extra cognitive load that isn't necessary and isn't really adding much value. JavaScript is simple, easy, and works well. I wish more people would invest in learning to write better JavaScript, than to have the flaky facade on top of it.
Then again, I'm not a front-end dev, I just do hobby projects with JS.
TS is fake in the sense that so many developers believe it to be more powerful than it actually is. If you use `any` at any point then you have virtually no guarantees. It also only helps partially when you don't validate data during runtime. Unfortunately, I've seen many developers write code as if no checks are needed during runtime because of Typescript, yet their application receives data structures from the outside.
If you are mostly writing JS to enhance a web page, I would say it is good enough.
I recently to wrote an application that interfaces with a non-trivial Json API which returns many different data types.
I defined all the interfaces produced by the API in TS, and once this was done the app practically wrote itself with hardly any surprises.
With the data structures documented, the logic is concise and readable. To me, this is "better Javascript".
Of course, if the API changes, randomly all the types are a lie... it would be nice if I could reuse the types to do some runtime validation of fetch results, pydantic-style.
JavaScript is actually awesome the same way that Python and Ruby are. The fact it is loosely typed makes it great for just whipping up something quick. For my own projects, I use plain JavaScript and may or may not use types via JSDoc. I'm not saying JavaScript isn't flawed, but I am more accustomed to it.
Typescript may have supplanteed plain JavaScript for production JavaScript applications. That doesn't mean there is no point in plain JavaScript ever. For many things I write, I have little interest in the strictness of even the loosest Typescript settings.
In terms of Typescript syntax, I don't think I would use it outside of my job at this point. Types are a good idea, but I have found JDDoc to be good enough in most cases.
I don't know if it makes sense to count TypeScript and JavaScript separately. We don't count type-annotated Python separately...
Should probably just read GitHub's post that this is entirely based off of: https://github.blog/news-insights/octoverse/octoverse-2024/
This doesn't tell us much and could simply be Typescript replacing some JavaScript as they say. Would be nice to see the actual figures. I suspect combined together they would show a steady figure.
Javascript + Typescript would be 1st
JavaScript is effectively deprecated next to TypeScript. You’ll see some projects in the middle clutch to “type annotated” JavaScript but it’s not popular. Most JS is untyped and on its way out.
I dislike TypeScript, and I feel it's mostly fake. There are plenty of ways to accidentally bypass the "type system" and do stuff that should be illegal in a statically typed language but work because there's JavaScript underneath. I feel TypeScript adds extra cognitive load that isn't necessary and isn't really adding much value. JavaScript is simple, easy, and works well. I wish more people would invest in learning to write better JavaScript, than to have the flaky facade on top of it.
Then again, I'm not a front-end dev, I just do hobby projects with JS.
TS is fake in the sense that so many developers believe it to be more powerful than it actually is. If you use `any` at any point then you have virtually no guarantees. It also only helps partially when you don't validate data during runtime. Unfortunately, I've seen many developers write code as if no checks are needed during runtime because of Typescript, yet their application receives data structures from the outside.
If you are mostly writing JS to enhance a web page, I would say it is good enough.
I recently to wrote an application that interfaces with a non-trivial Json API which returns many different data types.
I defined all the interfaces produced by the API in TS, and once this was done the app practically wrote itself with hardly any surprises.
With the data structures documented, the logic is concise and readable. To me, this is "better Javascript".
Of course, if the API changes, randomly all the types are a lie... it would be nice if I could reuse the types to do some runtime validation of fetch results, pydantic-style.
That's sort of nonsense.
JavaScript is actually awesome the same way that Python and Ruby are. The fact it is loosely typed makes it great for just whipping up something quick. For my own projects, I use plain JavaScript and may or may not use types via JSDoc. I'm not saying JavaScript isn't flawed, but I am more accustomed to it.
Typescript may have supplanteed plain JavaScript for production JavaScript applications. That doesn't mean there is no point in plain JavaScript ever. For many things I write, I have little interest in the strictness of even the loosest Typescript settings.
In terms of Typescript syntax, I don't think I would use it outside of my job at this point. Types are a good idea, but I have found JDDoc to be good enough in most cases.
AI will not replace developers, it will just push them to use Python..
Where Rust??
Even Go is struggling to make top 10s.
2024 is wild for programming languages.