3 ms·

Wow, I'm currently in Korea and I did not expect Naver to have projects like Lisp implementations at all. Their services (map, search, ...) are very common here

by emaro 4y ago

Wow, I'm currently in Korea and I did not expect Naver to have projects like Lisp implementations at all. Their services (map, search, ...) are very common here, but from the outside it looked more like a boring company. Great write-up. They also mention Tamgu, another language they developed, with native Korean language string support (`ishangul()`, `romanize()`).

apetresc 4y ago
I'm actually pretty fascinated how someone was able to get this project hosted on Naver's Github at all. It's probably not coming from corporate judging by how informal and personal the language is (and also that there's only a French and English version), so it's probably just the passion project of a random employee or contractor. Interesting that Naver lets them host it under their public brand. I can't imagine the Google of the 2020s allowing anything like this in under their public brand.
- clauderoux 4y ago
  Hello, I work in a laboratory specialized in Artificial Intelligence that belongs to Naver (NLE). These two languages are used in many research projects, especially for document processing before applying ML methods. We used Tamgu for instance in Machine Translation and in Sentiment Analysis. We have also published in the past datasets for conference papers, that required the tools to be open source, so that people could reproduce our experiments. This year for instance, we used the Prolog engine in Tamgu to produce a dataset to train a transformer on inference. The process to make them open source was quite thorough and quite painful, but I cannot complain. The case of LispE is little bit different, I created it to have a more flexible platform to experiment with functional features, which I could not do with Tamgu, which is too large now. The blogs are simply a way to make these tools more visible, and since I'm French, I usually write them in English and French.
  - apetresc 4y ago
    Awesome! Thank you for going through whatever red tape was required :) To be clear, my description of the language as "informal and personal" was not meant as a criticism - I love it. It's just so different from the fake-enthusiastic professionalism that is usually mandatory from corporate-branded projects like this. Hats off to you!

by emaro 4y ago

apetresc 4y ago

I'm actually pretty fascinated how someone was able to get this project hosted on Naver's Github at all. It's probably not coming from corporate judging by how informal and personal the language is (and also that there's only a French and English version), so it's probably just the passion project of a random employee or contractor. Interesting that Naver lets them host it under their public brand. I can't imagine the Google of the 2020s allowing anything like this in under their public brand.

clauderoux 4y ago
Hello, I work in a laboratory specialized in Artificial Intelligence that belongs to Naver (NLE). These two languages are used in many research projects, especially for document processing before applying ML methods. We used Tamgu for instance in Machine Translation and in Sentiment Analysis. We have also published in the past datasets for conference papers, that required the tools to be open source, so that people could reproduce our experiments. This year for instance, we used the Prolog engine in Tamgu to produce a dataset to train a transformer on inference. The process to make them open source was quite thorough and quite painful, but I cannot complain. The case of LispE is little bit different, I created it to have a more flexible platform to experiment with functional features, which I could not do with Tamgu, which is too large now. The blogs are simply a way to make these tools more visible, and since I'm French, I usually write them in English and French.
- apetresc 4y ago
  Awesome! Thank you for going through whatever red tape was required :) To be clear, my description of the language as "informal and personal" was not meant as a criticism - I love it. It's just so different from the fake-enthusiastic professionalism that is usually mandatory from corporate-branded projects like this. Hats off to you!