News for hackers. Stuff that matters.

A comment on How and Why We Switched from Erlang to Python (2011). Parent comment

Re:How and Why We Switched from Erlang to Python (2011) by jlouis on Sunday May 19, 2013 @02:38PM (#5733923)
Unicode is a big thing in R16 and R17 where more of the system will use the unicode support we do have. Erlang modules will use utf-8 encoding and so on.

As for a built-in bstring() type, it is being discussed, but there are other things more important to get into the language, maps for instance. Erlang is rather conservative in the speed with which we add stuff to the language.

Erlang has some of the fastest I/O in a runtime. But it is not easy to use correctly. The same goes for string processing. Erlang can be blinding fast at that, but you must understand how to make it fast.

[ Parent | on HN ]
Re:How and Why We Switched from Erlang to Python (2011) by yosh on Sunday May 19, 2013 @11:56PM (#5735784)
Having recently run into some non-obvious crappy performance characteristics with I/O in Erlang, I'm curious if you have any pointers to docs or code that shows how to use Erlang I/O correctly so it's fast?
[ Parent | on HN ]
Re:How and Why We Switched from Erlang to Python (2011) by digitalzombie on Monday May 20, 2013 @03:06AM (#5736318)
More important things...

please please have a record replacement already. There are like a couple of proposals for record replacement.

http://www.cs.otago.ac.nz/staffpriv/ok/frames.pdf

[ Parent | on HN ]