3 ms·
Isn't that the same with _any_ ecosystem? Ruby => Rails (most of the time...) Python => Django NodeJS => ExpressJS Ruby => RubyGems + Rake + Bundler Python =>
by edwinnathaniel 11y ago
Isn't that the same with _any_ ecosystem?
Ruby => Rails (most of the time...)
Python => Django
NodeJS => ExpressJS
Ruby => RubyGems + Rake + Bundler
Python => (finally something ... static) pip
NodeJS => NPM
Browser JS => Bower
NodeJS tries to be as simple as possible but at the end of the day, you need to use/download/learn libraries with different quality/documentation level and different API-feel/code-style.
- serve_yay 11y ago> Isn't that the same with _any_ ecosystem? It is!
- reilly3000 11y agoExcept it isn't. Attributes of languages include their documentation syntax and extension API. Getting this right makes a remarkable difference for how easily a person can grok a new library or extension and make it useful. A good language has a common "language" overall, not just code syntax.
- bshanks 11y agoWhich language(s) do you think do a particularly good job of documentation syntax and extension API?
- lmm 11y agoJava libraries tend to have "magic" that alters the language semantics. E.g. Spring's dependency injection breaks your reasoning about how an object is constructed. Hibernate breaks your reasoning about when object fields can change. Tapestry breaks your reasoning about basically everything. There's a difference between a library that follows the rules of the language and a framework that changes them. (admittedly to a certain extent I've heard the same said of rails)