It's interesting that they don't mention Kotlin Multiplatform or any sort of shared core logic between their iOS and Android apps. Seems like maybe the apps are fully independent codebases but with shared specifications and tests? They say that agents:

> Dramatically reduced the cost of maintaining parity between platforms through shared specifications, tests, and review checkpoints

I've used Kotlin Multiplatform on a mobile project built back before AI coding took off, and it was super nice to have shared core logic between the apps and there weren't really any downsides on the Android side, but on the iOS side it was definitely an extra layer that didn't feel fully native.

Speaking personally, JVM toolchain bits like Gradle being involved is a turnoff and has kept me away from KMP. Last I checked support wasn't really there yet, but I'd much rather go the other direction and use Swift Package Manager and the associated toolchain on Android.

I work on an open source app that uses a shared swift core for the iOS and android apps and I think it's awesome. I think having all your business logic in swift is great.

At work, we use react native, and although the upgrades and stuff are painful, I'd never give up the ability to ship over the air updates.

Max accounts get 15 daily runs included, any runs above that will get billed as extra usage.

Looks like I'm limited to only 3 cloud scheduled tasks. And I'm on the Max 20x plan, too :(

"Your plan gets 3 daily cloud scheduled sessions. Disable or delete an existing schedule to continue."

But otherwise, this looks really cool. I've tried using local scheduled tasks in both Claude Code Desktop and the Codex desktop app, and very quickly got annoyed with permissions prompts, so it'll be nice to be able to run scheduled tasks in the cloud sandbox.

Here are the three tasks I'll be trying:

Every Monday morning: Run `pnpm audit` and research any security issues to see if they might affect our project. Run `pnpm outdated` and research into any packages with minor or major upgrades available. Also research if packages have been abandoned or haven't been updated in a long time, and see if there are new alternatives that are recommended instead. Put together a brief report highlighting your findings and recommendations.

Every weekday morning: Take at Sentry errors, logs, and metrics for the past few days. See if there's any new issues that have popped up, and investigate them. Take a look at logs and metrics, and see if anything seems out of the ordinary, and investigate as appropriate. Put together a report summarizing any findings.

Every weekday morning: Please look at the commits on the `develop` branch from the previous day, look carefully at each commit, and see if there are any newly introduced bugs, sloppy code, missed functionality, poor security, missing documentation, etc. If a commit references GitHub issues, look up the issue, and review the issue to see if the commit correctly implements the ticket (fully or partially). Also do a sweep through the codebase, looking for low-hanging fruit that might be good tasks to recommend delegating to an AI agent: obvious bugs, poor or incorrect documentation, TODO comments, messy code, small improvements, etc.

I ran all of these as one-off tasks just now, and they put together useful reports; it'll be nice getting these on a daily/weekly basis. Claude Code has a Sentry connector that works in their cloud/web environment. That's cool; it accurately identified an issue I've been working on this week.

I might eventually try having these tasks open issues or even automatically address issues and open PRs, but we'll start with just reports for now.

0 7 * * 1-5 ANTHROPIC_API_KEY=sk-... /path/to/claude-cron.sh /path/to/repo >> ~/claude-reports.md 2>&1

Seems trivial.

A trivial way to rack up hundreds of dollars in API costs, sure.

But you can set up a claude -p call via a cronjob without too much hassle and that can use subscriptions.

Sure, now what happens if my laptop is asleep at 7am? Or if our scheduled build took an extra 30 minutes because of contention?

This is when you go buy a Mac Mini just to run the Claude cron job :)

I've been working on a toy Lispy language and self-hosting compiler that targets JS. My goal is to explore building a full-stack web framework with a template compiler similar to Svelte that runs minimal JS on the frontend.

https://github.com/iBelieve/knight

The Bible.

Mysterious Island (1874), Around the World in Eighty Days (1873), and other books by Jules Verne.

Books by James Fenimore Cooper.

The Sea-Wolf (1904) by Jack London.

The Count of Monte Cristo (1844) by Alexandre Dumas.

Oliver Twist (1839) by Charles Dickens.

We share some favorites.

20000 leagues under the sea by Jules Verne was my introduction to science fiction and I also enjoyed Mysterious Island (which overlaps, but is less science fiction).

I had forgotten James Fenimore Cooper, and I have forgotten almost everything about the books, but yes, these were in the school library too and I read them.

(we had no TV when I grew up so I read a lot, mostly books in the styles mentioned above but also historical books and fiction from the WWII, but obviously none of these are over 100 years old.)

Also the Bible, it might not be highly regarded here, and I'm obviously biased, but as someone who reads other texts as well I think a number of people here could find parts of it interesting, especially contrasting it to what school and others might have told you. (Spoiler: besides the endless listings of who was who that most people will learn to skip, the full version is also a lot messier than what anyone working in school or wanting your money will tell you ; )

Yes, unfortunately reqwest pulls in lots of dependencies, but I think you should be able to get a binary under 10MB if you compile in release mode using the --release flag.

Same here, Firefox 66 on Arch Linux.

What couchand said still applies to 1.0. So this should work:

    use actix_web::{web, App, HttpServer, HttpRequest, Responder};

   fn index(req: HttpRequest, info: web::Path<(u32, String)>) -> impl Responder {
       format!("[{}] Hello {}! id:{}", req.method(), info.1, info.0)
   }

Great to see actix-web reach 1.0. I've played with Rocket in the past and liked it, but ended up choosing actix-web recently for a production project because I don't want to rely on a nightly compiler for a production project. I'm only using actix-web in a small portion of a larger Rust project, but so far my experience with it has been quite pleasant.

First time I even tried to use Rocket, I couldn't get there Hello World thing compiled. I honestly don't know if it was my error or a nightly compiler incompatibility and that sucked.

For anyone looking for a hosted solution, https://surge.sh/ is super nice and simple without any of the complexity of managing the stack yourself. Deploying uses one simple command, and you get hosting and custom domains for free, though I believe SSL is paid for custom domains. (I'm not affiliated with Surge at all, just a happy user.)

I was actually wondering that myself: Is there interest in a hosted service? It'd be quite similar to (as many comments have suggested) Netlify and the one you linked to.

I was mostly going for a DIY solution since I wanted to "own" the bits being deployed while remaining as close to the infrastructure as possible. Providing a hosted service somewhat moves away from the DIY spirit; I suppose additional tools/UIs could be offered to simplify setup and deployment and still run everything directly on AWS, but at that point one might be inclined to just move to one of the other hosted solutions for the simplicity.