Java - Programming Language

Quote:

---

Originally posted by techyspecy
Yeah right :D, I needed this suggestion.

---

*shrug* I'm not suggesting anything...I'm telling you...whatever you or your business is doing .. someone is doing something wrong. If you guys are updating everytime MS updates..something is wrong. Its like a little kid and a toy store..every time the toy store gets a new toy the kid's parents buy him that toy? When does that ever happen? Should that happen?

Come on .. dont tell me you're struggling because of MS technology.

Realistically speaking all businesses operate like this..NOT just MS. Think about it..do you think NIKE the makers of sports shoes / appareal is going to leave the same line of shoes for one year? Of course not..you buy a set of Michael Jordan nike bball shoes and guess what..2 weeks later there's a better nike shoe out there. Are you going to spend the money 2 weeks later after you already spent 100 bucks...probably NOT. Televisions..you buy a nice HDTV one week..and the next week you go back to your local best buy / circuit city and theyve got flat panel HDTV's for only 10k more. Do you buy that a week later? Again probably not. MS is the same way..they are in the software industry...they too need to make money...if they don't have software coming out how is the company going to make a return on investment or any profit if we're in 2003 and they still have windows 98.

Puhleaseeeeeeeeeeee

Jon

Quote:

---

Originally posted by jhermiz
*shrug* I'm not suggesting anything...I'm telling you...whatever you or your business is doing .. someone is doing something wrong. If you guys are updating everytime MS updates..something is wrong. Its like a little kid and a toy store..every time the toy store gets a new toy the kid's parents buy him that toy? When does that ever happen? Should that happen?

Come on .. dont tell me you're struggling because of MS technology.

Realistically speaking all businesses operate like this..NOT just MS. Think about it..do you think NIKE the makers of sports shoes / appareal is going to leave the same line of shoes for one year? Of course not..you buy a set of Michael Jordan nike bball shoes and guess what..2 weeks later there's a better nike shoe out there. Are you going to spend the money 2 weeks later after you already spent 100 bucks...probably NOT. Televisions..you buy a nice HDTV one week..and the next week you go back to your local best buy / circuit city and theyve got flat panel HDTV's for only 10k more. Do you buy that a week later? Again probably not. MS is the same way..they are in the software industry...they too need to make money...if they don't have software coming out how is the company going to make a return on investment or any profit if we're in 2003 and they still have windows 98.

Puhleaseeeeeeeeeeee

Jon

---

First of all I am not struggling, its the corporate companies. Secondly don;t tell me these things as if I am a little kid. I don;t know the work culture in US, but every where else ( and I mean it ) companies are struggling. For instance my company bought RPG 3 ( thats AS/400 version 3 ) in 1991 and they have just now upgraded to RPG 4 ( RPG ILE ) in 2003. All functions of RPG 3 are still supported in RPG 4 ( same goes for JAVA ). This kind of upgradation is fine and can be justified. Not like MS releases VB 6 in 98 and .NET in 2001. What the heck is that ..... . Now all programmers in the company are crying for .NET ( after all nobody want to be left behind in any way ), and management cannot justify such upgradation ... ( they are also right to some extent ) and the WAR is going on whether to choose JAVA path or MS path .... This is absolutely ridiculous. Furthurmore, you tell me how much of VB 6 is still supported in VB. NET ???? :confused: :mad:

Quote:

---

Originally posted by techyspecy
First of all I am not struggling, its the corporate companies. Secondly don;t tell me these things as if I am a little kid. I don;t know the work culture in US, but every where else ( and I mean it ) companies are struggling. For instance my company bought RPG 3 ( thats AS/400 version 3 ) in 1991 and they have just now upgraded to RPG 4 ( RPG ILE ) in 2003. All functions of RPG 3 are still supported in RPG 4 ( same goes for JAVA ). This kind of upgradation is fine and can be justified. Not like MS releases VB 6 in 98 and .NET in 2001. What the heck is that ..... . Now all programmers in the company are crying for .NET ( after all nobody want to be left behind in any way ), and management cannot justify such upgradation ... ( they are also right to some extent ) and the WAR is going on whether to choose JAVA path or MS path .... This is absolutely ridiculous. Furthurmore, you tell me how much of VB 6 is still supported in VB. NET ???? :confused: :mad:

---

I dont agree at all. Your business logic should not rely on the software so much. It should rely on the fact that you have a good mindset on how to perform the business using technology..whether it be Java, MS, Plain ol C etc etc. You can write business logic through Pascal for all I care. The point is to write the software in a flexible way so that changes dont impact the business. Your business should not be worried too much about .NET / VB6...if they are than like I have said something is wrong..they should have thought of this from the get go.

Either way these are our opinions so I respect yours although I dont agree with it.

Im done :)

Jon

Quote:

---

Originally posted by jhermiz
Im done :)

Jon

---

So Am I ....

Quote:

---

Originally posted by techyspecy
Not like MS releases VB 6 in 98 and .NET in 2001

---

You're looking too closely at things though.
Microsoft never pretended that VB.NET would use the same syntax or anything as VB6.

Its like when people went from leaded petrol to unleaded petrol.
Yes it was a bit change for engines at the time.
But it was just that one set of changes.
Every unleaded petrol engine since then works on the same basic ideas.


Most if not all Microsoft products are backwards compatible.
There are a few cases where, due to huge technology advances, they aren't backwards compatible.
For example Exchange 5.5 > Exchange 2000 etc.


But for the mostpart Microsoft do a good job of things...

Quote:

---

Originally posted by plenderj
You're looking too closely at things though.
Microsoft never pretended that VB.NET would use the same syntax or anything as VB6.

Its like when people went from leaded petrol to unleaded petrol.
Yes it was a bit change for engines at the time.
But it was just that one set of changes.
Every unleaded petrol engine since then works on the same basic ideas.


Most if not all Microsoft products are backwards compatible.
There are a few cases where, due to huge technology advances, they aren't backwards compatible.
For example Exchange 5.5 > Exchange 2000 etc.


But for the mostpart Microsoft do a good job of things...

---

I do not know what backward compatibility are you talking about ... but on my machine, i upgraded from MSXML 3 to MSXML 4 and my code did not work. I had to go back to MSXML 3. Backward compatibility is nothing but fun in MS products ...

And don;t compare petrol with this industry. This is probably the only difference between petrol pump emplyee's and us. And petrol does not change every 2 years.