Subj : Re: Menushell.js
To   : Tracker1
From : echicken
Date : Sat Aug 29 2020 01:37 am

  Re: Re: Menushell.js
  By: Tracker1 to echicken on Fri Aug 28 2020 14:19:02

 Tr> replace any built in functionality you like. The hardest part for me, 
 Tr> is I've spent about a decade now using Node style build tooling, modules 
 Tr> and npm; so dealing with Synchronet's load/require interfaces is a bit 
 Tr> alien in practice. That and not having the autocomplete/tooling that VS 
 Tr> Code gives you isn't very fun as well.

Much the same, where JS is concerned I do a lot of work with node (and lately React), so there's stuff from that space that I'm accustomed to (tooling, dependency management, import/require and so on).

I've been working on Synchronet projects in parallel all along, so switching between the two mindsets is sort of second nature for me. Kind of a matter of not getting set in my JS ways. (This has also been helpful when I've had to write JS for other oddball environments, like in the Rhino engine embedded in some Java applications.)

I'd like it if we had some form of versioned package (and dependency) management, and if the module import/export style were more along the lines of ES6 'import' or node.js require(). And of course there's ES6 stuff that I miss.

On the other hand, Synchronet JS is sort of "back to basics" in a fun way. Between ES5, stuff being mostly synchronous, the sort of wild west of the exec directory tree, concerns about keeping things backward compatible, etc., it can keep you on your toes and require some creative thinking.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com
 þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

.