this post was submitted on 25 Sep 2024
893 points (87.5% liked)

Programmer Humor

19817 readers
65 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 months ago* (last edited 2 months ago) (2 children)

Library built this way because it supposed to be flexible and provide ground for complex usecases. It can only be flexible if your API works with simple abstractions which you can then compose. It’s not driven by “I need this specific utility for this specific scenario”. That would be zoo you have in JS where you have 10 ways to iterate over array and 9 of them wrong for your scenario.

Java’s OO is great because they design library with SRP in mind making sure there is few but good ways to do things.

BufferedReader cannot accept file name because it makes arbitrary reader… well buffered. It’s not BufferedFileReader, even that would accept something like Path or File, not string, because File can be remote file, should Reader now know all possible local and remote protocols and path formats? What else it must do?

Having it designed the way it is, allows Java to have utilities for various scenarios. Your scenario covered by standard lib too. See Files.readAllLines which, surprise-surprise, built on top of BufferedReader.

[–] [email protected] 6 points 2 months ago (1 children)

BufferedReader cannot accept file name because it makes arbitrary reader… well buffered. It’s not BufferedFileReader, even that would accept something like Path or File, not string, because File can be remote file, should Reader now know all possible local and remote protocols and path formats? What else it must do?

You're just describing the problem. Yes, I see where they're going with this. It's still a usability nightmare. I can't think of another language that makes you jump through hoops like this on IO, and they get along fine without it.

[–] [email protected] 2 points 2 months ago

I agree with you. It's a neat design idea to make things a bit more maintainable perhaps, but it's just annoying to program with.

[–] [email protected] 2 points 2 months ago

Library built this way because it supposed to be flexible and provide ground for complex usecases.

It’s definitely that, and not the fact that it was written in the first half of the nineties when everyone and their mother was all in on OOP/OOD to the detriment of usability.