How do you see `netlify dev` comparing to `firebase serve`? The `--live` feature sounds great and I can imagine the config variables are handled better, but otherwise I'm anticipating a similar experience. Is that correct or am I missing something core?
To add an interesting layer, financial institutions are investing in these solutions. Goldman previously invested in Plaid, and Fidelity invested in Quovo which takes a similar approach.
At some point I think it's on the banks to offer OAuth APIs, then Plaid can swap out one-by-one (if it hasn't already started).
Nylas is facing the same challenge in the email space. They have oauth for gmail, but user/pass for Exchange/SMTP.
I love content like this. I've found my knowledge becomes more specialized as I age, and content like this gives me an opportunity to grok other specialities with relative ease.
For whatever reason (I'm a software engineer), I particularly enjoy content about everyday physical goods. Knife steel has just been added to my bookmark list, but here are a couple more I think are worth sharing:
Any chance Stripe lifts some restrictions on prohibited businesses soon? Virtual cards can be particularly useful in travel, but that use case on Stripe has long been considered prohibited:
https://stripe.com/us/prohibited-businesses
Interesting to see Rails simultaneously embracing React with the Webpacker gem while also trying to offer a better solution in Turbolinks + Stimulus.
DHH's complaints here about React (and Redux especially) resonate with me, but I have a hard time believing a React-less approach is the best solution. I'd rather Rails roll its own enhancement of Redux - and perhaps CSS management - alongside a handful of component generators that make everything from "Javascript sprinkles" to SPAs easier to manage in Rails.
I may be mistaken, but I think the meat of this will be in post 2?
It sounds like your taking React's render() and replacing it with ERB. But, how are you giving the ERB file access to state and props?
I suppose if it's done well, this would make it easier for Rails devs to adopt single page apps. It sounds like you're abstracting away a lot of React and creating a Rails-ier API to it.