inline
> And maybe you should educate yourself to find out, what a feature like "weak
> references" can be used for. Else you are just not in the position to say:
> "-1 footgun most web-devs have no idea how to use correctly (including me)" -
> it is not a lack of the feature, but a lack of you
Kai, you are not speaking for all Web-Developers here and Web-Developers
are not the only users of JavaScript, please keep that both in mind. If
you do not like the idea of e.g. weak references, do not use them. But
for some caching tasks it is just necessary and I would love to see them.
You
> Deque isn't exotic data structure - but something needed.
javascript already has deque - Array.protoype.shift and Array.prototype.unshift
> Basic trees are not exotic.
i've only once encountered a use-case that required tree-balancing algorithms
and such (and it quickly turned out to be inappro
I agree - neural networks should not belong to standard library. And that's
why I said that PHP is overbloated.
But you claimed that JS standard library is similar in size to PHP - but it
isn't, it's much, much smaller.
Deque isn't exotic data structure - but something needed. Basic trees are
not
> let javascript do what it does best - as a high-level glue-language for
web-development. and let the people who hate javascript happily write
their algo libraries in c#/c++/java/etc and ship it as wasm.
This is unfair and misleading. For those that have no intention of using
another language an
no, its far more practical and cost-efficient to leverage existing algo/neural
libs through wasm than to try and reinvent them in javascript (and constantly
change the language spec), if there is a need for them. let javascript do what
it does best - as a high-level glue-language for web-develo
> its NOT a low-level language for creating esoteric data-structures and
algorithms in academia that have little relevance to web-development.
Let's not get into the realm of opinion stated as fact. It also doesn't
make sense to say that some things are useful in Node.js but then deny
other things
inline
> WeakReferences,
-1 footgun most web-devs have no idea how to use correctly (including me)
> OGG manipulation,
-0.5 slightly prefer it as an npm module
> MPEG manipulation,
-0.5 slightly prefer it as an npm module
> builtin support for Kerberos,
impartial
> Bzip2 bindings,
-1 use nodej
I disagree.
PHP have WeakReferences, OGG manipulation, MPEG manipulation, builtin
support for Kerberos, Bzip2 bindings, Zlib bindings, configurable random
number generation, OpenSSL bindings, simple hashing, drivers for databases,
ImageMagick bindings, arbitrary precision math, statistics support,
my thoughts are the opposite. javascript (similar to perl and php) already
has a huge number of specialized builtin functions and methods accumulated
over its 20+ year evolution that pretty much solves every practical problem
encountered in frontend programming (and effectively backend as well). th
My thoughts: big source of JavaScript criticism is its small standard
library and community attempts to solve that issue - hundreds of small
modules. Significant part of lodash should be present in standard library.
My lodash selection - chunk, dropWhile, first, last, flatten, fromPairs,
pull, with
11 matches
Mail list logo
