I think this kind of IDE would be very usefull during code-maintenance, especially when the code you maintain is written by you (which is often the case).
When developing new code, the bubble-concept could be too confusing, because it seems to hide the overall structure of the code. But during maintenance, when hunting bugs, I often don't want to see the whole picture (and hence the whole complexity), but am much more interested in smaller sections of a program, and the relations between them. The bubble concept would really help.
Well, to be fair, calling it KDE 4.0 suggests it's relatively bug-free (else it would have been 4.0-beta), and feature-complete (else it would have been 4.0-alpha).
Elections can and will always be manipulated as long as there are humans involved. If you make 1000's of people vote for a person by putting a gun against their head, you have succesfully manipulated the election.
True, however, manipulate 1000 votes by tampering with the machine is much less likely to get detected than the gun-method. So, it may be more difficult to fraud with electronic voting than with traditional voting, but if someone pulls it off, the effect is potentially much larger!
It's not a problem. When the (currently) fastest route gets jammed, it's no longer the fastest route. New traffic will get directed on a different (the new) fastest route.
Back in my day, we had nothing but some floating molecules on the loose, and we had to tie all sorts of dna together ourselfs, with our bare,... erh...
I can imagine Toyota does not want to shut the driver out completely.
What if the car hits another parked car when its performing a ful-automatic parking manouvre. Who's gonna be responsible for the damage? If the process it truly automatic, then Toyota would be responsible for any damage. I wouldn't trust the system that much no matter how precise it is, if I were Toyota.
But when the driver has some responsibility (braking), he will be responsible when the car hits another car, because he didn't brake in time.
What could be useful is - dare I suggest it - holding essential OS kernel files in ROM
Holding the OS in ROM does not solve the problem of vulnerabilities. True, they can't be modified from a remote location, but what if the OS was flawed before it got burned into ROM (which will be the case)? And as you pointed out, upgrading will be a great pain, so the average person won't even bother, leaving security holes even longer in the open.
What exactly is the harm in a coming soon website?
I think the harm is that register.com can use these coming-soon-websites to get advertising revenue by putting adds on 'property' (the domain) they don't own.
I can't help but think, though, that such a book will be dated quite quickly.
If I wrote the book, that'd be exactely what I want. If the book's outdated, it means it has brought all those problems to the attention, and that proper solutions were made. What more can you wish?
Slashdot Mirror
xkcd link
Actually, this prank pushed me over the edge to actually install flashblock :)
I think this kind of IDE would be very usefull during code-maintenance, especially when the code you maintain is written by you (which is often the case).
When developing new code, the bubble-concept could be too confusing, because it seems to hide the overall structure of the code.
But during maintenance, when hunting bugs, I often don't want to see the whole picture (and hence the whole complexity), but am much more interested in smaller sections of a program, and the relations between them. The bubble concept would really help.
link: http://www.ocregister.com/articles/berlin-cold-summer-2335473-east-hangar
It basically takes you through all the basic(++) features of vim.
vimtutor made me really appreciate vim.
Well, to be fair, calling it KDE 4.0 suggests it's relatively bug-free (else it would have been 4.0-beta), and feature-complete (else it would have been 4.0-alpha).
From what I've read it was neither of those...
Elections can and will always be manipulated as long as there are humans involved. If you make 1000's of people vote for a person by putting a gun against their head, you have succesfully manipulated the election.
True, however, manipulate 1000 votes by tampering with the machine is much less likely to get detected than the gun-method.
So, it may be more difficult to fraud with electronic voting than with traditional voting, but if someone pulls it off, the effect is potentially much larger!
It's not a problem. When the (currently) fastest route gets jammed, it's no longer the fastest route. New traffic will get directed on a different (the new) fastest route.
"I think you're letting your love for Open standards blind you from the fact that D3D is flat-out the winner, technology-wise."
There's more to 3D graphics than games.
OpenGL is only graphics, whereas DirectX is also about sound, networking and input devices.
:).
SDL is more comparable to DirectX (and it uses openGL
So... where are the screenshots?!
(Sorry, couldn't resist)
Not sure you are right there, this states the contrary...
Noo, just make it fly up-side-down!
That's a much more inventive solution than taking the easy road and call it 'airship'.
Now the rats can run for Governor of California
:)
Informative???
That's even funier than the comment itself
offtopic but fun:
:)
That litigious bastards linking seems to work prety well =)
First in the list
Organisms????
... erh...
Back in my day, we had nothing but some floating molecules on the loose, and we had to tie all sorts of dna together ourselfs, with our bare,
Oh yeah... And we liked it that way!
I can imagine Toyota does not want to shut the driver out completely.
What if the car hits another parked car when its performing a ful-automatic parking manouvre.
Who's gonna be responsible for the damage?
If the process it truly automatic, then Toyota would be responsible for any damage. I wouldn't trust the system that much no matter how precise it is, if I were Toyota.
But when the driver has some responsibility (braking), he will be responsible when the car hits another car, because he didn't brake in time.
What could be useful is - dare I suggest it - holding essential OS kernel files in ROM
Holding the OS in ROM does not solve the problem of vulnerabilities.
True, they can't be modified from a remote location, but what if the OS was flawed before it got burned into ROM (which will be the case)?
And as you pointed out, upgrading will be a great pain, so the average person won't even bother, leaving security holes even longer in the open.
This is a rip-off of a comment of some time ago.
Yep, sounds like a typical Hollywood movie you're describing there.
What exactly is the harm in a coming soon website?
I think the harm is that register.com can use these coming-soon-websites to get advertising revenue by putting adds on 'property' (the domain) they don't own.
I'm not joking! And don't call me shirley!
[(Leslie Nielsen (Airplane)]
I can't help but think, though, that such a book will be dated quite quickly.
If I wrote the book, that'd be exactely what I want. If the book's outdated, it means it has brought all those problems to the attention, and that proper solutions were made. What more can you wish?
Just a hyperlink to the reply suffices. So it won't influence your web-hosting costs.
Isn't haystack the problem that this tries to fix? I think this project should have been called 'needle' or possibly 'findy.
;)
Nooo, it refers to the HUGE requirements on your system to run it