I am aware of that option. However, AFAIK patching links do not prevent the user to press Back button.
1,939 karma · joined July 27, 2014
If Kubernetes is not involved, passing messages between Elixir nodes is easy. We just need the name of thr node (and a cookie, if needed).
Not sure if that is possible inside a Kube cluster.
In my opinion, the main drawback of LiveView is that we assume that the user do no click on the Back button of the browser. In other words, if the user changes the page by pressing the Back button, then Phoenix closes the socket, creates a new one, and the state is lost. I really like LiveView but not sure how to persist the state between page reloads without using Ecto (also, not sure if that is idiomatic).
- In vim, I can use vim-fugitive [1] to easily run git add and git commit. Not sure if helix has that level of integration with Git (I like the gutter, though). I know that we can use tools like lazygit within Helix, but I think :Gw and :Git commit are more ergonomic.
- I prefer vscode to code in Rust because of rust-analyzer [2]. That plugin gives me type type annotations along each variable. Helix can also provide some hints, but not that many as rust-analyzer.
Interesting talk about complexity: Complexity is when your systems interact. A complex system can become unreasonable. A complex system cab be generative and surprising!
- they offer good quality books
- they also offer a subscription where you can view all books and download one book per month
- when you buy a digital book, they give you the book in several formats (kindle and pdf)
- you can read the ebook in multiple devices
O'Reilly should follow the same business model.
> 3. Immediate Mission-Critical Updates > We do not skip the app store's review process, but we do offer a server-side solution that will allow you to make permitted changes (per app store rules) on critical bugs that may otherwise take days to clear the review process. You can roll these changes out immediately.
That point is a bit confusing. We can skip the app store's review process or not? In other words, in which cases we cannot skip the review process?
Do not get me wrong, I am really excited about this milestone. Also, I am waiting to see a demo in Android.
In [2], Wojtek Mach explains how the team behind Elixir build Livebook Desktop. He explains how the project started, some subtle bugs found when building the app for MacOS, some limitations of wxWidgets in Windows, and many other implementation details.
It would be awesome if the Elixir team releases something like elixir-desktop based on Livebook. That is, forking the Livebook repo and release an official template project for generating desktop applications based on LiveView. Right now, Livebook is distributed as an executable for Windows and Mac. Why not follow the same approach to allow developers to publish self-contained executables pretty much like Electron?
I am aware of LiveView Native [3] but I think they follow a different direction.
[1] https://github.com/elixir-desktop/desktop-example-app
Quick suggestion, it would be nice if the landing page [1] has more information or links to actual examples of how to use LiveView Native. That page has not been updated in a long time and give the (misleading) impression that the project is on hold.
In [2], Wojtek Mach explains how the team behind Elixir build Livebook Desktop. He explains how the project started, some subtle bugs found when building the app for MacOS, some limitations of wxWidgets in Windows, and many other implementation details.
It would be awesome if the Elixir team release something like elixir-desktop based on Livebook. That is, forking the Livebook repo and release an official template project for generating desktop applications based on LiveView.
[1] https://actualize.teachable.com/p/modern-javascript-explaine...