Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What Sucks About Erlang (2008)

damienkatz.net

Post reply on HN
Print view View original

101–105 of 105 posts

Re: What Sucks About Erlang (2008)

#101

Post by ermouth »

facetube wrote: post #99
ermouth wrote: post #98

Earlier quoted context omitted.

> I'm talking about the internals of couchjs. _list functions stream, and was specifically designed to be able to stream. However, streaming does not help much in this case, moreover too small chunks dramatically reduce already awful _list perf. Taking this in account I see no value for views to stream. Sending all emitted KVs for the doc to Erlang bits in one turn seems both much more predictable and safe. > Multipl…

> I‘ll give you no cite, sorry, because we discovered the effect during internal tests We discovered the issue in internal tests and reported it upstream where it was confirmed; there's nothing to discuss here. > BTW they may be patched without upgrade, with 5LOC long design document in Erlang. I don't have to hand-patch other database systems. Further, as of now there are no functioning packages for multiple version…

100M docs? Of json format? On commodity hardware? In 2003?

Hahaha, hello long waited friend from parallel universe!

Re: What Sucks About Erlang (2008)

#102

Post by facetube »

ermouth wrote: post #101
facetube wrote: post #99

Earlier quoted context omitted.

> I‘ll give you no cite, sorry, because we discovered the effect during internal tests We discovered the issue in internal tests and reported it upstream where it was confirmed; there's nothing to discuss here. > BTW they may be patched without upgrade, with 5LOC long design document in Erlang. I don't have to hand-patch other database systems. Further, as of now there are no functioning packages for multiple version…

100M docs? Of json format? On commodity hardware? In 2003? Hahaha, hello long waited friend from parallel universe!

Easy enough to convert on the way out, using a mature database system without these performance flaws. The app got done and performed well, and we weren't at the mercy of an unresponsive community that leaves seven year old dependencies in critical paths.

Keep going; it'll bite you eventually. Don't say you weren't warned.

Re: What Sucks About Erlang (2008)

#103

Post by __sr__ »

andy_ppp wrote: post #75
__sr__ wrote: post #72

Earlier quoted context omitted.

Is Elixir being used extensively outside Silicon Valley? Can you list some well known success stories? Looking at job listings and open source projects, it doesn’t seem to be widely used. In fact, I don’t know anyone outside Silican Valley who has built anything non-trivial in Elixir. I am not saying it is bad. But I’d like to know about it before I dive in.

Why exclude the success stories in Silicon Valley - seems like an arbitrary decision to exclude Discord say or Pinterest? It does seem there aren't that many very big companies outside of Silicon Valley using Elixir but maybe that's a factor of Silicon Vally having the vast majority of winners period.

Well, I don’t live in Silicon Valley, and as a result, the company I work for is not a Silicon Valley company. If I am going to convince the management to invest in Elixir, I need to be able to answer questions like this. Pretty much everyone I have spoken to about Elixir, inevitably brings up this point.

Re: What Sucks About Erlang (2008)

#104

Post by facetube »

HumanDrivenDev wrote: post #89
facetube wrote: post #46

Earlier quoted context omitted.

From the point of view of a single cluster or node (ignoring replication for a moment), it just doesn't have any strong notion of transactions. There's no write-ahead log, no rollback, and no situation where you'd be able to operate in a mode equivalent to something like `SERIALIZABLE` on a relational database.

oh right, I understand what you mean now. I guess most people should know that going in. Are their good master-master systems out there with local transactions?

The claim from daimenkatz was that transactions and MVCC are supported internally, but not externally. It's unclear to me if any of this is accurate. Here's the information that was offered: https://github.com/couchbaselabs/couchstore/wiki/Format. Let me know if you see MVCC or transactional behavior in there.

Re: What Sucks About Erlang (2008)

#105

Post by andy_ppp »

__sr__ wrote: post #103
andy_ppp wrote: post #75

Earlier quoted context omitted.

Why exclude the success stories in Silicon Valley - seems like an arbitrary decision to exclude Discord say or Pinterest? It does seem there aren't that many very big companies outside of Silicon Valley using Elixir but maybe that's a factor of Silicon Vally having the vast majority of winners period.

Well, I don’t live in Silicon Valley, and as a result, the company I work for is not a Silicon Valley company. If I am going to convince the management to invest in Elixir, I need to be able to answer questions like this. Pretty much everyone I have spoken to about Elixir, inevitably brings up this point.

I don't understand why you make the distinction between Silicon Valley and not Silicon Valley because where something is done makes absolutely zero difference as to if it's a good idea to use software or not.

If there was a text editor that you thought was good but was only in use in Silicon Valley would you still recommend it? I've never ever in my life discounted a piece of software because it was only in use in Silicon Valley.

Maybe you could expand on the argument because I don't understand it clearly!

Post reply on HN