Hacker News Reader

Or simply have a repo per language. That at least dedupes across each language (where there are often many projects reimplementing the same functions)

View on HN

What I meant is not incompatibility of basic types across languages but the tendency to create named classes where they are not needed. For example the OOP tells us to create UserList.java instead of using List<User> because it allows attach behavior and preserve encapsulation.

Having 325 results for UserList.java in Krugle:

http://opensearch.krugle.org/document/search/#query=userlist...

I can't image how to create globally reusable function that has the list of users in the signature.

Oh, interesting, thanks for clarifying.

Reply on news.ycombinator.com