You *cannot* get a pointer to a reference type in. NET, but only in an extremely limited fashion. >- Pointers gives up Java’s easier and more Secure Coding >model so on Linux.NET packages shared objects in a DLL. In other words, it’s almost exactly equivalent to a. NET uses custom attributes, which “decorate” methods, classes, fields, and properties with metadata about how they are used.Ī Windows DLL (“dynamic link library”) is just a shared library, nothing more, nothing less. JavaBeans requires one to write all sorts of ugly adapter classes and other ancillary rubbish. Microsoft’s component model is quite a bit superior to JavaBeans. >- VB.Net didn’t copy the JavaBeans model so we still have >Dll’s to deal with esp. Java: Sun hits a home run, and is so thorough, that they run around the bases Twice! I’ve never seen anything this Half-A**ed. – They use the toString() method on a String! ( Remember, with Microsoft, if there’s no example code, it’s Broke.
– They show an example of USING an async threaded class, but, Not how to code one. – They teach database coding using Grid Controls, which will kill database performance, fine for single user desktop apps. Microsoft MCSD education is still a joke: – managed and unmanaged code, together again: is this Microsoft keeping the ability to write it’s own spyware? – No Checked Exceptions means Microsoft won’t be coding any… same old crash city. – Pointers gives up Java’s easier and more Secure Coding model – VB.Net didn’t copy the JavaBeans model so we still have Dll’s to deal with esp. Make things easy for incompetent programmers and give up Enterprise Quality.
Net’s got the typical Microsoft problem.
net was created to be good if not better than java (collect(ion last 30 years good idea and copying a lot of java idea is not so difficult), M$ just missed the fact that we want to run code across various devices (not always running M$ OS).Įxcept GUI problem (swt, swing, awt, others) Java is fully portable – sorry always the same complains…we have in prod a lot of NT services running in admin user space, as comparaison hpux virtual vault webserver has 56 levels of privileges, gaining access is difficult if not impossible, and we have it under control. – our plattform run in production with 4 proc and 16gb ram with 260Gb database (we call it a street, handling 10000 users, adding a/more street and youre done) -> scalability is under control in J2EE world, I still want to see a windows 2003 handling so much proc and not rebooting because of patchs…(windows is trying now to go in advance computing and farms market) – a bug/security problem in the CLR/CLI which is closed sourceĪll application/language have bugs, closing source may have more! security by obscurity is bad…. If anyone has a link to an article that actually proves the whole “Write once, run everywhere” mantra in a big way, not just some one-off app, I’d love to read it. I’ve been a Java developer since ’97, but every place I’ve worked at has always been just one platform that the apps would run on. All this paper is doing is saying you can go with an all Microsoft package, or go with all IBM.Īnother thing I would like to see is an article that details a company that developed everything in Java, made a switch from their first platform to a totally new one and all that “Write once, run everywhere” stuff they wrote, did exactly that. If you want to go with the J2EE platform, here’s offerings from IBM, Sun, BEA, etc. This is the kind of paper that needs to be written by some unbiased third party that will say…if you go with.
Then, throughout the whole piece it’s IBM Whebsphere runs on all these platforms, IBM provides you with servers, IBM has middleware software you can use, IBM has this, IBM has that. They make this whole argument throughout this piece saying if you go with. This is a pretty good brochure, but one thing bothers me about stuff like this.