Yeah, but you've probably done a read and write independently. This is just about joining the two together.
> There's a method in one of the apache commons libraries for that.
Yup, and that's great to use that, and you'll no doubt end up with more efficient code most of the time if you do. But... you still should be able to write correct code for reading bytes from one stream, writing to another, without losing data in between.
With access to Google and the library documentation sure, but I don't use those APIs often enough to be worth keeping in memory.
Why the heck would you need Google
> and the library documentation
It's an online quiz.
> sure, but I don't use those APIs often enough to be worth keeping in memory.
You don't worry about it, but it tends to accumulate in one's mind anyway.
Here's the thing though. People are posting solutions on HN... and getting it wrong.
I guess I've been stuck in webapps and NoSQL libraries for a while now.
The methods are the same with a buffered input reader.
> I've written a command line in Java that reads commands, runs native commands, streams output to the console and even that doesn't need to read stdio as a stream.
So, the thing that you are struggling with is how to get to System.in? But no problem doing System.out?
That's not even what the various code samples that have been posted have failed.
> It's not that Java can't do that, it's that there are better idioms for most problems.
Java's actually very good at doing IO efficiently, and as has been demonstrated, the code for this is quite simple. Sure, you wouldn't implement "cat" in Java, but you would read and write to sockets & files with it, which provides all the knowledge one might need to figure out how to solve this. As has been pointed out, the Apache Commons libraries make it so this is a two line program with no branching or looping. That's about as simple as it gets.