What I don't like in JavaScript

Post by wruza » Wed, Apr 16, 2025, 8:47 PM UTC

hajile wrote: post #9

wruza wrote: post #6

What I don't like is lack of features that would erase whole classes of software around it. For example, function environments (substitute the global scope with another object for a single invocation) could delete lots of code and paradigm from vue/rx-likes. It also neither supports operator overloads (good thing in general) nor has a decimal type which is a must for human numbers like euros and kilograms. Rather it…

There is a decimal proposal for JS. It almost certainly won't use normal operators though because of the JIT implementor complaints about adding BigInt (not to mention recently dropping the record/tuple proposal over `===`). https://github.com/tc39/proposal-decimal

Then it's of little use imo. Library decimals already exist in multiple optimized forms.

Post by hajile » Thu, Apr 17, 2025, 2:08 AM UTC

wruza wrote: post #11

hajile wrote: post #9

Earlier quoted context omitted.

There is a decimal proposal for JS. It almost certainly won't use normal operators though because of the JIT implementor complaints about adding BigInt (not to mention recently dropping the record/tuple proposal over `===`). https://github.com/tc39/proposal-decimal

Then it's of little use imo. Library decimals already exist in multiple optimized forms.

It would still use faster JIT mechanisms internally and make strong guarantees, but the interface would suck.

JS really needs to add a "use type" or typed module feature with strong Hindley-Milner types. This would allow them to cut the rest of the really bad parts like the bad type coercion, but definite types would also mean that adding these new features to typed modules only would get rid of the performance issues for stuff like operator overloading because the types would be known in advance.

Re: What I don't like in JavaScript

Re: What I don't like in JavaScript