←back to thread

292 points kaboro | 1 comments | | HN request time: 0.203s | source
Show context
areoform ◴[] No.25058952[source]
> Sketch, to be sure, bears the most responsibility for its struggles; frankly, that native app piece reads like a refusal to face its fate.

Ben can write paeans to this new "cloud" business model. But at the end of the day, the question for us, the users is simple.

Do we own what we buy?

When I buy a Mac (and I've bought several), I am buying a computer. A general purpose computational device. And by selling it to me, the company is selling me a general purpose computational device.

What right does the company have to stop me from installing/modifying my device in any way that I see fit? Sure, they may refuse support/warranty, that is their prerogative, but what gives them the right to stop me from having someone else repair it? Or, to boot into Linux? Or, to open my own computer?

I have a MacBook Pro from 2016. Recently, I wanted to give it a thorough cleaning. So I took out my speciality screw driver and unscrewed the screws for the bottom plate.

It wouldn't budge.

It was then I realized that I needed suction cups and strength to move the plate downwards to unlatch something inside to make it "pop".

This design serves no engineering purpose. It exists to make it harder for me, the device owner, to access the device I've purchased without sacrificing dollars at the altar of Apple.

And this was their most "open" product. Prior to the M1 announcement, you couldn't boot into another OS - or significantly alter - your iOS device. And now we can't do so with our Macs. We seem to have collectively decided to blur the line of ownership.

A device we buy isn't ours even after purchase. No, we must continuously give our money to the corporation for the benefit of their revenue projections.

Which returns us to this,

> Sketch, to be sure, bears the most responsibility for its struggles; frankly, that native app piece reads like a refusal to face its fate.

With Sketch you own your data, and thanks to the open format, you can port that data to other mediums.

With Sketch you own a copy of the tool that allows you to do your job.

With these other, less powerful but "collaborative" software, you don't truly own your data or the tools to access it. You merely rent it.

Should there be an event where Figma is acquired or goes out of business, then (in all likelihood) every user of this platform will lack the ability and the choice to preserve their work for future generations (and for their business).

What are the odds of Figma staying as it is, in the control of founders, chugging along as a profitable business a year from now? 5 years from now? A decade? Two decades?

I do not wish to single out Ben, but this post is an exemplar of the shift in thinking being pushed by the current crop of tech cognoscenti. They have made a growing argument that the future is one without ownership. Where it's one where you don't own your devices, you rent them. And they assure us that's the future, and because that's the future, it's going to be amazing.

But that sounds like dystopia to me. It is one thing to have a tradeoff between accessing all the songs in the world and owning a few on vinyl to having the tools of your trade be abstracted away.

Spotify and Netflix aren't essential services to me. My computer is. My vector design software is. My ability to write code is. My ability to make things is.

They argue that there are benefits to "collaboration" with the "cloud", but that doesn't need to be so. The only reason why they're operating in the browser is because the tradition of web apps started within them. There is no reason why every other application can't collaborate natively, with combined local + server-based data storage with other apps across the world.

Video games do it all the time! Games like counterstrike etc are in some ways far more collaborative than a Figma file. The state of what occurs in the world depends on every other person in the world, with the context being time sensitive, and the state being additive. And it works beautifully.

If it can work for non-essential entertainment, why should we accept the reduced paradigm for our essential tools? Why should we buy into crippled software that is limited by the fact it runs in the browser? Why should we buy into the abusive business model of having to rent our ability to do work from another company? Why should we buy into the idea that we don't own the fruits of our labor? And that we don't get to have a copy of our work nor access it without paying the toll?

Bohemian Coding, if you ever read this, don't go down with this ship. Add support for Windows. Or, Linux. It will save your company.

replies(4): >>25059528 #>>25059624 #>>25059827 #>>25062166 #
1. mason55 ◴[] No.25059624[source]
IMO this argument blurs the line between two separate concepts.

I think it's fair to say that a company shouldn't be allowed to sue you or have you arrested for doing whatever you want to a device that you have purchased. For example, see the John Deere lawsuits where they are trying to DRM repairs to tractors and make it illegal to work on them.

What I think is less fair is arguing that a company has a requirement to make it easy or possible for you to work on your device. You're entering the world of engineering and end-user trade-offs and starting to talk about forcing companies to add or remove features that might be in the end-user's best interest.

Would a screw with a proprietary screw-head be ok if the company could argue that it made assembly easier? Would you require that they prove there is some tangible engineering benefit to all decisions? What's the line between "general purpose computing device" and "electronic toy"?

You could probably write a law that made it illegal to add restrictions whose sole purpose was to prevent the user from modifying or repairing their device but the only way you'd ever be able to enforce it is if someone was caught writing incriminating emails. Pretty much anything could have some imaginary engineering justification behind it.

If you can crack a proprietary protocol or re-create a proprietary screwdriver then more power to you, you shouldn't be arrested or sued. But telling a company they're not allowed to use a proprietary screw-head is a messy road to start down, and that's what you're saying when you're asking for companies to be forced to allow you to do what you want on your device.

Vote with your wallet and if the choice you vote for doesn't win then you're free to go create your own. But don't outlaw business models or legislate engineering choices. You should have a right to repair, you should have a right to get your data, you shouldn't have a right to tell me what my engineering choices need to be.