Three. :)
Yeah, I don't get it. The delivery of the talk is a little.. pointed.
But the perspective offered is incredibly compelling. And my work experiences -- both positive and negative -- are sympatico with so much said here.
1 karma · joined April 21, 2024
Yeah, I don't get it. The delivery of the talk is a little.. pointed.
But the perspective offered is incredibly compelling. And my work experiences -- both positive and negative -- are sympatico with so much said here.
Fun fact -- Ian (maintainer) is/was a backend dev at Square Enix.
https://pragprog.com/book/jgotp/designing-elixir-systems-wit...
It was hugely helpful to me in wrapping my head around something bigger than hello world.
I've been able to find high quality Elixir packages without trouble. I haven't had to fall back to Erlang packages for any holes but I feel confident because I could.
DIRT (h/t Bryan Cantrill? http://dtrace.org/resources/bmc/DIRT.pdf)
I hope to expand it to other more mundane CRUD-y microservices in the future just for the low maintenance, productivity, easy grokkability it offers.
(Presenting as "record stock growth" but in reality just trying to hold even value.)
IMO v1 is primarily about thoughtful multi-perspectival interactions. The Revolution is to come.
In my layman opinion -- the western central banks are in cahoots continually "soft landing" (optimistic) or manipulating (pessimistic) and at an accelerated rate since 2008.
The marketing isn't booming up. The nominal metric is falling rapidly.
EDIT: is/was, I've heard they turned some of it down supposedly.
This is a truism and from my experience it rings false. I ran an iPhone 5 for four years without feeling degraded.
FWIW, as background, I'm an ex-overclocking PC enthusiast and I consider myself very sensitive to any sorts of performance lag.
Amazon saw it and responded quickly.
I wrote C to get through school. I wrote PHP to hack CRUD web apps. I write JS because it's ubiquitous and I'm required to. I write Elixir because I love to do it.
Especially because:
1. It takes a lot of capital to even attempt.
2. The traditional players in position to do so do not have it in their DNA (Dell, HP, et all).
Low-ish volume- design your system such that data flows [at the relevant crucial points] through a single actor to ensure proper concurrency.
High volume- trickier but I think same idea in principle. First thought that comes to mind here is the new GenStage stuff in Elixir.
I thought it sounded like an early adopter money pit myself until I actually tried a Rift. It won me over even while underpowered (MB Air!) in very simple demos.
http://www.nhtsa.gov/About+NHTSA/Press+Releases/nhtsa-expand...
"The five recall phases are based on prioritization of risk, determined by the age of the inflators and exposure to high humidity and fluctuating high temperatures that accelerate the degradation of the chemical propellant."
So I guess I'm a phase 2 or 3 kind of owner. Meanwhile, sitting at the vaunted 10 year marker in a hot 'n humid climate...
"Automobile models and model years included in the first stage of this recent expansion of the Takata non-desiccated passenger front inflator recall"
Doesn't make me feel warm and fuzzy as a 2006 Odyssey owner.
FWIW, the Developer Edition feels pretty lean and mean. I haven't tried since I am a web developer, but it looks like you can remove most or all of the parts that make it web developer-y if you are so inclined.
Unnecessary interventions due to overly zealous electronic monitoring of "normal numbers", perverse financial incentives to turn rooms over quickly, and callous prioritization of personal time (by some not all) doctors make American hospital birth pretty terrifying to me.