Google’s copying of the Java SE API was fair use [pdf]

Re:Google’s copying of the Java SE API was fair use [pdf] by ChrisMarshallNY on Monday April 05, 2021 @11:04AM (#26699969)

It's been going on since the 1960s (maybe longer).

Personally, I think the best code is the code I don't write.

A significant part of my refactoring, is removing as much code as possible, by tweaking algorithms, deriving common base classes, and removing unused code branches.

Every line of code is a potential bug. The less code, the less bugs.

[ Parent | on HN ]

Re:Google’s copying of the Java SE API was fair use [pdf] by beckingz on Monday April 05, 2021 @12:56PM (#26701495)

Negative lines of code are a good day's work.

https://www.folklore.org/StoryView.py?story=Negative_2000_Li...

[ Parent | on HN ]

Re:Google’s copying of the Java SE API was fair use [pdf] by ChrisMarshallNY on Monday April 05, 2021 @01:16PM (#26701747)

Love that story!

[ Parent | on HN ]

Re:Google’s copying of the Java SE API was fair use [pdf] by BXLE_1-1-BitIs1 on Monday April 05, 2021 @01:46PM (#26702101)

There's a number of times I added significant new function to programs while ripping out great gobs of code.

My favorite was replacing a function call with a single character constant.

Then there were two employers who demanded code proliferation (management incentives tied to KLOCs?). Didn't last long at either place.

[ Parent | on HN ]