Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ddevault
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
63 ms
·
691.
▲
by
ddevault
6y ago
Even if we run the same math with 7 out of 10 bugs being memory safety related, and assuming that Rust prevents all of them, those same example programs end up with 30 bugs in Rust and 10 bugs in C. There's another argument I could m
692.
▲
by
ddevault
6y ago
Nice finds. I would agree that that's more arguably a bug in libc than in doas, but also note that the startup code for any language has to consider this case. As far as theoretical operating systems are concerned, this is a consequenc
693.
▲
by
ddevault
6y ago
More CVEs can also sometimes be a function of exposure; Joe Random's program probably has no CVEs but that doesn't mean it's more secure than Jane Popular's tool. In this case, however, both sudo and doas have sufficient
694.
▲
by
ddevault
6y ago
Adding features because they solve a specific use-case is grossly irresponsible. Solving a specific use-case is only one of many criteria that needs to be met for a feature to be justified. Others include "is it in scope?", "
695.
▲
by
ddevault
6y ago
>I think you'll find in disagreeing with the comment on logic errors you just said the same thing the comment did about logic errors. I think you'll find that my comment explicitly acknowledges this and expands on it with anoth
696.
▲
by
ddevault
6y ago
>But if sudo were written in Rust, it could have the same level of complexity and not be vulnerable. This is not true. Complexity breeds bugs, including security bugs, and memory safety doesn't change that. Your example is a good on
697.
▲
by
ddevault
6y ago
No, complexity strikes again. I haven't used sudo in years, preferring to use doas now. Its essential code is less than 500 lines and it does everything I've ever used sudo for, and that includes much more than `sudo <runupdate
698.
▲
by
ddevault
6y ago
Quote from said article: >The ruling had a major impact on campaign finance, allowing unlimited election spending by corporations and labor unions and fueling the rise of Super PACs. Later rulings by the Roberts Court, including McCutche
699.
▲
by
ddevault
6y ago
What the fuck is Google doing donating to members of Congress in the first place? It should be a crime. It was a crime, until Citizens United. Explain to me how this isn't bribery, plain and simple.
700.
▲
by
ddevault
6y ago
Flagging is entirely broken on Hacker News, which is a problem I've pointed out to the moderators before. It's basically a super-downvote and allows people to censor opinions that they don't like. Comparing with downvotes: -
701.
▲
by
ddevault
6y ago
Breaking changes to languages, APIs, operating systems and libraries are not putting lives at risk. All of the above have expressed their compatibility guarantees in clear terms. No one advertises Python as suitable for life-critical applic
702.
▲
by
ddevault
6y ago
And sourcehut! https://sr.ht/projects
703.
▲
by
ddevault
6y ago
This only matters if you care about propiretary platforms like Windows and Mac. And you should not care!
704.
▲
by
ddevault
6y ago
Aye, there are two definitions. They are not reliant on each other. The word "lead" also has several definitions, among them: the metal, and the thing you use to walk your dog. A dog needn't be involved in the former, nor the
705.
▲
by
ddevault
6y ago
Strong, perhaps, but not broad. Open source doesn't work like this. What you argue for may have merit, but it's not open source. Just give it a new name and allow it to flourish under that name. I've recommended "fair so
706.
▲
by
ddevault
6y ago
https://www.merriam-webster.com/dictionary/exploit Definition of exploit: transitive verb 1: to make productive use of : UTILIZE exploiting your talents exploit your opponent's weakness
707.
▲
by
ddevault
6y ago
The key insight is that FOSS doesn't make any attempt to answer that question. It has nothing to do with how you get paid, and concerns itself only with the matter of distribution and rights. It's still up to the author to come up
708.
▲
by
ddevault
6y ago
We still have Python, but use few to none of its OOP features. Almost all of our classes are just there to rig up SQLAlchemy (which totally blows, I regret using it). We're moving away from Python in general.
709.
▲
by
ddevault
6y ago
Not going to enable javascript and/or pay money to read this very hot take, but I can definitely agree that OOP is terrible. And, furthermore, spelled backwards it is "POO". Don't use Medium, please.
710.
▲
by
ddevault
6y ago
I have already repeatedly stated that they were within their legal rights, including in one of my replies to you. I assumed this was a given. When I said they "can't", I did not mean "can't (legally do this)",
711.
▲
by
ddevault
6y ago
>I don't agree that they are not open source Sorry, you are simply wrong on this matter. It's not a subjective issue, it s a statement of fact that these licenses are not open source. There was a recent attempt to change this w
712.
▲
by
ddevault
6y ago
>the community helped build the brand and recognition of ElasticSearch and the software itself. Elasticsearch accepts patches from the public, albiet accompanied by a signature on the CLA that grants Elastic unfettered rights to do any
713.
▲
by
ddevault
6y ago
I don't think that these licenses are relevant. If we can agree that they are not open source, then we can agree to the point I'm trying to make: changing from an open-source to a non-open-source license is a significant change wh
714.
▲
by
ddevault
6y ago
>Copyfarleft[1] has been discussed for almost a decade now and has spinoffs like Copyfair[2]. But not in the context of open source. At no point have any of these licenses made a successful bid for qualification under the OSD.
715.
▲
by
ddevault
6y ago
I agree that this should be a lesson about licenses and especially CLAs, which I address directly in the article. That doesn't prevent me from criticizing Elastic for what they've done.
716.
▲
by
ddevault
6y ago
>Or are there any other consequences of upstream doing this vs. someone else? Yep: the community is built around the upstream project, and has a lot invested in their continued existence as an open source entity. This move will force the
717.
▲
by
ddevault
6y ago
It doesn't actually have anything to do with the choice of the Apache license, though you would still be correct in that case. Elastic made users sign a CLA which signs over contributor rights for distribution without any conditions wh
718.
▲
by
ddevault
6y ago
Elastic explicitly addresses the question of open source in their FAQ: https://www.elastic.co/pricing/faq/licensing#does-this-mean-... Mongo has tried to get the OSI to approve it, but ultimately withdraw the lice
719.
▲
by
ddevault
6y ago
AGPL does not restrict how you use the software, rather, it requires that you offer the same freedoms to your users as the original license offered to you. You can sell AGPL'd software.
720.
▲
by
ddevault
6y ago
There's nothing wrong with using a licensing model like the one you describe. If don't want Amazon to use your software, then license it as such, whatever. However, that software is not open source. Furthermore, if you change a
More ›