copergi

12 ms·

31.
by copergi 12y ago
Unfortunately no.
32.
by copergi 12y ago
It is the least painful OS that still has good performance and scalability. I would use openbsd if it weren't for the fact that it is 50% slower and is basically useless on SMP systems (which is everything now). FreeBSD might as well
33.
by copergi 12y ago
I have in fact read them. I have even been very explicit and clear about my reading of them in the hopes that you will either understand what I am saying, or correct my misunderstanding. It is unfortunate that you wish to do neither. I m
34.
by copergi 12y ago
>BSD-license can be revoked by the copyright holder you know. No it can not. Someone can stop releasing their previously BSD licensed code under the BSD license, but all the existing copies people got under the BSD license are still gov
35.
by copergi 12y ago
>I've used awk extensively and am aware of everything you've told me. I never said awk was analogous to sed, they're quite different, which is why you'd use both, as I mentioned. I can't see any way to parse your
36.
by copergi 12y ago
>Which has nothing to do with what I asked about my freedoms as a user. Yes it does. The hypocrisy inherent in this line of reasoning is that the GPL exists specifically because the distinction between "user" and "develop
37.
by copergi 12y ago
>Can you explain to me how my computing freedom is enhanced by using a binary that's licensed under the Free BSD licence without the source being released? That isn't a thing. I find it hard to believe you are genuinely as con
38.
by copergi 12y ago
>This was brought nowhere better to the front than in this video https://www.youtube.com/watch?v=Nbv9L-WIu0s where they showed that the tools written because gnu tools were too big when measured in a running computer tak
39.
by copergi 12y ago
You might want to learn awk and rc before making claims about them. In particular, awk is significantly more powerful than you seem to realize, it is not analogous to sed at all. It is a specialized programming language for manipulating t
40.
by copergi 12y ago
>and using two languages (bash and awk) is more complex than one. If the two languages are combined still simpler than the one language, then it is not more complex. Note that bash is not what you would be using if following his lists.
41.
by copergi 12y ago
>Also wtf is wrong with NetBSD? It is a bit questionable to have netbsd in there since it isn't that bad, but I would assume the rationale is "it is more complex than openbsd".
42.
by copergi 12y ago
>Yes, giving users even a smidgen of freedom like the GPL does is harmful The point is that it does not give them enough freedom. Notice how "public domain" is in the less harmful category? And all the licenses in that catego
43.
by copergi 12y ago
>Sure I'm not perfect But your reasoning assumes you are. You do make these mistakes. Everyone does. And languages that prevent them are not dulling your tools, they are putting handles on them. Insisting that you need to work w
44.
by copergi 12y ago
>YAGNI (You Ain't Gonna Need It) in specific comes from Extreme Programming, which is big on engineering discipline How is extreme programming even remotely related to engineering discipline? It is a bunch of randomly tossed togeth
45.
by copergi 12y ago
>Are there any situations where you wouldn't be able to find bash in /bin/bash? Basically everything that isn't a typical gnu/linux distro or osx. Bash is not a standard tool, it is a gnu specific shell. Posix
46.
by copergi 12y ago
It has nothing to do with cynicism. This is literally taking an existing industry, and slapping a new name on it to sell products, consulting, etc. Go look at any of the current product's websites. Which ones demonstrate an understa
47.
by copergi 12y ago
Usually worse, it seems most people use chef or puppet. I understand what you are saying, but I am saying I believe otherwise. Operations has always relied heavily on automation. We managed several thousand unix machines with 3 or 4 peop
48.
by copergi 12y ago
>The bottom 60% ... left the industry I wish. They are still here and still copy+pasting commands they don't understand. The entire linux world is still dominated by these people. The whole "howto" culture is still very
49.
by copergi 12y ago
>I don't think most developers have the capability to be sysadmins or QA. No, but they tend to think they can.
50.
by copergi 12y ago
The problem is there's as many ideas of what "devops" means as there are people saying "devops". The concept of devops as you just described it makes absolutely no sense to me for example. Operations has always be
51.
by copergi 12y ago
I think it will require a bit of tweaking, but I would expect the other BSDs to adopt it once it is reasonably complete.
52.
by copergi 12y ago
>How about adding "completion of our manpages" That is pretty much a given. OpenBSD considers deficiencies in documentation the same as deficiencies in the software. >or "making our website less shitty" OpenBSD de
53.
by copergi 12y ago
>Is it guaranteed that this fork will be used in OpenBSD? It already is used in OpenBSD. The changes are being made in the OpenBSD source tree.
54.
by copergi 12y ago
>they care about usability and simplicity. But this is at odds with your previous observation, that BSDs have low adoption. They are vastly more simple than typical linux distros, a fact that linux users complain about when trying out a
55.
by copergi 12y ago
I can't tell if that is the most subtle trolling I've seen since the 90s, or if you are seriously saying "yes I know I was lying, but I am still lying so it is cool".
56.
by copergi 12y ago
>On current hardware, RPC is expensive no matter how you optimize You mean IPC? While hardware support could make it faster, it is already plenty fast. The whole "L4 only introduces 3% overhead" thing is pretty old news at th
57.
by copergi 12y ago
>What we need is None of the stuff you mention. Openssl is not in need of funding, or more eyes. Even the developers say more money won't fix it. Openssl is broken. It is so far gone that it is not salvageable. It needs replace
58.
by copergi 12y ago
>but they're a concept ahead of current hardware design How so? >they don't really bring the flexibility typically promised. Which ones have you tried?
59.
by copergi 12y ago
But you are falsely implying that the intent "be good for big projects" is opposed to the concept of "having useful abstractions". It is not. Go fails at being useful for big projects precisely because it fails to have
60.
by copergi 12y ago
Yes.

More ›