> So why don't we implement TCP separately in each application, the way it's don... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

lmm on Oct 6, 2023 | parent | context | favorite | on: HTTP/3 adoption is growing rapidly

> So why don't we implement TCP separately in each application, the way it's done with QUIC?

Because library/dependency management sucked at the time, and OSes competed for developers by trying to offer more libraries; on the other side we were less worried about EEE because cross-platform codebases were rare and usually involved extensive per-OS code with #ifdefs or the like.

I don't think we would or should put TCP in the kernel if it was being made today.

topspin on Oct 6, 2023 [–]

> Because library/dependency management sucked at the time

It still sucks. Thus Docker et al.

lmm on Oct 6, 2023 | [–]

Only in Python (and C/C++). No one else wants the overheard of Docker.

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact