Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
Streams is an universal concept not specific to any particular language. It originates from ancient Unix, most famously the stdout and stdin streams. And so they exist in pretty much any "C family" programming language and probably in a lot of other languages as well. Therefore stream is not a useful name and having Java as parent tag would be plain wrong.
What makes Java stand out is the outright ridiculous amount of different streams available, implemented as abstraction layers. Making a tag per Java stream would probably be way too detailed, but I'm not sure any users will find their way to some generic "java-stream" tag. Perhaps instead create tags with names corresponding to commonly used libraries, such as java.util.stream?
0 comment threads
Is stream the right name, or should it be more specific? If you came across that tag in the wild, would it be obvious that it's Java streams? We also have filestream, node:stream, QTxtStream, vfs-stream, and the more general data-streaming.
A moderator can both rename the tag (if that's warranted) and make it a child of java, but I think we want to get the name nailed down first to avoid confusing people with the parentage.
I'm butting in here as a non-expert to ask the question; I don't have an actual opinion on this.
1 comment thread
0 comment threads