Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - Alan Cox No Longer The Linux TTY Maintainer 1

The Slashdolt writes: After a stern criticism from Linus, the long-time kernel hacker Alan Cox has decided to walk away as the maintainer of the TTY subsystem of the Linux Kernel. Stating:

"...I've had enough. If you think that problem is easy to fix you fix it. Have fun. I've zapped the tty merge queue so anyone with patches for the tty layer can send them to the new maintainer."

Making it quite clear that he is serious.

Comment Re:Good thinking, (Score 1) 324

They're using this for their message passing, not their web stuff. For example, they accept tweets from sms, internet apps, etc. This system is used to handle all of those disparate messages in a performant manner. It's not about the calculation it's about concurrent message handling. Millions of people sending messages to them simultaneously.

Comment Re:Good thinking, (Score 1) 324

From the Article:
Scala is different from other concurrent languages in that it contains no language support for concurrency beyond the standard thread model offered by the host environment. Instead of specialized language constructs we rely on Scala's general abstraction capabilities to define higher-level concurrency models. In such a way, we were able to dene all essential operations of Erlang's actor-based process model in the Scala library.

However, since Scala is implemented on the Java VM, we inherited some of the deciencies of the host environment when it comes to concurrency, namely low maximum number of threads and high context-switch overhead. In this paper we have shown how to turn this weakness into a strength. By dening a new event-based model for actors, we could increase dramatically their efficiency and scalability. At the same time, we kept to a large extent the programming model of thread-based actors, which would not have been possible if we had switched to a traditional event-based architecture, because the latter causes an inversion of control.

Comment Re:Not all databases have to be relational... (Score 1) 267

The problem is that the programmers think they own the data when they don't. Your app will come and go and the data will remain. People will want to query that data, report on that data, or even transfer it into other databases. Database people think beyond the current requirements of your particular app.

Slashdot Top Deals

In any formula, constants (especially those obtained from handbooks) are to be treated as variables.