Nope.c – A web framework with a tiny footprint
nopedotc.com
Nope.c – A web framework with a tiny footprint
1–10 of 53 posts
Re: Nope.c – A web framework with a tiny footprint
#2Better use nxweb, this one isn't that secure: http://www.reddit.com/r/programming/comments/2bo44u/i_am_the...
Re: Nope.c – A web framework with a tiny footprint
#3This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main
I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
Re: Nope.c – A web framework with a tiny footprint
#4Looks great! You might want to fix the "node.c" that appears on a few pages (for instance the documentation), and limit the maximum value one can input into your factors calculator.
Re: Nope.c – A web framework with a tiny footprint
#5Looking at the source code : https://github.com/riolet/nope.c/blob/c883b11df78bb8115d5e51...
It tries to copy a buffer of 1024 byte (max) into a buffer of 512 bytes (by executing a request with an URL longer than 512 bytes).
It also runs 15 children process and use blocking socket, meaning that it's easily "DoS'able".
The overall code seems very "unsecure" and poorly designed.
Re: Nope.c – A web framework with a tiny footprint
#6"This webpage is not available"
Re: Nope.c – A web framework with a tiny footprint
#7This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
Yes, there are definitely huge speed gains possible and if you choose an implementation which is still interactive you get the benefits of both (I know one particular example in CL: teepeedee2, there are some blogs posts, e.g. http://john.freml.in/teepeedee2-c10k or so).
Re: Nope.c – A web framework with a tiny footprint
#8This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
They're completely static pages with no images; it's not hard to get that kind of speed. For example, sqlite.com seems just as fast to me.
Re: Nope.c – A web framework with a tiny footprint
#9This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
9.7k with everything inline can do that.
Re: Nope.c – A web framework with a tiny footprint
#10This site feels ridiculously fast. I've noticed that with other compiled frameworks too, e.g. CppCMS: http://cppcms.com/wikipp/en/page/main I wonder if it is just the lightweight HTML the websites use, or if there is really so much speed to gain from using a compiled language.
I tested this page because most of the site is too small to get meaningful comparisons:
http://nopedotc.com/gallery/facedetector
It is faster to load than a highly optimised page which is half the size running on a more conventional stack.
The initial DNS request was the biggest saving on time, though, weirdly enough, followed by the time to connect. I have no idea why this is, or how to minimise DNS request time in general.