It seems like it should be the same, as the thread is translated as a "thread", and as a "thread". It seems like when creating a thread (thread) and in the last run it can be broken into threads?

Does this thread generate similar ones (flows are the same as it is) or does it generate threads (which apparently are inferior flows)?

Also, are the read streams (from the console, the file) and the output (to the file) the same streams?

Why then do we not call their methods start , etc., but only close ?

Or you can run the thread by creating only an object of their type?

Are these all the same streams? And yet, the presence of 2 threads with thread and with runnable is due to the fact that it is impossible to inherit with the first one, but it is easier to start, and from the second one it is possible to inherit, but is it more difficult to start?

    2 answers 2

    It seems like it should be the same thing, as the thread is translated and so and so.

    Same. Now, if you meet the term Fiber - everything is a bit more interesting there, interaction with it happens as with a thread, but it is not a classic OS thread.

    It seems like when creating a thread (thread) and in the last run it can be broken into threads?

    Cannot be broken, beget - can. Generated threads have exactly the same capabilities.

    Also, are the read streams (from the console, the file) and the output (to the file) the same streams?

    No, we are talking about execution threads, and these are data flows, i.e. just byte swapping bytes from one place to another.

    And yet, the presence of 2 threads with thread and with runnable is due to the fact that it is impossible to inherit with 1st, but it is easier to start, and with 2m it is possible to inherit, but is it harder to start?

    I don’t try to judge API architects, but you should never inherit from a stream class. In most cases, you will generally need an ExecutorService, which will take control of the threads, and you will simply give it tasks for execution in the form of a Runnable or equivalent.

      Difficult translation. "Threads" are threads and streams, although at the source it means completely different things.

      In the literature, the most commonly used translation is “streams” in both cases (where it is clear from the context which threads are in question), but some people prefer to emphasize the difference by calling treads threads.

      PS Yes, and streams in the same Java are completely different: I / O streams, Stream API.