You’re overlooking Hotwire, PWA as a first-class concept, and Hotwire Native — the easiest way to take a functioning web app and migrate it to native mobile apps on both iOS and Android. I’d encourage you to take a fresh look at the new Rails technologies introduced in Rails 7 and Rails 8. You may find that the current Rails stack is the best fit for most, though not all, cloud applications that need a web client along with iOS and Android clients.
To start, you build a standard Rails web app, enabling you to interact with your customers. When you want to build that iOS and Android app, Hotwire Native makes it easy to create an app store app for each. From there, you can add native features as you need, as fast or ask slow as you like.
Excellent work on the mobile app though I would wonder, since HCB runs on Hotwire, why it was not written as a Hotwire Native app which would leverage the existing Rails Hotwire app and not require a complete rewrite?
Hotwire Native tbh wouldn't have been a bad choice at all to use tbh. Especially if you wanna maintain 1:1 parity with the website. It combines both being a "web app" and native features we could still use like Tap to Pay and Push Provisioning. The downsides of it is that it isn't a cross platform framework like React so all changes would have to be pushed to both an iOS app repo and an Android app repo. Another downside is that it isn't a "write once run anywhere" type application as you're integrating Hotwire into the native code so you have to be comfortable with both Kotlin and Swift (however if you're writing native modules in React Native same applies).
Both are 2 completely valid and separate paths you could take when building an app and I'd actually be curious what'd HCB Mobile look like if we did use Hotwire Native.
As I commented in similar question, check out any one of Irina Nazarova's talks about the startups that are starting with Rails. There are a growing number of them. Rails is having a resurgence. I believe it is because Rails is dedicated to the one person dev team, perfect for startups, as well as the Rails 7 shift away from the need for React, the Rails 8 shift towards full support for PWAs, and the Hotwire Native extension which makes transitioning from PWAs to native mobile apps easy.
Another observation, Chime is just one of the Rails companies which went public recently. Figma is a Ruby company that has done the same.
SF Ruby held one of our meetings at Y Combinator because they are big fans of Ruby on Rails. Check out any one of Irina Nazarova's talks about the startups that are starting with Rails. Rails is having a resurgence. I believe it is because Rails is dedicated to the one person dev team, perfect for startups, as well as the Rails 7 shift away from the need for React, the Rails 8 shift towards full support for PWAs, and the Hotwire Native extension which makes transitioning from PWAs to native mobile apps easy.
Also, remember, Chime is just one of the Rails companies which went public recently.
In the real world, we have many businesses which will look at ones gov't issued ID, most bars for instance. We have other businesses which will record the information off ones ID, most dispensaries for instance. I will go into the first. I will not go into the second. Verifying my eligibility is one thing. Recording my data for later use is a very different thing. I can tell the difference in the real world because I can see the process. Online, it is impossible to tell. Providers can build a reputation for privacy, think Proton.
You say we are looking for solutions. There are better solutions, including privacy preserving solutions, which can work. We just don’t have any of those yet.
I agree, and I advocate for adopting such solutions. I'm definitely not a fan of sending my ID to an arbitrary 3rd party with no visibility into how it will be processed. I am confident that if verification becomes the norm, a good solution will become ubiquitous (whether that's Google's ZKP or something else).
But, dismissing the whole verification effort on principle because "it's the internet and it's inherently for adults" is silly and unrealistic, IMO (not that you were). It's just not the world we live in anymore, the internet is used by everyone, for everything, and we should build accordingly.
> a good solution will become ubiquitous (whether that's Google's ZKP or something else).
Believing that Google's solution will be truly ZK, interoperable, or good is similarly silly, unrealistic, and not the world we live in anymore. Unfortunately.
The move away from Scheme has always saddened me. The first thing we learned in 6.001 was abstraction and invariance. These are still the core of writing good software. I still use these principles every day. There is a purity to Scheme. It is a beautiful light-weight language anyone can learn over a weekend. It does nothing magical for you which means you get to / have to build everything you want and you must understand how it fits together.
I agree. I was taught Scheme and I later taught it. It was a much cleaner and suitable language for teaching computer science than Python. Students could completely understand the language and how it worked by the end of a semester.
Scheme is much closer to mathematics, which made it much more suitable for teaching strong mathematicians arriving without coding experience. It also made the hackers more rigorous and broadened their minds from the imperative "do this then that" mindset.
There's a notable difference between those first taught scheme and those first taught Python. Of course, both can go on to learning Python or FP or whatever. But that foundation needs to be there to teach truly great coding for most mortals.
Not all questions have an answer that will satisfy you.
In this case, it probably exists because it's technically interesting, and for no other reason.
Although I can totally image a roulette style game played by people who like that kind of thing: one link leads to something nice like puppy photos, the other leads to something disgusting.
My vote is 'any 1 election runoff system'[score, star, approval, ranked choice, ...]. Every 1ER is better than first past the post. It would be nice if vote nerds would shut the frak up about this one is better than that on. Open primaries; top 4 or 5 go through to the general; general uses any 1ER. Were I writing a law to put this in place, I would say we should revisit which 1ER after X number of years or Y voting cycles.
