File:White x in red rounded square.svg Closed discussion, see full discussion. Result was:
:The following is an archived discussion concerning one or more redirects. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review). No further edits should be made to this section.
:The result of the discussion was delete
. signed, Rosguill talk 20:57, 6 May 2022 (UTC)
Virtual threads are not synonymous with Green threads, because green threads were one implementation of virtual threads, which is a larger concept. Therefore this redirect prevents review of a draft of a separate article on Draft:Virtual threads. There should be two separate articles, each cross-referencing the other.
It seems that the best way to resolve this issue is by discussing deleting the redirect (and then deleting the redirect, permitting two articles). Robert McClenon (talk) 18:56, 6 April 2022 (UTC)
:
{{resize|91%|Relisted to generate a more thorough discussion and clearer consensus.}}
Please add new comments below this notice. Thanks, ✗plicit 12:11, 14 April 2022 (UTC)
- Keep I am unconvinced that these are actually separate things; the lead of the article and the draft are basically identical. * Pppery * it has begun... 19:01, 14 April 2022 (UTC)
- Delete
:I wrote much of the Virtual Threads draft.
:Virtual Threads and Green Threads Are not the same thing
:Green Threads is some old single-threaded library unavailable for the last 20 years. I was a multi-threaded Java programmers for six years in the 2000s, I never heard of Green Threads.
:Virtual Threads is a many-to-many massive preemptive scheduling onto multiple parallel operating system threads
:The very important difference is that Virtual Threads uses all execution units of the hardware thereby providing about 10x performance gain at the price of multi-threaded synchronization. As far as I know, only Google and Oracle have implementations for public consumption. Google had it first, then Oracle spent five years getting it into Java. Virtual threads is suddenly important, because since 2020 consumer hardware often have a dozen execution units
:The other simpler thing that is much more common is coroutine-style time-sharing of a single thread, which is still single-threaded programming and brings no performance gains. This is where many scripting languages are stuck because of the Global Interpreter Lock. This is what Green Threads is. This is used because it can be implemented in an afternoon rather than five Oracle years rewriting the language runtime. Virtual Threads is extremely difficult to retrofit, which is why Google invented a new language Go. And it took Google five years getting virtual thread preemptive scheduling into Go.
:Green Threads is some 20-year-old no longer available library once used in Java by Sun Microsystems. It’a T-Ford most people have never heard of. Haraldrudell (talk) 01:39, 17 April 2022 (UTC)
:
{{resize|91%|Relisted to generate a more thorough discussion and clearer consensus.}}
Please add new comments below this notice. Thanks, CycloneYoris talk! 06:00, 22 April 2022 (UTC)
:: The article Green threads is about a general concept, not a specific Java library from my reading. * Pppery * it has begun... 05:06, 27 April 2022 (UTC)
- Comment - The redirecting of Virtual threads to Green threads was a serious violation of the Common Name guideline. Green threads violates the principles of recognizability and naturalness. A person with a background in information technology will have at least a general idea what is meant by virtual threads, and no idea what is meant by green threads, unless familiar with this particular implementation. So the redirection either was in the wrong direction or should not have been done, and in fact should not have been done. If virtual threads and green threads were the same, then Virtual Threads should be the primary title. However, green threads were only a particular implementation of virtual threads, and, has been noted, not as powerful as more modern implementations. Robert McClenon (talk) 01:08, 30 April 2022 (UTC)
:The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.