I think the ActionCable PR is here: https://github.com/rails/rails/pull/50979 -- it seems like it's going well, but taking some time. I think that should be interesting for some use cases, but we'll have to see if/how that makes deployment/operations more complex. For example, if you're better off with the bulk of your app running w/ threads on Puma, would you run the ActionCable stuff w/ fibers on Falcon? Or maybe you just have an app that's doing mostly streaming of AI API responses or something?
Anyway, I'd be careful about over-promoting Falcon/Async, even as one of the relatively few people that's running in a large-ish production app. In my case, I'm doing a LOT of hanging waiting on API responses from weather data sources, and I want to transform the JSON and do some data point conversion in real time. So even in my case, I think it's better for me to switch (see https://github.com/socketry/async-examples for me doing some experiments) because I'm often waiting on API responses (in real time) that can take 1-2 seconds (!) but then I'm still doing some heavy CPU work reading and writing JSON blobs. I saw a pretty good speedup with YJIT, so I think I'm not entirely IO bound, if that makes sense.
I think it's great to have more options for those of us that love Ruby, so we don't need to switch to Node.js or something else for this kind of work. But I think it's likely that existing Rails apps (and typical CRUD Rails apps etc) will probably want to stick with a thread-based model. We'll see how it all shakes out over the next couple years, and I think you're right that it's exciting stuff. Between all the work on YJIT etc, and the possibilities for Node.js-type or Go type use-cases being possible/reasonable with Fibers, it's a great time for Ruby!
I've been working from the British Library in London lately, and it's been great. If you're working at a library, though, please do consider making a donation. Sure it's free, but...
Ugh. The length of that article (and the reliance on Disqus for comments) is why I'm still using WordPress.
I'd use a hosted service, but I haven't found one that can properly import my posts and comments. Is there such a thing? I know Posterous is close, but I don't think they import comments.
I still love Mint, too. I wish someone would build a hosted version of something just like it. If you're thinking the same thing and want to team up, drop me a line ;)
The length of the article is in part due to how in-depth he goes, and in part due to how customised he wanted it. Realistically you could get a Jekyll site setup in ~10 minutes.
As to comments, on my Jekyll blog I opted not to bother with comments, but yeah, Disqus (or equivilent) is probably the best option. A possible second option would be to tell Apache to run all the .html files through PHP, and use PHP to add in a database-driven comments system. Sure, it won't be as fast as HTML-only, but it will still cut down the load time by not using any database queries for the rest of the site.
There are several reasons one may decide to use jekyll, but I think speed is the least important one. First, this is a solution for small websites and blogs. I don't see how a large scale website would be generated from static pages, anyway. Second, there are simple methods to cache wordpress content without resorting to static pages.
FWIW - I made "the simplest possible Wordpress theme" in an effort to understand what the bare minimum Wordpress theme requires (to get into their theme directory). You can see it here: http://wordpress.org/extend/themes/simplest
Anyway, I'd be careful about over-promoting Falcon/Async, even as one of the relatively few people that's running in a large-ish production app. In my case, I'm doing a LOT of hanging waiting on API responses from weather data sources, and I want to transform the JSON and do some data point conversion in real time. So even in my case, I think it's better for me to switch (see https://github.com/socketry/async-examples for me doing some experiments) because I'm often waiting on API responses (in real time) that can take 1-2 seconds (!) but then I'm still doing some heavy CPU work reading and writing JSON blobs. I saw a pretty good speedup with YJIT, so I think I'm not entirely IO bound, if that makes sense.
I think it's great to have more options for those of us that love Ruby, so we don't need to switch to Node.js or something else for this kind of work. But I think it's likely that existing Rails apps (and typical CRUD Rails apps etc) will probably want to stick with a thread-based model. We'll see how it all shakes out over the next couple years, and I think you're right that it's exciting stuff. Between all the work on YJIT etc, and the possibilities for Node.js-type or Go type use-cases being possible/reasonable with Fibers, it's a great time for Ruby!