Wikileaks To Leak 5000 Open Source Java Projects

Post by deno » Thu, Jul 29, 2010, 5:59 PM UTC

smcl wrote: post #103

maximilian wrote: post #99

Earlier quoted context omitted.

Higher rate my foot. Cell phones in Switzerland and Germany are crazy expensive. It costs people like 0.20 cents to call someone with a phone, and I pay like 0.25 cents or something. When I used to have a phone in Germany, I used to spend upwards of 90 euros a month calling like I was used to in the states, where I basically have as much calling as I need for $50 (including tax and all that sneaky bullshit). Cell pho…

Is that 0.25 cents (as written) or 25 cents ?

Post by MartinCron » Thu, Jul 29, 2010, 6:56 PM UTC

SoftwareMaven wrote: post #74

MartinCron wrote: post #56

Earlier quoted context omitted.

One of the things that I have used access controls for is to simplify the exposed surface that collaborators work with. This isn't a condescending "I don't trust you" intention. It's more along the lines of "of all the types and methods here, you only need to know about this small subset". It's customer service, I tell ya! And if the API isn't sufficient by not exposing enough, that's fine. It's always easier to expo…

Maybe easier for you (very debatable), but never easier for the guy who needed something exposed today to get his job done. I have never been bitten by over-promiscuous code entries in Python. The times I've gone beyond the published API, I knew I was doing it so I knew I had to keep track of it. And I've gone deep here (replacing Django's database handling in their unit testing framework). On the other hand, I can't…

Post by infinite8s » Thu, Jul 29, 2010, 7:17 PM UTC

sprout wrote: post #39

For a second I was actually hoping someone leaked Google's internal stack and all of it was GPL.

Post by infinite8s » Thu, Jul 29, 2010, 7:25 PM UTC

dustrider wrote: post #97

I can't decide whether this is serious or not. Don't doubt the actual wikileaks announcement just the comments from the various sources seem too funny to be true. favorite: "But use it exactly how I tell you to use it, because fuck you, it's my code. I'll decide who's the goddamn grown-up around here."

Post by MartinCron » Thu, Jul 29, 2010, 8:49 PM UTC

SoftwareMaven wrote: post #126

MartinCron wrote: post #123

Earlier quoted context omitted.

You may have a planes-that-crash bias there. You don't notice all the times you benefit from a well encapsulated service because it just works the right way. The rare handful of times when something that would be useful is marked private is what sticks out in your mind. I know that I would prefer to work with an interface with 10 public classes with 50 public methods than an interface with 100 public classes with 500…

Your argument assumes that you need language-enforced mechanisms in order to define a well-encapsulated API. That is simply not that case, as the many well designed APIs in Python, Ruby, and Lisp can attest (and many poorly designed APIs in Java as well). You can use documentation, conventions, and other mechanisms to define the publicly exposed API so one doesn't have to know the guts. But when I need to deviate fro…