1,554 karma · joined December 2, 2013
To me these phrases are more about the guarantees—if it does crash it recovers—and less about dogmatic advice that everyone follows.
But there's time and place for different levels of defensive programs. I get to pick and choose based on where I see risk, but I know the whole app isn't going to blow up if I missed something.
I've been in the situation where it's not a choice. So that is where my view comes from. It probably worked out better for me personally than if it didn't happen, so I'm not upset now.
That can be good for employees (money in your bank is a good thing), but only if they want to sell.
Edit: there's another thread with more info. This round looks to address a specific issue that would affect employees very negatively. So it seems like a good thing and not corp greed.
Maybe survivorship bias in the results? I know plenty of self pub authors that never cleared $1000 of sales. But then you have people that hit it big. Those people always seem to have a large existing audience, though.
Publishers are not all made the same. Pragmatic Bookshelf was great to work with and I'm thinking their estimate of 25k per book (to the author) is probably a good goal. Mine cleared that and then cleared my sales numbers goals as well.
You simply can't get that type of revenue unless you're at 50% royalty rate. Self publish is 100% of course, but pragmatic relationship definitely gave me a better product and marketing.
Pros: Gives a real work indicator of performance with very low risk. Data could be truncated and then backfilled before the final release.
Cons: not always possible depending on complexity or feature. Requires implementing the parallel path which carries some risk in itself.
It's a complete way to build complex apps. I've personally built fairly decent complexity SaaS (18mo of dev) completely on LiveView + some react when it made sense.
Saying it's just HTML pushed over WebSocket is like saying React is just virtual DOM with components. There's much more to it when you get into it.
Plus it's enjoyable. I had significantly more fun and development speed building on it than the typical React+API approach.
That said it's still situational and I don't blindly recommend it to everyone. I think Elixir has one of the best graphql implementations (Absinthe), so I still recommend React+GQL as well.
To be clear I don't believe that, but that's analogous to what I hear when I see this.
LiveView has composition of components, so there's an immediate answer to your question. You've already answered another piece with built-in soft real-time.
In all honesty, if you have looked at LiveView and don't understand what it brings then I'm not sure if you looked sincerely.
To me LiveView is not about interactive apps so much as it is a way to build applications, period. You can build in a way that may bring you more joy, performance, and dev speed than you could otherwise.
Interactivity is a side effect, and it's a great one. But I wouldn't recommend LiveView if someone only wanted interactivity. I'd recommend LiveView if someone wants a different way to build than the React+API status quo.
Even though it's still a little more than a normal dozen, it's well worth it since they taste better.
How would it be possible for them to police every action of their customers? I expect actions to be brought against the individual violators, and then escalated to Twilio, and handled appropriately. As is the case here.
It would be different if they actively support systemic violation, but I don't think that's the case?
Being able to do this at the programming language level is extremely powerful and creates an entirely different way of building applications. My go-to analogy is building a city (lots of individual, isolated, separate stack processes) instead of a big skyscraper (deep stack requests, concurrency difficult, error recovery manual).
You can build that city in a limited way with k8s, but there's way more overhead along the way, to the point of it not being enjoyable for me.
His point was that the paradigm is so different at the VM level, that many things become irrelevant to the conversation. That said, there still are concurrent programming challenges on the BEAM, but it's very minimal compared to languages where it's not baked in.
Ruby Ractor is a good example of how a VM-backed concurrency mechanism will likely change how programs in that language can be built.
I think it's even more nuanced, but doesn't really matter for this type of post.
(I am actively writing a chapter exploring this topic, so is has been top of mind.)
I found this a really interesting read, but this stuck out because it doesn't jive with my mental model of gen_server.
gen_server is fully serialized. Even the code underpinning it is not concurrent.
Now I guess gen_server does expose some top level functions to simplify sending/receiving a message into the process, but the process itself is serial.
And this is part of the genius of gen_server to me. You don't need to think about your state concurrently because it processes a single message at a time. Your system executes concurrently, but the individual components do not.
Maybe that is what the post means and I misinterpreted it.
My grandmother was in hospital on palatial care. We didn't know how long she would have, but it wasn't much.
I look an awful lot like my uncle due to having curly hair. I sat with her holding her hand for hours, just being with her and making sure she wasn't alone. She thought I was my uncle most of the time, but it didn't matter. (Very confused nurses when she called me her son.)
I still consider it one of the most important things I've done. Being there for someone in their final days is sad, but also a gift if they can be provided some comfort.
I was powering a fairly large amount of state, to the point we had to diff state changes due to browser message costs. It was difficult to write, but was incredibly powerful.
You get a crazy powerful state management model that can allow traditional web pages to feel like SPA (your extension around it at least)
It's a shame manifest v3 absolutely butchers this use case because there's no long term live-state management other than opening an extension tab.
But it turned out that our chem teacher wore open-toed shoes that day (not a lab day for her) so she made us detonate it all ourselves.
This was in 2010.
The book very specifically says to not make this due to how volatile it is.
We made it in the morning and put it in the undisturbed back room to dry for the afternoon.
We got news of it exploding during a silent study hall and scaring the crap outta everyone there, especially since it was a different teacher in the room. The air current from the AC set it off.
We were again (somehow) given permission to remake it since it went off.