Slashdot Mirror

← Back to Stories (view on slashdot.org)

When Should We Ditch Our Platform?

Posted by kdawson on from the future-shock dept.

odoketa writes "My organization recently had to replace our Web developer. It took us an extremely long time to find someone with the necessary skill set. I don't know if this is because of the platform we are running (which I will leave nameless), or simply because the fates conspiring against us. It's easy to assume that languages or platforms are popular based on buzz, but the rubber hits the road when you have to hire someone to maintain that code. How are folks out there determining when you've backed the wrong horse, and getting back on track?"

5 of 622 comments (clear)

  1. Solution by TheSpoom · · Score: 5, Funny

    Stop using FORTRAN. It really wasn't built for the web, you know.

    --
    It's better to vote for what you want and not get it than to vote for what you don't want and get it.
    - E. Debs
    1. Re:Solution by lexarius · · Score: 5, Funny

      You'll change your mind after you see FORTRAN on Rails.

    2. Re:Solution by Anonymous Coward · · Score: 5, Funny

      FORTRAN runs in Ruts, not on Rails, don't forget.

  2. Which platform? by Anonymous Coward · · Score: 5, Funny

    How do you expect Slashdot readers to tell you whether to ditch your platform unless they know whether it is Microsoft or not?

  3. Immediately by z-j-y · · Score: 5, Funny

    And I recommend Ruby on Rails. Its developer community has been growing exponentially, from 5 guys in 2006 to 10 guys in 2007. If you are extra conservative, you can try Groovy on Rails. It's just like Java, but better.