Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 4 of 4
  1. #1
    New to the CF scene
    Join Date
    Jan 2011
    Posts
    2
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Question ProIV (w/Java) vs. C#

    Greetings,

    This seemed like the best forum in here for my question, but if the mods feel it would be better suited elsewhere please move it.

    Our company has been developing a new core app. We attempted to use a firm from India first that used C# and ASP to make a web-based program, but it didn't meet our needs in the end. We started over and went with C# on a desktop platform using .Net 4.0 and Silverlight with Visual Studio. We've been at that for 6 months... but the developer had promised that it would only take him 3 months to do this. Having lost confidence in him to get the job done, we're looking at new options.

    One is a developer using ProIV and Java as his preferred method, and he claims that he believes it would be quicker for him to start over in ProIV/Java than to have anyone finish the existing development in C#. I'm not very familiar with ProIV, but this seems like a pretty wild claim.

    I wanted to explore a few forums and see if people's general experience with ProIV with Java is that it is substantially faster to develop in than C#, or that C# is just that much slower than anything else.

    I appreciate your opinions!

  • #2
    Supreme Master coder! Old Pedant's Avatar
    Join Date
    Feb 2009
    Posts
    25,020
    Thanks
    75
    Thanked 4,323 Times in 4,289 Posts
    This is the JavaSCRIPT forum. About the only thing that Java and JavaScript have more in common than Java and C# are the first 4 letters of their names. Hopefully, a moderator will move this to the Java forum.
    An optimist sees the glass as half full.
    A pessimist sees the glass as half empty.
    A realist drinks it no matter how much there is.

  • Users who have thanked Old Pedant for this post:

    E_Bay (01-12-2011)

  • #3
    Rockstar Coder
    Join Date
    Jun 2002
    Location
    USA
    Posts
    9,074
    Thanks
    1
    Thanked 328 Times in 324 Posts
    Quote Originally Posted by E_Bay View Post
    One is a developer using ProIV and Java as his preferred method, and he claims that he believes it would be quicker for him to start over in ProIV/Java than to have anyone finish the existing development in C#. I'm not very familiar with ProIV, but this seems like a pretty wild claim.

    I wanted to explore a few forums and see if people's general experience with ProIV with Java is that it is substantially faster to develop in than C#, or that C# is just that much slower than anything else.
    It sounds like the language is not the problem, it sounds like the problem is your developers and/or your interactions with them. Why has it taken longer than the original timeline? Have you been featuring creeping the project or have the requirements stayed constant but the developer continues to miss milestones? Since your first app didn't meet your requirements, did you improve your project requirements before the second app?

    As for the developer that wants to start over, they might be prejudice against C# (since he is a Java developer) but it is also more than possible the C# code was written extremely poorly. Or they just don't want to bother learning someone else's code. What are their reasons for wanting to start over?

    The performance of C# is more or less no worse than Java but the language is only part of it, you can write horrifically poor performing code in any language. If the C# app is nearly done you might want to just find someone to finish it.

    Quote Originally Posted by Old Pedant View Post
    Hopefully, a moderator will move this to the Java forum.
    Yep, done.
    Last edited by oracleguy; 01-12-2011 at 07:34 PM.
    OracleGuy

  • Users who have thanked oracleguy for this post:

    E_Bay (01-12-2011)

  • #4
    New to the CF scene
    Join Date
    Jan 2011
    Posts
    2
    Thanks
    2
    Thanked 0 Times in 0 Posts
    I appreciate the shift to the correct forum. I didn't mean to use the JavaScript forum for that.

    As for the questions posed...

    Why did it take so long? I personally believe that this project should have been estimated to start at 6 months now that we've gotten this far into it. The developer, however, assured us that he could do this in 3 months with a high degree of certainty - a number that ended up doubled before we backed out, and likely need to be tripled or more to complete it.

    The first time we did this, the folks in India worked for 14 months before we pulled the plug - but we chalked that loooong duration up to them having extreme issues grasping what we wanted out of the program. We'd have to send screens back multiple times for what I felt were minor fixes. They had issues like I couldn't believe.

    For example - I once asked them to use hyperlinks to open network drive mapped documents for internal users instead of forcing them to run through hoops to open them. They said it wasn't possible, and even if they could it was a security issue. I tried very hard to explain that only users who had authenticated to the network and mapped the drives could possibly access these files, but they wouldn't buy it. In the end I created a simple href tag in HTML on a blank page and directed it to open a document. It worked flawlessly. They asked me to send them my code so they could see how I did that.

    So when this guy showed up and said "three months" we thought that maybe a competent programmer could manage that. Our requirements didn't change drasitcally during development (maybe adding a couple weeks), but he admitted to me at the end that there were a couple major functions that he simply had no idea how to make work until he had spent a lot of time on them. I do admit that they were tricky issues, and he got them working perfectly, but one took 6-8 weeks to complete; a number I don't think he planned for at all in the beginning.

    So he kept telling us "another 30 days and this will be ready to test" for three months running and on the fourth month he said the same thing we said "We can't believe that, and if we can't believe that, we can't work with you" That he kept his inability to do this within the timeframe he advised hidden and hoped to string us along as far as he could was really disappointing.

    As for the new developer, I think it's a combination of not wanting to learn the old code and not being as good with C# as he would need to be. He was bandying around this concept of getting it done faster his way and starting over before he ever saw a line of the old code.

    His reasons for starting over are simply that he believes he can get a basic, pared-down system with no real efficiency gains or enhancements up and running in less time than it would take anyone to finish the more complex system we have mostly done. We so badly want to be on a new platform that we can start building up again and stop starting over from square one that it sounds enticing.


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •