Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re:Mozilla syndrome? (Score 2) 330

Removing unencumbered open code/GUI/interface etc. which is known to work for no good reason is unhealthy.

No, it's not "known to work". That's the problem. No one ever tests with those drivers anymore, they break frequently, and no one fixes them. That's why they were removed. If anyone cares enough to fix and maintain them instead of just complaining on Slashdot, they will be added back to the tree.

Comment Already broken (Score 3, Informative) 330

Most or all of these drivers were already broken because no one cared enough to maintain them or even test them from time to time. Anyone who needs the old drivers can compile out an older version of Mesa from git and run that. Which they already had to do.

It was also said that if someone comes along who is actually interested in maintaining one of the removed drivers, that the driver would be restored to the source tree.

Nothing to see here, move along.

Comment Re:ooo ooo! (Score 1) 585

Government should raise taxes on gasoline so that people drive less, not force them to drive inappropriate vehicles because of mandates. The result will be much better.

There's no need. The price of gasoline has gone up faster than the government or anyone else would have dreamed of 10 years ago. The price of gasoline tripling hasn't really stopped that many people from driving as one would expect. It just increased the profit margins of the oil companies.

Comment Re:Was this article all a mistake? (Score 2) 688

I've never really tried Mono, but I understand it has very good .NET support these days:

The easiest way to describe what Mono currently supports is: Everything in .NET 4.0 except WPF, EntityFramework and WF, limited WCF.

Mono runs on OSX, Linux, and the BSDs. And even on Windows.

You should actually try it, especially on non-Windows. I've never seen an application written for .NET that works out of the box with Mono on Linux.

Microsoft

Was .NET All a Mistake? 688

mikejuk writes "The recent unsettling behavior at Microsoft concerning .NET makes it a good time to re-evaluate what the technology is all about. It may have been good technology, but with the systems guys building Windows preferring to stick with C++, the outcome was inevitable. Because they failed to support its way of doing things, .NET has always been a second-class Windows citizen unable to make direct use of the Windows APIs — especially the latest. .NET started out as Microsoft's best challenge to Java but now you have to ask: what has the excursion into managed code brought the Microsoft programmer, and indeed what good has it done Microsoft? From where we are now, it begins to look very much like an unnecessary forced detour, and Windows programmers are going to be living with the mess for years to come."

Slashdot Top Deals

If a thing's worth doing, it is worth doing badly. -- G.K. Chesterton

Working...