4 ms·

especially since you need to enable the cookie container functionality manually and you can override it by yourself

by merb 7y ago

Dolores12 7y ago
or use different language with good library that support 8-year old RFC.
- manigandham 7y ago
  C# is a language but .NET is a runtime and standard library. If this issue is really such a problem, you can use any of the dozens of open-source libraries available or just implement your own cookie container that follows this RFC in about a day. It sounds like you're picking on a strange issue to disparage .NET without any real experience in it.
  - Dolores12 7y ago
    No, i just didn't like the wording in the original post mentioning all 'modern workloads' , while ubiquitous thing like cookies in httpclient is still not according to 8 year old standard. Does it make any sense now?
    - manigandham 7y ago
      Modern workloads refers to the kind of applications commonly built today, like http/json/grpc webservices running in containers. And yes the HttpClient is modern. Your entire argument so far has been a single RFC issue that is labeled up-for-grabs because it's so minor and doesn't really affect anyone. Claiming the http functionality and the whole stack isn't modern because of it just doesn't add up.
      - merb 7y ago
        especially since cookiejar is kinda useless. you can't use it with more than a single server, anyway..
    - saberience 7y ago
      You are being over the top and quite frankly ridiculous. I've been using .Net Core in production since its initial release while working for a famous games company (which you probably heard of) and now for a multi billion dollar FinTech firm, and the whole time I have been using HttpClient or libraries using HttpClient for connecting to services/apis. If your whole reason for not using .Net Core is based around this weird and honestly unimportant edge case, all that tells me is that you have a strange bias against the framework for some other reason and looking to nitpick.
    - nbevans 7y ago
      That "8 year old standard" you linked to is just a draft and proposed standard. Nobody implements draft specs in production grade libraries/frameworks. Especially not Microsoft.

especially since you need to enable the cookie container functionality manually and you can override it by yourself

by merb 7y ago

especially since you need to enable the cookie container functionality manually and you can override it by yourself

Dolores12 7y ago

or use different language with good library that support 8-year old RFC.

manigandham 7y ago
C# is a language but .NET is a runtime and standard library. If this issue is really such a problem, you can use any of the dozens of open-source libraries available or just implement your own cookie container that follows this RFC in about a day. It sounds like you're picking on a strange issue to disparage .NET without any real experience in it.
- Dolores12 7y ago
  No, i just didn't like the wording in the original post mentioning all 'modern workloads' , while ubiquitous thing like cookies in httpclient is still not according to 8 year old standard. Does it make any sense now?
  - manigandham 7y ago
    Modern workloads refers to the kind of applications commonly built today, like http/json/grpc webservices running in containers. And yes the HttpClient is modern. Your entire argument so far has been a single RFC issue that is labeled up-for-grabs because it's so minor and doesn't really affect anyone. Claiming the http functionality and the whole stack isn't modern because of it just doesn't add up.
    - merb 7y ago
      especially since cookiejar is kinda useless. you can't use it with more than a single server, anyway..
  - saberience 7y ago
    You are being over the top and quite frankly ridiculous. I've been using .Net Core in production since its initial release while working for a famous games company (which you probably heard of) and now for a multi billion dollar FinTech firm, and the whole time I have been using HttpClient or libraries using HttpClient for connecting to services/apis. If your whole reason for not using .Net Core is based around this weird and honestly unimportant edge case, all that tells me is that you have a strange bias against the framework for some other reason and looking to nitpick.
  - nbevans 7y ago
    That "8 year old standard" you linked to is just a draft and proposed standard. Nobody implements draft specs in production grade libraries/frameworks. Especially not Microsoft.