It is a sad fact that many sites that promote JAVA are written in PHP:
www.JavaWorld.com
www.eclipse.org
www.netbeans.org
www.myeclipse.com
Does this make PHP better, I think not, but it does show that JAVA is a pain to put something up and it is easier, faster and robust enough to program it in PHP.
I compared my 2006 F250 Crew Cab Long Bed with a 5.4L Gas engine to the Tesla Motors Tesla Roadster Electric car ( http://www.teslamotors.com/ ). I wanted to see what was the breakeven point for the Tesla (how many miles I had to drive before the Tesla would make sense).
In my estimates, I am not counting Insurance, Maintenance, Taxes or Cost of Financing.
I am also making the assumption, that I will never go to Home Depot, haul something or plan anything with my family. Nor will I consider the coolness factor. I am also not assuming that my range is less than 200 miles each day.
I am also assuming that both vehicles will last forever.
So here it goes:
My truck cost me about $32,500 and gets about 13.8 MPG using cheap regular gas.
I posted this when Tesla was a mere $100K. Oh yes, I know the truck is a different class of vehicle. Just want to put things in perspective.
The Tesla Roadster cost $100,000 and gets about 50 miles on a buck.
I am assuming that Gas prices are $4.00 per gallon and the mileage on both vehicles are the same rate (i.e. average cost of City/Highway).
The Answer:
I would have to drive 250,000 miles before the cost benefit of owning the Tesla Roadster.
At $3.00 per gallon, I would have to drive my truck 350,000 miles before I broke even.
I don't know what gas prices will be in the future. I was told in the 70's we would soon run out of oil and gas prices would be $5.00 per gallon in 70's money. In the 80's and 90's gas was cheap and we forgot the 70's. Last year we thought gas prices would never go south of $3.00 again.
I know my truck will get at least 250,000 miles on it, I just don't know what the Tesla will get, it is an unproven vehicle since there is none on the road with over 40,000 on it.
Geekoid, I see your point and that is if I had a $70,000 sport car, then I can see it being cost efective. But I just wanted to compare it to what I have now.
Sure the car is a babe magnet, but I use the truck all the time and my wife prefers to use it on trips since it has soo much room in the cab.
What I am basically saying, is too drive my truck in a 50 mile commute every day, it would not be cost effective to use one of these $100,000 car, no matter how you do the math
I compared my 2006 F250 Crew Cab Long Bed with a 5.4L Gas engine to the Tesla Motors Tesla Roadster Electric car ( http://www.teslamotors.com/ ). I wanted to see what was the breakeven point for the Tesla (how many miles I had to drive before the Tesla would make sense).
In my estimates, I am not counting Insurance, Maintenance, Taxes or Cost of Financing. I am also making the assumption, that I will never go to Home Depot, haul something or plan anything with my family.
I am also assuming that both vehicles will last forever.
My truck cost me about $32,500 and gets about 13.8 MPG.
The Tesla Roadster cost $100,000 and gets about 50 miles on a buck.
I am assuming that Gas prices are $4.00 per gallon and the mileage on both vehicles are the same rate (i.e. average cost of City/Highway).
The Answer:
I would have to drive 250,000 miles before the cost benefit of owning the Tesla Roadster.
Now the I must admit that the Tesla Roadster is more of a babe magnet than my F250, but I will not factor in the cost of a divorce from my wife.
MacworldExpo.com is hosted on several Windows 2003
on
The Odds at Macworld
·
· Score: 2, Funny
Just wanted to throw that into the mix. Useless info, with humor
The real question is why do I have to do the coversion? The conversion basically is the number of miliseconds from Jan. 1, 1970 and then convert it over. Is there something that I am missing?
Would the code be different for every application that uses a preparedStatement? I think not. So the question still remains, Why?
If it was truely OOP it should be transparent to me.
First if you are a web developer JAVA has no concept of a disconnected record set. So you have to write your connection code and closing code each time you want info from the database.
Second Java has scores of Model View Controllers too many to think of. It is interesting that none has been ported to.NET. There is a reason..NET doesn't need one and Java doesn't have one.
Thirdly.NET has many debugging and profiling features that Java developers can only dream of.
Fourthly, Java has been around for many years now, there is still no single accepted Connection Pool. Honestly Java developers how many of you spent days if not weeks trying to debug someone's connection pool or write your own. My next question is why do you need to do that.
.NET controls are the same for Windows.NET as they are for ASP.NET. Sure there are differences, but it is not like going from the web to Swing in Java. You might as well go from a Horse and Buggy to a Diesal Train (let you figure it out).
The.NET controls are extremely powerful and something just not found in Java (JSF -- is too much code compared to.NET).
The C# language is much better, you can have switch case statements with complex data types like String. And hundreds of other enhancements.
The Java language sometimes is a mess. For example using a date as an argument in a prepared statement, you must convert the date to java.sql.date from java.util.date, why, because the Java Gods were just too lazy to do it internallly.
C# has richer collections such as DataTables, DataSets.
Also, one thing I have notice is that there are plenty of starter / training applications for.NET out there that does not rely on a product other than the out of the box.NET. Java has its Pet Store and that is about it, and it is mostly regarded as how not to write a Java program.
EJBs, is 1.0 compatible with 1.1, or 2.0 or 3.0. For you non Java developers the answer is no. Why do Java developers require a lot of time to modify their code from one JDK to another or from one server to another?
Java has a rich history of different "Best Practices". From Applet only to Servelet only, to JSP, to Bean only, to EJB to now POJO (Plain Old Java Objects) which you have to download a 18 MB file implement.
In Java you must write all of you Javascript for your web pages, while in.NET the server does the vast majority for you. In.NET the server looks at the client browser and sends the appropriate JavaScript. Infact, I can say that when I did.NET my JavaScript ability was severly degraded because of it.
I can literally go on for hours. Sure when you look at the language, there is not much difference, but the devil is in the details..NET has a far richer development framework, that only Sun can dream of. Sun has the problem of either rewriting everything or patching what is obviously a dated language and framework.
Microsoft has done an outstanding job, ASP.NET 1.0 to 2.0 is an incredible leap that the likes of Java has no real comparison. And yes ASP.NET 1.0 runs on an ASP.NET 2.0 IIS box.
I am a JAVA developer and a.NET developer, Currently I am doing Java (in fact I am the only.NET developer in my shop) and each day, I ask the same question, why is is so much of a pain to do a simple thing in Java? Followed by my next question, Why to do anything in Java, do you need to download and implement stuff like STRUTS, SpringFramework etc.?
My final comment, is this, if the only thing that matters is time to market then.NET is the way to go. If the only thing that matters is cross platform than JAVA is the way to go.
The problem with the space shuttle can be summed up in two questions:
1. How much does the shuttle weighs empty ($10,000 per pound to get into space)?
2. Which is more important, get things up into space, or get things from space and bring it to earth?
The first question reveals the hidden cost of the shuttle and the poor design.
The second question goes with the first in that if the purpose is to put things into space than disposable is the way to go. More weight the spacecraft weighs, the less you can put up there.
My questions about the new Moon Rocket are two fold:
1. If you need two rockets (One being larger than the Saturn V) just to bring four humans to the moon, what do you need to take the same size crew to Mars and land on Mars and then return?
2. Why don't Nasa use a ferry system? Store the Command Modulbe (Apollo Speak) on the Space Station and supply it with fuel and just send up replacement parts for the LEM (i.e. the part that was left on the moon) as well. Assemble them at the space station then take it to the Moon. The vehicle that brings the people to the station can be smaller and can be use to land back on earth? A lot more complicated, but a whole lot cheaper reusing these systems this way?
It is a sad fact that many sites that promote JAVA are written in PHP: www.JavaWorld.com www.eclipse.org www.netbeans.org www.myeclipse.com Does this make PHP better, I think not, but it does show that JAVA is a pain to put something up and it is easier, faster and robust enough to program it in PHP.
I compared my 2006 F250 Crew Cab Long Bed with a 5.4L Gas engine to the Tesla Motors Tesla Roadster Electric car ( http://www.teslamotors.com/ ). I wanted to see what was the breakeven point for the Tesla (how many miles I had to drive before the Tesla would make sense). In my estimates, I am not counting Insurance, Maintenance, Taxes or Cost of Financing. I am also making the assumption, that I will never go to Home Depot, haul something or plan anything with my family. Nor will I consider the coolness factor. I am also not assuming that my range is less than 200 miles each day. I am also assuming that both vehicles will last forever. So here it goes: My truck cost me about $32,500 and gets about 13.8 MPG using cheap regular gas. I posted this when Tesla was a mere $100K. Oh yes, I know the truck is a different class of vehicle. Just want to put things in perspective. The Tesla Roadster cost $100,000 and gets about 50 miles on a buck. I am assuming that Gas prices are $4.00 per gallon and the mileage on both vehicles are the same rate (i.e. average cost of City/Highway). The Answer: I would have to drive 250,000 miles before the cost benefit of owning the Tesla Roadster. At $3.00 per gallon, I would have to drive my truck 350,000 miles before I broke even.
I don't know what gas prices will be in the future. I was told in the 70's we would soon run out of oil and gas prices would be $5.00 per gallon in 70's money. In the 80's and 90's gas was cheap and we forgot the 70's. Last year we thought gas prices would never go south of $3.00 again.
I know my truck will get at least 250,000 miles on it, I just don't know what the Tesla will get, it is an unproven vehicle since there is none on the road with over 40,000 on it.
Geekoid, I see your point and that is if I had a $70,000 sport car, then I can see it being cost efective. But I just wanted to compare it to what I have now.
Sure the car is a babe magnet, but I use the truck all the time and my wife prefers to use it on trips since it has soo much room in the cab.
What I am basically saying, is too drive my truck in a 50 mile commute every day, it would not be cost effective to use one of these $100,000 car, no matter how you do the math
I compared my 2006 F250 Crew Cab Long Bed with a 5.4L Gas engine to the Tesla Motors Tesla Roadster Electric car ( http://www.teslamotors.com/ ). I wanted to see what was the breakeven point for the Tesla (how many miles I had to drive before the Tesla would make sense).
In my estimates, I am not counting Insurance, Maintenance, Taxes or Cost of Financing. I am also making the assumption, that I will never go to Home Depot, haul something or plan anything with my family.
I am also assuming that both vehicles will last forever.
My truck cost me about $32,500 and gets about 13.8 MPG.
The Tesla Roadster cost $100,000 and gets about 50 miles on a buck.
I am assuming that Gas prices are $4.00 per gallon and the mileage on both vehicles are the same rate (i.e. average cost of City/Highway).
The Answer:
I would have to drive 250,000 miles before the cost benefit of owning the Tesla Roadster.
Now the I must admit that the Tesla Roadster is more of a babe magnet than my F250, but I will not factor in the cost of a divorce from my wife.
Just wanted to throw that into the mix. Useless info, with humor
/ /macworldexpo.com
http://toolbar.netcraft.com/site_report?url=http:
The real question is why do I have to do the coversion? The conversion basically is the number of miliseconds from Jan. 1, 1970 and then convert it over. Is there something that I am missing?
Would the code be different for every application that uses a preparedStatement? I think not. So the question still remains, Why?
If it was truely OOP it should be transparent to me.
Let me give it a try from a web developer.
.NET. There is a reason. .NET doesn't need one and Java doesn't have one.
.NET has many debugging and profiling features that Java developers can only dream of.
.NET controls are the same for Windows.NET as they are for ASP.NET. Sure there are differences, but it is not like going from the web to Swing in Java. You might as well go from a Horse and Buggy to a Diesal Train (let you figure it out).
.NET controls are extremely powerful and something just not found in Java (JSF -- is too much code compared to .NET).
.NET out there that does not rely on a product other than the out of the box .NET. Java has its Pet Store and that is about it, and it is mostly regarded as how not to write a Java program.
.NET the server does the vast majority for you. In .NET the server looks at the client browser and sends the appropriate JavaScript. Infact, I can say that when I did .NET my JavaScript ability was severly degraded because of it.
.NET has a far richer development framework, that only Sun can dream of. Sun has the problem of either rewriting everything or patching what is obviously a dated language and framework.
.NET developer, Currently I am doing Java (in fact I am the only .NET developer in my shop) and each day, I ask the same question, why is is so much of a pain to do a simple thing in Java? Followed by my next question, Why to do anything in Java, do you need to download and implement stuff like STRUTS, SpringFramework etc.?
.NET is the way to go. If the only thing that matters is cross platform than JAVA is the way to go.
First if you are a web developer JAVA has no concept of a disconnected record set. So you have to write your connection code and closing code each time you want info from the database.
Second Java has scores of Model View Controllers too many to think of. It is interesting that none has been ported to
Thirdly
Fourthly, Java has been around for many years now, there is still no single accepted Connection Pool. Honestly Java developers how many of you spent days if not weeks trying to debug someone's connection pool or write your own. My next question is why do you need to do that.
The
The C# language is much better, you can have switch case statements with complex data types like String. And hundreds of other enhancements.
The Java language sometimes is a mess. For example using a date as an argument in a prepared statement, you must convert the date to java.sql.date from java.util.date, why, because the Java Gods were just too lazy to do it internallly.
C# has richer collections such as DataTables, DataSets.
Also, one thing I have notice is that there are plenty of starter / training applications for
EJBs, is 1.0 compatible with 1.1, or 2.0 or 3.0. For you non Java developers the answer is no. Why do Java developers require a lot of time to modify their code from one JDK to another or from one server to another?
Java has a rich history of different "Best Practices". From Applet only to Servelet only, to JSP, to Bean only, to EJB to now POJO (Plain Old Java Objects) which you have to download a 18 MB file implement.
In Java you must write all of you Javascript for your web pages, while in
I can literally go on for hours. Sure when you look at the language, there is not much difference, but the devil is in the details.
Microsoft has done an outstanding job, ASP.NET 1.0 to 2.0 is an incredible leap that the likes of Java has no real comparison. And yes ASP.NET 1.0 runs on an ASP.NET 2.0 IIS box.
I am a JAVA developer and a
My final comment, is this, if the only thing that matters is time to market then
The problem with the space shuttle can be summed up in two questions:
1. How much does the shuttle weighs empty ($10,000 per pound to get into space)?
2. Which is more important, get things up into space, or get things from space and bring it to earth?
The first question reveals the hidden cost of the shuttle and the poor design.
The second question goes with the first in that if the purpose is to put things into space than disposable is the way to go. More weight the spacecraft weighs, the less you can put up there.
My questions about the new Moon Rocket are two fold:
1. If you need two rockets (One being larger than the Saturn V) just to bring four humans to the moon, what do you need to take the same size crew to Mars and land on Mars and then return?
2. Why don't Nasa use a ferry system? Store the Command Modulbe (Apollo Speak) on the Space Station and supply it with fuel and just send up replacement parts for the LEM (i.e. the part that was left on the moon) as well. Assemble them at the space station then take it to the Moon. The vehicle that brings the people to the station can be smaller and can be use to land back on earth? A lot more complicated, but a whole lot cheaper reusing these systems this way?