So my college is writing a desktop app (usually my domain), and he doesn't want to do internationalisation because of time constraints. HARD CODED STRINGS EVERYWHERE!

Welcome to devRant! Ouch. That could come back to bite your colleague.

Thanks @Jumpshot44
Yeah, I'm working on him to see the error of his ways. I'm considering branching his code to fix it and then send him a pull request.

wow. there are tools to handle that these days. I haven't used them to know how good they are but you can use a shortcut key to do almost all the work for you. name it, add text, done.

I know @flag0. I tried convincing him, but he is adamant that it is not worth the effort for this project and that it does not have any value other than for translations. Ugh.

@phaestion reusability(theoretically) and easily edit all UI messages at one place. I bet he hard codes all the UI too.

Same deal here...working on a web app that's been alive for 5+ years, old school ASP.Net. International market opens up, "Sure we can localize it, should take less than a month"..."Wait, how do we localize it?"...FML

Exactly @flag0!

This is the worst case scenario @digital216. I'd rather do it right from the beginning than have a headache down the road.

@phaestion I even made a prototype app to show them how easy it would be to do the localization if we did it the right way first. They don't feel we have the time or manpower to do that...So you have the time to do it the wrong way? LOL

I mean, JavaFX makes it SUPER hard to do i18n. One properties file per language? Fuck this shit.

It is just the worst! Especially when those damn IDEs present the different translations in an easy to edit table. Ugh!