News for hackers. Stuff that matters.

A comment on Why We Chose Rails to Build Gitlab. Parent comment

Re:Why We Chose Rails to Build Gitlab by freehunter on Thursday January 24, 2019 @04:19PM (#18993064)
None of the people complaining are the developers (the developers like Java). They're all (enterprise) end users. The "modern" solution is something where the customers don't know it's Java, don't have to hear the words "tomcat" and don't bring to mind all the baggage associated with those names.

There's nothing wrong with Perl or PHP either, but plenty of end users have seriously negative associations with the technology and will blame every fault on the technology because it's had a rough history. All of those languages/ecosystems scream "dotcom" to enterprise users and they don't want to hear that they're paying $1.5m for a system that's built in what they consider to be legacy languages.

[ Parent | on HN ]
Re:Why We Chose Rails to Build Gitlab by purple_ducks on Friday January 25, 2019 @04:15AM (#18996646)
Were the companies you were working for agencies?

> that's built in what they consider to be legacy languages

Who's the software company in this situation - you or them or both?

What's the modern solution which they expect you to be on? Go?

What characteristics does it have?

A solution could just as easily be packaged for them in such a way that they just have to run "java -jar someuberjar.jar"

[ Parent | on HN ]