You are reading a single comment by @BobFrankston and its replies.
Click here to read the full conversation.
-
I think if a tutorial / guide includes third party code/module/something, a version number would be really helpful. Most likely more informative than a simple last modified timestamp. (You mean last modified date on the docs site. For some reason Robin and / or MaBe seems to think about timestamp here?)
And a "support status" of the thing. Some JS modules state something like "Module xy is extremely beta.".
The docs site in my experience:
- Information about official Espruino's is usually pretty up to date. If there is a breaking change, usually the docs are updated, or someone notices and pings Gordon.
- Info about ESP8266 and ESP32, is a bit outdated - that's community effort...
- Info about third party stuff that don't get enough use, like VSC/TS integration - well, yeah :/
On the other hand: if there is no breaking change, stuff works just as it worked years ago, should someone just crawl the whole docs site, and bump last modified if it still works?
The link at the bottom of the page is useful: Last updated, and also list of commits, so you can the see changes as well.
- Information about official Espruino's is usually pretty up to date. If there is a breaking change, usually the docs are updated, or someone notices and pings Gordon.
AkosLukacs
@BobFrankston
Same reason you put a use-by date on food packages. If the VSC post hasn't been updated in 2 years I know that it's a dead-end and no one cares. I can't update till it works well enough for me to learn.
In this particular case, it seems to have been an incomplete effort and worth a reboot rather than a fix. I strongly want VSC/TS support but will start a new thread.