by matttthompson on 9/25/14, 7:00 PM with 28 comments
by matttthompson on 9/25/14, 7:11 PM
by treve on 9/25/14, 7:31 PM
However, I think the library name is a bit of a poor choice. I don't want to take away your thunder, I just picked this post to do my rant :).
There seems to be a lot of new general-purpose libraries with very poor non-descriptive names coming out.
Whenever I need to dive into a new codebase, in a language and ecosystem I'm unfamiliar with, it's extremely hard to figure out which dependency and library does what. I was tasked to dive into a massive RoR application recently, and I ended up having to write a glossary first to remember what every non-descriptive noun implied.
After getting familiar with a particular language's ecosystem, this problem becomes tends to go away, and as a library writer, it becomes easier to fall into the same trap by picking a name that's marketable and distinct.
But I feel we're collectively making it increasingly harder for people to ramp up in new ecosystems and maintain future legacy codebases.
For names of large applications this is not as bad, and some of these applications become household names, but I think we should try to avoid this for general-purpose utilities.
by perishabledave on 9/25/14, 9:27 PM
So... what do those guys at Panic have you working on? ;)
by ardfard on 9/26/14, 2:35 AM
by jtokoph on 9/25/14, 7:28 PM