part-1/
>
>> On Mon, Aug 17, 2020 at 2:56 PM Dan Peddle wrote:
>> This feels like rich territory for a blog post, if someone feels qualified?
>> Specifically, just running the typescript tool chain for jsdoc annotations,
>> which are excellent for all the reasons men
This feels like rich territory for a blog post, if someone feels qualified?
Specifically, just running the typescript tool chain for jsdoc annotations,
which are excellent for all the reasons mentioned above (comments only, vanilla
js etc).
> On 17. Aug 2020, at 19:35, Andrea Giammarchi
>
Have to agree, mixing sync and async code like this looks like a disaster
waiting to happen. Knowing which order your code will be executed in might seem
not so important for controlled environments where micro optimisations are
attractive, but thinking about trying to track down a bug through
It's really a shame few mention jsdoc anymore. It provides mechanisms to
achieve all of these developer experience quality of life improvements without
needing transpiling, and on top of standard js of various flavours,
progressively.
> On 26. Mar 2019, at 06:43, Ranando King wrote:
>
>
imagine you are shipping a module for use by others, and you don't want to
expose internals to consumers. private methods and properties help to know that
only the public API is in use, giving confidence in publishing updates or fixes.
another use case is knowing that naughty developers aren't
horic if", as it allows the body of the statement
> to
> refer back to the condition value. It's especially helpful in languages
> with
> truthiness, which ECMAScript has, as it allows access to the *specific*
> truthy
> value without further finagling.
>
> Thoughts?
>
gt;
>
> _______
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
--
Dan Peddle
*tel*: +49 157 3918 2066
*email*: d...@flarework.com
*www*: http://flarework.com
*in*: http://pt.linkedin.com/in/dan
7 matches
Mail list logo
