5 ms·
It also depends on what you need to do with the web. Perl is currently the best language for interacting with Unicode, for example. If you web needs include Uni
by pyre 15y ago
It also depends on what you need to do with the web. Perl is currently the best language for interacting with Unicode, for example. If you web needs include Unicode, you might have trouble with Ruby or Python, unless you're willing to accept half-ass, partial, or just plain wrong Unicode implementations.
- ashrust 15y agoI agree, I love Python but I've spent untold hours dealing with its unicode issues.
- codygman 15y agoEverything unencoded is unicode in 3 isn't it?
- lloeki 15y agoStrings are unicode. Bytes are encoded data. With Python 2 strings you have to be proactive about it and - always use u"" unless you know what you're doing - segregate non-unicode data to boundaries by decode()ing early and encode()ing late, or you're guaranteed to shoot yourself in the foot sooner or later but if you do it it's quite smooth sailing. Also, #/usr/bin/env python # -*- encoding: utf-8 -*- helps a lot. All that just brings you closer to Python 3 anyway and really helps when using 2to3.
- ashrust 15y agoAgreed, however I've run in to compatibility issues with 3 a few times and so resolved to stick w/ 2, deal with the text parsing issues myself, keep the libraries I like and leave the ops team alone.
- petercooper 15y agoRuby's character encoding and Unicode support is pretty strong. I'm intrigued how you think it's half-ass, partial or just plain wrong (Really! If there's something really borked with it, it's in my interest to know :-)). Every string has full encoding support and it's baked right in to the language.
- pyre 15y agotchrist's OSCON Unicode talks: http://98.245.80.27/tcpc/OSCON2011/index.html http://98.245.80.27/tcpc/OSCON2011/index.html Specifically the third talk: http://98.245.80.27/tcpc/OSCON2011/gbu.html http://98.245.80.27/tcpc/OSCON2011/gbu.html http://98.245.80.27/tcpc/OSCON2011/gbu.pdf http://98.245.80.27/tcpc/OSCON2011/gbu.pdf Excerpts: Its String functions like upcase or capitalize won’t even look at anything but ASCII. It’s completely missing a whole lot of critical Unicode functionality: casemapping & -folding grapheme support normalization collation text segmentation, &c &c &c. Every Ruby string carries around its encoding, instead of sanely unifying into Unicode internally like nearly everything else does. Also: > baked right in to the language is not synonymous with "intelligently implemented" Note that I wasn't implying that "half-ass," "partial," and "just plain wrong" necessarily all apply to Python and/or Ruby's implementations. Some may apply to some areas while others may not, and really this extends outside of just Python and Ruby, but I'm trying to stay in context here.
- petercooper 15y agoThis is interesting stuff - thanks for sharing, I'll be checking it out. The upcase/downcase stuff definitely checks out so far :-)
- minikomi 15y agoAs someone building websites using ruby & dealing with Japanese, I have to agree.. incompatible character encodings: UTF-8 and ASCII-8BIT gets pretty tiresome! Using 1.9.2 at least you have .force_encoding ... feels pretty wrong but sometimes it's just needed to get the job done..