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

Erlang/OTP 25.0 Release

erlang.org

Post reply on HN
Print view View original

121–125 of 125 posts

Re: Erlang/OTP 25.0 Release

#121

Post by jacquesm »

brightball wrote: post #108
jacquesm wrote: post #106

Earlier quoted context omitted.

I'm aware of all of that but none of that answers the question.

It’s suggesting that there’s probably not much of a point to it.

Not for you. But I know quite a bit about the guts of the BEAM VM and I think this is a very interesting development and if the jump is large enough it may well obviate the need for a whole slew of situations where you now have to fall back to externally loaded functions in different languages, and that would make a bunch of stuff far more elegant. Yes, those externally loaded functions will (always) have a speed advantage, but if the advantage drops below the level of the cost of adding an external module then that would be pretty good news.

Re: Erlang/OTP 25.0 Release

#122

Post by innocentoldguy »

pjmlp wrote: post #119
deckard1 wrote: post #111

Earlier quoted context omitted.

> NoSQL crowd has largely died out. yeah, that was rather curious. Similar to how XML died out. Not with a bang but with a whimper. Not that NoSQL or XML are completely gone today, just like PHP. But suddenly one day you recognize these topics are no longer appearing on HN or elsewhere. Then you realize you're getting old and... oh my god... we're actually stuck working in a fashion industry and nothing matters, life…

Between XML, JSON, YAML and TOML, I would rather my configuration files served in XML, with schema validation and graphical IDE tooling, thank you very much. :)

I personally prefer JSON to XML. I've seen XML abused in some pretty terrible ways. For example, I worked at an education start-up several years ago and the education company Pearson delivered bubble test questions to us in XML where half of the questions' text were in tag attributes and the other half was in the body of the tag. JSON (and YAML/TOML) make it a lot harder to do stupid things like that. They're also easier to parse, in my opinion.

Re: Erlang/OTP 25.0 Release

#123

Post by innocentoldguy »

Jeff_Brown wrote: post #20

I taught myself Erlang last year and loved it until I tried to write an application. The OTP documentation, while voluminous, was confusing and seemed to have important omissions, and I found little if any community.

OTP is different, but there are a lot of good resources for understanding it. I liked:

Elixir in Action.

The Little OTP Book.

Designing Elixir Systems with OTP.

Pragmatic Studio's Elixir OTP course.

Re: Erlang/OTP 25.0 Release

#124

Post by innocentoldguy »

jacquesm wrote: post #7

Have there been benchmarks of the JIT vs say JS or the JVM?

Here's a good comparison between Elixir, Go, and Node:

https://stressgrid.com/blog/benchmarking_go_vs_node_vs_elixi...

Some of the things I like better about Elixir and Erlang vs. Go and Java are:

- In Elixir/Erlang, all processes are stored in private memory and can only be accessed via defined message interfaces. In both Go and Java, processes are stored in public memory.

- Elixir/Erlang processes are a lot smaller, memory-wise, than Go/Java processes.

- We moved all of our development at my current company from Java to Elixir because Elixir, being functional, makes writing multi-threaded applications a lot faster/easier. Elixir is also cheaper to deploy. At least that has been our experience.

- I like the syntax of both Elixir and Erlang better than Go, Java, or JS.

- I don't have as much experience with Node/Express, but in my limited testing with Node/Express vs. Elixir/Phoenix, the latter is several times faster and much more scalable. It also makes better use of hardware (which I believe is discussed in the link above).

I hope at least some of this helps answer your question.

Post reply on HN