Explosives were used in Kuwait to put out well fires, via oxygen starvation, so that they could safely be capped. This well isn't on fire, and assuming the well casing is intact, we'd want to preserve that as best as possible. Blowing it up would do nothing but make the mess harder to contain.
In addition to the other responses, the Deepwater Horizon was drilling 13,000 feet below the seafloor to reach the oil (a very average borehole depth).
Earthquakes don't typically open up 2.5mile deep fissures to cause leaks like this. For the shallow reserves, they've probably already leaked out if they were geologically unstable, and we probably didn't notice because we weren't paying attention for a dozen or so millenia, not centuries, if we existed at all when it occurred. Most oil is produced from stuff that lived 10 to 160 million years ago. If it leaked out even 1 million years ago, we'd wouldn't see any current ecological effects.
To summarize Limbaugh, it is natural, and nature will take care of it. Just not in our life time, and depending on how bad we fuck up, possibly not in the rest of human history.
Apple isn't being douchey about video formats, unless you consider "we don't want to suck" as being douchey. It's that a dedicated H.264 decoder chip exists in the iPhone (and most new smartphones) and provides significant performance gains in terms of framerate, video quality and battery life vs. other formats that are decoded on the CPU, at relatively low hardware cost. As far as I'm aware, a Theora decoder chip is not in popular use, if it exists at all.
H.264 provides a better experience for the user, which is why Apple chose it. It's their same reasoning for denying Flash on their mobile devices. Flash, in their browser, degrades the performance to a level they are unhappy with. Flash, as a common programming target, becomes a lowest common denominator and hands API control and release cycles over to a 3rd party. I don't like Apple making those decisions for me, so I don't own their devices, but there are millions of people who don't care about this and just want the best experience.
While I'm happy Google is giving me a choice to use Flash on my phone, I'm not overly excited about its arrival either, I've programmed in Flash before, and I agree with many of Jobs' criticisms. My hope is that Apple's scorn will force them to improve their product.
If you're afraid of their intelligence gathering and profiling, the worst action you could take would be removing yourself from the honeypots. That's like waving a giant red flag saying "I've caught on to the scam!" If they're using the data for nefarious reasons, you're going to be identified as someone who, early on, proved troublesome.
If you're already on the networks, you'd be far more likely to fly under the radar by gently subverting your profile into something that will be perceived innocuous instead of an abrupt removal. Corrupting their data is far more protective than merely limiting what they have available.
Yeah, and you had to drive to a store or order from a catalog to get that 486 software. And you pretty much had to buy everything.
Browser based apps are about the "here and now...anywhere, usually for free". It's the delivery mechanism that matters. There are more games available to you at any moment on the internet than were ever available for the 486. Where's the 486 equivalent to Last.FM, Hulu/YouTube, or Picasa? Even stuff that was possible on a 486 was often much slower and/or far more expensive than current Google Apps alternatives.
Especially if you wanted to run it inside a VM and only allocate some fraction of the cores to that instance. Still gotta pay for the cores/box, not cores assigned. Thanks Oracle.
Other than price rape, and a general level of half-assery that ensures they'll have to visit you on site to fix the shit they sold to your boss, I don't understand why enterprise software needs to know what hardware you're using anyways.
Assuming these would be returned from a framework library, or I can't readily access the source and this is just part of documentation.
The first example is fairly readable, concise and sensible. Knowing a little about how Ruby handles things as objects, I "get it" and am comfortable with what @posts would probably contain. I'm fairly certain @posts is a plural set/object of more Post objects, which represents a row in a database, where status is public, then ordered descending. I can probably iterate through it. As an outsider, I could read this, lookup the column names for the row and almost immediately start using it.
Knowing some of the problems with PHP and its community, I can make no assumptions about what $records will really be unless I know the author's style or am already familiar with the codebase. Ignoring your writeup justification for shortening, I can't guess what _model is, I don't know what blogs really represents, and I'm uncertain why fetchAll needs an array object passed as a parameter, I have to mentally replace the question mark with "public", then assume the second parameter is an order-by parameter since I see the DESC. Before I would be ready and comfortable to use $records in a meaningful way, I'd have to dump it to the screen or use a debugger, plus lookup the syntax for fetchAll, and I'd really want to know what _model and blog actually represented since you're now magically assuming the blog object links to a table somehow. I do not know if blog is iterable or if it's rows it has grabbed are even accessible. $records may be the result of some manipulation it performs on the query result. I just don't know, and that makes me uncomfortable.
So while you've reduced character quantity to near comparable levels, you've not matched readability or understanding. You've merely condensed complex code into short complex code. Honestly, I think it's a philosophy difference between PHP and Ruby. Ruby the language strives for the principle of least surprises, and if the programmers utilizing it adhere to that, I can grasp their code pretty quickly. PHP is a grab-bag; you can make no assumptions, which is both a strength and a weakness.
Granted, PHP can still be used successfully to start and run a business, but as a programmer with no professional experience in either language, I'm gravitated towards the Ruby example.
I don't know why Sprint is hemorrhaging customers, just go to the various sites and compare plans and prices. Verizon is a better network but often 40% more expensive for equal services (and Sprint gets to piggyback for free if needed), T-Mobile is close but not quite as good, and AT&T is currently considerably worse in all respects except offering the iPhone.
Unless you're an international traveler, refuse to use subsidized phones, or obsessed with the iPhone, Sprint is the clear winner.
Significant features (first great spam filter, threaded conversations, search)
First to offer generous storage quotas
Service integration with Chat, Docs, Calender, Reader, Maps, etc
Adequate and responsive mobile support
One of the first to bring IMAP and SSL connections to everyday email
Unobtrusive ads on page, and none have ever been injected into sent email
Sure, AOL has caught up to a lot of these, but strictly as a "me-too" effort to not alienate and lose [even more] users.
While it's probably not right to make judgments based on email domains, even while AOL has historically been associated with low technical competency, I see nothing wrong with discriminating based on usernames. For professional disclosure, I would expect a professionally acceptable username (i.e. no l33tspeak, nothing using "420", "69", drug-related or sexually provocative words, and nothing too crazy sounding unless you've got an significant and established online identity under that guise, and no generics like admin or webmaster@randomuselessdomain.com).
I'm a software developer, and having done it for a few years now, I spend my free time brewing beer and baking bread. Sometimes dealing with less rigid systems is far more enjoyable.
But the last 35 minutes are non-interactive, it's just watching files transfer and letting it reboot. The important, interactive part of the install where the user must actually use stuff is entirely in a DOS/curses like environment. Setting the system time with a GUI is not an important step.
Vista and 7 improve on it, but neither are as slick as Ubuntu's liveCD method.
I would suggest against ASM as a first step. Kids of the last two decades (myself included) have grown up around computers, they're already thinking several levels abstracted from the bare metal, and when they think 'programming computers' they probably want to see problems and results at their current level of abstraction and understanding, and gain knowledge they can use.
When a person mostly understands their current "layer" is when they should move up or down in abstraction. Given a one-on-one scenario, I suggest asking about their interests and find out where they are the most knowledgable, then use that as a starting point.
Teaching them about registers and opcodes will probably not integrate with any of their current knowledge. Much like in school, I disliked math, not because it was hard, but because teachers could rarely relate it the my world or current knowledge. Basic mental methaphors. We're not building a house, we're building a network of information. Foundations matter, but they're not always the starting point.
While the evolution of genres into sub-genres is expected, ironically, the Christian rock branch seems the least inspired of them all due to it's outright imitation of 'regular' rock.
If Christian musicians were genuinely good at what they did, you would expect to see many of them able to cross over into mainstream. It happens, but it's extremely rare, or the Christian visage is dropped along the way. Why is a self proclaimed nation under God unwilling to buy Christian music?
Either way, I expect message-based videogames would follow the same trend. There's a market for it, but only a small subset of the mainstream would buy it. Figure out how to pitch a game that can meet a minimum level of production quality (Deer Hunter level) at a price point someone is willing to risk against that small market, and you've got a money making idea. Good luck, FSM be with you.
On the other hand, "Old Testament God" slaughtered humans like it was going out of style and made us do all sorts of silly things. If we want to view it as a set of Russian dolls, then perhaps we're just experiencing the same steps towards maturation?
I've only ran OSX on a single core Atom/GMA950 machine (built for the purpose of OSX), but found it to be fine.
Obviously it's no media center or number crunching machine, but it browses the web wirelessly, handles non-HD Flash and all normal website Flash, and will play back non-HD videos without a problem. It runs Photoshop and Eclipse without problems. Loading apps is slower than my quad-core box, and it gets bogged down with intense multitasking, but it's not miserable either. It would even run VMware Fusion + an ubuntu virtual machine at a level I'd still call responsive.
I'm genuinely curious, where is your bottleneck? What OS's are you using? Is it a problem of expectations? I've been nothing but happy with the performance for the $180 in parts.
A cancer treatment from Microsoft would mean that you'd have to continually buy a license to maintain use of the treatment from them or they'd cut you off and let you die. You may survive, but you're enslaved to them.
Then again, that's not far off from current medical practices either.
I can one up you on titles. The company I work for was bought by a larger contracting company. Within my original organization, I'm a Software Engineer I to HR, in the larger company, I'm an Associate Programmer II for payroll purposes, but in the host company I'm an Application Developer & Support for contractual purposes. Within the host company, other departments refer to me as Software Analyst.
Titles are fluff. Yes, they can reflect real world salaries, and make a difference in getting past HR resume keyword filters, but I've got 3 official titles for the same entry level crap job. I could just as easily be Jr. Software Developer, Web Programmer, Enterprise Web Developer, Jr. Java Architect, etc, and it wouldn't matter at all. I don't mind being lumped into IT, as what I do is "technology regarding information", but the IT industry is horrible about creating crap titles that mean nothing, and really bad about consistently differentiating "code monkey" workers from actual computer scientists.
Projectors are becoming smaller and smaller (see that new Nikon camera). Bendable/rollup displays are in R&D. Displays quality keeps improving. TV-Out is old news and HD capable phones are already just around the corner. Mobile HD displays are just a matter of time. Hell, current top-tier cellphones have better resolution than SDTVs.
And I can already update my resume on Google Docs from my phone. Printing it out is only an issue of interfacing. There's no technological barrier to it right now, there's just no demand. Some HP printers already connect to Google Maps, it's perfectly conceivable that any network enabled printer could be accessed via a phone.
Never is a strong word. Unless by 'cellphone' you mean it in the most literal sense of the word, a cellular phone sans other capabilities, your statement is already false.
Explosives were used in Kuwait to put out well fires, via oxygen starvation, so that they could safely be capped. This well isn't on fire, and assuming the well casing is intact, we'd want to preserve that as best as possible. Blowing it up would do nothing but make the mess harder to contain.
In addition to the other responses, the Deepwater Horizon was drilling 13,000 feet below the seafloor to reach the oil (a very average borehole depth).
Earthquakes don't typically open up 2.5mile deep fissures to cause leaks like this. For the shallow reserves, they've probably already leaked out if they were geologically unstable, and we probably didn't notice because we weren't paying attention for a dozen or so millenia, not centuries, if we existed at all when it occurred. Most oil is produced from stuff that lived 10 to 160 million years ago. If it leaked out even 1 million years ago, we'd wouldn't see any current ecological effects.
To summarize Limbaugh, it is natural, and nature will take care of it. Just not in our life time, and depending on how bad we fuck up, possibly not in the rest of human history.
Apple isn't being douchey about video formats, unless you consider "we don't want to suck" as being douchey. It's that a dedicated H.264 decoder chip exists in the iPhone (and most new smartphones) and provides significant performance gains in terms of framerate, video quality and battery life vs. other formats that are decoded on the CPU, at relatively low hardware cost. As far as I'm aware, a Theora decoder chip is not in popular use, if it exists at all.
H.264 provides a better experience for the user, which is why Apple chose it. It's their same reasoning for denying Flash on their mobile devices. Flash, in their browser, degrades the performance to a level they are unhappy with. Flash, as a common programming target, becomes a lowest common denominator and hands API control and release cycles over to a 3rd party. I don't like Apple making those decisions for me, so I don't own their devices, but there are millions of people who don't care about this and just want the best experience.
While I'm happy Google is giving me a choice to use Flash on my phone, I'm not overly excited about its arrival either, I've programmed in Flash before, and I agree with many of Jobs' criticisms. My hope is that Apple's scorn will force them to improve their product.
Well, he did say he bought them on credit. Hard times, man, hard times.
If you're afraid of their intelligence gathering and profiling, the worst action you could take would be removing yourself from the honeypots. That's like waving a giant red flag saying "I've caught on to the scam!" If they're using the data for nefarious reasons, you're going to be identified as someone who, early on, proved troublesome. If you're already on the networks, you'd be far more likely to fly under the radar by gently subverting your profile into something that will be perceived innocuous instead of an abrupt removal. Corrupting their data is far more protective than merely limiting what they have available.
Yeah, and you had to drive to a store or order from a catalog to get that 486 software. And you pretty much had to buy everything.
Browser based apps are about the "here and now...anywhere, usually for free". It's the delivery mechanism that matters. There are more games available to you at any moment on the internet than were ever available for the 486. Where's the 486 equivalent to Last.FM, Hulu/YouTube, or Picasa? Even stuff that was possible on a 486 was often much slower and/or far more expensive than current Google Apps alternatives.
Yeah, software hasn't progressed at all.
Especially if you wanted to run it inside a VM and only allocate some fraction of the cores to that instance. Still gotta pay for the cores/box, not cores assigned. Thanks Oracle. Other than price rape, and a general level of half-assery that ensures they'll have to visit you on site to fix the shit they sold to your boss, I don't understand why enterprise software needs to know what hardware you're using anyways.
I don't believe politicians under 50 understand technology any better than their elders.
Disclaimer: I'm not a PHP or Ruby programmer. I come from the land of Java and Python.
@posts = Post.where(:status => 'public').order('created DESC')
$records = $this->_model->blogs->fetchAll(array('status = ?' => 'public'), 'created DESC');
Assuming these would be returned from a framework library, or I can't readily access the source and this is just part of documentation.
The first example is fairly readable, concise and sensible. Knowing a little about how Ruby handles things as objects, I "get it" and am comfortable with what @posts would probably contain. I'm fairly certain @posts is a plural set/object of more Post objects, which represents a row in a database, where status is public, then ordered descending. I can probably iterate through it. As an outsider, I could read this, lookup the column names for the row and almost immediately start using it.
Knowing some of the problems with PHP and its community, I can make no assumptions about what $records will really be unless I know the author's style or am already familiar with the codebase. Ignoring your writeup justification for shortening, I can't guess what _model is, I don't know what blogs really represents, and I'm uncertain why fetchAll needs an array object passed as a parameter, I have to mentally replace the question mark with "public", then assume the second parameter is an order-by parameter since I see the DESC. Before I would be ready and comfortable to use $records in a meaningful way, I'd have to dump it to the screen or use a debugger, plus lookup the syntax for fetchAll, and I'd really want to know what _model and blog actually represented since you're now magically assuming the blog object links to a table somehow. I do not know if blog is iterable or if it's rows it has grabbed are even accessible. $records may be the result of some manipulation it performs on the query result. I just don't know, and that makes me uncomfortable.
So while you've reduced character quantity to near comparable levels, you've not matched readability or understanding. You've merely condensed complex code into short complex code. Honestly, I think it's a philosophy difference between PHP and Ruby. Ruby the language strives for the principle of least surprises, and if the programmers utilizing it adhere to that, I can grasp their code pretty quickly. PHP is a grab-bag; you can make no assumptions, which is both a strength and a weakness.
Granted, PHP can still be used successfully to start and run a business, but as a programmer with no professional experience in either language, I'm gravitated towards the Ruby example.
I don't know why Sprint is hemorrhaging customers, just go to the various sites and compare plans and prices. Verizon is a better network but often 40% more expensive for equal services (and Sprint gets to piggyback for free if needed), T-Mobile is close but not quite as good, and AT&T is currently considerably worse in all respects except offering the iPhone.
Unless you're an international traveler, refuse to use subsidized phones, or obsessed with the iPhone, Sprint is the clear winner.
"Being able to have a straight tube delivering bags of blood between OR and blood bank is an amazing time saver for staff."
So...a truth table of tubes?
Sure, AOL has caught up to a lot of these, but strictly as a "me-too" effort to not alienate and lose [even more] users.
While it's probably not right to make judgments based on email domains, even while AOL has historically been associated with low technical competency, I see nothing wrong with discriminating based on usernames. For professional disclosure, I would expect a professionally acceptable username (i.e. no l33tspeak, nothing using "420", "69", drug-related or sexually provocative words, and nothing too crazy sounding unless you've got an significant and established online identity under that guise, and no generics like admin or webmaster@randomuselessdomain.com).
A project that doesn't get outsourced to India and look what happens.
I'm a software developer, and having done it for a few years now, I spend my free time brewing beer and baking bread. Sometimes dealing with less rigid systems is far more enjoyable.
But the last 35 minutes are non-interactive, it's just watching files transfer and letting it reboot. The important, interactive part of the install where the user must actually use stuff is entirely in a DOS/curses like environment. Setting the system time with a GUI is not an important step.
Vista and 7 improve on it, but neither are as slick as Ubuntu's liveCD method.
I would suggest against ASM as a first step. Kids of the last two decades (myself included) have grown up around computers, they're already thinking several levels abstracted from the bare metal, and when they think 'programming computers' they probably want to see problems and results at their current level of abstraction and understanding, and gain knowledge they can use.
When a person mostly understands their current "layer" is when they should move up or down in abstraction. Given a one-on-one scenario, I suggest asking about their interests and find out where they are the most knowledgable, then use that as a starting point.
Teaching them about registers and opcodes will probably not integrate with any of their current knowledge. Much like in school, I disliked math, not because it was hard, but because teachers could rarely relate it the my world or current knowledge. Basic mental methaphors. We're not building a house, we're building a network of information. Foundations matter, but they're not always the starting point.
While the evolution of genres into sub-genres is expected, ironically, the Christian rock branch seems the least inspired of them all due to it's outright imitation of 'regular' rock.
If Christian musicians were genuinely good at what they did, you would expect to see many of them able to cross over into mainstream. It happens, but it's extremely rare, or the Christian visage is dropped along the way. Why is a self proclaimed nation under God unwilling to buy Christian music?
Either way, I expect message-based videogames would follow the same trend. There's a market for it, but only a small subset of the mainstream would buy it. Figure out how to pitch a game that can meet a minimum level of production quality (Deer Hunter level) at a price point someone is willing to risk against that small market, and you've got a money making idea. Good luck, FSM be with you.
On the other hand, "Old Testament God" slaughtered humans like it was going out of style and made us do all sorts of silly things. If we want to view it as a set of Russian dolls, then perhaps we're just experiencing the same steps towards maturation?
But us beer snobs...we're legit.
Old P3 laptop = 12lb ugliness, crap battery life, no wireless.
New Atom netbook = 2.5 lb sleekness, +6hrs battery life.
I've only ran OSX on a single core Atom/GMA950 machine (built for the purpose of OSX), but found it to be fine.
Obviously it's no media center or number crunching machine, but it browses the web wirelessly, handles non-HD Flash and all normal website Flash, and will play back non-HD videos without a problem. It runs Photoshop and Eclipse without problems. Loading apps is slower than my quad-core box, and it gets bogged down with intense multitasking, but it's not miserable either. It would even run VMware Fusion + an ubuntu virtual machine at a level I'd still call responsive.
I'm genuinely curious, where is your bottleneck? What OS's are you using? Is it a problem of expectations? I've been nothing but happy with the performance for the $180 in parts.
A cancer treatment from Microsoft would mean that you'd have to continually buy a license to maintain use of the treatment from them or they'd cut you off and let you die. You may survive, but you're enslaved to them. Then again, that's not far off from current medical practices either.
I can one up you on titles. The company I work for was bought by a larger contracting company. Within my original organization, I'm a Software Engineer I to HR, in the larger company, I'm an Associate Programmer II for payroll purposes, but in the host company I'm an Application Developer & Support for contractual purposes. Within the host company, other departments refer to me as Software Analyst.
Titles are fluff. Yes, they can reflect real world salaries, and make a difference in getting past HR resume keyword filters, but I've got 3 official titles for the same entry level crap job. I could just as easily be Jr. Software Developer, Web Programmer, Enterprise Web Developer, Jr. Java Architect, etc, and it wouldn't matter at all. I don't mind being lumped into IT, as what I do is "technology regarding information", but the IT industry is horrible about creating crap titles that mean nothing, and really bad about consistently differentiating "code monkey" workers from actual computer scientists.
I'll drink to that.
Projectors are becoming smaller and smaller (see that new Nikon camera). Bendable/rollup displays are in R&D. Displays quality keeps improving. TV-Out is old news and HD capable phones are already just around the corner. Mobile HD displays are just a matter of time. Hell, current top-tier cellphones have better resolution than SDTVs.
And I can already update my resume on Google Docs from my phone. Printing it out is only an issue of interfacing. There's no technological barrier to it right now, there's just no demand. Some HP printers already connect to Google Maps, it's perfectly conceivable that any network enabled printer could be accessed via a phone.
Never is a strong word. Unless by 'cellphone' you mean it in the most literal sense of the word, a cellular phone sans other capabilities, your statement is already false.