I worked at Lindows/Linspire so below is obviously biased.
> The desktop was under-powered
It was the first sub $200 PC, what did you expect? The PC actually sold very well.
> their software manager lacked too many apps and... it still suffered from dependency hell - leading to breakage.
It was Debian under the hood and later Ubuntu and had every package in respective apt repo. It made available every major GUI based desktop app at the time via a graphical installer as the target user had no clue what CLI was nor “apt-get”. This turned a lot of existing Linux users off but they (you) were never the target market.
Linspire also made huge strides in specifically addressing dependencies including developing a package manager called Opium (https://cseweb.ucsd.edu/~lerner/papers/opium.pdf). A number of these features went on to be folded directly into apt itself.
> Linspire's attempt at low-cost did Linux a lot of harm.
To the target market/user Linspire did far more good than harm. To the community, Linspire/Lindows gave back a ton. This included:
- Financial supporter to Wine
- Financial supporter to ResierFS (far ahead of any filesystem at the time… horrible tragedy what happened with his wife Nina)
- Financial supporter to Debian (RIP Ian)
- Financial supporter to Mozilla Firefox/Thunderbird (ex. inline spell checking was first found in Linspire)
- Funded gaps in applications such as NVU HTML editor
- First sub $200 PC in retail store
- First commercial “app store” (https://en.wikipedia.org/wiki/CNR_(software))
- Was sued for Microsoft for trademark infringement and walked away with $20 million (https://en.wikipedia.org/wiki/Microsoft_Corp._v._Lindows.com,_Inc.)
- Fastest Linux installer at the time by wide margin
- Early adopter of Haskell
- First distro to use Bittorrent for distribution
- Funded Desktop Linux Summit
- Funded initiative to translate major apps into 50+ languages
All told Linspire put millions per year back into the community. One can argue business model to death but over 10 years of hindsight now show that consumers simply had no appetite for commercial desktop Linux (nor do they still).
Where Linspire really fell on its face was running as root. There could have been much more elegant solutions to solve this but decision was solely outside of engineering.
IMHO, there is a market for desktop linux. My wife and my (old) mother have linux (ubuntu gnome). I provide the (remote) support. I think one of the problems of desktop linux is that it tries to much to mimic windows with its limitatiions. As an old linux user, I want network transparency. In particular, I want to be able to wake my PC from my phone, to connect to it to browse and download files, then to shut it down. Graphical remote access (like vnc) would be appreciated.
There are many, many remote desktop solutions for Windows, and they even solve the NAT piercing problem for you. How often do you use X network sessions over the internet (i.e., not on a LAN)? 15 years ago I used remote X via LAN quite a lot, but getting it to work over the internet was always a royal PITA, to the point where I stopped bothering. VNC-like approaches for Windows (CoPilot and similar) pretty much always work on the first try (well they did 5-ish years ago when I last used them - can't say for sure right now).
There are Wake On LAN Android apps, and I presume IOS too. There are many mobile torrent clients, and shell emulators. Those who can work with a CLI can set up their desktop/server/mobile integration on Windows just as easily as on Linux. Look, it's true that for some things Linux (rather, 'a Unixy OS') is easier, but that doesn't mean there's a market for desktop Linux. Those who are hardcore enough to want it, don't want to pay for it; and those who want to pay have plenty of solutions on Windows.
Signed up. Added a few accounts. Tried adding a custom app and it wanted me to subscribe for $29 per month.
I would happily pay for a service like this but not $300+ per year. As is, there is a free account or one targeted at businesses. What about an upgraded single user tier in the $50 per year range?
Also, as others stated, permissions on Github, Dropbox, etc. seem excessive.
Agreed, right now I use a spreadsheet to track subscriptions, it works great. I think an app like this can replace and add value to a simple spreadsheet but $300 more dollars year to track services I already subscribe too is way to much.
I would shoot for lower per year cost, around the $20 to $25 mark.
Not publicizing this since it’s not officially launched (close to finished), but check out an app I’ve been working on. Receiptdefender.com. Add any subscription as a recurring receipt and you now will see how much you’re spending very easily!
P.S. Native apps will be out right after launch :)
Currently the freelancer price is $10 a month. Not set in stone and no credit card needed to sign up. Would love thoughts from here!
Thanks for giving us your feedback, means a lot. At the moment we've aimed this at businesses, and are seeing a fair bit of response asking for something consumer focused.
Definitely thinking about how we could approach this.
- Their performance claims are incredibly biased. Amazon S3 has far better write performance than their claims.
- They claim 100% S3 compatibility but it fails a large number of API calls using Ceph’s s3-test. I didn’t dig into this too far but they do claim “No need to change your S3-compatible application” so changing my endpoint + credentials should have worked. To their credit - PUT, GET and DELETE did work but that is only 3 of 100’s of API’s.
- Their durability claims are highly suspect. I would want to see a white paper breaking this down.
- Their first round was debt financing.
Why this business model does’t work...
Most people don’t use S3 alone. S3 is a source for other AWS services. That being said, Wasabi becomes a more expensive option as you have a 4 cent egress fee to access data from the rest of your AWS infrastructure. The only place Wasabi becomes cheaper is for those using S3 direct/alone which is a very small subset of S3 usage. AWS is very open about this in white papers, conferences, tech talks, etc.
Wasabi is an economy at scale play that cast way too far a net. There is opportunity in specific vertical markets to sell a solution (object paired with compute) but a pure S3 endpoint will never take substantial marketshare away from AWS.
> They claim 100% S3 compatibility but it fails a large number of API calls using Ceph’s s3-test. I didn’t dig into this too far but they do claim “No need to change your S3-compatible application” so changing my endpoint + credentials should have worked. To their credit - PUT, GET and DELETE did work but that is only 3 of 100’s of API’s.
Validating claims of S3 compatibility is important. The S3 API has corner cases like and misfeatures like BitTorrent hosting but sometimes vendors omit key features like multi-part upload and v4 signatures. s3-tests[1] is the best way we have to evaluate implementations yet only Ceph and S3Proxy seem to contribute to it. Users should hold vendors' feet to the fire about these these claims.
>but a pure S3 endpoint will never take substantial marketshare away from AWS.
Perhaps in the "dev/ops" world, but S3 as a standalone repository could absolutely work for most enterprises and quite frankly soho users as a backup target. That being said, I have almost no faith this will survive and as such wouldn't trust it with my backups.
It would be a great destination for cloud backup, where one of the concerns is loss of all your backed up data due to malicious action - look at the trouble the hackers had to go to in Mr Robot to take out their offsite tape backups. I'd be more concerned though with the durability of the company rather than their disk systems over the long term though.
Separate AWS account with write-only permission to backup S3 objects from production pushed out to the backup account. Enable versioning and glacier in backup account. Lock down backup account credentials appropriately. (And add alerting and periodic fire drills of course.)
Also you can change your s3 bucket to enable multi-factor delete, which essentially makes it immutable unless you delete using a 2fa device, which shouldn't really happen accidently.
I've found that most people / companies actually do use S3 alone. Adoption of S3 on it's own is far greater than the rest of their services, at least in my experience.
Great decision! I have done the same and not looked back.
The first few years are the worst. You’ll have times when you are worried and want to throw in the towel or just plain overwhelmed. Unless you are destitute and need the money from a full time job - push through this! The freedom on the other side is worth the sacrifice.
- Automate everything you can. Billing, business related payments, etc. Give yourself the option to skip a day or two and not think about it.
- Get a good CPA! Anything you need for the “business” is now a write off. The comments that you'll pay more in taxes are total BS. As an unmarried, childless and non home owning CA resident I lost over 42% of my income to taxes working for someone else. I now have an effective rate of ~25% when you take into account all the write offs.
- Once you establish yourself you can be more selective in not taking clients that tie you to a specific physical location. Accommodating timezones from the other side of the planet is far less demanding when you are doing it barefoot on the beach.
I played the startup game for a long time. I had some mild success but over same timeframe I would have made far more doing my own thing earlier. I now make substantially more than my fancy titled tech job. More so, I work far less and wouldn’t give up my free time to make more. I choose when I work, how I work and to some degree the type of work.
Last thing, don’t listen to the people who tell you it can’t be done or not worth it. I have witnessed a lot of people attempt this and fail with the number one reason by a large margin being succumbing to the doubt instilled by others. Worse, its instilled by people with no experience in doing it themselves or in some cases jealousy. Yes, it will be hard in the near term. Yes, you will have many failures along the way. Shake yourself off and start over. Find other like minded people to learn from.
I see very few people asking what jenny_2’s long term career goals are. If your desire is more entrepreneurial then take a year off and make a decision later as to whether you go back. Things change dramatically in a year (especially in a startup) so if you commit to founders now to stick it out and decide in a year to go back to school so be it. I guarantee you their commitment to you is just as loose given you make it big.
I see this as a much simpler question of whether you are going to take a year off. All the variables for which you base that decision will change over the course of the next year so start with the first step and if you choose to leave let the rest play out over time.
In my own experience leaving school is the right choice for some. I left school for startup in the original 90’s boom and although I’m not a Zuckerberg I have had great experiences with startups successes and failures. I’ve also had no issue growing into an executive role in the valley along with a “seat at the table” where colleagues went the more traditional college route. I will however fully admit I am not the norm.
> The desktop was under-powered
It was the first sub $200 PC, what did you expect? The PC actually sold very well.
> their software manager lacked too many apps and... it still suffered from dependency hell - leading to breakage.
It was Debian under the hood and later Ubuntu and had every package in respective apt repo. It made available every major GUI based desktop app at the time via a graphical installer as the target user had no clue what CLI was nor “apt-get”. This turned a lot of existing Linux users off but they (you) were never the target market.
Linspire also made huge strides in specifically addressing dependencies including developing a package manager called Opium (https://cseweb.ucsd.edu/~lerner/papers/opium.pdf). A number of these features went on to be folded directly into apt itself.
> Linspire's attempt at low-cost did Linux a lot of harm.
To the target market/user Linspire did far more good than harm. To the community, Linspire/Lindows gave back a ton. This included:
All told Linspire put millions per year back into the community. One can argue business model to death but over 10 years of hindsight now show that consumers simply had no appetite for commercial desktop Linux (nor do they still).Where Linspire really fell on its face was running as root. There could have been much more elegant solutions to solve this but decision was solely outside of engineering.