GNU libmicrohttpd 0.9.57 Brings Significant Improvements

[phoronix]

Phoronix: GNU libmicrohttpd 0.9.57 Brings Significant Improvements

The libmicrophttpd GNU project is the C library that makes it easy to run an HTTP web-server as part of another application while being as small as about ~32k compiled...

http://www.phoronix.com/scan.php?pag...rohttpd-0.9.57

[uid313]

But can you really trust a daemon written in a volatile language such as C?

[[email protected]]

But can you really trust a daemon written in a volatile language such as C?

I know right? They should rewrite it in Go.

[tildearrow]

But can you really trust a daemon written in a volatile language such as C?

But can you really stop complaining about stuff not being written in Rust? (not everything written in C is bad)

Typos:

libmicrophttpd...
...Solarius

[waxhead]

But can you really trust a daemon written in a volatile language such as C?

Blasphemy! Languages comes and goes but C remains... If you write crappy software in C you don't understand it properly.

In other news... I have just been using libmicrohttpd for a project at work. It's great! Now I only need to compile the blasted thing on WinDOWNS syndrome and I got a very portable and flexible user interface!

[smitty3268]

I suppose this is probably pretty useful for routers and other embedded hardware where you want to throw up a web interface that's lightweight on the device.

[chilek]

But can you really trust a daemon written in a volatile language such as C?

When will you introduce your system kernel written in Rust?

[starshipeleven]

But can you really trust a daemon written in a volatile language such as C?

Yes. We can.

[uid313]

But can you really stop complaining about stuff not being written in Rust? (not everything written in C is bad)

You're right, not everything is written in C is bad. There is plenty of good software that we all love and use that is written in C.
Not everything needs to be written in Rust, example games need not to be.
But I believe that security-sensitive software such as daemons, parsers and decoders ought to be written in a safe(r) language.

Blasphemy! Languages comes and goes but C remains... If you write crappy software in C you don't understand it properly.

Yes, and the reality is that either people there lots of people who don't understand C or even when they really do understand C they still manage to do mistakes with it.
It is too easy to shoot yourself in the foot.
Look how proven insecure software such the X Window System and OpenSSL is.

Putting many restrictions inside a language can provide safety. But once you know why those restrictions are added and how to deal with it, you won't need those to be built in.
Besides, there are many projects written in C proven to be robust and safe.

It is too complicated for humans to code reliably in C.
There plenty of projects written in C that is proven unsafe too. Just look at OpenSSL, which is a cryptography project so it ought to be really reliable, but reality shows a different picture.
Maybe Linus Torvalds and Daniel J. Bernstein can code in C, but the reality is there lots of vulnerabilities in software coded in C.

When will you introduce your system kernel written in Rust?

I am way too stupid to write anything in C or Rust. Even if I could, I am way too stupid to write a kernel.
However, there is a OS written in Rust named Redox.

[DrYak]

I am way too stupid to write anything in C or Rust. Even if I could, I am way too stupid to write a kernel.
However, there is a OS written in Rust named Redox.

So you consider your self "way too stupid to write anything in C or Rust" but think that somehow this shouldn't stop you from debating about computer languages that you don't even understand ?