"At its core, Fresh is a routing framework and templating engine that renders pages as they are requested, on a server."

Whoa, that's wild. Rendering. Pages. On the server. The future is now! 🥲

deno.com/blog/fresh-is-stable

@132ikl the latter is more popular in Apple communities though

java, a boiler plate driven language designed for writing verbose object oriented instant legacy code

@rysiek late for the party, but I don't see anyone mentioning sli.dev/

I have used it recently and was very happy with the results. Will use it again for sure.

Guess who is writing a livechat app with Hanami, Hotwire and Iodine.

"It was an interesting talk, even scandalous."

I think this might be the best feedback I have ever received to any of my presentations.

The title was:
Entity Component System for "serious applications" [in Ruby]

@Corfiot @feditips I'm rather looking for migrating my account from Mastodon to Pleroma instance some day

@feditips whoa, cool that it's now possible to fully migrate the account. Does it only work between Mastodon instances or others (like Pleroma) too?

@andy_twosticks I don't know. I see they use Stoplight, so maybe when there is a problem with some server in federation it breaks the circuit and the problem grows?

Anyway, based on the blog post:

"Under normal load, our 25 Sidekiq threads would max out at around 300 jobs in the queue, which would easily be cleared well within a minute."

That's what? 5 seconds per job?

@andy_twosticks Not sure I understand. If you write slow jobs, they will be slow, no matter what job processing tool you use and increasing concurrency or resources (if they are limiting) is the only thing you can really do.

@andy_twosticks It sounds like the server resources were the problem, Sidekiq should not have any problems with this size of the queue (unless it runs out of RAM for Redis)

I briefly tried the official Mastodon app, but I still like Husky more.

Show older
Ruby.social

A Mastodon instance for Rubyists & friends