bradgessler

Exactly. iPadOS can’t run a Unix shell and docker, but macOS can.

I don’t even want touch to work on the iPad running macOS. Just let me run my own input hardware against it.

I want macOS on my iPad Pro so I can plug my Moonlander keyboard into it and have a “laptop” that doesn’t destroy my wrists.

MCP has been a weird ride. I built https://terminalwire.com before MCP was a thing to make it way easier for people to add a CLI/TUI to their web apps/SaaS.

Then MCP comes out and AI explodes, sucking all the air out of the room for non-AI tools.

Now it seems like AI can work with CLIs better than MCP, so I’m tempted to slap AI integration all over the project to better convey the idea.

It’s crazy how quickly MCP has run it’s course and watching an entire ecosystem rediscover things from first principals.

I just setup private video for https://beautifulruby.com and can confirm the trickiest part is setting up and hosting HLS.

I extracted a RubyGem at https://github.com/beautifulruby/hls that I use to point at a folder full of videos, then my scripts converts them into HLS and uploads them to a private Tigris S3 bucket. I then have to rewrite playlists from the server with pre-signed S3 URLs.

It’s not that it’s difficult per se, but it does require a meticulous attention to detail to put all the pieces together.

A few things:

https://terminalwire.com streams a TUI/CLI from web apps without having to build an API and

I recently finished 45 videos at https://beautifulruby.com/phlex, so now I’m talking more about them and

Updating https://sitepress.cc to work with Rails 8.1 and thinking about another set of videos for it at https://beautifulruby.com/sitepress.

Quite the plot twist there

I’m surprised 1Password isn’t trying to get into this game.

Imagine a browser that lets people define sandboxes and scope credential that an LLM may access to complete certain tasks?

I’d love to have a browser download all of my utility bills for taxes. I’d setup a browser, limit it to a few URLs, give it access to a few credentials, and then let it rip.

Shoot me an email, brad@beautifulruby.com

I recently finished shooting a video course for Phlex and I found that naming the Turbo Stream section at https://beautifulruby.com/phlex#unit-5 was the most challenging because of Turbo Streams and Turbo Broadcasts.

My recommendation: Turbo Drive & Pagemorphs are what most people should use for most problems. Drive reduces flickering between page loads and Pagemorphs list to channels on the server to reload the page if something changed.

I think Turbo would benefit from positioning itself more closely to Rails and simplifying the terminology. If you look at the https://hotwired.dev website, you won’t find Rails and you’ll find a bunch of words like Stimulus, Drive, Streams, Broadcast, etc. The docs aren’t entirely coherent either.

I keep sending links like this to AWS when their sales reps reach out, then I ask for a discount, and they never get back.

I love that this was completely overshadowed by "Zed works in Windows!"

This team ships so much that if they sold an LTS product, it means they'd support the release for 24 hours.

I’m surprised none of the frontier model companies have thrown this test in as an Easter egg.

Imagine the UI we’d have if somebody gave them jellybeans instead.

There's a picture floating around out there of the Apple design team putting actual physical pieces of glass over icons that they printed out. What's funny (not really) is how much more readable that paper would have been if they simply removed the glass.

If you can’t make it to this conf and live in the Bay Area, you should checkout the monthly SF Ruby meetups.

But you really should go to this conference.

When we did annual pen testing audits for my last company, the security audit company always offered to do phishing or social engineering attacks, but advised against it because they said it worked every single time.

One of the most memorable things they shared is they'd throw USB sticks in the parking lot of the company they were pentesting and somebody would always put the thing into a workstation to see what as on it and get p0wned.

Phishing isn't really that different.

Great reminder to setup Passkeys: https://help.x.com/en/managing-your-account/how-to-use-passk...

It's bittersweet.

The suckiest thing is if the fork pans out, it will look a lot like JS: "Which package manager do you want to use?". That beautiful simplicity of "just use bundler and ruby gems" will be gone.

One thing I will give them massive credit for is walking-the-walk. There wasn't really that much complaining for the aggrieved maintainers of RubyGems. They made a public statement describing their grievances, then quietly got to work on a fork. Taking on a fork of RubyGems seems impossible and foolish, but they now have a non-zero chance of succeeding because they're doing it.

Most people I've talked to inside of big orgs are going to stick with the "safe boring" thing, which will probably be RC backed by Shopify. They will probably throw security bureaucracy at the problem, which will make SOC 2, ISO 270001 auditors. I don't think we'll see a lot of innovation coming from RC since the executive director is non-technical and has demonstrated a very ham-fisted approach to running the organization that seems to be out of touch with developers.

On the flip side, I think if gems.coop takes off, it will be because it's a "better mousetrap". One of the people behind it, André, is working on https://rv.dev, which promises to be a faster, "all-in-one", tool for managing ruby versions, gem dependencies, and even has an "npx-like" run this from from the CLI, the right version of Ruby will install, the gems will install, and it will run. That's a much better DX that I could see developers going for.

I've seen discussions on the periphery of adding namespaces to gems, bringing in checksums, and overall taking a more aggressive technical approach to security. I could see that "winning" over a long enough timeframe if RC continues on their current course.

From a fund-raising PoV, I'm starting to put together the clues that André believes organizations with the means to pay for OSS infrastructure should pay for it. I think I agree with this point-of-view and think it's a path for funding that's more transparent than "A group of donors". I hope we start to see infrastructure run in a manner where the costs are accurately estimated, then divided by the number of companies with the means to pay to arrive at the price.

There's absolutely on consensus on my final point, but I think the root cause of RC's catastrophic failure is having too much of a concentration of funding from a few donors. If you're new to this drama, a major donor pulled funding from RC because they didn't ideologically agree with a conference guest. The details are out there if you want to dive into it, but to keep this thread on point, I hope Ruby Co-op figures out how to spread out their funding model across 100's or 1000's so this doesn't happen again.

Yeah, something that’s messed up that they don’t think is messed up is running `fly console` fires up another instance, which isn’t attached to the same volume, so you have to run `fly ssh console —pty`

It’s certainly not intuitive. It would be awesome if they sweat these details, but their deal is “here’s a bag of sharp knives”, which is good for some use cases.

The DX for deploying SQLite apps to Fly.io is rough. I'm a few hours into trying to get a production Rails app booting, but running into issues getting the database to initialize, migrate, and become writable. The root of my problem was the eager loading of a gem I wrote, but there were several layers of runners above it that made it hard to diagnose.

I wish they'd put a bit more effort into the DX here, but it probably doesn't make much sense from a biz PoV since big customers aren't going to be running these kinds workloads.

Curious if anybody here is deploying SQLite apps to production and what host they're using?

I changed the layout of my Moonlander's to roughly match that of my MacBook and it works reasonably well.

It’s also the SF Bay Area, which h has a very high cost of living. That context is important. Also the article was corrected, the rate was $150.

I have done that! Reminded me of some dunes I scaled in Jordan.

I need to do that next time I’m driving between Chicago and Michigan. I haven’t seen the dunes there yet and I bet it’s incredible.

Unfortunately the dunes and lake are not visible from that stretch of I-94.

Southern Indiana is another beautiful part of the state. It's mostly rolling hills with lush green forests and farms.

There’s a lack of transparency playing out compounded by a poor job rolling out would should be the equivalent of boring corporate security bureaucracy.

Usually when this kind of stuff is rolled out, it’s agreed upon in some form and documented. Then when people are surprised, it’s a matter of pointing to the section in the doc that’s relevant and everybody goes on their way.

From the outside it appears this had none of that, so people are understandably surprised, sad, or angry. Since there’s a lack of transparency, people are filling in the blanks.

No, I'm saying there's a lot of people who won't even know this happened. Fewer will know that it happened, but they'll view it as a scenario where the ends justify the means.

I'm on the record saying RC did a poor job rolling out these changes and treated the maintainers poorly.

There will be a lot of amazing Rubyists that leave, which is terrible, but it won't be "the shadow of a community left" because there's way too many people who depend on it to feed their families.

There’s been a ton of that, yes, but for most people who are building applications and websites with Ruby, it’s been stable, productive, and prosperous.

How has it been “eating itself alive”?

I was 3 miles from the epicenter. By far the strongest I’ve felt since I moved here 15 years ago. Hard to imagine what a 6+ would be like on the Hayward fault.