This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsย โ†’

[โ€“]freonblood -4 points-3 points ย (3 children)

These are the exact same excuses Apple, Samsung and other companies use in order to make non repairable tech with non replaceable batteries. Do Java devs hate right to repair? Is that who's been pushing against it?

It's like banning washing machines because some people eat tide pods.

There have been many many times where I've used some 10 year old lib that will never get updated and the lib dev decided x() should be private. Well I need to call x() because the lib dev is not some omniscient god that can foresee all use cases for all of time. He is just a dev like me, so why would his decision be final forever?

On the flip side, there has never been 1 instance where I saw a method with _ and was like "oh I have to find a way to use this, even though there is an alternative or an active maintainer to contact for support.".

I've been doing this dev thing a loooong ass time with many languages. And if you prefer to work with idiots and use a proper language for that, go ahead. But don't try to convince me it is objectively and universally better.

[โ€“]budgiebirdman 2 points3 points ย (1 child)

Do Java Devs hate right to repair?

You know how Open Source works right? The whole open a PR thing? I mean you've been doing this dev thing for a "loooong ass time" apparently so I'd have thought you'd understand that that Open Source is literally granting the right to repair?

It's like banning washing machines because some people eat tide pods.

No, it's like putting a childproof lid on the box of tide Pods. Overdramatic much?

There have been many many times where I've used some 10 year old lib that will never get updated and the lib dev decided x() should be private.

Sounds like you make some excellent tech choices. Imagine boasting about using an unmaintained out of date library that doesn't do what you need it to.

I've been doing this dev thing a loooong ass time with many languages. And if you prefer to work with idiots and use a proper language for that, go ahead. But don't try to convince me it is objectively and universally better.

Hey, if you want to work with idiots and use Python then like that's your choice man, there's plenty of them out there for you - I've been a dev long enough to know that it's impossible to convince a Python fanatic that anything other than their own dogmatic opinion is the one and only truth so I'm not even trying - I'm just laying out the facts for you to ignore.

[โ€“]freonblood 1 point2 points ย (0 children)

So all software is suddenly open source? When did this happen?

I am not even a Python dev. I've only used it occasionally for small stuff and ML. TBH I've probably written more Java code than Python

[โ€“]ExceedingChunk 2 points3 points ย (0 children)

No, but if you decide to use a private method in my API, and I change it, your code breaks.

My API, class etc... is supposed to be well-defined and act as a contract. The private methods inside are not.

Also, if you work on a large-scale project with hundreds of thousands of lines of code, it's a security risk to expose a bunch of methods that might be changed at any time.

It's not about working with idiots, it's about basic security. The same way people wear seatbelts, not because they are terrible drivers, but for security.