> -----Original Message----- > From: Peter Lind [mailto:peter.e.lind@xxxxxxxxx] > Sent: Saturday, October 02, 2010 2:17 AM > To: Per Jessen > Cc: php-general@xxxxxxxxxxxxx > Subject: Re: Re: Friday's Post > > On 2 October 2010 11:05, Per Jessen <per@xxxxxxxxxxxx> wrote: > > Peter Lind wrote: > > > >> On 1 October 2010 20:21, Per Jessen <per@xxxxxxxxxxxx> wrote: > >>> Peter Lind wrote: > >>> > >>>> C# has by now exceeded Java by quite a bit - > >>> > >>> I've been away from the Java "scene" since 2002 (when I worked for > >>> BEA deploying J2EE on Linux/390), but assuming you're talking about > >>> "deployed lines of code" or some other real-life measurement, I find > >>> it hard to believe that C# should have exceeded Java. > >> > >> Language functionality. I'd much rather use C# than Java as I can do > >> more in C# and easier than with Java. For instance, C# 4 has " > >> support for late binding to dynamic types". Does Java have an > >> equivalent? Is it planned? > > > > I don't know, but Java obviously supports late binding. > > > > I was looking more for dynamic types, much more of interest to the average > PHP dev as that's one of the typical stumbling blocks when switching > languages. And no, far as I can tell Java doesn't offer that. > > Regards > Peter > > -- > <hype> > WWW: http://plphp.dk / http://plind.dk > LinkedIn: http://www.linkedin.com/in/plind > BeWelcome/Couchsurfing: Fake51 > Twitter: http://twitter.com/kafe15 > </hype> > I haven't done a lot of coding in Java & ASP.NET/Winform (specifically C#) yet. But from what I've seen and like so far is that ASP.NET supports unsigned primitive types (S/Byte, U/Int16, U/Int32, U/Int64) while Java doesn't - even though there are requests to have it implemented/supported back in late 1990s. Also, it's a shame that the same support doesn't carry to MS' SQL Server. It's a +1 for MySQL here! But then, if you intend to use MS' MVC in the future, it's only officially supported in v3.5+ (it's MS way of forcing people to upgrade). That being the case, it's no longer 'deploy anywhere' since Mono only supports up to v2, IIRC. PHP & Java has the major advantage of 'develop anywhere' & 'deploy anywhere'. Thus in the long run, you have lower TCO, IMO, due to the licensing for the OS and individual 'client access'... Anywhere = any OS that will support the JDK and/or PHP binaries. Regards, Tommy -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
