Great list that sparked my memory. The tmux scroll back issue was very frustrating for me, and ultimately what made me stop using it. What got me hooked on trying to use it - I do remember being amazed I could close my laptop, go home, and just reopen my laptop and immediately start typing away on my remote terminal without issue most of the time.
A few other issues I do remember running into (probably 10 years ago?):
1. Because it was udp, sometimes a captive portal, work, or hotel firewall blocked it.
2. It was also not installed by default anywhere, so sometimes sysadmins at work were unwilling to install it for me.
3. I sometimes ran into issues with color handling and utf8. I honestly don't remember if it was mosh or my terminal, though. It seemed to happen more often when I used mosh, but I could be misremembering.
It is an advanced driving assistance system. It kind of drives your car for you (lane centering, basic obstacle avoidance, and adaptive cruise control all without you have to touch the wheel or the pedals) as long as you’re looking forward and paying attention to the road.
They have demonstrated full self driving capabilities with a car driving “itself” to Taco Bell. I have a comma3 and have never had much success with that feature. The car drove itself very slowly and seems to just weirdly creep through stop signs. I think the last time I tested that was over a year and a half ago, so it may have improved.
I use mine only on the highways. I noticed for long trips (6+ hours), I can drive longer distances in one go and not feel as fatigued when I reach my destination. As an example, a 10 hour trip to visit family (11-12 hours including stops) I can do by myself in one day with the comma device instead of stopping halfway, or splitting driving time with someone else. For shorter trips (3-6 hours), I arrive to my destination with more energy than when I drive without these features. I am also able to focus more on potential obstacles further down the road than without it.
I think my device has already paid for itself thanks to a couple year period where I had to do that 12 hour trip I mentioned a couple times per month. Plus it is a really nice dash cam.
If you're considering a similar pattern with Flutter rather than ReactNative, they call it "add to app" and there's a couple good talks on how others have approached this [1], [2] from the recent FlutterConUSA, as well as a couple articles that include details and case studies [3], [4]
I haven't tried this myself with a large project (just small examples as proof-of-concepts), but the approach seems very sound. One thing I liked is once you have the legacy app shell figured out, it's not a crazy approach to mock out the bridge/native services and run the app in just flutter (or react native) for development/testing acceleration, then adding final integration testing/QA with the full legacy app shell. I've seen some odd behaviors from apps that have used this approach that I would have to imagine can be serious headaches to debug. That said, it does seem the approach pays off long-term.
There's not much published online about it, but I believe Headspace has used this approach for its mobile app. See [5]
A few other issues I do remember running into (probably 10 years ago?):
1. Because it was udp, sometimes a captive portal, work, or hotel firewall blocked it.
2. It was also not installed by default anywhere, so sometimes sysadmins at work were unwilling to install it for me.
3. I sometimes ran into issues with color handling and utf8. I honestly don't remember if it was mosh or my terminal, though. It seemed to happen more often when I used mosh, but I could be misremembering.