From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.9 required=5.0 tests=HTML_10_20,HTML_MESSAGE autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id EF5C8BBCA for ; Wed, 14 May 2008 07:04:19 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: At0BAGMPKkhKfS4ec2dsb2JhbACCNDePLgEMAwQECQ8FlHqGMQ X-IronPort-AV: E=Sophos;i="4.27,484,1204498800"; d="scan'208";a="26145088" Received: from yw-out-2324.google.com ([74.125.46.30]) by mail4-smtp-sop.national.inria.fr with ESMTP; 14 May 2008 07:04:19 +0200 Received: by yw-out-2324.google.com with SMTP id 5so1922136ywb.3 for ; Tue, 13 May 2008 22:04:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; bh=2wCjOtJZiaM9aPorN5jB+5XCMRGCODUQA68djiyvvj0=; b=GBQ/adt/oFSXbedwMCvqva9h1xyHr2irYwT+2zVpaEyqRSbiu3IXGtjxcKKAPIEfV1OUR+WnbijnC1jOUCYye+9F5vK37TeIKu+XFLMwPmDPxxZW+xR7u10Z5d2ROVIavnGHnv8H0scI0Gi10jF2+ML3E2QOE8J36DY3QZ5xGgU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=vfLU03Qc92hk0M+PdlGL0w2hQi7KOKaEJcUzKNCsyltEhV43Xa6E/hn5fYBWpqvjZPvsCvbffDxD1e4yeH/FjTPauiqezcU0PKtGftF5+hS2gklB3YIfdNwZYWw2WKAk81DyjYEz/HxJrEdxaDOSA6sf+SdpBqIBNKCajTCj5aI= Received: by 10.150.54.1 with SMTP id c1mr653372yba.62.1210741458030; Tue, 13 May 2008 22:04:18 -0700 (PDT) Received: by 10.150.52.20 with HTTP; Tue, 13 May 2008 22:04:17 -0700 (PDT) Message-ID: <2a1a1a0c0805132204m33659840k1f84eb59f93bd3e4@mail.gmail.com> Date: Wed, 14 May 2008 01:04:17 -0400 From: "Mike Lin" Sender: nilekim@gmail.com To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Re: Why OCaml sucks [unicode] MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8564_28587329.1210741458015" X-Google-Sender-Auth: 0f609050efdf2014 X-Spam: no; 0.00; mikelin:01 ocaml:01 runtime:01 bindings:01 bindings:01 caml-list:01 philosophy:02 philosophy:02 string:02 string:02 programming:03 programming:03 library:03 library:03 gui:03 ------=_Part_8564_28587329.1210741458015 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Re: unicode support, anyone else who was around programming Win32 5-10 years ago (before .NET) might join me in offering a wary word of caution: the otherwise-disarming "let's just support both in one runtime" philosophy can be taken too far. In the nightmare scenario (which was reality until Windows 9x finally died an overdue death) you end up with two versions of every library function that takes a string. (This when we now have like 3 contenders for a standard library and n GUI toolkit bindings!) I'll take a couple days to try to reason out more specifically about how that got so out of control, but I just want to note that there is a precedent for trying to have a sympatric speciation between ASCII and unicode software and, while it was necessary for historical reasons, it was pretty godawful to deal with! Bitter and traumatized, Mike ------=_Part_8564_28587329.1210741458015 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Re: unicode support, anyone else who was around programming Win32 5-10 years ago (before .NET) might join me in offering a wary word of caution: the otherwise-disarming "let's just support both in one runtime" philosophy can be taken too far. In the nightmare scenario (which was reality until Windows 9x finally died an overdue death) you end up with two versions of every library function that takes a string. (This when we now have like 3 contenders for a standard library and n GUI toolkit bindings!)

I'll take a couple days to try to reason out more specifically about how that got so out of control, but I just want to note that there is a precedent for trying to have a sympatric speciation between ASCII and unicode software and, while it was necessary for historical reasons, it was pretty godawful to deal with!

Bitter and traumatized,
Mike

------=_Part_8564_28587329.1210741458015--