HN user

philipov

6,212 karma
Posts1
Comments1,993
View on HN

Well, when was the last time you wrote machine code by hand?

... but then they went and changed what coding meant.

We've always been layering abstractions on top of abstractions. If we get to an abstraction that works well enough that you no longer have to dive down into the previous layer, we say we've solved coding, and change what coding means. Obviously LLMs aren't there yet.

Why would Trump's previous associations with the Democratic party prevent him from spiting someone else's associations with the Democratic party? That would require he not be a complete hypocrite. On the other hand, associating SBF with the Democrats makes them look bad. Why pardon an albatross around the neck of your enemies?

yeah, the useful thing about ublock isn't just that it stops ads from loading, but that it lets you remove unwanted divs. There are lots of unwanted divs that have nothing to do with ads, such as removing annoying Use Our AI buttons, or the Shorts section of youtube.

The future will certainly change things, but who can change the direction of a tidal wave? It will go where it wants, not where we want. The best a single individual can do is flee to higher ground.

Unless you happen to have a media empire at your disposal. Maybe then you can change the future. The problem is that those people are changing things for the worse.

It was already necessary to solve the problem of humans contributing infringing code. It was solved by having contributors assume liability with a DCO. The policy being discussed today asserts that, because AI may not be held legally liable for its contributions, AI may not sign a DCO. A human signature is required. This puts the situation back to what it was with human contributors. What you are proposing goes beyond maintaining the status quo.

This policy effectively punts on the question of what tools were used to create the contribution, and states that regardless of how the code was made, only humans may be considered authors.

From the foundation's point of view, humans are just as capable of submitting infringing code as AI is. If your argument is sound, then how can Linux accept contributors at all?

EDIT: To answer my own question:

    Instead of a signed legal contract, a DCO is an affirmation that a certain person confirms that it is (s)he who holds legal liability for the act of sending of the code, that makes it easier to shift liability to the sender of the code in the case of any legal litigation, which serves as a deterrent of sending any code that can cause legal issues.
This is how the Foundation protects itself, and the policy is that a contribution must have a human as the person who will accept the liability if the foundation comes under fire. The effectiveness of this policy (or not) doesn't depend on how the code was created.

You are falling into the trap of thinking there's a single monolithic being called Software Developers that has inconsistent opinions. In fact, you're observing different people with conflicting values.

I always understood it as advice for school children who don't know how to express themselves in writing and end up with a blank page. You are encouraged to imagine you're talking to someone to overcome the hurdle of translating thoughts into words.

Yes, perl is considered write-only because it is a mess of features that allow unhygienic programming habits to flourish - it is full of hard-to-trace magical behavior. Completely different than APL, which has had perl's write-only label applied to it by programmers not used to reading terse mathematical notation.