Post 9iKbVRRpMNstqU6vbs by wrenpile@mastodon.social
(DIR) More posts by wrenpile@mastodon.social
(DIR) Post #9iJT2CsfRoTRTeFnZQ by wrenpile@mastodon.social
2019-04-29T21:27:17Z
0 likes, 0 repeats
Not sure about public awareness, but the Wikipedia page says "UTF-8 was first officially presented at the USENIX conference in San Diego, from January 25 to 29, 1993."
(DIR) Post #9iJT2DPdTEqT7tg7xQ by xahlee@mstdn.io
2019-04-29T22:09:46Z
0 likes, 0 repeats
@wrenpile when is the first time you hear about utf8 monthly? i think that'd be a good estimate of public awareness.but, are you trying to say js could've been utf8?
(DIR) Post #9iJWh643zixG4Ym1p2 by wrenpile@mastodon.social
2019-04-29T22:50:46Z
0 likes, 0 repeats
@xahlee Sorry, I don't know what you mean by utf8 monthly.Sure, I think js *should* have chosen utf8.
(DIR) Post #9iJXkOCt69GRAA2Ea0 by xahlee@mstdn.io
2019-04-29T23:02:34Z
0 likes, 0 repeats
@wrenpile let me rephrase. do you remember the year when you hear utf8 often? like, almost every month?that's what i think a good estimate of when the general programer community is aware of utf8.as to whether js should've been utf8. My comment before was no. 1 reason is, js is to follow java steps due to marketing reasons. 2, utf8 didn't enter mainstream consciousness until about a decade later.Do you agree with either of these reasons?
(DIR) Post #9iJklCvRpH6Zrtb8pU by wrenpile@mastodon.social
2019-04-30T01:28:23Z
0 likes, 0 repeats
@xahlee Sorry, I can't remember when utf8 became a big part of my life.And I really have no idea whether the early JS team felt it was important to follow Java's practices where possible.I do remember that when I first encountered JS and Java, around the same time (I can't put a date on it now), I was struck by how ponderous Java was - I just didn't want to go near it if I could possibly avoid it.
(DIR) Post #9iJmCgnSyPFGHkX6e0 by xahlee@mstdn.io
2019-04-30T01:44:34Z
0 likes, 0 repeats
@wrenpile i see.about js following java due to marketing reasons, that i was pretty sure. Brendan designed and implemented js in 10 days. Design was based on Scheme lisp and Self lang. But Netscape just made a deal with Sun Micro to include Java, Sun was putting millions into marketing Java. Netscape wants a ride of that. So js syntax was to follow Java. I assume, so is its string.
(DIR) Post #9iJmOLdXTJtk8KRt32 by xahlee@mstdn.io
2019-04-30T01:46:40Z
0 likes, 0 repeats
@wrenpile we are discussing whether js string could've been utf8 instead of utf16.So, in my opinion, it could not have been utf8, due to the 2 reasons: marketing force, and utf8 was really not ready yet.(note, when something is invented, conception date, prototype date, or publish date), isn't the same as when it gained potential to be accepted. So, i think, utf8, even if already robust, the industry is not ready to back it.
(DIR) Post #9iJmUbro2dqyCw6l9c by xahlee@mstdn.io
2019-04-30T01:47:48Z
0 likes, 0 repeats
@wrenpile also, even if js string is utf8, it remains a open problem how how its string methods work with strings. Since, if string is utf8 bytes, bytes are not chars.golang, ruby, python, each devised different ways to deal with this, as you may know.
(DIR) Post #9iKbVRRpMNstqU6vbs by wrenpile@mastodon.social
2019-04-30T11:19:24Z
0 likes, 0 repeats
@xahlee True that.
(DIR) Post #9iKcAheM1fp7y5e3H6 by wrenpile@mastodon.social
2019-04-30T11:26:52Z
0 likes, 0 repeats
@xahlee Speaking of marketing force, Microsoft was all in on utf16 early on.