# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 6
# self = https://watcher.sour.is/conv/2fw7dha
The problem isn't with NodeJS or NPM, it's the developers that are so willing to use horrible frameworks/libraries/tooling that is just simply not needed. NodeJS gives you so much out of the box, and NPM is simply a place to store your packages. With Deno, you won't even need a package manager as it takes a step closer to go modules approach.
If you're going to use React, TypeScript, NextJs, Webpack, Styled Components, Material UI, Jest, and the 10k dependencies that comes with it, then yeah, your dev environment is going to be slow, bloated, and incredibly frustrating to work with. Not to mention have security issues. I've literally just done a fresh create-react-app installation (latest version 5.0.1 as I write this), and boom, 6 high severity vulnerabilities.
But it doesn't have to be this way. Choose lightweight libraries that do one thing really well, and build your project from the ground up yourself.
Your primary arguments is basisally "frameworks" and I completely agree! 💯 I like Go a lot because the culture and ecosystem tends to encourage libraries over frameworks and standard library over external dependencies 👌
One thing we've talked about in the past is this ridiculous culture in the NPM (note I'm deliberately not mentioning JavaScript or NodeJS here) of packaging the tiniest / stupidest things as a "library"
This is how (I think) you end up with 10k dependencies 🤣
Your primary arguments is basisally "frameworks" and I completely agree! 💯 I like Go a lot because the culture and ecosystem tends to encourage libraries over frameworks and standard library over external dependencies 👌
One thing we've talked about in the past is this ridiculous culture in the NPM (note I'm deliberately not mentioning JavaScript or NodeJS here) of packaging the tiniest / stupidest things as a "library"
This is how (I think) you end up with 10k dependencies 🤣
Your primary arguments is basisally "frameworks" and I completely agree! 💯 I like Go a lot because the culture and ecosystem tends to encourage libraries over frameworks and standard library over external dependencies 👌
One thing we've talked about in the past is this ridiculous culture in the NPM (note I'm deliberately not mentioning JavaScript or NodeJS here) of packaging the tiniest / stupidest things as a "library"
This is how (I think) you end up with 10k dependencies 🤣
Your primary arguments is basisally "frameworks" and I completely agree! 💯 I like Go a lot because the culture and ecosystem tends to encourage libraries over frameworks and standard library over external dependencies 👌
One thing we've talked about in the past is this ridiculous culture in the NPM (note I'm deliberately not mentioning JavaScript or NodeJS here) of packaging the tiniest / stupidest things as a "library"
This is how (I think) you end up with 10k dependencies 🤣
@prologic and with some people who decide to break them to destroy thousand of projects in a couple minutes...