By crashing and having it start into a good state, the system will at least be operational again.
1,554 karma · joined December 2, 2013
By crashing and having it start into a good state, the system will at least be operational again.
* BEAM provides out-of-the-box capability to network nodes together. This is extremely important in real-time flows because server A may originate a message that needs to get pushed to a user connected to server B + C (2 tabs open). The capability to both connect + send messages between nodes is built in.
* The process model in the BEAM provides a really natural fit for WebSocket connections. Each connection is its own process, and other processes are spawned off of that for various needs. The benefit here is that a failure in one process (connection drop, code error, crash, etc) won't affect other users. It's not an issue of whether the code is written well to prevent it, it's just intrinsic to the runtime. State is also stored per-process, which is convenient when it comes to writing your application.
Phoenix itself has a really nice abstraction over WebSockets (Channels, which this post goes in depth on). I won't say too much since the article does, but it's just really enjoyable to work with. Also, Phoenix LiveView is built on channels, so knowing channels provides some benefit there.If it's interesting to you, I wrote a book that basically walks you through "I don't know anything about Elixir" to building a demo "sneaker drop" store https://pragprog.com/titles/sbsockets/real-time-phoenix/
An asset is typically the final rendering of something, not the source that was used to develop that asset (image of design on Dribbble vs the Figma / Sketch files used to produce it). It's common for renderings to be made available online—although usually not explicitly licensed—but I more rarely see source made available.
The website mentions how the design world is closed off and they wanted to open this to do something about that. The attitude of "the implementation should also be open-source" seems like it reduces their efforts on the design side.
The assets are downloadable, open source in that you have access to the raw design asset, and are usable without attribution or payment. What about this is not open?
"[The smartest racer will win, not just the strongest. Well who are we kidding, you need a good bit of luck too.]"
That's certainly true given the sheer luck on display (peloton lost track of breakaway) and how smart Kiesenhofer is. I also think it's interesting how much she dislikes riding in the peloton. She's 10ft off the back in the starting roll-out.
Sure you can argue that the pure tech worked as designed, but the system includes the human element as much as the tech element.
I see the value in this, but I actually disagree with the article in terms of that being the best solution. Long-polling is significantly different than polling with a cursor offset and returning data, so you wouldn't shoe-horn that into an existing endpoint.
I think that a combo of webhooks / events is nice, but "what scope do we cut?" is an important question. Unfortunately, it feels like the events part is cut, when I'd argue that events is significantly more important.
Webhooks are flashier from a PM perspective because they are perceived as more real-time, but polling is just as good in practice.
Polling is also completely in your control, you will get an event within X seconds of it going live. That isn't true for webhooks, where a vendor may have delays on their outbound pipeline.
Here's the article about it that has a picture of his sandal setup: https://cyclingtips.com/2021/06/lachlan-morton-just-rode-two...
Lachlan did a full 10-12 hour day in sandals because he was having knee pain starting.
If you ever need any help with content in the book, or a sounding board for Phoenix questions, feel free to DM me on the forums. I appreciate your points and generally agree with them, even the not-so-good ones.
I got super burnt out over the last year and there was not really another option imo. I had been working on my own company on the side and I feel immensely more recharged working on it. For people that have been sitting at home and not spending their salaries for the past year, that might be an appealing option.
This is a good point that I hadn't really thought about previously. I agree with your thoughts much more when I consider the different needs between libraries and applications.
I wouldn't care if someone else posted your comment, but you've been downing (non-constructively) on Elixir in this thread and other posts you've made on Hacker News.
I picked up Elixir probably 4-5 years ago when a co-worker kept recommending it and wanted to explore it more. We finally got the approval to do a microservice in it that was well-suited for it. Over time it became one of the two "blessed languages" alongside Ruby, and was probably adopted by 40% of teams. Our monolith was still Ruby, so a lot of teams had to use Ruby.
I found that people could pick up the language fairly quickly, but it would take a few stumbles on OTP before things started to click there. People generally seemed to like learning it, though. Maybe they were just being polite.
For me, Elixir has been the most fun I've had programming since I started. It allows me to more consciously design my systems because I don't really feel limited by it—this is why I'm bullish on the language. I enjoyed programming in Ruby, but felt limited to doing things a certain way.
There's also still a ton of opportunity in the community (which is excellent as it is, imo). For example, I wrote a book with Pragmatic that I don't think I would've been able to write in the Ruby world. If you're the type of person who likes exploring, figuring things out, and documenting afterwards, then you could make a nice name for yourself in the community.
Hiring is still a bit rough. If you're trying to scale to 50+ engineers then you're going to need someone skilled in training to bring the team up. Throwing them into the deep end won't work. I think smaller teams should generally not have as big of a problem? I'm curious to see how my former employer will maintain Elixir—grow or shrink adoption—over the next 2 years.
I will say that maintenance of hand rolled Sass has not been great overtime. It's really hard to tell what's in use and what's not.
Before Tailwind with PostCSS, I'd probably hand roll some Sass-powered UI, or find a template to base it off of.
If the content doesn't violate any rules and people want to read it, then it has a place. If it does violate rules, then communicate those clearly. Given that, I think that this is most likely not an issue of rules violation but of Facebook not wanting the content on their platform (and not wanting to actually justify that).
Is there any good literature or patterns on supporting dumps in the tens of millions or larger?
I wrote a sheets plug-in that uses our cursor API to provide a full dump into a spreadsheet. Our professional services team is in love with it, so I bet they'd love generic data export capability.
Speaking from experience...we want to make it easy but also want to keep it performant. Getting the data all in one go is generally not performant and is easy to abuse as an API consumer. For example, always asking for all of the data rather than maintaining a cursor and secondary index (which is so much more performant for everyone involved).
Looking back, I would exclude classic pagination from a public API and go full cursor. Possibly include an optional total count that can be requested (counts are expensive in PG though).
Page changes are still initiated by the client in LiveView (although can be server initiated)
LiveView is just channels under the hood. Once you consider that, long polling may seem more obvious