coming from a python background, it would be nice if javascript had some
core design-philosophy to guide its evolution rather than haphazardly
following fads and cues from other languages. currently, my strawman idea
of what constitutes javascripty-ness is:
"achieving your ux-workflow objective, such that passing end-to-end data
between [client/server/storage] nodes and components requires the fewest
and least-complicated transformation-steps possible."
for example, i wouldn't consider the temporal-proposal very javascripty,
since it uses excessive [class] transformations to baton-pass datetime
between nodes, compared to say ... using static-functions that input/output
mostly canonical-isostrings.
coming from a python background, it would be nice if javascript had some
core design-philosophy to guide its evolution rather than haphazardly
following fads and cues from other languages. currently, my strawman idea
of what constitutes javascripty-ness is:
"achieving your ux-workflow objective, such that passing end-to-end data
between [client/server/storage] nodes and components requires the fewest
and least-complicated transformation-steps possible."
for example, i wouldn't consider the temporal-proposal very javascripty,
since it uses excessive [class] transformations to baton-pass datetime
between nodes, compared to say ... using static-functions that input/output
mostly canonical-isostrings.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20190520/ba053893/attachment-0001.html>
coming from a python background, it would be nice if javascript had some core design-philosophy to guide its evolution rather than haphazardly following fads and cues from other languages. currently, my strawman idea of what constitutes javascripty-ness is:
"achieving your ux-workflow objective, such that passing end-to-end data between [client/server/storage] nodes and components requires the fewest and least-complicated transformation-steps possible."
for example, i wouldn't consider the temporal-proposal very javascripty, since it uses excessive [class] transformations to baton-pass datetime between nodes, compared to say ... using static-functions that input/output mostly canonical-isostrings.