(It only needs to be strong on any part that protrudes from the water - which might be a lot to avoid sinking it when it recoils.)
You underestimate the amount of pressure that submerged objects are subject to. For roughly every 10 meters of depth, the pressure increases by a factor. At 90 meters depth, the pressure is about 1000% of Earth's atmosphere at sea level.
They still call it alpha, but apart from it sometimes hanging the browser for a minute at start, but then working... and a bit of memory leaking... it is no different from the r32 bin Windows release version.
So, you mean it works exactly like the Windows release version?;-)
As I sit here happily running 32-bit firefox in Windows 7 64-bit, I'm having trouble understanding what photo editing has to do with the need for a 64-bit web browser.
Because people who need a 64-bit system for things like photo editing also want to run web browsers. That really didn't occur to you?
It occurred to them, as you might have noticed by them specifying that they use a 64-bit OS that allows them to run the 64-bit photo editors, and a 32-bit browser works just fine. You failed to point out how changing from a 32-bit browser to a 64-bit browser makes a difference to photo editing when the OS is already 64-bit.
We've managed to land several rovers on Mars. How many Martian rovers have landed on Earth? Zero. I suggest that our missile defenses are quite adequate.
You only need permission when filming on property that you don't own. The people giving said permission aren't the ones regretting letting Jackson "film down there".
Drop the van on a hairpin-covered trampoline on the Moon. You'll need to be in a vacuum because your van's terminal velocity in Earth's atmosphere is less than 250 mph.
How is the terminal velocity of the van in Earth's atmosphere relevant if the van is being dropped on the Moon? And why does it need to be a vacuum? Next you'll be suggesting that it needs to travel at the speed of light in order to exceed escape velocity, even though some significantly lower speed would also be sufficient.
While you are correct, it doesn't give us the excuse to essentially lock ourselves even deeper into the problem by making the underlying programming environments inaccessible to other localisations.
I never suggested it was inheritance or polymorphism, nor did I suggest it had to be. I also wasn't suggesting it as a serious solution, perhaps I should have used a sarcasm tag or something.
Thanks for making my point for me though;-)
You're welcome, my intention was to agree with you.
Re:Underhanded Way to Increase Comments in Code
on
Dumbing Down Programming?
·
· Score: 2, Insightful
The calculate distance comment is completely redundant as the variable that it is being assigned to is already named distance. Unless, of course, the intention was to state that it was in fact calculated instead of magically pulling a number out of a hat. You don't need one liner calculations to be commented to state their intentions if the variable names are chosen properly (which is what self documenting code is largely about).
This progression toward using English words and syntax to program a computer is less about dumbing down code and more about encouraging people to document their code. Ideally, a programmer should document each section of code by writing a block of comments explaining (1) why the code is used and (2) how the code works -- in plain English
Why English? Programmers come from other nationalities as well and a programming office in France may choose to use French to document their code, name variables and functions etc. Making a computer language more like English might arguably make it easier for English speaking end users to start programming, but makes it harder for non-English speakers. Ideally, programming languages should be "human language" agnostic without being totally foreign (somewhat non-trivial to do). Totally verbose English is in my opinion the wrong way to go.
Completely broken? No, it still functions correctly most of the time, so just partially broken. Writing bug free software is virtually impossible, so while blaming your browser might seem like a good idea, the only way to guarantee that you aren't using a broken browser is to not use any browser.
The GPL isn't even about the original code, it's about modifications to the code.
No, it's about redistribution of the code. You can copy GPL code, modify it to your hearts content and never release any changes, as long as you don't redistribute the binaries. Conversely, if you redistribute an application that uses GPL protected code (even if the GPL code is unmodified) you still need to follow the terms of the GPL licence.
The main reason support firms recommend holding off is because they need time to play with it themselves before they are prepared to commit to supporting it. Apparently they don't follow Microsofts advice to start preparing early by using the betas and release candidates.
(It only needs to be strong on any part that protrudes from the water - which might be a lot to avoid sinking it when it recoils.)
You underestimate the amount of pressure that submerged objects are subject to. For roughly every 10 meters of depth, the pressure increases by a factor. At 90 meters depth, the pressure is about 1000% of Earth's atmosphere at sea level.
So you want ray tracing. Why didn't you just say that?
They still call it alpha, but apart from it sometimes hanging the browser for a minute at start, but then working... and a bit of memory leaking... it is no different from the r32 bin Windows release version.
So, you mean it works exactly like the Windows release version? ;-)
As I sit here happily running 32-bit firefox in Windows 7 64-bit, I'm having trouble understanding what photo editing has to do with the need for a 64-bit web browser.
Because people who need a 64-bit system for things like photo editing also want to run web browsers. That really didn't occur to you?
It occurred to them, as you might have noticed by them specifying that they use a 64-bit OS that allows them to run the 64-bit photo editors, and a 32-bit browser works just fine. You failed to point out how changing from a 32-bit browser to a 64-bit browser makes a difference to photo editing when the OS is already 64-bit.
That would certainly explain why we can't find any Martians on Mars.
We've managed to land several rovers on Mars. How many Martian rovers have landed on Earth? Zero. I suggest that our missile defenses are quite adequate.
You only need permission when filming on property that you don't own. The people giving said permission aren't the ones regretting letting Jackson "film down there".
You do realise he comes from New Zealand and doesn't exactly need permission to film there, right?
Intel has competed fairly and lawfully.
I'll elaborate for them. If GNOME is the violating component, and GNOME is removed, then Red Hat is no longer liable. Red Hat will be fine.
You had me until "crashes". All software is vulnerable to bugs, and bugs aren't intentional.
Russia doesn't need to do anything to bring down the American economy. America did a fairly decent job of that itself not too long ago.
Compiz? On KDE4? KDE4 has it's own compositing window manager, it does not use Compiz.
Drop the van on a hairpin-covered trampoline on the Moon. You'll need to be in a vacuum because your van's terminal velocity in Earth's atmosphere is less than 250 mph.
How is the terminal velocity of the van in Earth's atmosphere relevant if the van is being dropped on the Moon? And why does it need to be a vacuum? Next you'll be suggesting that it needs to travel at the speed of light in order to exceed escape velocity, even though some significantly lower speed would also be sufficient.
While you are correct, it doesn't give us the excuse to essentially lock ourselves even deeper into the problem by making the underlying programming environments inaccessible to other localisations.
Thanks for making my point for me though ;-)
You're welcome, my intention was to agree with you.
The calculate distance comment is completely redundant as the variable that it is being assigned to is already named distance. Unless, of course, the intention was to state that it was in fact calculated instead of magically pulling a number out of a hat. You don't need one liner calculations to be commented to state their intentions if the variable names are chosen properly (which is what self documenting code is largely about).
This progression toward using English words and syntax to program a computer is less about dumbing down code and more about encouraging people to document their code.
Ideally, a programmer should document each section of code by writing a block of comments explaining (1) why the code is used and (2) how the code works -- in plain English
Why English? Programmers come from other nationalities as well and a programming office in France may choose to use French to document their code, name variables and functions etc. Making a computer language more like English might arguably make it easier for English speaking end users to start programming, but makes it harder for non-English speakers. Ideally, programming languages should be "human language" agnostic without being totally foreign (somewhat non-trivial to do). Totally verbose English is in my opinion the wrong way to go.
Simple:
when trying to remove the last character, print the character to the screen
When they did this to a car, it heated it and didn't rely entirely on radiation pressure.
Or they might just have wings that provide lift, allowing it to go as far as it has fuel.
Do they know they can type in the address bar?
Have you ever heard of typosquatting? Or searching for some general piece of information without knowing what site hosts that information?
Completely broken? No, it still functions correctly most of the time, so just partially broken. Writing bug free software is virtually impossible, so while blaming your browser might seem like a good idea, the only way to guarantee that you aren't using a broken browser is to not use any browser.
The GPL isn't even about the original code, it's about modifications to the code.
No, it's about redistribution of the code. You can copy GPL code, modify it to your hearts content and never release any changes, as long as you don't redistribute the binaries. Conversely, if you redistribute an application that uses GPL protected code (even if the GPL code is unmodified) you still need to follow the terms of the GPL licence.
The main reason support firms recommend holding off is because they need time to play with it themselves before they are prepared to commit to supporting it. Apparently they don't follow Microsofts advice to start preparing early by using the betas and release candidates.