3 ms·
except for the fact that you shouldn't have to write your own server?
by meesterdude 9y ago
except for the fact that you shouldn't have to write your own server?
- pebers 9y agoWhy not? Plenty of languages don't come with one built in at all, or not one widely used in production (e.g. Python's http.server, there are a heap of other Python web servers out there).
- codegladiator 9y agoThey count 24 lines of code as "infuriating amount of code to write". Why do you think they would interested in writing a web server ?
- meesterdude 9y agoTo be fair, 24 lines for something you know should be doable in only a few (or one!) is pretty darn frustrating.
- codegladiator 9y agoI was counting less the 50 lines as "few lines".
- meesterdude 9y agowhen you set out to solve a particular problem, do you really think its a worthwhile use of your time and effort to create a webserver? Mind you i'm not talking so much about "built-in" webservers than I am about reusing an existing, battle tested one from a 3rd party (e.g. OSS) so you can focus on the actual problem your trying to resolve.
- pebers 9y agoIf the problem I'm trying to solve is "I want a better webserver", then yes :) That's a little tongue-in-cheek, but I assume is more or less the motivation behind all web servers in use today; otherwise we'd all be using httpd or something.
- meesterdude 9y agoYes, if you want to build a better webserver, go right ahead. But I think we're in agreement, that you shouldn't be reinventing wheels that you are not purposefully trying to reinvent. If we always started from scratch, nobody would get anything done.
- lobster_johnson 9y agoBut that depends on what you're trying to accomplish. It's intended as a high-level, general-purpose server. It will always lack features if you go advanced enough.