We have the virtual machine kids fighting it out in one corner. We had native platform dudes in another. We had the obligatory mac vs pc vs linux still going at it after 20 years We even had an appearance from some GPU fanboys.
We have never seen so many replies marked down with Troll and Flame bait.
I could actually picture foam coming from some of the fanboys mouths as they had to respond to every thread they could. And correct the religious misdeeds of the others.
All going at it at once. Who wins? ( ME. I was highly entertained by the carnage. )
Because his opinion is against a fairly standard convention he declares himself right and the opposite opinion to be myth.
How arrogant can you get. Really.
"I think MS Windows sucks Donkey Nuggets. Therefore everyone should switch to Android. The power I wield is frightening."
I've been writing code for over 20 years. One thing you learn is that you don't want those "Hey how do you do xyz with method ABC in the code you wrote 10 years ago." calls. How do you avoid this your code follows you like a bad poo cling on. YOU COMMENT YOUR CODE. With descriptions, examples, purpose and anything else that is relevant. You probably should spend as much if not more time on the comments than the code. Cause it will save you heaps of time in the future.
As for documentation that is external to the code? Well it's useless. Because repositories change move and mutate. Over the years the design/requirements/arch docs all seem to vanish. The only thing that seems to live on is the actual code. Why. The code is the business not the power point slide show. The code therefore should also be the documentation.
So Mr. I'm 20something and know everything about writing code. Time to join the real world. I for one never want to have to fix your code.
I've seen so many of these sorts of articles lately on/.
It's really devaluing/.
It would be nice to have some mod facility to get these nuked. It's disappointing that such a long running resource like/. is now being infected with self promotion. One of the best self promotion FAILS was the one about face book switching to some C++ frame work from php in order to save 10s of thousands of servers resources. I'm still laughing about that one.
At no point did I say cheap. I said heavy lifters are cheaper. When you talking about millions of dollars cheaper is far better.
Also if you don't learn how to utilize the resources out in space you ain't doing any exploration. Cause it's going to cost ridiculous amounts of money to get those resources into space if you don't use the resources up there.
Well it's not to lift a space station in one go. That's just stupid. First off you would have to build it in one impossible strong piece. The current system of lifting smallish pieces and assembling them in space will continue.
It's to lift FUEL.
A large lifter has to have 1 complete set of instruments. ( Plus it's redundancy ). A small lifter has to have EXACTLY THE SAME instruments. Thus the efficiency of the lifter drops and the expense per lift increases.
As a whole a large lifter would have approximately the same loss ratio as the large lifter. So in the end you would loose about the same tonage of valuable cargo with small lifters as you would with large lifters. But as I just pointed out. IT COSTS MORE.
Also note that there is not a launch on the planet these days that is not insured. Insurance is a means of spreading out the losses of the cost of the total sum of all lifts. The losses typically include the value of the earnings of the item being luanched. So the only real loss when something blows up is the time it takes to launch the next one.
So a bigger lifter only makes sense. Buy volume and tonage more of the lifter is devoted to the cargo. The higher the cargo to lifter ratios the more cost effective the operation is.
A larger lifter is much more flexible and adaptable. The smaller the lifter the more complex it is to adapt the payload to the lifters restrictions of weight and size. A bigger lifter would obviously have fewer restrictions. For example. Would it be cheaper to design and build a satellite that has to fold up to a super tiny space or a satellite that simple just has to unfold it's solar panels. Clearly the second one. It would also be more likeley to be designed tested and built far in advance of the smaller one. Thus a larger lifter also reduces the cost of the payloads themselves.
In the end a large lifter is so clearly the only way to go.
Clearly you have not even looked at the big picture.
First off the fuel is Hydrogen and Oxygen. Which by product is water.
The space program has given us. world wide telecommunications, GPS, weather satellite. How many lives and how much energy have those things saved? GPS alone applied to the transport industry has been a huge fuel saver.
"If" we develop fusion we will need fuel. Where is the highest concentration of fusion fuel? The moon.
Would it not be more ecological to mine asteroids than the amazon?
What about the development of clean 24/7 solar power? That can only be achieved in space.
The Moon program of the 60's gave us the transistor and ultimately the processor in your computer you used to view this. How many lives have been saved by the chip. Hybrid cars would be impossible with them.
The space program is possible the last area where mega projects can have significant positive impact on the planet, man and our future.
And lastly the resources in space are LIMITLESS. Once we learn how to tap them properly.
Steve Ballmer on stage at any time is always funny.:) Developers Developers Developers..... bahahahahahahaha
Sony root kit. I'm still finding PC's infected with this beast.
Zune. Do they still make this thing. I actually saw one in the wild once. Man that thing is UGLY.
The Kindle the most pointless electronic gizmo ever. It's not a laptop, phone, or book. You don't own the content. and it's UGLY. You want how much??????
This couldn't have back fired on this clown any worse. I really hope he didn't make a fool of himself telling everyone he was going to get rick of consulting from this. Cause man he ain't getting anywhere near my work.
This guy was talking non-sense. 1-10. If I was executing a single use once ever to run piece of code maybe this would be true. But facebook would never execute a line of code once.
In reality the ratio is more like 1-1.2. For well written code on both sides of the fence. Code that runs a LOT.
Also a large scale env would have plane and simple implemented a ton of optimizations for caching, CDN, that would make the choice of language almost moot. The language choice really boils down to the choice of lead arch and his/her favorite resume boosting tech of the moment. Of course you stuck with that choice for much longer than anyone ever guesses.
Language pro-con this that and the other thing become part of the hallway conversations that eat up valuable time. I always go with what will get me to market the fastest. I can't worry about if I made the wrong choice in languages simply because in two years one of the other languages may be better. It's just too hard to see out farther than 6 months.
This story makes assumptions on system architecture that point blank would just not be true in a large scale deployment.
Sure C++ is more efficient that PHP. But where does it say that EVERYTHING or even most is served via a php interpreter. In a large scale world dynamic caches and CDN's would have offloaded all of the cachable content and it would have never hit the php interpreter. Guess what a C++, Java, anything else env would do exactly the same thing.
You would be amazed at how much off load is possible. What you think is dynamic content is usually just a very simplistic dynamic wrapper over large swaths of static content. A seemingly dynamic html is really just a collection of static html blobs that can be held by a cache or CDN close to the consumer and assumbled as a complete html document on the fly by an web aware accelerator.
These 30,000 boxes that are spoken of are most likely composed of a large verity of purpose specific hardware. Where the purposes are much more diverse than a simple php / mysql combo's. Lets face it. Face book is across the planet and is relatively speedy all across the planet. This implies that a distributed CDN is in place. With local content caching nearest the consumer. Instantly this means we have more purposes than just php/mysql for the hardware. Authentication is usually offloaded by large scale web shops for a host of reasons. So lets add that kit to the list of purpose built. I could go on and on about the various purposes.
So it's fairly obvious that the statement we could shut off 22K+ worth of machines by simply ( nothing simple about this ) changing languages is just non-sense.
Plane and simple a large scale web environment is only partially the application hosting equipment. A very large part of the environment is the infrastructure, network, CDN, Caches, accelerators, security,.... equipment. Yes I can write a little fancy web app and run it on my netbook and wow people. It's a whole other matter to scale that up to 10's of millions of concurrent users spread across the planet.
Lets face it. That amount of equipment consumes one hell of a power bill. I'm positive that "Facebook" has already done an enormous amount of work to reduce that bill. Not for save the planet reasons but for simple dollar reasons. Can they do more. Absolutely. But it won't be a simple we'll just change everything over to this new language this weekend and then hit a bunch of power switches. The amount of power consumed by the massive development work force to write test document deploy this new wonder solution would probably leave "Facebook" in an energy debt for another several years.
PS. Good luck with that sales pitch if you ever make it near the office doors of facebook.:)
The reason we are often called IT people is simply a result of how badly IT people abuse IT titles, definitions and words.
I'm an IT guy. How are non-IT people suppose to keep up with the vernacular if we keep on insisting to invent new words and meanings for existing words every six months. IT as an industry is very well known for BUZZ word bingo. We are called the IT guy/gal simply because that's the only phrase that is general enough to be understood.
I'm very senior in my field. However I refuse to give myself a title that pumps my ego. I simply go by the title Senior Consultant. Why? Simple because everyone who has a buzz word bingo multi-word title is typically full of BS. Thus tainting the title and the meaning of the associated titles. I have colleagues in my company that are almost militant about making sure their title has all the most leading edge buzz words.
It's our own bloody fault we get called "IT Guy". Once real professional standards are applied Universally in the industry we will start to see real titles stick.
My advice is don't sweat it. If you wanna put them in their place simple ask them to get you a coffee and a sandwich while you fix their trivial problem.:)
Yah but mono ain't C# at the end of the day is it.
It will always be that bastard language child that sorta looks like it's dad. Sometimes it wants to do it's own thing and express it's own individuality sometimes it wants to be just like dad. In the end it's not dad.
And cool apps just don't cut it at the Enterprise level. For id skimming iPhone apps sure but not big boy stuff.
And really do we want to have a copy of something that is associated with the most hacked OS on the planet? No! I want something in my data center that is fast cheap to build and requires little attention. Windoz anything requires 24/7 hotline loven. I really don't want something that quacks like a duck walks like a duck but it's a turkey.
Hell I'll take perl, ruby, python and php before a C# or it's bastard children.
C great language did exactly what it was designed to do. But carries a lot of burden. C++ come on it didn't even have a string class. Thus pointer math hell. C#, Ok it learned a lesson and found the joy of a string class. But really it's a windows only lang. Java. Excuse me web apps that take 8Gig of ram spread across a farm of servers. This slow elephant remade the hardware business.
All of the above never really understood concurrent / multithread / parallel. ( Sorry Java devs still have issues with the concept. GC & log4j come to mind as things that forgot they were in a threaded env. )
So the "Go" lang it just might deserve a look. Clearly web centric. Clearly built for tons of concurrent comms. Recompiles in a blip thus useful for real time compiling alla jsp. I'm very performance centric. If I can replace my J2EE bloat ware with a trunk full of tiny Go apps I will.
I'm definitely watching this space for developments.
You think you have ever angle covered. You are proud of how tight the whole design is. Then along comes some moron and BOOOMMMMM. They defeat your planning in 1 second.
Happens all the time.
I've had a lot of managers in companies look at me when I say that. First off the idiots get very offended. The smart ones get it. The phrase acts like pre-filter before any work is actually done.
As a result over the years I have learned that design and implementation has to have certain attributes. - flexibility. We will have to come back and alter/fix something. - redundancy. Their has to be more than 1 method of doing something. In your case a window and a fan as my backup second option. - slack. Things never fit exactly into the specifications. Whether it be a measurement of distance. A power consumption claim. or a throughput estimate. Always add more during the build. It's cheaper.
It's the arrogant that think it works out of the box first time.
I have to agree. Eclipse has become an un-usable mess.
I actually went back to a decent text editor. When I went back into the repository I found I wrote more code with the text editor than I did with Ecilpse by shear line count. I also had less bugs. This I completely did not expect at all. I also billed less time to "life cycle" AKA bug fixes. I guess looking back at it now I can attribute it to having less distractions and being required to actually research the interfaces I was using.
Now I definitely want to get a decent IDE. I believe it would make my code better. But Eclipse is not it.
Seriously how the hell does an editor/ide require over 1Gig of ram to run efficiently. That's just crazy. Can't even run it on a 32bit machine.
The process concentrates sea water to brine by an evaporation method. So why waste this low grade stream it is still has high in moisture content. There is already a condenser in this system. I'm thinking this can somehow boost output of clean water.
"The Phone is the network" What the heck does this mean. That's like saying "The medium is the message", "The ego is the soul" or some other rubbish like that. All I see is a some dude that is getting too old to hang out with college kids but is still doing it by pretending to be some great thinker type. Always sitting at the most exposed spot in the coffee shop legs cross pretending to read something that will impress a 19 year old book worm.
--- Secondly there is no Android network restriction! Just get on the net and order say a HTC Hero. Put your sim and you're away. Hell I live in Aus. I ordered an andriod phone in from over seas. Dropped my sim in and bam I'm gold.
iPhone is all about vendor lock in. Lock in is a gold mine for any company. Apple knows this. AT&T paid or rather gives huge portions of profit because of the iPhone lock in draw. Competition only occurs when the players are forced or force each other to play on the same field.
2010 will see a lot of changes on this front. I'm guessing the lock in will be gone for the iPhone. Pre, Andriod, even winMo 6.5/7.0 are eating in on the market. ---
Besides Apple has already decided the market needs another kick in the nuts. With the new APPLE tablet like thing. It's mostly phone but a little more net app machine. I recon they will call it "iMe" nothing more selfish then selfish^2.
---
But good god please stop the use of "_____ is the _____" references. You sound like a twat.
Slashdot Mirror
Great thread.
This one sucked in every fanboy on the /.
We have the virtual machine kids fighting it out in one corner.
We had native platform dudes in another.
We had the obligatory mac vs pc vs linux still going at it after 20 years
We even had an appearance from some GPU fanboys.
We have never seen so many replies marked down with Troll and Flame bait.
I could actually picture foam coming from some of the fanboys mouths as they had to respond to every thread they could. And correct the religious misdeeds of the others.
All going at it at once. Who wins? ( ME. I was highly entertained by the carnage. )
A lot more than you think that's for sure.
Discovered bugs != Actual bugs
Because his opinion is against a fairly standard convention he declares himself right and the opposite opinion to be myth.
How arrogant can you get. Really.
"I think MS Windows sucks Donkey Nuggets. Therefore everyone should switch to Android. The power I wield is frightening."
I've been writing code for over 20 years. One thing you learn is that you don't want those "Hey how do you do xyz with method ABC in the code you wrote 10 years ago." calls. How do you avoid this your code follows you like a bad poo cling on. YOU COMMENT YOUR CODE. With descriptions, examples, purpose and anything else that is relevant. You probably should spend as much if not more time on the comments than the code. Cause it will save you heaps of time in the future.
As for documentation that is external to the code? Well it's useless. Because repositories change move and mutate. Over the years the design/requirements/arch docs all seem to vanish. The only thing that seems to live on is the actual code. Why. The code is the business not the power point slide show. The code therefore should also be the documentation.
So Mr. I'm 20something and know everything about writing code. Time to join the real world. I for one never want to have to fix your code.
Doh my spelling has always SUCKED.
I've seen so many of these sorts of articles lately on /.
It's really devaluing /.
It would be nice to have some mod facility to get these nuked. It's disappointing that such a long running resource like /. is now being infected with self promotion. One of the best self promotion FAILS was the one about face book switching to some C++ frame work from php in order to save 10s of thousands of servers resources. I'm still laughing about that one.
I can confirm it is a rumor. :)
100% correct. This will be a total flop without the logo.
Point taken. I meant to type IC. Integrated Circuit. IC leading to chip.
Thanks for the correction :)
At no point did I say cheap. I said heavy lifters are cheaper. When you talking about millions of dollars cheaper is far better.
Also if you don't learn how to utilize the resources out in space you ain't doing any exploration. Cause it's going to cost ridiculous amounts of money to get those resources into space if you don't use the resources up there.
In space?
The easy ones are:
Solar power
Hydrogen
Oxygen
Iron
But everything else is out there. We just have to figure out where and how to get at it in a cost effective manor.
The point is public interest is a dead end for funding.
A big lifter brings space closer to profitability. Once it is profitable then the space exploration takes off.
Um heavy lifters would be used for what exactly?
Well it's not to lift a space station in one go. That's just stupid. First off you would have to build it in one impossible strong piece. The current system of lifting smallish pieces and assembling them in space will continue.
It's to lift FUEL.
A large lifter has to have 1 complete set of instruments. ( Plus it's redundancy ). A small lifter has to have EXACTLY THE SAME instruments. Thus the efficiency of the lifter drops and the expense per lift increases.
As a whole a large lifter would have approximately the same loss ratio as the large lifter. So in the end you would loose about the same tonage of valuable cargo with small lifters as you would with large lifters. But as I just pointed out. IT COSTS MORE.
Also note that there is not a launch on the planet these days that is not insured. Insurance is a means of spreading out the losses of the cost of the total sum of all lifts. The losses typically include the value of the earnings of the item being luanched. So the only real loss when something blows up is the time it takes to launch the next one.
So a bigger lifter only makes sense. Buy volume and tonage more of the lifter is devoted to the cargo. The higher the cargo to lifter ratios the more cost effective the operation is.
A larger lifter is much more flexible and adaptable. The smaller the lifter the more complex it is to adapt the payload to the lifters restrictions of weight and size. A bigger lifter would obviously have fewer restrictions. For example. Would it be cheaper to design and build a satellite that has to fold up to a super tiny space or a satellite that simple just has to unfold it's solar panels. Clearly the second one. It would also be more likeley to be designed tested and built far in advance of the smaller one. Thus a larger lifter also reduces the cost of the payloads themselves.
In the end a large lifter is so clearly the only way to go.
Clearly you have not even looked at the big picture.
First off the fuel is Hydrogen and Oxygen. Which by product is water.
The space program has given us. world wide telecommunications, GPS, weather satellite. How many lives and how much energy have those things saved? GPS alone applied to the transport industry has been a huge fuel saver.
"If" we develop fusion we will need fuel. Where is the highest concentration of fusion fuel? The moon.
Would it not be more ecological to mine asteroids than the amazon?
What about the development of clean 24/7 solar power? That can only be achieved in space.
The Moon program of the 60's gave us the transistor and ultimately the processor in your computer you used to view this. How many lives have been saved by the chip. Hybrid cars would be impossible with them.
The space program is possible the last area where mega projects can have significant positive impact on the planet, man and our future.
And lastly the resources in space are LIMITLESS. Once we learn how to tap them properly.
Ah that was good for a Laugh.
Steve Ballmer on stage at any time is always funny. :) Developers Developers Developers..... bahahahahahahaha
Sony root kit. I'm still finding PC's infected with this beast.
Zune. Do they still make this thing. I actually saw one in the wild once. Man that thing is UGLY.
The Kindle the most pointless electronic gizmo ever. It's not a laptop, phone, or book. You don't own the content. and it's UGLY. You want how much??????
All in all a good read. Thanks.
I hear you.
This couldn't have back fired on this clown any worse. I really hope he didn't make a fool of himself telling everyone he was going to get rick of consulting from this. Cause man he ain't getting anywhere near my work.
This guy was talking non-sense. 1-10. If I was executing a single use once ever to run piece of code maybe this would be true. But facebook would never execute a line of code once.
In reality the ratio is more like 1-1.2. For well written code on both sides of the fence. Code that runs a LOT.
Also a large scale env would have plane and simple implemented a ton of optimizations for caching, CDN, that would make the choice of language almost moot. The language choice really boils down to the choice of lead arch and his/her favorite resume boosting tech of the moment. Of course you stuck with that choice for much longer than anyone ever guesses.
Language pro-con this that and the other thing become part of the hallway conversations that eat up valuable time. I always go with what will get me to market the fastest. I can't worry about if I made the wrong choice in languages simply because in two years one of the other languages may be better. It's just too hard to see out farther than 6 months.
This story makes assumptions on system architecture that point blank would just not be true in a large scale deployment.
Sure C++ is more efficient that PHP. But where does it say that EVERYTHING or even most is served via a php interpreter. In a large scale world dynamic caches and CDN's would have offloaded all of the cachable content and it would have never hit the php interpreter. Guess what a C++, Java, anything else env would do exactly the same thing.
You would be amazed at how much off load is possible. What you think is dynamic content is usually just a very simplistic dynamic wrapper over large swaths of static content. A seemingly dynamic html is really just a collection of static html blobs that can be held by a cache or CDN close to the consumer and assumbled as a complete html document on the fly by an web aware accelerator.
These 30,000 boxes that are spoken of are most likely composed of a large verity of purpose specific hardware. Where the purposes are much more diverse than a simple php / mysql combo's. Lets face it. Face book is across the planet and is relatively speedy all across the planet. This implies that a distributed CDN is in place. With local content caching nearest the consumer. Instantly this means we have more purposes than just php/mysql for the hardware. Authentication is usually offloaded by large scale web shops for a host of reasons. So lets add that kit to the list of purpose built. I could go on and on about the various purposes.
So it's fairly obvious that the statement we could shut off 22K+ worth of machines by simply ( nothing simple about this ) changing languages is just non-sense.
Plane and simple a large scale web environment is only partially the application hosting equipment. A very large part of the environment is the infrastructure, network, CDN, Caches, accelerators, security, .... equipment. Yes I can write a little fancy web app and run it on my netbook and wow people. It's a whole other matter to scale that up to 10's of millions of concurrent users spread across the planet.
Lets face it. That amount of equipment consumes one hell of a power bill. I'm positive that "Facebook" has already done an enormous amount of work to reduce that bill. Not for save the planet reasons but for simple dollar reasons. Can they do more. Absolutely. But it won't be a simple we'll just change everything over to this new language this weekend and then hit a bunch of power switches. The amount of power consumed by the massive development work force to write test document deploy this new wonder solution would probably leave "Facebook" in an energy debt for another several years.
PS. Good luck with that sales pitch if you ever make it near the office doors of facebook. :)
The reason we are often called IT people is simply a result of how badly IT people abuse IT titles, definitions and words.
I'm an IT guy. How are non-IT people suppose to keep up with the vernacular if we keep on insisting to invent new words and meanings for existing words every six months. IT as an industry is very well known for BUZZ word bingo. We are called the IT guy/gal simply because that's the only phrase that is general enough to be understood.
I'm very senior in my field. However I refuse to give myself a title that pumps my ego. I simply go by the title Senior Consultant. Why? Simple because everyone who has a buzz word bingo multi-word title is typically full of BS. Thus tainting the title and the meaning of the associated titles. I have colleagues in my company that are almost militant about making sure their title has all the most leading edge buzz words.
It's our own bloody fault we get called "IT Guy". Once real professional standards are applied Universally in the industry we will start to see real titles stick.
My advice is don't sweat it. If you wanna put them in their place simple ask them to get you a coffee and a sandwich while you fix their trivial problem. :)
Yah but mono ain't C# at the end of the day is it.
It will always be that bastard language child that sorta looks like it's dad. Sometimes it wants to do it's own thing and express it's own individuality sometimes it wants to be just like dad. In the end it's not dad.
And cool apps just don't cut it at the Enterprise level. For id skimming iPhone apps sure but not big boy stuff.
And really do we want to have a copy of something that is associated with the most hacked OS on the planet? No! I want something in my data center that is fast cheap to build and requires little attention. Windoz anything requires 24/7 hotline loven. I really don't want something that quacks like a duck walks like a duck but it's a turkey.
Hell I'll take perl, ruby, python and php before a C# or it's bastard children.
But that's just my opinion. :)
C++ did not have a string class when it first came out. Thus the landscape of C++ code was polluted for ever more with dodgy string classes.
Note I used "didn't" in my statement.
I've been around for a long time.
C great language did exactly what it was designed to do. But carries a lot of burden.
C++ come on it didn't even have a string class. Thus pointer math hell.
C#, Ok it learned a lesson and found the joy of a string class. But really it's a windows only lang.
Java. Excuse me web apps that take 8Gig of ram spread across a farm of servers. This slow elephant remade the hardware business.
All of the above never really understood concurrent / multithread / parallel. ( Sorry Java devs still have issues with the concept. GC & log4j come to mind as things that forgot they were in a threaded env. )
So the "Go" lang it just might deserve a look. Clearly web centric. Clearly built for tons of concurrent comms. Recompiles in a blip thus useful for real time compiling alla jsp. I'm very performance centric. If I can replace my J2EE bloat ware with a trunk full of tiny Go apps I will.
I'm definitely watching this space for developments.
I have a phrase I use.
"You can never out smart an idiot!"
You think you have ever angle covered. You are proud of how tight the whole design is. Then along comes some moron and BOOOMMMMM. They defeat your planning in 1 second.
Happens all the time.
I've had a lot of managers in companies look at me when I say that. First off the idiots get very offended. The smart ones get it. The phrase acts like pre-filter before any work is actually done.
As a result over the years I have learned that design and implementation has to have certain attributes.
- flexibility. We will have to come back and alter/fix something.
- redundancy. Their has to be more than 1 method of doing something. In your case a window and a fan as my backup second option.
- slack. Things never fit exactly into the specifications. Whether it be a measurement of distance. A power consumption claim. or a throughput estimate. Always add more during the build. It's cheaper.
It's the arrogant that think it works out of the box first time.
I have to agree. Eclipse has become an un-usable mess.
I actually went back to a decent text editor. When I went back into the repository I found I wrote more code with the text editor than I did with Ecilpse by shear line count. I also had less bugs. This I completely did not expect at all. I also billed less time to "life cycle" AKA bug fixes. I guess looking back at it now I can attribute it to having less distractions and being required to actually research the interfaces I was using.
Now I definitely want to get a decent IDE. I believe it would make my code better. But Eclipse is not it.
Seriously how the hell does an editor/ide require over 1Gig of ram to run efficiently. That's just crazy. Can't even run it on a 32bit machine.
Maybe I'll take a look at NetBeans again.
So I read the thing.
The process concentrates sea water to brine by an evaporation method. So why waste this low grade stream it is still has high in moisture content. There is already a condenser in this system. I'm thinking this can somehow boost output of clean water.
GAH!
I can't take it.
"The Phone is the network" What the heck does this mean. That's like saying "The medium is the message", "The ego is the soul" or some other rubbish like that. All I see is a some dude that is getting too old to hang out with college kids but is still doing it by pretending to be some great thinker type. Always sitting at the most exposed spot in the coffee shop legs cross pretending to read something that will impress a 19 year old book worm.
---
Secondly there is no Android network restriction! Just get on the net and order say a HTC Hero. Put your sim and you're away. Hell I live in Aus. I ordered an andriod phone in from over seas. Dropped my sim in and bam I'm gold.
iPhone is all about vendor lock in. Lock in is a gold mine for any company. Apple knows this. AT&T paid or rather gives huge portions of profit because of the iPhone lock in draw. Competition only occurs when the players are forced or force each other to play on the same field.
2010 will see a lot of changes on this front. I'm guessing the lock in will be gone for the iPhone. Pre, Andriod, even winMo 6.5/7.0 are eating in on the market.
---
Besides Apple has already decided the market needs another kick in the nuts. With the new APPLE tablet like thing. It's mostly phone but a little more net app machine. I recon they will call it "iMe" nothing more selfish then selfish^2.
---
But good god please stop the use of "_____ is the _____" references. You sound like a twat.