ramchip

28 ms·

301.
by ramchip 5y ago
There's a comment here: https://blog.erlang.org/the-road-to-the-jit/#maturing-the-ne... I feel like I saw graphs in one of the presentations, but I don't recall which, or if it was about the final iteration o
302.
by ramchip 5y ago
Who's "we"?
303.
by ramchip 5y ago
Elixir has a few interesting abstractions for that: GenStage, Flow, Broadway. https://github.com/dashbitco/flow
304.
by ramchip 5y ago
Just an example, but if a significant part of your pay is stocks, it's possible that you need several (4+) months of salary in an account for the tax payment to go through plus afford normal expenses.
305.
by ramchip 5y ago
It really depends where you live, where I live in Asia electric (induction) is the high end option and gas is the standard. Electric also doesn't work great with a wok.
306.
by ramchip 6y ago
Japanese cell phone companies did something similar for many years, they all offered two-year contracts with a cancellation fee of around $100, and you could only cancel in the last month before it auto-renewed. The government finally passe
307.
by ramchip 6y ago
It's standard terminology, yes. A quick google would lead you to: https://en.wikipedia.org/wiki/Act_of_God
308.
by ramchip 6y ago
The license is Affero GPLv3. Does this mean anyone who self-hosts an app using this needs to make their source code available?
309.
by ramchip 6y ago
There’s a few papers about it such as: - “Heap architectures for concurrent languages using message passing” - “Exploring Alternative Memory Architectures for Erlang: Implementation and Performance Evaluation” - “A Case for the Unified Heap
310.
Erlang/OTP 24 Release Candidate 1(erlang.org)
116 points by ramchip 6y ago|15 comments
311.
by ramchip 6y ago
It's unfortunate that this number stills gets thrown around: https://stackoverflow.com/a/26447543
312.
by ramchip 6y ago
Lightweight threads in Erlang/Elixir were created as a unit of fault tolerance. A lightweight thread can suddenly exit when it hits an error, and the VM mechanisms give you guarantees that any resource it owned will be freed (memory, s
313.
by ramchip 6y ago
Modelling a problem like this with tons of Erlang processes tends not to go very well: - It's slow, really slow, and memory heavy. All communication between processes involves copying and context switch. - It's easy to introduce d
314.
by ramchip 6y ago
Yeah... sometimes you get a junior engineer who's drunk the koolaid a bit too much and think they need a bunch of fancy tech for their web dashboarding dealing with 5 req/s. But I think it's pessimistic to reduce it to people
315.
by ramchip 6y ago
A lot of web services do a little bit of work, wait on a DB query, do a little bit of work, wait on DB, etc. It’s even more true with websockets, which spend most of their time idle waiting for messages. Good concurrency support lets you ha
316.
by ramchip 6y ago
I would take this benchmark with a huge grain of salt: https://64.github.io/actix/#blazingly-fast-or-not
317.
by ramchip 6y ago
I think latency also matters a lot for client-side DB connection pooling. If the DB is a 10ms round-trip away, and queries take 10ms, the process on the DB side is only really busy half the time.
318.
by ramchip 6y ago
What's cake wrangling?
319.
by ramchip 6y ago
CPython has no compilation step. It reads source code and generates bytecode at runtime; this bytecode is cached inside `pyc` files. The bytecode is interpreted. Erlang (pre-JIT) has a compilation step. The compiler reads the source code an
320.
by ramchip 6y ago
It's true it can feel cryptic at times. The good news is improving error messages and ease of use is a major focus area in next year's release. This PR from a few days ago looks like a very nice improvement in that direction: htt
321.
by ramchip 6y ago
I think it’s a common trap for Erlang beginners to try to represent all entities (player, monster, room, etc.) as processes sending messages to each other, the way you’d use classes in OOP. It’s one way to learn the concepts, but in real ap
322.
by ramchip 6y ago
Yep. Erlang uses a single TCP connection between each pair of nodes. Older versions had problems with large messages blocking heartbeats (and other messages) for a long time, but that's been resolved last year in https://git
323.
by ramchip 6y ago
It's great to see some type checking sneaking in Elixir :)
324.
by ramchip 6y ago
It’s true even with distribution, see e.g.: http://erlang.org/faq/academic.html#idp33052176 http://erlang.org/pipermail/erlang-questions/2017-September/...
325.
by ramchip 6y ago
> I'm going to be honest: naming this product was hard, because it's not quite like any other cloud technology that is widely-used today. Perhaps I'm missing something important, but isn't this quite similar to Orlean
326.
by ramchip 6y ago
https://erlang.org/doc/apps/erts/ThreadProgress.html
327.
Elixir v1.11 first release candidate(github.com)
2 points by ramchip 6y ago|0 comments
328.
by ramchip 6y ago
Perhaps you're thinking of Facebook chat? https://www.quora.com/Why-was-Erlang-chosen-for-use-in-Faceb... https://www.quora.com/When-did-Facebook-switch-away-from-usi...
329.
by ramchip 6y ago
I love how much thought and polish went into this, just like so many other Erlang features in recent years: counters, persistent_term, thread progress, ETS scaling, process groups... There's been talks of JIT for quite a few years, but
330.
by ramchip 6y ago
I misunderstood then - I interpreted the parent as being about the wall socket, because I wasn't aware that rewiring the actual plug was a thing you could do (or that these things ever failed, in fact). I guess I'm a double embarr

More ›