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

The Erlang Runtime System

happi.github.io

Post reply on HN
Print view View original

21–27 of 27 posts

Re: The Erlang Runtime System

#21

Post by alberth »

nrser wrote: post #12
andy_ppp wrote: post #9

The thing that gets me about Erlang and Elixir is that it has transparent and simple to use microservices out of the box. These services are machine transparent, can be called locally and remotely, provide bounded contexts within your application, are robust and supervised against crashes, are simpler to deploy and far far simpler to develop, can be discovered using a variety of solutions or your own code. They also…

If it's feasible to write (most) all of your app backend in Elixir, then I think it's a pretty great option. I feel like language context switches tend to be very expensive and error prone for developers, plus the increased hiring and on-boarding cost associated. I think the core advantages of micro-services are: 1. Polyglot applications. There often is some library in a language for a use case, but there is also oft…

If Polygot is important to you, check out https://www.graalvm.org

>> “High-performance polyglot VM. GraalVM is a universal virtual machine for running applications written in JavaScript, Python 3, Ruby, R, JVM-based languages like Java, Scala, Kotlin, and LLVM-based languages such as C and C++.

Re: The Erlang Runtime System

#22

Post by pivo »

andy_ppp wrote: post #13
probablybroken wrote: post #11

Earlier quoted context omitted.

But then you need to either replace your existing team with erlang developers, or retrain them ( and then have to suffer years of criticism and staff losses from those who disagree with the move. ) Probably easier, and potentially more appealing to current managers to recruit more sysadmins / tech ops and have a larger organisational pyramid under them. ( I say this as an erlang developer who works in a primarily jav…

I don't actually know Erlang but Elixir has all of the same properties and is simple to learn in my opinion.

Erlang is also simple to learn! Simpler, I think, than Elixir just because Erlang is a simpler language. It’s the concepts that Erlang and Elixir share that take the most effort to lean.

Re: The Erlang Runtime System

#23

Post by etxm »

pivo wrote: post #22
andy_ppp wrote: post #13

Earlier quoted context omitted.

I don't actually know Erlang but Elixir has all of the same properties and is simple to learn in my opinion.

Erlang is also simple to learn! Simpler, I think, than Elixir just because Erlang is a simpler language. It’s the concepts that Erlang and Elixir share that take the most effort to lean.

Agree! The Erlang syntax only takes a day or two to learn. It’s succinct! You won’t be an OTP wizard but it doesn’t take much to become fluent with the language itself.

Re: The Erlang Runtime System

#24

Post by always_good »

promopacket wrote: post #3
signa11 wrote: post #2

dupe: https://news.ycombinator.com/item?id=16952311

Submissions without discussion aren't duplicates.

Especially not on a forum where new posts don't bump the topic. Commenting on that 7-day-old topic means your post goes unread indefinitely. Which is about as fulfilling as typing your comments into your diary.

Re: The Erlang Runtime System

#25

Post by regulation_d »

andy_ppp wrote: post #13
probablybroken wrote: post #11

Earlier quoted context omitted.

But then you need to either replace your existing team with erlang developers, or retrain them ( and then have to suffer years of criticism and staff losses from those who disagree with the move. ) Probably easier, and potentially more appealing to current managers to recruit more sysadmins / tech ops and have a larger organisational pyramid under them. ( I say this as an erlang developer who works in a primarily jav…

I don't actually know Erlang but Elixir has all of the same properties and is simple to learn in my opinion.

I think they’re both pretty simple languages, as far as the basic grammar goes. OTP is a whole other thing. But it strikes me that if you have one person on a team who knows OTP well, that person can assist the others when OTP issues come up.

Re: The Erlang Runtime System

#26

Post by mncharity »

alberth wrote: post #21
nrser wrote: post #12

Earlier quoted context omitted.

If it's feasible to write (most) all of your app backend in Elixir, then I think it's a pretty great option. I feel like language context switches tend to be very expensive and error prone for developers, plus the increased hiring and on-boarding cost associated. I think the core advantages of micro-services are: 1. Polyglot applications. There often is some library in a language for a use case, but there is also oft…

If Polygot is important to you, check out https://www.graalvm.org >> “High-performance polyglot VM. GraalVM is a universal virtual machine for running applications written in JavaScript, Python 3, Ruby, R, JVM-based languages like Java, Scala, Kotlin, and LLVM-based languages such as C and C++.

For anyone else wondering...

"Support for Ruby, R, or Python 3 is still experimental in GraalVM. We are actively working on stability and support for all modules for those languages. At this point in time, we can run simpler applications of Ruby and R, but we do not have the same full compatibility we provide for Java and Node.js applications. Our Python implementation was just recently started and can only run small examples."[1]

[1] https://www.graalvm.org/docs/why-graal/

Re: The Erlang Runtime System

#27

Post by [deleted] »

nrser wrote: post #12
andy_ppp wrote: post #9

The thing that gets me about Erlang and Elixir is that it has transparent and simple to use microservices out of the box. These services are machine transparent, can be called locally and remotely, provide bounded contexts within your application, are robust and supervised against crashes, are simpler to deploy and far far simpler to develop, can be discovered using a variety of solutions or your own code. They also…

If it's feasible to write (most) all of your app backend in Elixir, then I think it's a pretty great option. I feel like language context switches tend to be very expensive and error prone for developers, plus the increased hiring and on-boarding cost associated. I think the core advantages of micro-services are: 1. Polyglot applications. There often is some library in a language for a use case, but there is also oft…

[deleted]
Post reply on HN