Comment by ImPostingOnHN
6 days ago
> Make points. mAnY lAyERs aside if it doesn’t actually do anything you have not ported anything.
You might consider reflecting on this long thread which seems to be solely about your personal definition of the word "port", and arguing with others that the definition should be what you say.
Particularly because you're now stooping to insulting other HN posters over one technical definition of one word.
I am not redefining what a port is – but you are
No amount of whining is going to change anything.
The only thing that would change my opinion is if it actually worked.
And I don't think I was being insulting at all.
What I replied to:
"pretty clear you don't know well enough what you are talking about" is the real insult in this thread, which is what I called out :) Those statements are so boring and don't prove anything. Anyone can say "You don't know what you are talking about" but he hasn't proven anything. It's just an empty insult.
Making letters lower/upper to stress emphasis in a reply to that is part of conveying that.
You haven't changed my mind at all so far, I still think this doesn't qualify as a port.
Question for you: What would you use this project for in production? How could I replace k8s today with this browser port?
> I am not redefining what a port is – but you are
> You haven't changed my mind at all so far, I still think this doesn't qualify as a port.
as it turns out, I'm not actually interested in debating over the meaning of a word, or convincing anyone to change their mind on it
> K8s doesn't run containers, container runtime environments do.
> K8s sits on top of those and orchestrates them.
> I'm not actually interested in debating over the meaning
Ok.
Did you know that k8s came after containerization, and means nothing without it