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

 



Forgot your password?
typodupeerror
×

Comment Well, there's a reason for most Dell quality probs (Score 1) 604

I've purchased two Dell laptops, and both of them have had issues.

However, they have both been relatively low-end models, and the issues have been minor. I suspect they take a lot of shortcuts to get the price down, so I'm not really outraged about it ... the lesson is just not to buy cheap crap :)

My tower at work is a Dell Optiplex running Vista - *VISTA* - and it hasn't had any issues at all.

Comment Re:AppleCare memo on how to mislead users... (Score 1) 417

-1, Moronic
-1, Missing the point
-1, Fundamental misunderstanding of capitalism

"Your own means" is theft from the credit card company, not theft from Apple. It will only lead to your own balls getting kicked. (Again, if you count getting conned into buying a first-gen iPhone 4 as getting kicked in the balls; which, unfortunately, is increasingly looking like the correct interpretation of it.)

Comment Re:One of the biggest problems is configurability (Score 1) 120

I do agree that many of the function names are, quite frankly, *wacky* ... but the online manual more than makes up for it. I just toss it in my firefox search bar, and I can generally find any function definition (and, in some cases, arcane function names) nearly as fast as I can type it.

I've found it very difficult to find similarly useful resources in other languages (javascript in particular, if you can count it as a language ;-)).

I'm not sure exactly what about it makes it so easy to use for regular reference - but I do know that it is about a billion times better than most docbook-generated documentation I've ever seen. Usually docbook/javadoc makes me want to stab my eyes out with a rusty grapefruit spoon.

Comment Re:Phasing out support for 10.4? I still run 10.3! (Score 2, Insightful) 440

How hard is it to just keep up on security patches for old browsers?

A security patch isn't as simple as deciding "Oh, we don't want to have that vulnerability any more" and commenting out a setting. If it was that easy, there wouldn't be very many vulnerabilities at all.

On the one hand, any time you find a new vulnerability (or a new class of vulnerabilities), you have to audit all the nooks and crannies of the code base in order to identify either the problem itself, or the problem areas that are affected.

On the other hand, any time you change a line of code, you have to recompile. That means, to release the patch, you'll have to recompile for *every target OS*, and you'll have to *test* on every one of those OSes.

Surely when considering both of those complicating factors, you can see what Mozilla's motivations might be for retiring old support branches with a relatively limited user base?

Slashdot Top Deals

"Money is the root of all money." -- the moving finger

Working...