Live data from Hacker News

Wikileaks To Leak 5000 Open Source Java Projects

steve-yegge.blogspot.com

11–20 of 140 posts

Re: Wikileaks To Leak 5000 Open Source Java Projects

#13
I sympathize, yet encapsulation is appropriate for some projects. Not all users of a library want to frequently update to their own code. Forbidding encapsulation and deprecation would increase this cost. Also, it's comforting to be able to refactor the guts of a class without harming users.

Re: Wikileaks To Leak 5000 Open Source Java Projects

#14
post #9

It's interesting to see how important compiler-enforced access specifiers were to C++ and Java. It seems they are going out of fashion. In the Python world they were always considered a bit silly.

The languages have fundamentally different goals.

If you explained Unix file permissions to a Windows guy, he'd probably think it was silly. They exist for a purpose though- just not a purpose the Windows guy has spent much time with.

Re: Wikileaks To Leak 5000 Open Source Java Projects

#18
post #13

I sympathize, yet encapsulation is appropriate for some projects. Not all users of a library want to frequently update to their own code. Forbidding encapsulation and deprecation would increase this cost. Also, it's comforting to be able to refactor the guts of a class without harming users.

The issue is less about encapsulation and more about language-enforced encapsulation. Encapsulation is good, but encapsulation that's enforced by the language is debatable.

Re: Wikileaks To Leak 5000 Open Source Java Projects

#20

Personally I would prefer a script that made all variables private and removed setters, but I suppose that would be more useful than funny.

The problem with blocking the intended side-effects in side-effect-driven programming is that the programs will break. A script to re-write all Java into Clojure would be useful, too, but really kind of not the point.
Post reply on HN