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

I agree completely, and yet I would still prefer language to be used consistently.



I think the "information want to be free" crowd is very consistent. They want the information to be free. They don't want artificial scarcity.

Sure they'll use IP as a means to an end, but that doesn't mean they believe IP is a good idea in general. It's just one of few tools that exist to solve it.

In an ideal world all software would be forced to be FOSS, and we'd have to come up with ways of funding it that aren't based on artificial scarcity.


It seems like a bit of a strong restriction to have in the law that if I distribute an executable (which people may reverse engineer, modify, redistribute as they wish) that I am obligated to provide the source code upon request.

Like, what if I want to release a rather difficult puzzle in the form of an obfuscated executable and provide a reward to the first person who solves it? If I’m required to release the source code upon request, then that kind of spoils the puzzle. (Sure, I can say that anyone who gets the source code this way is ineligible for the prize, but how could I tell?)

This is of course a somewhat silly and niche edge case. Still though, it doesn’t seem natural/appropriate for a law would prevent such a thing.

Whereas, agreeing to only distribute modifications I make to some software written by others if I’m willing to distribute the source code to my modifications, well, that would just be an agreement I would be making, and seems unobjectionable.

Though, I wouldn’t really claim that all IP is illegitimate. I think many IP protections go way too far and last too long, but, I think some amount of copyright and patents is probably a good idea, though for a much shorter duration. So maybe I’m not really in the camp being described.

I think the freedoms described in the GPL are good.

I guess one alternative could be to say that all software written “for a useful purpose” (or something like that) has to have the source code made available, and that could handle the puzzle case I mentioned?

It does seem important to avoid the case where one needs to use some software for something but is prevented from modifying it due to not having the source code.

So… maybe if one is only required to provide the source code if someone could reasonably be described as “needing” the software for something? (E.g. if you “need it in order to get your printer working”, or the like.)


The puzzle case is no different to how you can't sell somebody a rubiks cube without allowing them to "solve" it by taking it apart and putting it back together.

You can make a physical item intentionally hard to work with or modify, but I see that as a shortcoming of our current legal standard—that's why we need some kind of "right to repair" framework. Requiring people to distribute human-readable code alongside software follows the same underlying philosophy as physical "right to repair" requirements.


I wasn’t thinking forbidding them from decompiling it or anything. I don’t think any rights are violated if government doesn’t issue any further copyright protections (even though I don’t think this for the best).

I am not saying that the puzzle author should have any legal authority to restrict people from disassembling the puzzle.

I’m just saying that the government shouldn’t compel the puzzle designer to distribute disassembled versions of the puzzle.

If other people want to take apart their rubix cubes, they’re free to, I just shouldn’t be forced to help them take it apart.


A reasonable tradeoff to explore is that software ought to work like a halfway-point between copyright and patents: in exchange for an exclusive right to distribute your binaries for 10-15 years, you provide your documentation for how it works (including source code) so others can build on your work after the exclusivity period ends. The exclusive right does not cover the basic idea/independent implementations of the same functionality.

Potentially utilitarian software and creative software could be treated differently, e.g. have an escrow for games (for which user customizations are less important).

Obviously DRM to restrict user modifications is unethical and harmful toward functioning markets and should be illegal.


>Though, I wouldn’t really claim that all IP is illegitimate. I think many IP protections go way too far and last too long, but, I think some amount of copyright and patents is probably a good idea, though for a much shorter duration.

For what it's worth that's the camp I'm in as well, I'm just being a bit silly for the sake of argument.


They want other people's information to be free for them. I doubt very much that they want their professional work to be free to other people.

It takes a certain kind of insanity to think that it's feasible to spend millions of dollars writing software when your customers are all entitled to take it for free.


I’ve heard an argument that people / companies would still pay for custom development, like they do now. It is a pretty weak argument, but I do see the point.


Sure, custom development could still be a thing under such a framework because there is only a single potential user, but can you imagine how catastrophically expensive that would be? The business of software development would be absolute misery to work in as the core skill would be to write such convoluted, impenetrable, single use code at the pain of being put out of business by source code copiers. Software would be completely out of reach to most consumers and small businesses. Basically we would be back in the 70s where computing was only available to large enterprise.


I'm with you until the final sentence. From my perspective, that's the current state of software development. Hundreds of megabytes of JavaScript and "assets" for what could be a 60KiB bundle of HTML, or a 500KiB Win32 program.


Forgot the name, but it's a variant of Hawthorne's laws for computers. If tech gets faster, programs will work to fill that newfound space and performance. even if it's just a simple web text page.

But no one complains and it lets them ship faster. So not much will change here.


> But no one complains and it lets them ship faster

I think we’re past even that point by now. Not only the code we ship now is slow, it’s also harder to build and maintain, and expensive to run. I have no idea how we got here to be honest.


It's called Wirth's law.


Yeah, the reality is, our industry produces a lot of garbage right now. That wouldn’t change.

Still, there are people who care about quality, and some of them also share their work with others. Those people would exist regardless of whether there is copyright or not. The only difference is, we won’t have LICENSE files anymore.


What if I hand-code something in asm?

What if I tell you I hand-coded something in asm, but secretly used a Rust compiler with an obfuscator?


Not everyone is stupid; people would catch on very quickly.


Things are often inconsistent however there are cases where something appears inconsistent but it is only lack of knowledge of observer that displays it as inconsistent. At least that is what I have learned today in some different matter (I was that observer).


Then you’ll have to invent new language for one or the other because they’ve different and merely related meanings.

I agree though. We should always intend for accurate and consistent language.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: