News for hackers. Stuff that matters.
Re:2012: A Year in PHP by viraptor on Tuesday January 08, 2013 @08:12PM (#5029556)
> Particularly for early and reliable UTF8 support

What do you mean by that? It has a rather simple concept of strings and a very interesting set of mb_... functions as far as I remember. PHP strings are just bytes and are not even encoding-aware themselves.

Re:2012: A Year in PHP by contingencies on Tuesday January 08, 2013 @08:19PM (#5029581)
Back in the day, when Ruby was almost inoperable with UTF8, you could basically just run strings through PHP's normal functions and all would work well. So, code just worked. Even with MySQL, if you had utf8 tables. The only time you needed 'mb_' IIRC was for regex or unicode character based length checking.

In hindsight I think having this just work for a lot of people is where PHP trumped perl and ruby in a way.

Re:2012: A Year in PHP by viraptor on Tuesday January 08, 2013 @08:30PM (#5029614)
Hmm... I don't know what ruby and perl did, but "not barfing at 8bit characters" means something completely different for me than "unicode support". The second would know about various encodings, normalisation, sane comparisons, etc. Depends on your use case I guess.