OSDev.org

Just as a matter of interest, do you actually have experience of working in the software industry?

iansjack wrote:Just as a matter of interest, do you actually have experience of working in the software industry?

No, nor do I intend to. I've seen code that comes out of "the software industry" and I've seen code that comes from independent developers, and needless to say that latter is always more efficient and easier to maintain than the former. You don't have to have worked in the software industry to know that the only HTTP response codes needed for 99% of use cases are 100, 200, 206, 301, 302, 303, 304, 403, 404, 418, 500, 503 and a generic "not implemented" handler for any others. I'm not saying that this will give you a full-featured, robust, standards-compliant web browser, but it will give you enough to get you started with something that you can actually use to browse the internet without worrying about proxies, gateways, authentication, caching, and a bunch of other stuff that you don't need.

That explains a lot.

iansjack wrote:That explains a lot.

I see you didn't actually read either of my last two posts properly.

I read both of your posts fully.

Opinions based on a lack of evidence or experience are not always valid.

iansjack wrote:I read both of your posts fully.

Prove it. Look at the last post, talking about web protocols.

One of my last HTTP pieces lists three status codes explicitly, of which one of them is not on your list. I can't delve into details because of an NDA. However it does prove to me personally that your idea of good code is distinct from company reality. I'm pretty sure the same process goes for iansjack when he said "that explains a lot".

In addition, I do not accept the unfair burden of proof to a party that demands it but refuses to participate.

Combuster wrote:One of my last HTTP pieces lists three status codes explicitly, of which one of them is not on your list. I can't delve into details because of an NDA.

So because of an NDA you can't tell me which HTTP status code is not on my list? How do I even know that your project fits the description of "enough to get a working HTTP client" (to which my list applies) and not "specialist software that needs to implement particular complexities of a standard"? Herein lies the problem with commercial software development, and why I hope to never get caught up in it.

Combuster wrote:However it does prove to me personally that your idea of good code is distinct from company reality.

Did I ever say that my idea of good code is code that doesn't implement a standard properly? No, I said that good code should be efficient, and shouldn't sacrifice efficiency for edge cases that are beyond the scope of the code. I also said that many OSdevers are likely to appreciate an overview of common protocols and formats in a way that they can implement to make their OS useful/interesting and as a starting point for developing more robust applications; I did not say that this is "good code" in an absolute sense (if there even is such a thing) but that it doesn't give the developer more work than is necessary for the scope of the project (where said scope is "play an MP3 file from my music collection on my OS" or "post to OSdev forums from my OS") and thus discourage them.

onlyonemac wrote:No, nor do I intend to.

I am greatly relieved to hear that.

onlyonemac wrote:I've seen code that comes out of "the software industry" and I've seen code that comes from independent developers, and needless to say that latter is always more efficient and easier to maintain than the former.

A ridiculous statement. One among many you have made.

gerryg400 wrote:

onlyonemac wrote:I've seen code that comes out of "the software industry" and I've seen code that comes from independent developers, and needless to say that latter is always more efficient and easier to maintain than the former.

A ridiculous statement. One among many you have made.

In what way is that ridiculous? Suppose I rephrase it then to "I perceive that the latter is always more efficient and easier to maintain than the former"? Now are you going to argue with my perception of things?