import asyncdispatch
import jester
routes:
get "/":
resp "Hello World"
runForever()
Command: nim c -d:release --opt:size file.nimThe size on my Mac is 349K and that's with very little tweaking.
import asyncdispatch
import jester
routes:
get "/":
resp "Hello World"
runForever()
Command: nim c -d:release --opt:size file.nimThe size on my Mac is 349K and that's with very little tweaking.
You can't draw whole conclusions between two languages with just one tiny command; even the OP, comparing a language to itself, ran a whole lot more in-depth analysis to figure out what costs were being paid where.
It is cool it’s that small so easily though!
1: shout-out to https://crates.io/crates/cargo-bloat which is very cool
I'm not saying we should draw conclusions based on just this comparison. But it is an additional nugget of information and an invitation for others to also give Nim a try when targeting embedded systems :)
I'm not sure Rocket is Rust's leading framework. It certainly looks nicer than some, but still requires Rusts's nightly build, IIRC. I'm sure that means a lot of people opt for something like actix-web, or just fall back on hyper. My impression is that Rust's users are pretty widely spread across the frameworks that exist, so it may not be that you picked the wrong framework, but that isn't really a "leading" framework yet.
Someone might jump in with better info on the usage rates than me and correct me though, since this is mostly observational on my part. :)
http://www.arewewebyet.org/topics/frameworks/
Also just for fun I did try out Iron, Actix-web, and Gotham, and they all put out pretty similar figures (iron&gotham bit smaller, actix-web bit bigger). I do feel like Rocket is being a good representative example here.
That being said, I wouldn't be surprised if Rocket would be bit more feature-packed than Jester.
Thanks for the leg work. :)
(Unless I misread your comment, and "RustEvStrFo" doesn't have the same negative connotation to you...)
Edit: if you look at the commenter's profile, you'll see that he does that really often, on threads talking about Rust, Go or C. I think the comparison to the Rust Evangelism Strikeforce holds.
Isn't that what the Rust Evangelism Strikeforce is known for?
In any case, I think being a core developer on something means a much higher bar for accuracy/relevance/general public behaviour when discussing it and its competitors: everything one says about the project is a semi-official representation of it. Certainly the Rust core developers try to be careful about conveying an accurate picture of costs as well as benefits when answering questions or correcting misconceptions[1]. That is certainly something I found weighed on my mind a lot when I was on the Rust teams: anything I said about it could become part of "the Rust project" (as an idea people have) itself.
[1]: One extra point is that, IME, this is often how Rust team members interact with social media: they won't be the first person to bring up Rust in a thread. Of course, it's fair to say that Rust has a bigger mindshare and more people outside the project team members will bring it up/compare to it than Nim, but one possible alternative approach to awareness is more whole threads (i.e. submitted articles) about Nim rather than just comments within threads about other technologies.
(To be clear, this is just a reply to the parent comment, I'm not trying to say the original Nim comment was "NESF"-ish or "RiiN".)
https://www.reddit.com/r/programming/comments/83n32i/the_def...
In any case, for that specific comment, see Steve's analysis in response to your ping:
> But a brand new account with three trolly comments is different than an actual Rust advocate. Just like I'd ignore our local anti-rust trolls, I'd also ignore any pro-Rust trolls.
Your comment on the other hand...