319 karma · joined May 14, 2009
Counterpoint: You know and can use the code before you pay anything. If you decide to prefer a certain library over another, this decision is based on real-world experience with that library. This decision might imply that you pay for support later on -- where support sometimes means implementing requested features.
Anyway, you're right with respect to the lack of standard way. One thing I personally find most annoying is function naming. Some functions use the dot convention (do.this), some use camel case (doThis), some use underscores (do_this) etc. And what is most annyoing: this is even true for novel functions that were just introduced in recent releases.
If this is your understanding of philosophy, I'd say you're misusing philosophy for dealing with personal problems.
Done.
Question: W to F?
Answer: F the W(orld)!
Chorus: W the F! ... (repeat)
Hero: For the win!I'm going to tell that a colleague of mine who wants to quit his current job because everything he does is talking and negotiating (i.e. deciding or rather preparing decisions) without ever getting anything done.
> That said, "convert everything to your native Unicode format at the edges and reconvert it back out at the edges" is at least a tolerable answer.
It obviously isn't for the ruby developers. If it were so they had chosen utf8 as internal encoding, which they didn't because they didn't consider this a tolerable answer. Even though you can get ruby 1.9 to work this way, this approach could still cause some headache.
With respect to performance boost: Startup time didn't improve. And IIRC the same is true for certain string operations. Both are important in the field where ruby originated and where I personally still find it most useful -- scripting or rather as perl-replacement.