1 dead, 1 missing, and 13 came damn close and needed rescue choppers during a hurricane, endangering both themselves and the people who had to save them. Its inexcusable and criminally negligent. It probably doesn't deserve quite the amount of media attention its getting, but it was amazingly stupid.
The navy has much bigger, more modern ships. There's also national security risks if the navy boats are damaged. No such problems for a movie prop.
And like I said- it may be safer for the boat. It isn't safer for the crew. This wasn't a surprise storm, this had been forecast for a week. Tie up the boat, stay in a hotel (preferably about 100 miles or so inland), and then repair the boat as needed. The health and safety of the crew is far more important than the ship. The owners deserve to be sued into oblivion for even asking. It is NOT acceptable to risk 16 lives to save money on repairs. Hell, take it to a dry dock if you're that scared.
They were idiots for going out to sea. Even if it was marginally safer for the boat to be at sea than in port for the storm, it was safer for the crew to be in port, or in hotel rooms 100 miles inland. Those people died due to a combination of greedy ownership that valued the ship more than the crew's safety and their own stupidity in not refusing. All this for a reproduction used in movie shoots. A senseless waste.
Exactly what do you think is going on that requires full cores for each of those? The vast majority of load time is downloading files (images, videos, etc). The processing times are minimal. Worse, these activities are not isolated (rendering would require result updates from flash, jscript, etc), so breaking them into separate threads would just mean that one of them is stuck waiting for the others to finish. You'd have a single digit speed increase, and probably a low digit at that. It's just not a parallelizable problem.
The gain Chrome got from breaking into multiple threads wasn't render speed. It was allowing you to change tabs if there was a misbehaved app (in flash, js, etc) on one tab. Having multiple threads on the same core would give them the same benefit, it was breaking it out into threads that was the win, not running them on parallel cores.
Also lack of need. How many apps does the average person run at once? How much of the CPU do they peg? Most apps can't easily be parallelized, so they'll never see a speedup from more cores. For the average web browser/email/office app person, there's no gain even on 2->4 cores.
Exceptions are expensive and should be reserved for when things go massively wrong. Returning null is generally the way things should work if you want an error to be recoverable at all. Exceptions are way way way overused.
Example- Android will throw an exception if you try to hide a dialog window that was already hidden. Why? The end result is what you wanted- it just means every dialog hide has to be exception wrapped (especially since there are timing issues you can't avoid that will cause this).
Another example- file IO. Trying to open a file that doesn't exist is a common case and should return an error, not throw an exception.
Basically if you think its likely someone will ever want to catch the error rather than see a stack trace in a log there, it probably shouldn't be an exception.
I don't disagree with you on what a code review *should* be for. And when done right (there are various ways to do it right), they're very helpful. But my experience is that they always devolve into pointless style nitpicking when you throw style guides and That Anal Retentive Guy into the code review.
Maybe you should actually read my posts. I say outright that some style things are important and some aren't. Meaningful variable names fall into the are category. Indentation doesn't.
>No you are not. You just have not yet seen bad code. Imagine 4000 lines in a single function with indentation errors. Or rather than errors, mix of different styles, created by dozens of developers. Format the same code to use a single style and it becomes much more readable (but obviously still needs a lot of refactoring).
I've seen 10K. The fact it was 10K was pretty bad. The fact it had indentation changes didn't slow me down at all. I'd agree if we were talking no indentation at all, but mixing lengths doesn't matter one bit.
Hey, I have a jackhammer with a very fragile glass tube filled with poison gas. Want to use it? Why not? It's not safe? Don't blame the tool, learn to use it!....Or just don't use shitty tools.
Your argument would have some merit if the tool gave you the freedom to do something powerful that could be misused. C/C++ pointer arithmetic, for example. Or manual memory management. But indenting? Nope, that argument doesn't remotely pass the smell test, because the feature doesn't allow you to do anything new with the language. It was a design mistake because Guido didn't think things all the way through. And now he's stuck with it, unless he wants to break backwards compatibility. Given that there's plenty of other options out there that are just as good as Python, it's easier just to avoid Python and use less flawed tools.
No, really he's not. I am quite capable of reading code with different indent styles, brace styles, etc. I do so on a regular basis, even when working with language approved styles as I regularly program in multiple languages. I have no trouble with it mixing program to program, file to file, or even function to function. In fact, most code bases I've worked on looked like that. And there was no noticable speedup in places that did enforce a style vs those that didn't.
In fact, he actually tends to harm code quality. Why? Because he bogs down code reviews. Rather than looking for serious maintenance or correctness problems, we focus on his half dozen style complaints. This wastes our time and causes people to hate code reviews, or take them less seriously. The places I've worked with style guidelines all had shitty code review processes, and this was the reason.
So no, that anal retentive asshole made everyone's job far worse. There are code style issues that matter, like naming variables well and commenting sufficiently. Formatting is not one of them, and being particularly picky about it is a BIG red flag about both a person and a company.
I like you. There are style things that are important, but it's not how the code is laid out in the editor. Concentrate on the important things, not the things everyone has to deal with.
And that's why I've wasted weeks of my life fixing Python bugs due to developers using different amounts of spacing. Python took the worst possible path- requiring whitespace to have meaning, but not requiring a specific type/amount of whitespace. Had they made n spaces the requirement for an indent and anything other than n an error, it would have been fine. As it is, it's completely broken and a large cause of errors on every python programmer with more than 1 dev I've ever worked on. It's to the point that when I work on python, I copy the spacing from the line above and paste it to make sure it works.
Also, the choice makes it damn near impossible to use google as a resource. You can't copy paste from the web and get it to compile without worrying about the spacing on every line. Where any other language just works, and you can make it look pretty once you've tested it.
I've never seen how to choose variable names or when to comment in a coding style. Typically, people are expected to just know that. Every coding style guideline I've ever used has been nit picky bullshit about braces and spacing, enforced by that one anal retentive asshole every workplace seems to have.
It will run on x86. But the features you're asking for? Nope, and they have no plans to- it's not what Android does, and it would totally break their activity lifecycle model. Its not meant to be a desktop OS. You could use it as one, but why?
Simple- it wouldn't. Android on a desktop box would work just like Android on a phone. It wouldn't keep separate users. Why would it? It's not a multi-user system. You seem to want a new feature to Android for a desktop box. Since desktop isn't their goal, I doubt they'd add it.
For the record- I don't see why you'd want Android on a desktop, it would be a bad experience. But nothing is stopping you right now, x86 support is out.
This neither proved nor disproves evolution. Evolution is what happens after life exists. This is evidence for abiogenesis, which is an entirely separate theory- the theory that life can be formed from non-living components.
Also, your comment is entirely ridiculous. Any proof of evolution would require an experiment designed by scientists. But I am glad that you're keeping up the high level of logical reasoning, I haven't seen such amazing deductions since the 1950's batman series.
Legally, they do. Only charities are allowed not to. IANAL, but I don't know of any other legal exceptions. here are the legal criteria
The following six criteria must be applied when making this determination:
1. The internship, even though it includes actual operation of the facilities of the employer, is similar to
training which would be given in an educational environment;
2. The internship experience is for the benefit of the intern;
3. The intern does not displace regular employees, but works under close supervision of existing staff;
4. The employer that provides the training derives no immediate advantage from the activities of the intern;
and on occasion its operations may actually be impeded;
5. The intern is not necessarily entitled to a job at the conclusion of the internship; and
6. The employer and the intern understand that the intern is not entitled to wages for the time spent in the
internship.
If you're doing work that they would otherwise hire someone to do (as is completely the case in software), you must pay them at least minimum wage. I believe media companies get away with it by not having them do work but just be gophers, and they're supposed to soak up knowledge by being around the action, not actually doing any of it.
Also, you don't understand what evolution is. Evolution says what happens *AFTER LIFE STARTED TO EXIST* and how it changes over time. How those original life forms were created is an entirely different theory.
There's going to be the rare amazing exception. But how many kids do you know right out of college with the focus, discipline, talent, understanding of the way the world works to be able to build a business? 1 in 100,000 maybe? I'm not saying it can't work, but it's a hard low probability road. It's not a wise choice.
Not to mention- the economy has jobs for programmers. The unemployment rate for programmers in Seattle is negative- more openings than job seekers.
Slashdot Mirror
1 dead, 1 missing, and 13 came damn close and needed rescue choppers during a hurricane, endangering both themselves and the people who had to save them. Its inexcusable and criminally negligent. It probably doesn't deserve quite the amount of media attention its getting, but it was amazingly stupid.
The navy has much bigger, more modern ships. There's also national security risks if the navy boats are damaged. No such problems for a movie prop.
And like I said- it may be safer for the boat. It isn't safer for the crew. This wasn't a surprise storm, this had been forecast for a week. Tie up the boat, stay in a hotel (preferably about 100 miles or so inland), and then repair the boat as needed. The health and safety of the crew is far more important than the ship. The owners deserve to be sued into oblivion for even asking. It is NOT acceptable to risk 16 lives to save money on repairs. Hell, take it to a dry dock if you're that scared.
They were idiots for going out to sea. Even if it was marginally safer for the boat to be at sea than in port for the storm, it was safer for the crew to be in port, or in hotel rooms 100 miles inland. Those people died due to a combination of greedy ownership that valued the ship more than the crew's safety and their own stupidity in not refusing. All this for a reproduction used in movie shoots. A senseless waste.
If we're really lucky, it'll take out all the high frequency traders systems for a few days and we can have an actual market without parasites.
Nah, who am I kidding. If that actually happened they'd keep Wall Street closed.
Exactly what do you think is going on that requires full cores for each of those? The vast majority of load time is downloading files (images, videos, etc). The processing times are minimal. Worse, these activities are not isolated (rendering would require result updates from flash, jscript, etc), so breaking them into separate threads would just mean that one of them is stuck waiting for the others to finish. You'd have a single digit speed increase, and probably a low digit at that. It's just not a parallelizable problem.
The gain Chrome got from breaking into multiple threads wasn't render speed. It was allowing you to change tabs if there was a misbehaved app (in flash, js, etc) on one tab. Having multiple threads on the same core would give them the same benefit, it was breaking it out into threads that was the win, not running them on parallel cores.
Also lack of need. How many apps does the average person run at once? How much of the CPU do they peg? Most apps can't easily be parallelized, so they'll never see a speedup from more cores. For the average web browser/email/office app person, there's no gain even on 2->4 cores.
Exceptions are expensive and should be reserved for when things go massively wrong. Returning null is generally the way things should work if you want an error to be recoverable at all. Exceptions are way way way overused.
Example- Android will throw an exception if you try to hide a dialog window that was already hidden. Why? The end result is what you wanted- it just means every dialog hide has to be exception wrapped (especially since there are timing issues you can't avoid that will cause this).
Another example- file IO. Trying to open a file that doesn't exist is a common case and should return an error, not throw an exception.
Basically if you think its likely someone will ever want to catch the error rather than see a stack trace in a log there, it probably shouldn't be an exception.
I don't disagree with you on what a code review *should* be for. And when done right (there are various ways to do it right), they're very helpful. But my experience is that they always devolve into pointless style nitpicking when you throw style guides and That Anal Retentive Guy into the code review.
Maybe you should actually read my posts. I say outright that some style things are important and some aren't. Meaningful variable names fall into the are category. Indentation doesn't.
>No you are not. You just have not yet seen bad code. Imagine 4000 lines in a single function with indentation errors. Or rather than errors, mix of different styles, created by dozens of developers. Format the same code to use a single style and it becomes much more readable (but obviously still needs a lot of refactoring).
I've seen 10K. The fact it was 10K was pretty bad. The fact it had indentation changes didn't slow me down at all. I'd agree if we were talking no indentation at all, but mixing lengths doesn't matter one bit.
Hey, I have a jackhammer with a very fragile glass tube filled with poison gas. Want to use it? Why not? It's not safe? Don't blame the tool, learn to use it! ....Or just don't use shitty tools.
Your argument would have some merit if the tool gave you the freedom to do something powerful that could be misused. C/C++ pointer arithmetic, for example. Or manual memory management. But indenting? Nope, that argument doesn't remotely pass the smell test, because the feature doesn't allow you to do anything new with the language. It was a design mistake because Guido didn't think things all the way through. And now he's stuck with it, unless he wants to break backwards compatibility. Given that there's plenty of other options out there that are just as good as Python, it's easier just to avoid Python and use less flawed tools.
No, really he's not. I am quite capable of reading code with different indent styles, brace styles, etc. I do so on a regular basis, even when working with language approved styles as I regularly program in multiple languages. I have no trouble with it mixing program to program, file to file, or even function to function.
In fact, most code bases I've worked on looked like that. And there was no noticable speedup in places that did enforce a style vs those that didn't.
In fact, he actually tends to harm code quality. Why? Because he bogs down code reviews. Rather than looking for serious maintenance or correctness problems, we focus on his half dozen style complaints. This wastes our time and causes people to hate code reviews, or take them less seriously. The places I've worked with style guidelines all had shitty code review processes, and this was the reason.
So no, that anal retentive asshole made everyone's job far worse. There are code style issues that matter, like naming variables well and commenting sufficiently. Formatting is not one of them, and being particularly picky about it is a BIG red flag about both a person and a company.
I like you. There are style things that are important, but it's not how the code is laid out in the editor. Concentrate on the important things, not the things everyone has to deal with.
And that's why I've wasted weeks of my life fixing Python bugs due to developers using different amounts of spacing. Python took the worst possible path- requiring whitespace to have meaning, but not requiring a specific type/amount of whitespace. Had they made n spaces the requirement for an indent and anything other than n an error, it would have been fine. As it is, it's completely broken and a large cause of errors on every python programmer with more than 1 dev I've ever worked on. It's to the point that when I work on python, I copy the spacing from the line above and paste it to make sure it works.
Also, the choice makes it damn near impossible to use google as a resource. You can't copy paste from the web and get it to compile without worrying about the spacing on every line. Where any other language just works, and you can make it look pretty once you've tested it.
Unless you use a version control method which can autoformat on checkin and checkout
I've never seen how to choose variable names or when to comment in a coding style. Typically, people are expected to just know that. Every coding style guideline I've ever used has been nit picky bullshit about braces and spacing, enforced by that one anal retentive asshole every workplace seems to have.
Some people don't even use a font- I work with a blind programmer. He uses a screen reader.
It will run on x86. But the features you're asking for? Nope, and they have no plans to- it's not what Android does, and it would totally break their activity lifecycle model. Its not meant to be a desktop OS. You could use it as one, but why?
Simple- it wouldn't. Android on a desktop box would work just like Android on a phone. It wouldn't keep separate users. Why would it? It's not a multi-user system. You seem to want a new feature to Android for a desktop box. Since desktop isn't their goal, I doubt they'd add it.
For the record- I don't see why you'd want Android on a desktop, it would be a bad experience. But nothing is stopping you right now, x86 support is out.
Android does exist on x86. They officially support it in the NDK, and several OEMs have released products on it.
This neither proved nor disproves evolution. Evolution is what happens after life exists. This is evidence for abiogenesis, which is an entirely separate theory- the theory that life can be formed from non-living components.
Also, your comment is entirely ridiculous. Any proof of evolution would require an experiment designed by scientists. But I am glad that you're keeping up the high level of logical reasoning, I haven't seen such amazing deductions since the 1950's batman series.
Legally, they do. Only charities are allowed not to. IANAL, but I don't know of any other legal exceptions. here are the legal criteria
The following six criteria must be applied when making this determination:
1. The internship, even though it includes actual operation of the facilities of the employer, is similar to
training which would be given in an educational environment;
2. The internship experience is for the benefit of the intern;
3. The intern does not displace regular employees, but works under close supervision of existing staff;
4. The employer that provides the training derives no immediate advantage from the activities of the intern;
and on occasion its operations may actually be impeded;
5. The intern is not necessarily entitled to a job at the conclusion of the internship; and
6. The employer and the intern understand that the intern is not entitled to wages for the time spent in the
internship.
If you're doing work that they would otherwise hire someone to do (as is completely the case in software), you must pay them at least minimum wage. I believe media companies get away with it by not having them do work but just be gophers, and they're supposed to soak up knowledge by being around the action, not actually doing any of it.
Also, you don't understand what evolution is. Evolution says what happens *AFTER LIFE STARTED TO EXIST* and how it changes over time. How those original life forms were created is an entirely different theory.
http://en.wikipedia.org/wiki/Miller%E2%80%93Urey_experiment
We can make the building blocks of life from inanimate objects.
There's going to be the rare amazing exception. But how many kids do you know right out of college with the focus, discipline, talent, understanding of the way the world works to be able to build a business? 1 in 100,000 maybe? I'm not saying it can't work, but it's a hard low probability road. It's not a wise choice.
Not to mention- the economy has jobs for programmers. The unemployment rate for programmers in Seattle is negative- more openings than job seekers.