Waiting for them to make a Mac port, since coding happens on a "real" computer (for now, anyway).
Simply, it is an adapter that lets you use SQL syntax to introspect Ethereum blockchain data (blocks, and transactions.) Typically people do this using a JS API built into the node software [1], and it may/may not be ones' cup of tea.
May be unfair to all parties involved that a situation is described on hearsay, with the source not identified, and not even being a direct source (someone who wasn't at the event, and who heard about it weeks later.)
For example, Apple Pay works great at Whole Foods. I use it every time. Other people in line painstakingly pay with credit cards, despite holding an iPhone in their other hand. The new chip cards take longer to process, even, 5 seconds or so.
"The price of this book is five dollars" vs.
"This is five dollars" (meaning "this book's price is") vs.
"This is five dollars" (meaning "five dollars are sitting here on the table.")
I know what you're saying, there is ambiguity, but these make sense to people based on context.
[1] https://docs.google.com/spreadsheets/d/1m89CVujrQe5LAFJ8-YAU...
On the other hand, if you take Seattle's Belltown, there will be art stores, realtor offices, and other things you rarely ever ever need, and yet you have to drive five minutes to buy a bottle of water.
It seems that over the years, their PM team is more confident (capable?) in keeping a good balance between core chat usability and all the "extras", perhaps because they are not playing catch-up in the market.
Quick feedback: flicking away a card takes too long (vertical distance) of a flick. I have to carefully drag it from top to bottom for the card to flick away. Wish it was more sensitive. Perhaps 30% of the screen height is enough of a threshold. Otherwise, thank you. Going to be using this!
The key is stored in the same system somewhere (or your app wouldn't function). A rogue employee can find the key if they want. Is there a practical benefit other than additional compliance checkboxes being checked?
Elixir (due to Erlang base) is great for long-running or distributed services and includes tooling to, for example, easily introspect the state/memory usage of your services down to a single mutable data structure, to heal from failures, and to hot-swap upgrade/code while the server is still running, and to perform node-to-node RPC.
Go would be a replacement for something that was previously written in C/C++, that may need concurrency, and that should compile to native code. You get very fine-grained control of everything from network to file operations and excellent concurrency constructs. A web crawler, a device driver, or writing an Nginx/HAProxy-type daemon, all may be great example use cases.
One could write their next social network/app backend using Go (just as one could do it in C), but it would probably take more work than just using a higher-level language.
Think of:
items = ["file_a", "file_b", "file_c"]
Enum.map items, &HelpfulDownloaderModule.download/1
Short syntax:
Enum.map [1,2,3], &(&1 * &1)
Enum.map [1,2,3], (fn num ->
num * num
end)
square_me = &(&1 * &1)
Enum.map [1,2,3], square_me
square_me_too = fn(num) -> num * num end
Enum.map [1,2,3], square_me_too
def square(num) do
num * num
end
def doing_something() do
...
Enum.map [1,2,3], &square/1
Enum.map [1,2,3], &SomeOtherModule.square/1
...
endComing from imperative languages especially (speaking for myself), have to re-think/re-learn how you write code, but it does end up being a worthwhile investment
The Elixir community may be an amalgamation of Rails folks looking for better runtime performance and cool new tech, and Erlang folks looking for syntactic sugar and a growing developer community. (I'm neither.)
Elixir's author was one of Rails core contributors, which probably also helps in bringing the Rails crowd over. One could think of Elixir as a "better" version of Rails rewritten on top of the Erlang stack, even if Rails and Elixir are apples and oranges under the hood.
See also: the inverse of OP's article, the creator of Erlang trying out Elixir (2013) [1]
[1] http://joearms.github.io/2013/05/31/a-week-with-elixir.html#...