5 ms·
Rust on Nails: A full stack architecture for Rust web applications
- Crabber 5y agoUnless I'm missing something this article just appears to be a tutorial on how to use existing web libraries together, not a framework.
- danappelxx 5y agoIt 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?
- neura 5y agoIIRC this is how TurboGears started out.
- yashasolutions 5y agoI love the name, might not be a real framework but the name is awesome. Someone make it a framework.
- cies 4y ago> might not be a real framework so what's lacking? i'd say it already beyond rails 1.0 :)
- legalcorrection 5y agoInteresting 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.
- paulryanrogers 5y agoTrade dress should only apply where there is a real risk of user confusion. Doubtful anyone would confuse this with ROR.
- legalcorrection 5y agoRisk 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.
- throwaway81523 4y agohttp://www.coboloncogs.org http://www.coboloncogs.org is still going strong ;)
- turnsout 5y agoHopefully 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.
- cies 4y ago> not just a pattern/architecture I'd argue that the "pattern/architecture looking frameworks" show a higher degree of loose couple and are thus better.
- radicalriddler 5y agoThis 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? Otherwise, it looks clean.
- waf 5y agoI'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?
- lionside 5y agoHaha 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! [1] https://github.com/Wulf/create-rust-app https://github.com/Wulf/create-rust-app
- viccuad 5y agoNice conventions! Would be cool to have the frontend be wasm-compiled rust instead of typescript.
- Valodim 5y agoMaybe 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.