231 karma · joined May 27, 2016
Do you have a source for that, because that's not the impression I, as a non German European, have.
defmodule(Foo, [{:do, def(:bar, [{:do, "baz"}])}])
Even aliases (like Foo) are also a kind of syntactic sugar for a specific type of atom (Foo is actually the atom :"Elixir.Foo")Later, when most households in the Netherlands where start getting PCs (80286/386/486 era), I felt right at home using msdos.
Nowadays I really appreciate vaporwave aesthetics and I'm sure it's because of being absorbed in the world of msx computers, including reading magazines and such, as a kid.
I can believe private enterprise usage is higher, but I imagine FAANG and similar companies also have quite a lot non public Linux servers. Not trying to rebut your overall point, but I'm not sure the total non public % is much different.
See https://www.erlang.org/doc/apps/erts/time_correction.html#in... for more info. It's about time handling in the Erlang run-time system, but the issue it describes is universal.
And having an Erlang background, I would say timestamps are also tricky in the context of distributed systems.
As usual, emacs has a mode for everything:
While I wouldn't go as far as saying that elixir has the same benefits as lisp regarding uniform syntax in combination with a flexible macro system, elixir's macro system is undoubtedly powerful. The big difference with a lisp is that elixir's macro's operate on an intermediate ast representation that looks a lot like lisp code. So while elixir doesn't have a very uniform syntax itself, I think its macro system gives comparable power and flexibility.
Trying to make Vanilla JS a strict definition seems pointless to me in the first place.
I guess that would be me. I mostly work in the terminal and I just don't care that much about the window manager. As long as it's simple, works consistent and looks somewhat nice and clean, I'm fine. Gnome fills that role for me.
I'm a Elixir and Erlang developer who is just starting to explore ML, but these libraries seem solid and well designed.
But isn't that introducing incidental complexity? Not sure if you actually disagree.
The other storage engine riak could use was google's levellb.
At the time bitcask was as fast or faster than leveldb for most tasks. This was I think around 2010. I have no idea how it compares with a recent version of rocksdb, but at the time it was pretty fast.