https://www.retailbankerinternational.com/news/occ-grants-co...

https://www.linkedin.com/posts/mercuryhq_big-news-not-a-bank...

https://futo.tech/about

There are numerous examples of people needing a smartphone to do things in their daily lives. I’ve read compelling stories of people who ran into trouble after ditching their smartphone.

There are lots of parallels to the railroad monopolies. Choice is not as available as you say it is.

Here is the description for the Rails World 2026 Opening Keynote:

"Opening Keynote highlighting what's new in Rails, what's coming next, and where Rails is headed in the future."

DHH literally did not cover that. Not even close!

The first response in the conference chat described it as the "worst opening keynote possible to setup the Rails World conference." While someone soon disagreed with that, another guy later said he felt it undermined the later talks, and someone else said the Laracon conference had more about what the framework is doing in the AI age. He barely mentioned Rails. I get how he was excited about his experiments but I certainly wish he had focused more on what Rails is doing for this new era.

You said FAANG, so perhaps you're in California, a state that has laws regulating health insurance to an extent that make it unique in the USA?

An older relative had a very successful small conglomerate of businesses. One of them manufactured something costing close to $100 that Wal-Mart was interested in selling in its stores. After extensive negotiations, my relative told the Wal-Mart VP no because Wal-Mart was pressuring them to use cheaper parts that would make the product wear out more quickly. Wal-Mart didn't care because they'd be able to make the sales and then consumers would come back to buy again sooner, but my relative felt that was dishonorable. The VP said it was the first time a potential supplier ever walked away from him. They are notorious for their abuse of suppliers, and the ethical concerns are often very palpable. You might suggest this is simply market forces playing out, but we decided long ago that monopoly power often leads to a market we don't want to see in this country.

We the people get to decide what kind of society we want to live in. Their monopoly power means that in so many of the rural areas where they are, they might be one of the few viable employers. When people are poor, it's not so easy to just tell them to relocate to another geographical area, so it's easier for the entities benefiting from that to maintain the status quo at the expense of others. If we decide that for Wal-Mart to stay in business in the USA they need to pay employees more, with health insurance, then so be it. If they can't, then they can just go out of business and be replaced by a company that is able to navigate that balance better, offering pretty low prices while paying a bit more in wages.

I had always been good at grammar in high school, but this was a different world and I had no idea what I was in for. We spent the first two weeks discussing the differences between the and a, and the next two weeks on the differences between this and that, and the rest of the semester felt more abstract. It was quite illuminating for me.

And these are the biggest ads I've seen obscuring a webpage in a very long time!

Here's an archive of their momentous blog post:

https://forums.anandtech.com/threads/ie-update-to-debut-ahea...

They shipped a beta later that year, but the full release arrived in late 2006. That was 4 years since their prior release, an eternity in those days!

It's better to find out quickly if you can get traction rather than building something requiring more maintenance. For most bug fixes or enhancements, you make them in the Jumpstart Rails side and they should up instantly in the mobile apps without going through app review again! Most projects are not being built in companies the size of Shopify, so I caution anyone who wants to just get the project out there to use platforms that give them more leverage. And no, I'm still not a fan of low-code or no-code, because I know what it's like to have to maintain apps over many years.

Oh, and I still always warn clients to stay away from native mobile unless they absolutely need it, because even with AI, maintaining just a web app is still light years faster, and far more pleasant. I know from very, very, very recent experience that testing subscriptions is still annoyingly cumbersome in the flaky Apple and Google sandbox environments, and Stripe for web apps is night and day easier to test. Testing on mobile is better than it used to be, but sometimes when I'm waiting for builds onto a physical device or for confusing settings in App Store Connect or Google Play Console to take effect (or just fine where they've been moved to), I think about how a manager 20 years ago was telling me how slowly his development lifecycle was when he used to burn software onto ROM chips. So web is still the way to go, and native mobile only if you absolutely have to. And if you have tons of time or money, sure, start with plain native.

Edit: As a web developer for decades, I still find both Jumpstart iOS/Android and Flutter to be preferable to React Native.