Hopefully someone rolls this into a framework, not just a pattern/architecture. The beautiful promise of Rails is "convention over configuration." In contrast, the workflow in the post involves a heavy degree of configuration and customization.
Interesting question whether this violates the Ruby on Rails trademark. When someone made a clothing company called The South Butt, The North Face sued and had a pretty decent case. They settled so no court decision, but seems analogous.
Risk of confusion is the overall standard but that doesn't always mean what you think it does. In a case where it's two products competing in the same market (i.e. two web frameworks, assuming that someone develops this into an actual framework), similarity of the marks is usually enough to establish risk of confusion.
And generally, risk of confusion doesn't just mean that people will literally confuse the two products as identical. It's also about the risk that someone would think there is an affiliation or other connection between the two products.
Finally, this would not be trade dress. It's about similarity of the product name, so just a plain trademark.
This is a pretty cool article for web stuff in Rust, definitely getting more in depth than what I know of Rust and Rust Web stuff.
I would like to see something in this article to address the > 1 second index.html response time that the cloak website seems to have. Are there caching options for views?
Maybe I'm missing it, but there seems to be no mention of i18n. That's a pretty integral part of any kind of serious website or one that might become one, but it's for some reason often just skipped.
Haha love the name. Sad to see it’s not an actual framework. For those looking for something more akin to a framework, try create-rust-app [1]. I plan to add a templating plugin soon!
I'd love to see an additional section on unit testing -- if we wanted to write some assertions on our async http handler that queries the database, what would that look like? Would we need to structure the code differently in order to test it?
It looks like the article describes a series of conventions for Nails projects to follow, and I think that still provides value. If it was packaged up for you (or even a template), would it be missing any functionality you would expect from a framework?
