Are you sure? All the discussion I can find online makes it seem to me like TPL and friends are just executing tasks on thread pools until completion. (see e.g., https://github.com/dotnet/runtime/issues/50796 for some discussion)
I don't think this is the same thing. As far as I can tell, the task abstraction is a threapool where you can submit operations and return futures. If a task blocks indefinitely, the underlying threadpool OS worker thread will be blocked, and the threadpool either has to run with less resources or spawn a new worker. Virtual threads are an M:N abstraction: blocking on a virtual thread will not block the underlying OS thread.
.NET might indeed have a virtual thread abstraction and if it does you could of course implement the Task abstraction on top of either virtual threads or OS threads, but what you linked to is not a proof that it does.
That looks similar to Java FutureTasks + Executors which is a very different concept from virtual threads.
Virtual threads mean that a blocking thread can yield to any other non blocking thread seamlessly and with very little overhead. .NET Tasks cannot do this as far as I can tell.
> Virtual threads offer a more efficient alternative to platform threads, allowing developers to handle a large number of tasks with significantly lower overhead.
they should have just called them "Tasks" leaving the already overloaded term "virtual" out of the conversation.
We went through a lot of iterations on what they should be called. They were originally called Fibers, but since they were extremely thread like it was decided they should be actual threads, so they should be some type of thread. Once that decision was made the question then becomes which adjective to add to Thread, and things like LightWeight, Small, etc. were ruled out as smaller or more lightweight threads might be introduced in the future.
IMHO virtual is the perfect word. The JVM's entire schtick is abstracting (virtual) hardware (machine). A simple API pertaining to intent, that can be materialized depending on OS and hardware.
Calls are virtual, though under the hood the compiler may inline them.
Memory is managed, though through analysis some allocations will go on the stack.
Threads are now (no full grandfathering, but they tried) virtual, and the runtime may now optimize them differently on different OSes and hardware.
JavaFX is not really a part of Java and isn’t actually shipped with most builds of OpenJdk. Azul Zulu is the only build that I know of that you can get FX built in.
Agreed, I feel like I’ve seen this pitch before. Intel’s OneAPI was supposed to solve this heterogeneous hardware/platform problem but doesn’t seem like they’ve made any dent.
Curious to see what Modular is planning. They’ve definitely got star power so hopefully it’s not just hype.
AI defamation is just the next iteration of fake news which was an evolution of spam and trolling which is correlated to anonymity and freedom of speech. So just saying that tech is accelerating processes that would otherwise be so slow to be impossible but also that human rights feed into these bad results, and is not just about tech or big corps but also about our excessive reliance on tech, eg trusting wikipedia and google results and chatbots, at the end it’s humans trusting the wrong sources, regardless of how sources are coming to exist
The Italian gov might be crowded with subpar intelligence, but OpenAI didn’t do a great job at reassuring people either in terms of how they handle data, how they trained models, what they share with plugins, privacy and security blah blah
that will largely depend on how you market yourself. most people (at least in the industry I work in -- design) will go from job to job and get hired purely based on their written experience, with just a resume and a very simple pdf portfolio.) other, like myself on the other hand, try to market themselves, for example as consultant or freelancers and in this case having a publicly available portfolio, that you can show to people and that you can drive traffic towards does greatly help with getting offers.
that being said, I personally am not at a point where I get a lot of offers just through my website, I find that LinkedIn is still the no. 1 tool when it comes to networking with potential clients, but I'm continuing to improve and see what others -- that do mainly get clients from just them visiting their portfolio -- are doing differently.
