# 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 11
# self = https://watcher.sour.is/conv/syipe3a
@abucci Dependendies suck πŸ˜†

Too many moving parts πŸ€¦β€β™‚οΈ
@abucci Dependendies suck πŸ˜†

Too many moving parts πŸ€¦β€β™‚οΈ
@prologic This is my only problem with Go, but it applies to just about every "modern" language. Language-specific package managers make it too easy to introduce another dependency to your project.

This eventually gets to a point where you get is-even, with 207,899 weekly downloads, the full source code of which is pasted below.


'use strict';

var isOdd = require('is-odd');

module.exports = function isEven(i) {
  return !isOdd(i);
};


is-odd gets 439,933 weekly downloads, and depends on is-number which gets a staggering 68,678,128 downloads per week. I'll leave it as an exercise for the reader to go read the source code of those. Don't worry, it's not a big time commitment.
@mckinley In the specific case the NodeJS ecosystem and community,
I agree it's frankly terrible and particular Patons taken way too far to an extreme.

if you do a bit of digging you realize that this problem stemmed from a cultural belief that every single package needed to be as small as possible to the point where even single functions were packages 😳

I blame I misunderstood UNIX philosophy on this one because I think that's where it originally stemmed from but it was completely misunderstood πŸ˜†

Fortunately the Go ecosystem and community does not have such an insane view of packages and dependencies (mostly) 🀞in fact there's actually a general strong tendency to favor fewer dependencies and use more of the standard library πŸ‘Œ
@mckinley In the specific case the NodeJS ecosystem and community,
I agree it's frankly terrible and particular Patons taken way too far to an extreme.

if you do a bit of digging you realize that this problem stemmed from a cultural belief that every single package needed to be as small as possible to the point where even single functions were packages 😳

I blame I misunderstood UNIX philosophy on this one because I think that's where it originally stemmed from but it was completely misunderstood πŸ˜†

Fortunately the Go ecosystem and community does not have such an insane view of packages and dependencies (mostly) 🀞in fact there's actually a general strong tendency to favor fewer dependencies and use more of the standard library πŸ‘Œ
@prologic personally I think the problem with node in particular stems from
1. Cramming as many people as possible through "coding bootcamps" on the promise that anyone can learn to code and get a high-paying job in a few weeks
2. Companies largely using the frontend as branding and spyware, as opposed to useful applications

1. means that people learn to copy-paste from Stackoverflow or use libraries, because a bootcamp does not teach language fluency. 2. means there's corporate pressure to focus on visual design and surveillance at the expense of all else. People are given little time to design good application code, even if they had the skills to do that, which I posit the majority most likely don't.
@abucci Yup this too πŸ‘Œ
@abucci Yup this too πŸ‘Œ
@mckinley really the language authors should have added thoseto the standard spec by now. That is just obscene.
@mckinley really the language authors should have added those to the standard spec by now. That is just obscene.
@mckinley really the language authors should have added those to the standard spec by now. That is just obscene.