Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cot: The Rust web framework for lazy developers

cot.rs

Post reply on HN
Print view View original

51–60 of 71 posts

Re: Cot: The Rust web framework for lazy developers

#51

Post by eklavya »

gwbas1c wrote: post #7

> ORM integration I don't trust a web framework that's opinionated about how I use my database. It's very hard to get a web framework right, and it's very hard to get an ORM right. Getting both right is nearly impossible. In a situation like this, try to be the best web framework you can be, and then gravitate towards whatever ORM(s) becomes popular. Take a look at Express for Node.js. It's my favorite web framework…

It's probably not for you, it is absolutely for me. I am looking for a micronaut for Rust.

There are many options to build your own thing on hyper | axum | tonic | tower if you want.

Re: Cot: The Rust web framework for lazy developers

#52

Post by johnisgood »

dlisboa wrote: post #42
echelon wrote: post #26

Earlier quoted context omitted.

> Rust already has several server frameworks The incredible proliferation of Rust web frameworks should be an almost blinding beacon advertising how well-suited Rust is for web backend development. The biggest takeaway that anyone new to Rust or new to Rust-on-backend should have: Rust absolutely rocks for backend development. It's getting a tremendous amount of attention, people are trying a lot of things, and it's…

> For anyone scared of Rust or the borrow checker: due to the nature of HTTP services and request flow logic, you almost never bump into it when writing backend Rust. I’d say for anyone worrying about it just use ‘clone()’ everywhere you can. If you’re coming from any interpreted language the performance and efficiency will just be so much better that it doesn’t matter.

clone(); )?; all that stuff is just meh.

Re: Cot: The Rust web framework for lazy developers

#53

Post by akkad33 »

ost-ing wrote: post #18
pimeys wrote: post #12

I really wish Rust projects would stop using the term "blazing speed". It is almost like a meme already. You can write slow code in Rust pretty easily, so speed is something extra. And I am a Rust developer... Seeing this term makes me cringe every time.

> And I am a Rust developer... Seeing this term makes me cringe every time. I write blazingly fast statically allocated Rust on my Arch Linux Thinkpad, btw.

If not a joke can you explain what is statically allocated rust

Re: Cot: The Rust web framework for lazy developers

#54

Post by johnisgood »

johnisgood wrote: post #52
dlisboa wrote: post #42

Earlier quoted context omitted.

> For anyone scared of Rust or the borrow checker: due to the nature of HTTP services and request flow logic, you almost never bump into it when writing backend Rust. I’d say for anyone worrying about it just use ‘clone()’ everywhere you can. If you’re coming from any interpreted language the performance and efficiency will just be so much better that it doesn’t matter.

clone(); )?; all that stuff is just meh.

I mean, who thinks using .clone() everywhere is such a good idea?

Re: Cot: The Rust web framework for lazy developers

#55

Post by SahAssar »

akkad33 wrote: post #53
ost-ing wrote: post #18

Earlier quoted context omitted.

> And I am a Rust developer... Seeing this term makes me cringe every time. I write blazingly fast statically allocated Rust on my Arch Linux Thinkpad, btw.

If not a joke can you explain what is statically allocated rust

It's blazingly fast and made with love.

Re: Cot: The Rust web framework for lazy developers

#56

Post by sgt »

parhamn wrote: post #31

I'm still surprised no one in the golang world has put together a Django type framework. While I like the bring-your-own unixy philosophy of this stuff in the go world; I still really loved django for quick decent applications.

And that's why Django is still a perfect choice for your web app. You can always create additional services in Golang

Re: Cot: The Rust web framework for lazy developers

#57

Post by airstrike »

iknowstuff wrote: post #28
airstrike wrote: post #21

Earlier quoted context omitted.

The README itself says it should feel familiar to Django, which it certainly does from a developer API perspective based on my cursory review of the guide I think Rails caters to a specific type of audience. Personally, I hate the idea of "scaffolding" my app. I'm fine just writing that plumbing code and seeing how all the pieces interact. And I never understand this "just accept the status quo" take. If we all did t…

So use axum and do whatever you want? Or better yet, hyper?

Why can't people use the tool they want?

Re: Cot: The Rust web framework for lazy developers

#58

Post by echelon »

johnisgood wrote: post #54
johnisgood wrote: post #52

Earlier quoted context omitted.

clone(); )?; all that stuff is just meh.

I mean, who thinks using .clone() everywhere is such a good idea?

It's a suggestion for beginners writing their first Rust program. You wouldn't do this once you feel comfortable with the language.

Re: Cot: The Rust web framework for lazy developers

#60

Post by maleldil »

RestartKernel wrote: post #37
graypegg wrote: post #24

Earlier quoted context omitted.

Ditto for "type safety". This always feels like reaching for onnnne more feature on these project hype sites. "I don't expose the public API as Any!" feels about on the level of "has documentation"... which they also pitch as a feature.

I personally like to explicitly know beforehand if a JavaScript or Python package comes with type annotations, which is not a given.

This is true. If I'm choosing a package to use, and among the options, there's one with annotations and one without, I'll use the one with annotations unless there's a glaring feature missing. A recent example was moving from tenacity to backoff for retrying.
Post reply on HN