And that's kind of the idea that all the big companies have. See Typescript (Microsoft), Golang/Kotlin (Google), Rust (Mozilla), Swift (Apple) etc... fix "old" (like all the ones you mentioned) and limiting languages.
Everyone wants to make a language only with "good stuff", and I don't think these big companies - with huge budgets and whole teams of engineers - enjoy making crappy languages.
If you really want to start this epochal work, I'd recommend you to throw down a whitepaper, providing the most valid reasons and your solutions to the respective problems. Then it will be hard to convince other programmers to learn your language.
But first, if I were you, I would better study my "competitors" such as Scala, Ruby, PHP, JS (the latest versions), Haskell, Elixir, Clojure, C# etc...
I've worked with JS quite a lot. So I know it fairly well. And I know what I'm talking about when I say that sometimes I wish something was a different way. Also, I'm not trying to compete with other languages. I'm totally fine if literally only one other person uses my language, as long as they're satisfied with it. And if I end up the only one using it, that's fine too.
I'm not questioning that you don't know what you're talking about, I'm just saying that you haven't explained the reasons for the limitations you've found.
What don't you like about Javascript? Being untyped? Being limited to memory access? Exploding when working with floating point numbers?
If you don't like the name "Javascript", or if you just want to make a language "because you want to" you are free to do so, but I don't think these are valid reasons.
And that's kind of the idea that all the big companies have. See Typescript (Microsoft), Golang/Kotlin (Google), Rust (Mozilla), Swift (Apple) etc... fix "old" (like all the ones you mentioned) and limiting languages.
Everyone wants to make a language only with "good stuff", and I don't think these big companies - with huge budgets and whole teams of engineers - enjoy making crappy languages.
If you really want to start this epochal work, I'd recommend you to throw down a whitepaper, providing the most valid reasons and your solutions to the respective problems. Then it will be hard to convince other programmers to learn your language.
But first, if I were you, I would better study my "competitors" such as Scala, Ruby, PHP, JS (the latest versions), Haskell, Elixir, Clojure, C# etc...
I've worked with JS quite a lot. So I know it fairly well. And I know what I'm talking about when I say that sometimes I wish something was a different way. Also, I'm not trying to compete with other languages. I'm totally fine if literally only one other person uses my language, as long as they're satisfied with it. And if I end up the only one using it, that's fine too.
I'm not questioning that you don't know what you're talking about, I'm just saying that you haven't explained the reasons for the limitations you've found.
What don't you like about Javascript? Being untyped? Being limited to memory access? Exploding when working with floating point numbers?
If you don't like the name "Javascript", or if you just want to make a language "because you want to" you are free to do so, but I don't think these are valid reasons.
Small nitpick: Everything in JS is a float, so it always explodes. :P