#2,061 in Computers & technology books
Reddit mentions of Concurrent Programming on Windows
Sentiment score: 2
Reddit mentions: 4
We found 4 Reddit mentions of Concurrent Programming on Windows. Here are the top ones.
or
- With the fun local couch co-op and online multiplayer you remember, up to four players can experience countless hours battling together.
- With beautifully refined artwork and 4K resolution support, Vanillaware's signature art style will come alive as you bludgeon, cleave, shoot, and loot through the dungeons of Hydeland.
- A newly recorded soundtrack by fabled composer Hitoshi Sakimoto, supported by a live orchestra, will accompany daring treasure hunters on their search for the Dragon's Crown.
- Rejoice, because English and Japanese audio options will now be available! Plus, game text will be localized in French, Italian, German, and Spanish.
- If you already own Dragon’s Crown, your saves won’t go to waste. There will be online cross-play & cross-save compatibility with existing PS3 and Vita versions. All patches, features, and the Storyteller Voice Pack DLC from the original game will be included.
Features:
Specs:
| Height | 9.2 Inches |
| Length | 7 Inches |
| Number of items | 1 |
| Weight | 3.3510263824 Pounds |
| Width | 2.1 Inches |
Most of what he says carries over to the .NET world with minor changes. And vice-versa - Joe Duffy's Concurrent Programming on Windows addresses some of the same things, even though it's really a Windows / .NET book.
threads are threads. The names of the functions we call change from platform to platform but the basic synchronization problems are the same everywhere.
One more plug: Allan Downey's free Little book of Semaphores will blow your mind if you're interested in really learning threads.
> You might adopt new things, but you're not adopting new ideas.
Bad ideas? No.
> Even Visual Studio doesn't work that way anymore and it's moving to more processes,
Yes, that's why the VS 2015 performance is much better than VS 2017 on the same hardware.
> For a dozen reasons, including security, performance
Can you elaborate how the split to multiple processes improves the performance? To create a new process is very expensive operation, compared to a new thread. The same with sharing data across processes versus threads. There is no benefit.
Process isolation can "resolve" poor code quality when a buggy code is more isolated. Again, it isn't any improvement, just a poor fix of having more incompetent developers on the board :-/
> When you're using synchronisation primitives you're doing message passing via shared state, and every time you hit one your code becomes synchronous.
No, you don't understand basic things. Recommended reading Concurrent Programming on Windows
If you want to learn it the right way, read this book. I warn you, it is deeply technical. But there is no better source.
https://www.amazon.com/Concurrent-Programming-Windows-Joe-Duffy/dp/032143482X
Now, all that said, there are various synchronization primitives that can be used, and there also some generic rules that you should always try to follow:
Primitives:
Anyway, this is probably the most detailed response I've ever typed to anything on the internet, so... I'll leave you with some recommendations.
I think Jared Parsons summarizes the problems pretty well here and here.
You can also have a look at Joe Duffy's blog. I'd also highly recommend his book Concurrent Programming on Windows. He discusses general operating systems concepts, some of which are specific to Windows, concurrent programming in C# and C++, and various other details... Really great read.