4 ms·
As the lead developer on a global site, I can explain very succinctly: i18n adds complexity a lot of complexity to your code, and complexity in your code slows
by dasil003 16y ago
As the lead developer on a global site, I can explain very succinctly: i18n adds complexity a lot of complexity to your code, and complexity in your code slows you down.
If you are an early stage startup with a shaky business model and are still pivoting rapidly you just shot yourself in the foot by internationalizing. You know that quick feature you just hacked together in an afternoon? Now you need to design it first with localized text in mind, then have it translated, then run it through QA because you don't speak the language, finally deploy it where you have new caching and scalability aspects to consider. It's not far off to consider an order of magnitude slower, especially if your translators are across the pond and turnaround is now a 12-hour minimum.
Consider the startup that has users and is starting to gain some traction. Suppose your team is <10 and revenue is covering 50% of your costs, you feel like you are about to break out. If you decide to i18n to 7 European languages at that point what can you expect? Well, I don't think it's unreasonable to expect double your revenue, but you should also expect your costs to double as well, between all the translating work, multilingual support costs, increased code complexity, legal costs, and all the nitty gritty details that are going to bite you. Plus now you are slower, so you've just pushed yourself further from profitability.
If you are small, it's much cheaper to double your revenue in your local market rather than expanding. Once you get big and your code fits the business model, then suddenly i18n becomes much more of a fixed cost, and a smaller percentage of your overall cost as well.
- tomjen3 16y agoIf that is so big an issue, just keep it in english - you won't get as many users, but you would get more than you would if your service was only for Americans. And hey, England, Wales, Scotland and both Irelands do speak English natively.
- ryanwaggoner 16y agoNot to mention Canada, Australia, New Zealand, and a bunch of other countries where English is the de facto official language.
- dasil003 16y agoThat doesn't really address the original question though does it? In any case, you're still not out of the woods. Here are some examples of things we deal with as an international VOD site: * Multi-currency support (without Braintree helping us it would have been impossible at our volume, customers DON'T like currency conversion fees). * Non-language localization issues. * Local legal issues (we couldn't offer subscriptions in France due to their bass-ackwards public policy) * Global film rights issues * The fact that films are known by different titles in different countries, even if they are both English. * 24-hour user cycle, no good time for maintenance, have to think harder about when to schedule email communications/feature launches, etc. Not that that stuff is so terrible, but it does end up introducing a lot of work you haven't anticipated (eg. what happens to account credit when users move between countries), and you're still not really localized.
- skowmunk 16y agoGreat explanations, you have put the gist of the issue here in the most succint way while covering almost the entire breadth of the problem. I know I may get downvoted for posting just an agreement/appreciation. But sometimes, it just feels good to openly acknowledge good knowledge and logic. So be it.
- dasil003 16y agoIt also feels good to hear it from someone who can appreciate the issue, since internally all we hear is pressure from partners who are chomping at the bit for full i18n.
- skowmunk 16y agoHi, I was going over your past comments and it looks like we have very similar views (though, mine may be nowhere as extensive). Right from your views on whining about paying taxes, realities of globalization, the tendency to be blunt and directly address the facts underlying an issue instead of being politically correct or soft pedal it, your incisive comments, ability to grasp and have very logical opinions on very diverse topics - they are impressive. I also found your comments, while some were very tough, were also very fair, which I repect in a person. Can I a request a favor from you: Would you mind reviewing/critiquing my business idea/application for YC? I think I can be considered as an outsider to the tech industry and relatively new to the world of web startups, the perspectives of a person with as much experience in the technical/start up world as you can be very helpful. (not to mention your no bull but modest approach, as was apparent in your comments) If you are ok with it, can we discuss further on email? In which case, it would be perfectly fine with me if you want to communicate through an anonymous email id (I can understand, you don't know me) and I can give you information to establish my credentials through my linkedin profile or any other agreeable and credible method. It would be great if you can let me know either way, either as a reply to this 'comment' or to this email id: skowmunk at gmail. Thanks, Skomunk. (ps: Dunno if you would believe, but "Great explanations, you have put ...." and this were definitely not pre-planned or anything like that. It was after posting it that I started going through your past comments and a "why not try asking?" just stuck)
- auxbuss 16y agoI agree that managing multi language sites/apps adds a significant people cost. This is often woefully underestimated by the business. It's not the tech so much as the content. It's also hard to manage the content unless the development environment supports it. However, you can do yourself a huge favour by starting out using UTF8 across the board -- for Europe/US, in particular, and this sweeps up Arabic, Cyrillic, and a few others en route. Retro-fitting character encoding is laborious and, for the data, may not be viable (due to time, effort, and cost) if there is enough of it.