Linked by Thom Holwerda on Thu 31st Aug 2006 22:53 UTC
"Concurrent programming is difficult, yet many technologists predict the end of Moore's law will be answered with increasingly parallel computer architectures - multicore or chip multiprocessors. If we hope to achieve continued performance gains, programs must be able to exploit this parallelism. Automatic exploitation of parallelism in sequential programs, through either computer architecture techniques such as dynamic dispatch or automatic parallelization of sequential programs, offers one possible technical solution. However, many researchers agree that these automatic techniques have been pushed to their limits and can exploit only modest parallelism. Thus, programs themselves must become more concurrent."
Thread beginning with comment 157793
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Parallel difficult? Why?
by FunkyELF on Fri 1st Sep 2006 14:21
in reply to "RE: Parallel difficult? Why?"
Member since:2006-07-26
Just like manual memory management, synchronization is NOT easy and very error-prone in non-trivial programs. And it doesn't scale well, anyway.
Well put. I like the comparison to memory management. I am not a parallel programmer but I'd like to be. Memory management was hard to master in C and C++ but I'm glad I did before I learned Java with garbage collection. I feel parallel programming is the same way. I better learn it at a lower level before a new paradigm emerges making it easier.
RE[2]: Parallel difficult? Why?
by BryanFeeney on Fri 1st Sep 2006 15:43
in reply to "RE: Parallel difficult? Why?"
Member since:2005-07-06
Indeed, and what's more, it requires a whole lot more forethought than memory management. I usually end up modelling things out on paper, with UML and - occasionally - state-diagrams before splitting up a program. The sort of gotchas that can occur with concurrent programming (especially using the current crop of popular languages) are nightmarish.
The solution is to create a completely new paradigm. One example is the use of futures (http://en.wikipedia.org/wiki/Future_%28programming%29) and "promise pipelining" currently seen in languages like E and Alice.
Of course, given that it's taken 30 years for techniques like total OOP and lambdas to arrive in a mainstream language (C# 3), I'm not optimistic about any of these techniques gaining mainstream acceptance in the near future.
Edited 2006-09-01 15:44
RE[3]: Parallel difficult? Why?
by Sphinx on Fri 1st Sep 2006 16:32
in reply to "RE[2]: Parallel difficult? Why?"
Member since:2005-07-09
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
"In the first episode of Microsoft's new film series 'On the Whiteboard', Editor Pamela Woon chats with two-time Oscar winner Randy Thom about the (often underestimated) importance of sound in human-technology interactions. Thom, the lead sound designer at Skywalker Ranch who worked on films such as The Incredibles, Castaway and Forrest Gump, says that people rarely consider the significance of those signature sounds that come from their trusty devices, whether it be a cell phone, a computer or a tablet."
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
"Microsoft has sensationally abandoned its controversial plans to restrict the sharing of XBox One games, and has also removed daily online authentication requirements for its forthcoming console", reports The Guardian. They had no choice. Still a good move.
Linked by Thom Holwerda on 06/19/13 22:28 UTC
"A snippet of code in the Steam digital distribution platform has revealed that Valve may be planning to let users easily share their games with friends in the future. The Verge has verified the code's authenticity, which was originally spotted by a member of the NeoGAF gaming forum; the code references a 'shared game library' and a notification that would alert a user when their games are currently in use by a borrower." This would change the, uh, game.
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Official Apple statement on PRISM and privacy: "Regardless of the circumstances, our Legal team conducts an evaluation of each request and, only if appropriate, we retrieve and deliver the narrowest possible set of information to the authorities. In fact, from time to time when we see inconsistencies or inaccuracies in a request, we will refuse to fulfill it." This is basically Apple re-publishing their earlier statement in a more official manner. You either believe it, or you don't.
Linked by Anonymous on 06/18/13 22:26 UTC
The open source Contiki operating system and its commercial Thingsquare distribution are making strides towards the connected home. According to a Computerworld article, a new LED light bulb manufacturer is putting small computers into their light bulbs. Each computer runs the Contiki OS, which gives each bulb an IP address and allows them to be controlled with a smartphone application. To connect the bulbs to the application, the bulbs use both Wi-Fi and the much lower power IEEE 802.15.4 mesh technology.
Linked by Thom Holwerda on 06/18/13 22:25 UTC
"Google asked the secretive Foreign Intelligence Surveillance Court on Tuesday to ease long-standing gag orders over data requests it makes, arguing that the company has a constitutional right to speak about information it's forced to give the government. The legal filing, which cites the First Amendment's guarantee of free speech, is the latest move by the California-based tech giant to protect its reputation in the aftermath of news reports about sweeping National Security Agency surveillance of Internet traffic." Draining the ditch after the cow has drowned in it.
Linked by Thom Holwerda on 06/18/13 17:45 UTC
"I can't find one person who has been using the Nexus 7 for an extended period of time, and hasn't seen a massive downgrade in performance. Just what kind of downgrade are we talking here? I cannot pick up my Nexus 7 without experiencing problems like a lag of ten seconds, or more, just to rotate the display; touches refusing to acknowledged; stuttering notification panel actions; and unresponsive apps." Fully and utterly agreed. My Nexus 7 was blazing-fast and awesome for a few months, and at some point, it just started sucking. Just like that. I've tried loads of ROMs, and nothing helps.
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
A new release of the hobby operating system MenuetOS! The release notes are a bit non-descript, but you'll have to take what you can get: "updates and improvements (picview, httpc, ehci, ...)".
Linked by Thom Holwerda on 06/17/13 17:58 UTC
"The Internet is one of the most transformative technologies of our lifetimes. But for 2 out of every 3 people on earth, a fast, affordable Internet connection is still out of reach. And this is far from being a solved problem. There are many terrestrial challenges to Internet connectivity - jungles, archipelagos, mountains. There are also major cost challenges. Right now, for example, in most of the countries in the southern hemisphere, the cost of an Internet connection is more than a month's income. Solving these problems isn't simply a question of time: it requires looking at the problem of access from new angles. So today we're unveiling our latest moonshot from Google[x]: balloon-powered Internet access." Insane.
Linked by Thom Holwerda on 06/17/13 17:52 UTC
"MineAssemble is a tiny bootable Minecraft clone written partly in x86 assembly. I made it first and foremost because a university assignment required me to implement a game in assembly for a computer systems course. Because I had never implemented anything more complex than a 'Hello World' bootloader before, I decided I wanted to learn about writing my own kernel code at the same time. Note that the goal of this project was not to write highly efficient hand-optimized assembly code, but rather to have fun and write code that balances readability and speed. This is primarily accomplished by proper commenting and consistent code structuring." Just cool.More News »
Sponsored Links
Member since:
2005-08-08
> IME, this is all hogwash. Programming with threads is not that difficult, after learning some basic principles. Just because somebody somewhere was caught by racing condition or something similar does not justify introducing "new principles".
When "somebody somewhere" translates to "nearly everybody, everywhere" it does.
Just like manual memory management, synchronization is NOT easy and very error-prone in non-trivial programs. And it doesn't scale well, anyway.