3 ms·

Javascript doesn't have a good enough standard library to execute on this. You need frameworks just to patch up the runtime (or otherwise avoid the holes). Last

Javascript doesn't have a good enough standard library to execute on this. You need frameworks just to patch up the runtime (or otherwise avoid the holes). Last time I checked they didn't even have decent hashmap or set implementations (let alone decent serde support).

wbobeirne 2y ago
This was true in the lodash and jquery as essential days, but hasn't been the case for years. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
- ForTheKidz 2y ago
  Ah, I stand corrected. I have more recent examples but I struggle to recall them. Map and Set were certainly the two largest absences I remember.
  - stank345 2y ago
    Yeah, those were two big sticking points. There's also Object.groupBy() now which was another thing I always missed from the standard library. Proposals tend to get adopted at a snail's place but it's neat to see what's coming down the pike: https://github.com/tc39/proposals https://github.com/tc39/proposals
  - runako 2y ago
    Worth noting that those features were indeed added after the creation of e.g. React, but both have been widely available for ~10 years now.
- romellem 2y ago
  > hasn't been the case for years For 10 years, actually. ES6 - otherwise known as ECMAScript 2015 - did in fact come out 10 years ago. - https://en.wikipedia.org/wiki/ECMAScript_version_history#6th_Edition_%E2%80%93_ECMAScript_2015 https://en.wikipedia.org/wiki/ECMAScript_version_history#6th... It truly did improve the JS landscape by an order of magnitude. For those unfamiliar with the extensive features this brought to JS, here is a good list: - https://rse.github.io/es6-features/ https://rse.github.io/es6-features/
  - everybodyknows 2y ago
    ES6 modules make it straightforward to reform great piles of unstructured JS hackery into hierarchical dependency-controlled units for which you can actually reliably draw a block diagram. Hmm, or maybe get Claude to draw it for you ...
onli 2y ago
No regular frontend needs any of that. Serde support, that's a ridiculous requirement for painting some web boxes on a display. Plus, as the other comment noted, the basic JS types go a long way now.
- ForTheKidz 2y ago
  You don't need javascript at all to render. Oh for a version of the WWW that never allowed javascript at all.... money destroys absolutely everything it touches.
metalforever 2y ago
Alright, I've been in the industry a very long time but moved to backend when it got complex. I am wondering why you need a decent hash map or set implementation. This is supposed to be done on the backend. The frontend is for presentation. Your backend should not give you elements with duplicates (why you don't need set). "Decent hash map" sounds like you just don't like the hash map implementation because you are trying to do something complex with the Map implementation, in which case it belongs on the backend.
- deleted 2y ago
  [deleted]

wbobeirne 2y ago

This was true in the lodash and jquery as essential days, but hasn't been the case for years. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

ForTheKidz 2y ago
Ah, I stand corrected. I have more recent examples but I struggle to recall them. Map and Set were certainly the two largest absences I remember.
- stank345 2y ago
  Yeah, those were two big sticking points. There's also Object.groupBy() now which was another thing I always missed from the standard library. Proposals tend to get adopted at a snail's place but it's neat to see what's coming down the pike: https://github.com/tc39/proposals https://github.com/tc39/proposals
- runako 2y ago
  Worth noting that those features were indeed added after the creation of e.g. React, but both have been widely available for ~10 years now.
romellem 2y ago
> hasn't been the case for years For 10 years, actually. ES6 - otherwise known as ECMAScript 2015 - did in fact come out 10 years ago. - https://en.wikipedia.org/wiki/ECMAScript_version_history#6th_Edition_%E2%80%93_ECMAScript_2015 https://en.wikipedia.org/wiki/ECMAScript_version_history#6th... It truly did improve the JS landscape by an order of magnitude. For those unfamiliar with the extensive features this brought to JS, here is a good list: - https://rse.github.io/es6-features/ https://rse.github.io/es6-features/
- everybodyknows 2y ago
  ES6 modules make it straightforward to reform great piles of unstructured JS hackery into hierarchical dependency-controlled units for which you can actually reliably draw a block diagram. Hmm, or maybe get Claude to draw it for you ...

onli 2y ago

No regular frontend needs any of that. Serde support, that's a ridiculous requirement for painting some web boxes on a display. Plus, as the other comment noted, the basic JS types go a long way now.

ForTheKidz 2y ago
You don't need javascript at all to render. Oh for a version of the WWW that never allowed javascript at all.... money destroys absolutely everything it touches.

metalforever 2y ago

Alright, I've been in the industry a very long time but moved to backend when it got complex. I am wondering why you need a decent hash map or set implementation. This is supposed to be done on the backend. The frontend is for presentation. Your backend should not give you elements with duplicates (why you don't need set). "Decent hash map" sounds like you just don't like the hash map implementation because you are trying to do something complex with the Map implementation, in which case it belongs on the backend.

deleted 2y ago
[deleted]