hamidreza-s

13 ms·

1. 1.▲
   by hamidreza-s 11y ago

   That's a good pint! I also can say that it is a matter of perspective. From an Erlang developer point of view, the processes are executing in a preemptive manner without telling them when to yield. The important factor is the reduction
2. 2.▲
   by hamidreza-s 11y ago

   Although writing C code for NIFs is not a regular task for Erlang developers, it must be done with extreme care because not only a long-running NIF could degrade the responsiveness of the VM, but also when it crashes the whole VM will crash
3. 3.▲
   by hamidreza-s 11y ago

   There are lots of demands for making things concurrent, fault-tolerant and distributed nowadays, not only in big companies but also among startups. Erlang already has those features as well as standard tools (OTP) which lets everyone to cre
4. 4.▲
   Erlang Scheduler Details and Why They Matter(hamidreza-s.github.io)

   188 points by hamidreza-s 11y ago|30 comments
5. 5.▲
   by hamidreza-s 11y ago

   Thanks for reading my post and taking time to write about it. As the title of post which emphasizes on "WHY GC matters", I tried to reason why we should understand the underlying of a system, say Erlang, Go, Java or whatever else.
6. 6.▲
   by hamidreza-s 11y ago

   .