"both of which change constantly. As these change, perfectly good code becomes obsolete, begins to conflict with newer versions of the OS, browser, system DLLs, and so forth."
My VB6 apps developed on NT 4 are still working just fine on Windows XP. My.Net apps are working just as expected on 2K and XP (98 machines can be a bit iffy). So yes, things do change, but as long as there is a.Net Framework for your OS and the development version, you're all good.
Well, I think the orginal poster was saying that the.NET runtime is not very backward compatible. For instance, one can take a Java app that was written in 96 on JDK 1.1 and run it on 1.1, 2.0, 3.0, 4.0, and now 5.0 without issues. There was a major change in the event model between JDK 1.0.2 and JDK 1.1, and that frustrated many people. To my knowlege, there has not been a major change breaking backwards compatibility since. The APIs have changed but with the old signatures in tact with deprecation warnings.
Personally, I raved about.NET when it first came out because I loved how the ASP.NET code-behind pages made developing web apps almost like developing traditional apps. However, I have heard from multiple people that 1.1 broke many things in 1.0 so that your code had to be rewritten. I heard this again between 1.1 and 2.0. I still like many things about.NET. But as I start to consider writting a new app, I cannot help but wonder how many more times they'll break it backwards compatibility. In a large project, it would be very frustrating to go back and update working code every release. That is time consuming. Depricated APIs are ok because they still work and let you go back and change them when you get time.
I have to disagree. I have Microsoft's business practices more than anyone; but in this case, they are just restricting it from other OSes. That is not the same as bundling it and making sure that it cannot be unbundled. IE and Media player cannot be uninstalled. VFP can.
ICQ, Yahoo, AIM, and Odigo all have applet versions. Although they do run on the client, they are contained within the browser. Perhaps they will be able to be started via Java WebStart in the future. That is still started from the server. In any case, the only IM that didn't have a server based contact list was ICQ and now they have finally adopted it with the introduction of their applet.
I can already run them on Windows. In fact, I can run them on windows with IBM's or Sun's Virtual Machine. Should I want it to run on.NET, I would have to rewrite all the code to use.NET APIs instead of Java APIs. Since I have two years invested in our current project, that is a lot of rewritting that I cannot afford. Plus, I would lose the WORA app that we currently have.
FYI: JUMP is only for the Java language and not the API. Furthermore, it's only for Java syntax up to 1.1.4 (Microsoft's final release of Java from 1996?)
I don't mean that C# isn't cross platform because it isn't WORA. I mean that it is not WORA and it is also not cross platform. It probably read that I was talking about C# but I actually mean.NET in this case. I should have written more clearly. Yes, you can probably compile many command line C# apps on UNIX. But as soon as you get into network, GUI, data structures APIs, etc it will not compile. You would have to use a toolkit such as QT or GTK for the GUI. You would then have to make UNIX calls using socket.h for networking. With all this, yes you could get a C# app to compile and run. So, it's a cross platform language like C++. But it takes C# out of the scope of.NET. So,.NET is not cross platform.
As for Java's WORA, I've had no issues.
As for Java's lack of non-blocking I/O up until 1.4, that sucked.
The thing that makes Java WORA is the fact that the API goes with the language and the runtime enviroment. C# will be providing two of the three, the Runtime and the language. But seriously, how many C# apps will run on FreeBSD without that API?
I am working with Swing in a database app for a manufacturing company. In an instance where we have many items to select from we use the load on demand approach. For this particular case, we made our on Java Bean that consists of a JTextField and a very small button with the caption of "?" in red just to the right of it. So, if a user doesn't know the part number off the top of their head, they click the "?" next to the TextField. Then and only then does the application poll the database for the whole list which is then displayed in a new modal frame. This design results in the initial frame loading quicker up front because it's not waiting to for a combobox to load up all it's values first. It also makes for a more efficient use of memory.
Borland JBuilder does this as well. The first time you go to help it takes a little longer because they wait until it's needed to create the object. The designer is coded the same way. Again, the result is more efficient use of memory and the distribution of work so that everything doesn't have to be loaded at the same time when the application first launches.
In the old days of AWT in 1996, Java did limit you to the lowest common denominator. Swing fixed that by making a standard GUI API for the Java Platform. So, if Mac didn't have the concept of a combo box, it suddenly could if the app were programed in Java. This did however have a speed penality. AWT was a wrapper for local GUI API calls. Swing is not using native calls; but rather, implements it's on controls.
I have just downloaded Mozilla for the first time in a long time. I like it much better than IE. I went to 98lite and noticed that the final version for ME was released. The 2000lite will come soon. Until then, I guess I'll have to waste my disk space. Mozilla is much nicer than people let on.
I have about 30 people on my yahoo contact list. Almost everyone I know switched to it after trying it. It's small, notifies you of updates, has voice chat and dialpad like functionality built in, has yahoo supported clients for almost all systems, has an applet client should you want to use it on someoneElse's computer without installing it, and is really really small.
I bought the game along with a few others in hopes that I would have time to play them. Then I graduated college and got married. I have so many other things going on that all I find time for anymore is a game of tetris here and there. Everything is just as I bought it except the shrink wrap. If you want it for $25USD + shipping, shoot me an e-mail.
That is why I find Jedi Knight to be the best FPS
on
Europe's Version of E3
·
· Score: 1
The story/music is more important than the graphics. The engine for this games sucks but it's still my favorate.
Go to dice.com and search for programming jobs in the advanced search with the field of telecommute. It tured up printer driver, sound driver, and many other jobs you'd probably like.
Slashdot Mirror
"both of which change constantly. As these change, perfectly good code becomes obsolete, begins to conflict with newer versions of the OS, browser, system DLLs, and so forth."
.Net apps are working just as expected on 2K and XP (98 machines can be a bit iffy). So yes, things do change, but as long as there is a .Net Framework for your OS and the development version, you're all good.
.NET runtime is not very backward compatible. For instance, one can take a Java app that was written in 96 on JDK 1.1 and run it on 1.1, 2.0, 3.0, 4.0, and now 5.0 without issues. There was a major change in the event model between JDK 1.0.2 and JDK 1.1, and that frustrated many people. To my knowlege, there has not been a major change breaking backwards compatibility since. The APIs have changed but with the old signatures in tact with deprecation warnings.
.NET when it first came out because I loved how the ASP.NET code-behind pages made developing web apps almost like developing traditional apps. However, I have heard from multiple people that 1.1 broke many things in 1.0 so that your code had to be rewritten. I heard this again between 1.1 and 2.0. I still like many things about .NET. But as I start to consider writting a new app, I cannot help but wonder how many more times they'll break it backwards compatibility. In a large project, it would be very frustrating to go back and update working code every release. That is time consuming. Depricated APIs are ok because they still work and let you go back and change them when you get time.
My VB6 apps developed on NT 4 are still working just fine on Windows XP. My
Well, I think the orginal poster was saying that the
Personally, I raved about
I have to disagree. I have Microsoft's business practices more than anyone; but in this case, they are just restricting it from other OSes. That is not the same as bundling it and making sure that it cannot be unbundled. IE and Media player cannot be uninstalled. VFP can.
ICQ, Yahoo, AIM, and Odigo all have applet versions. Although they do run on the client, they are contained within the browser. Perhaps they will be able to be started via Java WebStart in the future. That is still started from the server. In any case, the only IM that didn't have a server based contact list was ICQ and now they have finally adopted it with the introduction of their applet.
I can already run them on Windows. In fact, I can run them on windows with IBM's or Sun's Virtual Machine. Should I want it to run on .NET, I would have to rewrite all the code to use .NET APIs instead of Java APIs. Since I have two years invested in our current project, that is a lot of rewritting that I cannot afford. Plus, I would lose the WORA app that we currently have.
FYI: JUMP is only for the Java language and not the API. Furthermore, it's only for Java syntax up to 1.1.4 (Microsoft's final release of Java from 1996?)
Sun's JVM does beat IBM's on Win32
-----
IBM, HP, SGI, Apple, Blackdown, etc have all made Java compatable JDKs. Did sun fuss? No. Why, because they are not as big as Microsoft? No.
Because EVERY company other than Microsoft followed the spec.
-----
I don't mean that C# isn't cross platform because it isn't WORA. I mean that it is not WORA and it is also not cross platform. It probably read that I was talking about C# but I actually mean .NET in this case. I should have written more clearly. Yes, you can probably compile many command line C# apps on UNIX. But as soon as you get into network, GUI, data structures APIs, etc it will not compile. You would have to use a toolkit such as QT or GTK for the GUI. You would then have to make UNIX calls using socket.h for networking. With all this, yes you could get a C# app to compile and run. So, it's a cross platform language like C++. But it takes C# out of the scope of .NET. So, .NET is not cross platform.
As for Java's WORA, I've had no issues.
As for Java's lack of non-blocking I/O up until 1.4, that sucked.
-----
The thing that makes Java WORA is the fact that the API goes with the language and the runtime enviroment. C# will be providing two of the three, the Runtime and the language. But seriously, how many C# apps will run on FreeBSD without that API?
:-)
Answer: Hellow World
-----
I am working with Swing in a database app for a manufacturing company. In an instance where we have many items to select from we use the load on demand approach. For this particular case, we made our on Java Bean that consists of a JTextField and a very small button with the caption of "?" in red just to the right of it. So, if a user doesn't know the part number off the top of their head, they click the "?" next to the TextField. Then and only then does the application poll the database for the whole list which is then displayed in a new modal frame. This design results in the initial frame loading quicker up front because it's not waiting to for a combobox to load up all it's values first. It also makes for a more efficient use of memory.
Borland JBuilder does this as well. The first time you go to help it takes a little longer because they wait until it's needed to create the object. The designer is coded the same way. Again, the result is more efficient use of memory and the distribution of work so that everything doesn't have to be loaded at the same time when the application first launches.
-----
In the old days of AWT in 1996, Java did limit you to the lowest common denominator. Swing fixed that by making a standard GUI API for the Java Platform. So, if Mac didn't have the concept of a combo box, it suddenly could if the app were programed in Java. This did however have a speed penality. AWT was a wrapper for local GUI API calls. Swing is not using native calls; but rather, implements it's on controls.
-----
In the old days, the JDKs were released way out of sync. Today, JDK 1.3 is available for Windows, Solaris, and Linux. You can't keep looking to 1998.
-----
ICQ and AIM have this too now days... but yes, Yahoo had it back when they didn't.
-----
I cannot believe you forgot Yahoo. It is small, fast, stores your contact list on the server, has almost no ads, and has Linux and FreeBSD clients.
They are also on the IMunited committee.
http://messenger.yahoo.com
-----
Unfortunately, news articles are not as fun to read a second time.
We should start calling these things CornFlake posts. Read em again, for the first time.
Ada was beautiful. Generic types. OO design... Speed on par with C...
Compilers were too expensive at the time so everyone went C instead.
But those Oracle extenstions will work with Oracle running on any platform. ;)
I have just downloaded Mozilla for the first time in a long time. I like it much better than IE. I went to 98lite and noticed that the final version for ME was released. The 2000lite will come soon. Until then, I guess I'll have to waste my disk space. Mozilla is much nicer than people let on.
I have about 30 people on my yahoo contact list. Almost everyone I know switched to it after trying it. It's small, notifies you of updates, has voice chat and dialpad like functionality built in, has yahoo supported clients for almost all systems, has an applet client should you want to use it on someoneElse's computer without installing it, and is really really small.
I bought the game along with a few others in hopes that I would have time to play them. Then I graduated college and got married. I have so many other things going on that all I find time for anymore is a game of tetris here and there. Everything is just as I bought it except the shrink wrap. If you want it for $25USD + shipping, shoot me an e-mail.
The story/music is more important than the graphics. The engine for this games sucks but it's still my favorate.
Small, fast, efficient, stable, feature rich...
Ummm, WindowMaker
I like to call this technology NIS + NFS
I still think I'd better hurry and get a patent on hot grits before the trolls beat me to it!
Go to dice.com and search for programming jobs in the advanced search with the field of telecommute. It tured up printer driver, sound driver, and many other jobs you'd probably like.
Joseph
It's called Subspace and it rocks :)
It's especially cool if you get the starwars patch for ships/sounds.