Java vs C#

Java and C# are pretty much similar, just keep in mind that Java supports cross-platform compatibility. You should be fine with either one.

.NET is also getting pretty decent cross platform support. With the exception of a few modules.
 
I tried writing a pong game back in the day, it worked, sort of. I think i still have a copy of Ralf browns interrupt list printed. My earliest was commodore 64 (only thing my parents could afford).
I wrote space invaders in C. Was the coolest game at the time.
I got everything working hundreds, then failed when it came to the sprites. I could not get those simple little ships to render properly. In a fit I deleted all my code and vowed to never do anything requiring graphics again. Big regrets for deleting the code and not keeping my calm.

To this day, I steer away from anything requiring graphics.
 
I wrote space invaders in C. Was the coolest game at the time.
I got everything working hundreds, then failed when it came to the sprites. I could not get those simple little ships to render properly. In a fit I deleted all my code and vowed to never do anything requiring graphics again. Big regrets for deleting the code and not keeping my calm.

To this day, I steer away from anything requiring graphics.

I'm seeing a trend here with the games. Mine was a Lunar Lander type game. I got it mostly working, but occasionally, the ship would fall through the "terrain" (i.e., sequential line segments) at the bottom. I've always been fascinated by graphics since - it's probably what eventually got me into doing maths. All my code from then is gone ... tapes stretched. :p
 
Is it true that Java is Cross Platform while C# is restricted to .Net? And if it is true will it not be safe to go with Java?
 
Is it true that Java is Cross Platform while C# is restricted to .Net? And if it is true will it not be safe to go with Java?

.NET has a cross platform implementation. Mono, also MS have opened a lot of the code for this very reason.
 
Is it true that Java is Cross Platform while C# is restricted to .Net? And if it is true will it not be safe to go with Java?

Linux supports Mono which is trying to replicate .NET, but it's not 100% perfect.
 
Linux supports Mono which is trying to replicate .NET, but it's not 100% perfect.

True, but Microsoft are now coding new technologies to aid in the use of crossplatform. i.e. vNext as an example which incorporates the new Roslyn compiler (as a service).
 
.NET has a cross platform implementation. Mono, also MS have opened a lot of the code for this very reason.

Mono isn't supported by Microsoft and it's not guaranteed to be compatible with .NET; it's a great product though and at least gives .NET some legs :)
 
Mono isn't supported by Microsoft and it's not guaranteed to be compatible with .NET; it's a great product though and at least gives .NET some legs :)

It becomes more compatible as time go's by. Like i said above, new MS tech is being designed with mono in mind.
 
Last edited:
Java for servers and Android. C# for Windows. Objective-c for OSX/iOS. It's ridiculous to ask which has a brighter future as they all have their place.

Objective-C has one foot in the grave. I wouldn't recommend anyone start on it at this point.
 
Is it true that Java is Cross Platform while C# is restricted to .Net? And if it is true will it not be safe to go with Java?

vNext will change things. Microsoft is really embracing open source these days and like I said, the future looks really bright for C#.

Of course there's nothing wrong with Java but I've coded in quite a couple of languages over the years and I really love what they've done with C#. Plus there's Visual Studio. I swear once you work in Visual Studio it's very difficult to make use of other IDEs again.

Either or. I don't think you can go wrong with picking either of these languages. Maybe try them both out?
 
Time flies :) Although, if I do the math more accurately, it would have been about 28-29 years for me. I started with Acorn Basic in 1983, and only got a PC in 1985-86 (where I used GW Basic and Pascal). I also messed about with Clipper and COBOL around the time, but most of their utility was lost on me at the time. I used some funky C and C++ compilers for a bit, but found Turbo Pascal a lot easier - it was also easier to integrate ASM into it (even before the asm blocks were supported) - I switched to Turbo C when it came out, and Turbo C++ a bit later. Coding was a lot of fun back then, although whenever I see old pics of me at my PC, I think to myself - How the hell did I manage to work on that monitor??? :p On the PC, I started with one of those green monitors, and on the Acorn, I used one of those tiny portable B/W TV's if you remember those.

Similar here. I started on mainframe with Fortran in Std8. Before PCs. Then onto Superbrain with 64K memory!!. Then PC & GW basic. Wrote my matric CompSci project in GW basic in '83. Had to interface to mainframe to get screendumps printed.... Then TPascal, Borland C++. Wrote a navigation system with BCPP. Then some realtime C&C++ on iRMX. Then Delphi. Still have some Delphi apps out there running for the last 25 years. Now C# all the way. Run C# on Win / Mobile & Linux
 
Similar here. I started on mainframe with Fortran in Std8. Before PCs. Then onto Superbrain with 64K memory!!. Then PC & GW basic. Wrote my matric CompSci project in GW basic in '83. Had to interface to mainframe to get screendumps printed.... Then TPascal, Borland C++. Wrote a navigation system with BCPP. Then some realtime C&C++ on iRMX. Then Delphi. Still have some Delphi apps out there running for the last 25 years. Now C# all the way. Run C# on Win / Mobile & Linux

What's your experiences with Lisp?
 
Time flies :) Although, if I do the math more accurately, it would have been about 28-29 years for me. I started with Acorn Basic in 1983, and only got a PC in 1985-86 (where I used GW Basic and Pascal). I also messed about with Clipper and COBOL around the time, but most of their utility was lost on me at the time. I used some funky C and C++ compilers for a bit, but found Turbo Pascal a lot easier - it was also easier to integrate ASM into it (even before the asm blocks were supported) - I switched to Turbo C when it came out, and Turbo C++ a bit later. Coding was a lot of fun back then, although whenever I see old pics of me at my PC, I think to myself - How the hell did I manage to work on that monitor??? :p On the PC, I started with one of those green monitors, and on the Acorn, I used one of those tiny portable B/W TV's if you remember those.

My first program that was of any use was a Clipper program which calculated audit risk and determined audit transaction testing sample sizes. I wrote import programs for every client that could export data frm their system. We had 2 desktops at work. One had a green screen. i bought my own laptop(weighed a ton) and used it on audit assignments. I reckon I shaved 2 days of the audit planning time compared to other seniors who did it the manual way.
It was at this point I decided that CA wasn't for me :)
 
Not the first choice for desktop applications, as far as server and embedded software goes this couldn't be farther from the truth.

Company I work for is currently running Oracle Forms on Oracle Application Server. Busy planning to drop Oracle Forms and are considering a choice between C# and Oracle ADF(which is basically Java. JDeveloper). Unfortunately they seem to be leaning towards ADF. I would prefer C#. We have more C# developers than we have Java developers. I suspect they are being swayed by the fact they won't need to change the Oracle Application Server infrastructure, which has already been upgraded.

Our Application servers run on Unix.

If Microsoft could support Unix they would get more folks over to C#
 
Last edited:
Mono isn't supported by Microsoft and it's not guaranteed to be compatible with .NET; it's a great product though and at least gives .NET some legs :)

http://xamarin.com/pr/xamarin-microsoft-partner

Whilst Xamarin today offers a viable alternative, it too is presented with somewhat of a dilemma as it's seamless Apple framework support is composed of wrappers around Objc frameworks; so whether they'll have success in achieving the same with swift is still currently debatable.
 
Last edited:
Objective-C has one foot in the grave. I wouldn't recommend anyone start on it at this point.
whilst Swift's performance results: faster than Objc, and occasionally better performance than C++, coupled with a newer popular syntax assures this. Today and for at least the next 2 to 3 years, Understanding Objc is really the only realistic way to effectively code in Apple's world.
 
Swift is better than both

As a very young language I'd say not yet; but it's down to metal performance results are very promising for it's future. Neither C# or Java currently have any chance to match or better Objc performance let alone C++ (re JIT); whereas Swift out of the box is doing just that.

http://www.jessesquires.com/apples-to-apples-part-two/
https://mikeash.com/pyblog/friday-qa-2014-07-04-secrets-of-swifts-speed.html

Swift's performance today is arguably being hindered by it need to for a solid Objc interop; but I'm fairly sure that will be addressed in roughly 2 to 3 years with pure swift frameworks (next year's WWDC should give a clearer picture if Apple's intentions)

Ps. you might also want to look at this: http://www.remobjects.com/elements/silver/
 
My first program that was of any use was a Clipper program which calculated audit risk and determined audit transaction testing sample sizes. I wrote import programs for every client that could export data frm their system. We had 2 desktops at work. One had a green screen. i bought my own laptop(weighed a ton) and used it on audit assignments. I reckon I shaved 2 days of the audit planning time compared to other seniors who did it the manual way.
It was at this point I decided that CA wasn't for me :)

Interesting transition story. BTW, do you remember these "portable" PCs: http://en.wikipedia.org/wiki/IBM_Portable_Personal_Computer (weight: 13.6kg - although the one I had (borrowed from my uncle since he was out of town) weighed a bit more because it had a double height and length 10MB HDD in it). Oh, and when I bought my first 20MB HDD a few years later, the seller told me that 20MB meant that the space was "basically infinite". :D
 
Top
Sign up to the MyBroadband newsletter
X