Note that there are some explanatory texts on larger screens.

plurals
  1. POJava data streaming class selection
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIf you're not aware of the functionality of all the stream-based classes in Java, do you think it's really appropriate to assert that there are too many? Perhaps you meant: "I'm confused by all the stream-based classes in the Java API" which would be rather less argumentative.
      singulars
    2. COThere are too many. If there's so many as to confuse me, there are more than are necessary, since many languages only require one. Java branches off with many specific subtypes - for what I assume is readability and simplification of code - but it complicates the development process by selection. Too many for what is needed. Just my opinion - not gospel. After all, if it's necessary for me to research and know which type to use for a specific situation, that's just ridiculous. In another language, they have one binary reading construct. Maybe less generalized but is more fundamental
      singulars
    3. COCertainly just opinion, and one which I disagree with. By extension, perhaps there should actually just be *one* class - not just for IO, but for *everything*? Then you'd never have to select anything. Clearly that's ridiculous - it makes sense to pick the right class for what you want to represent... and that's true for IO as well. Perhaps you'll find that when you understand the types available a bit better, you'll find your code clearer due to the split...
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload