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

 



Forgot your password?
typodupeerror
×

Comment Re:Linux users...screwed again (Score 4, Informative) 138

Obligitory link - http://www.youtube.com/watch?v=N6Vf8R_gOec

24 Displays done under Linux - on October last year. The drivers were carefully teased into that condition, and so the tech is on it's way.

Be aware that the RANDR/Xinerama maturity in Linux is weak, so it will take a few years for it to be able to handle >2 - note that it's take almost a decade to get reasonable 2-head support...

HP

Submission + - HP to Buy Palm (hp.com) 1

Daengbo writes: "HP and Palm, Inc. (NASDAQ: PALM) today announced that they have entered into a definitive agreement under which HP will purchase Palm, a provider of smartphones powered by the Palm webOS mobile operating system, at a price of $5.70 per share of Palm common stock in cash or an enterprise value of approximately $1.2 billion. The transaction has been approved by the HP and Palm boards of directors.

The combination of HP’s global scale and financial strength with Palm’s unparalleled webOS platform will enhance HP’s ability to participate more aggressively in the fast-growing, highly profitable smartphone and connected mobile device markets. Palm’s unique webOS will allow HP to take advantage of features such as true multitasking and always up-to-date information sharing across applications."

Bug

What Aspects of Open Source Projects Do You Avoid? 344

paulproteus writes "I'm a Debian developer and a part-time contributor to a few smaller projects. I do a lot of free software-y and open source-y things. Sometimes, though, I don't do them. I figure some other Slashdotters might have similar hang-ups — we contribute to a project, but there are parts that we really dread thinking about. So I wrote a post about having these hang-ups, and I made a place on the web to share how others can help your project. What are the parts that, in your projects, you would be relieved if someone else looked at for you?"

Submission + - 'Good Enough' Software QA trending us into Failure (boldinventions.com)

An anonymous reader writes: Faced with the inescapable conclusion that complex software can never be 100% tested, companies have been forced into a 'Good Enough' strategy. As complexity increases, the probability of unexpected bugs increases with it. At the same time, hardware vendors have been dramatically increasing the capability of embedded CPU hardware, and therefore much more can be done in software. So all our consumer products which contain embedded systems are trending on a death march toward unreliability, or unsustainable QA costs. In end will consumers simply continue to downgrade their expectations when it comes to product reliability, or will something have to change?

Comment Although it's a tech demo, you can do 24 screens (Score 5, Interesting) 105

From the launch activities for the 5800 family.

http://www.youtube.com/watch?v=N6Vf8R_gOec

24 monitors, 4 cards, 1 PC. All consumer grade. All running Linux. And yes, there is bezel correction.

Yes, there are black lines for the monitors. I couldn't get the budget to do 24 50" Plasmas. But think beyond the demo part of the tech and think about the possibilities.

Comment Don't confuse "support" with "capability" (Score 1) 176

The economics are fairly simple.

Your support, validation and sustaining costs don't contribute to the bottom line of your business. If you have a part of the product that takes a unnecessarily large proportion of the bottom line, you look at the value proposition. You do something as simple as removing the client for a platform, you save money.

BUT, if the product is based around open standards, the Linux community has a high probability of making something that will work anyway. For FREE. No support costs for a client, no development and validation costs either. Linux, with it's "Freedom" has an extremely high cost to be an ISV on, you have kernels, X versions, distributions.. All subtley different and all having precious consideration for the cost of operating in that ecosystem.

Google has many examples of killing/not creating a client, but fostering the capability. Google talk is a great example. Google still gets the branding value of the service, but doesn't need to have a client, I have *NEVER* heard anyone talk about "Google's JMPP or Jabber Service". I would expect that this is the same, but for google voice. The people carrying credit will probably be handled.

Comment Re:That is the question... (Score 1) 38

Judging by your posts and your handle, you work in or around servers - a lot.

You would probably be aware that security, stability, and all such things are a set of tradeoffs of risks and benefits/costs.

You can make a system 100% secure, but it may not be useable. You can make a system five 9's stable, but you have to pay for it. You make the assessment of the risk (in this case data corruption), against the benefit/costs (double the speed in some cases).

SuSE seemed to have made the assessment of risk without understanding the cost. They enabled barriers by default to take the high moral ground, but then didn't understand the cost of doing so.

Your analogy about buying a new gas oven is interesting. You look at the manuals and there are *many* ways that you can blow up your oven. It is just that the risk (of someone naively or accidentally blowing themselves up) has been balanced against the benefit of lower consumption of energy. There are many ways of managing risks - redundancy, accepting the risk, etc.

My prime point was that the benchmarking which yeilded questions - without the answers given - are extremely valuable. They allow the upstream people developing systems to understand that they need to consider the bigger picture and apply a risk/cost/benefit judgement and not close of all risks. I would expect that in later versions of SuSE they have turned off barriers now that the risk has been sufficiently understood and the costs determined as being commercially relevant.

Or using your analogy. The tests that the oven may blow up but save 50% on the energy bill has been shown that the net benefit is on the side of the oven that may potentially blow up!

Comment That is the question... (Score 2, Informative) 38

The Phoronix benchmarking is intended to provide you the answers as to why. It is to highlight the stuff that has happened.

If performance management is going on within the kernel community, then this shouldn't come up as a shock. The whole purpose of independent testing is that you see something that looks out of place, investigate and resolve. A perfect example is http://www.phoronix.com/scan.php?page=article&item=intel_atom_four&num=1 phoronix article, that showed that SuSE was trailing. This causes this http://lizards.opensuse.org/2008/12/16/comments-on-phoronix-benchmarking-opensuse-111/ discussion.

The question and answer don't need to be provided by the same voice. It is when you have someone questioning, and then someone answering, then you have a discussion, then finally you have progress.

To make it worse, there is virtually no reason that any number of the organizations supporting the leading developers can't invest a small amount of infrastructure and run the tests themselves. Phoronix Test Suite is absolutely trivial to use. The amount of "software development in autopilot" is frightening, this applies equally to Open Source as it does to Proprietary.

Slashdot Top Deals

The one day you'd sell your soul for something, souls are a glut.

Working...