Live data from Hacker News

Spreadsheet Assassins – A short history of "software as a service"

thebaffler.com

11–20 of 83 posts

Re: Spreadsheet Assassins – A short history of "software as a service"

#11

Lovely; a monthly sub to an article talking about monthly subs. You have to realise I will never, ever, going to pay ‘thebaffler’ and especially an article explaining that everyone wants subscriptions in a site that gives me one article and the rest is a subscription.

More than "one free article"; I checked and TheBaffler seems to allow you read 4 articles(/mth?) before subscription-walling.

Re: Spreadsheet Assassins – A short history of "software as a service"

#14
> The result? Some SaaS companies achieve gross profit margins of 75 to 90 percent, rivaling Windows in its monopolistic heyday.

Gross profit is a misleading statistic in the software industry, where almost all of the effort comes from building the thing.

Re: Spreadsheet Assassins – A short history of "software as a service"

#15
I subscribed to the Baffler because they write well, and to break out of my own echo chambers a bit.

Glad to see them on HN, but a bit disappointed in the response. They article is mostly correct in it’s lampooning.

Even if you disagree with points or find it ironic that they offer a subscription (btw equating producing a publication with SaaS is quite erroneous) — I think its useful to take this as a datapoint on how people outside tech see tech. That matters.

Re: Spreadsheet Assassins – A short history of "software as a service"

#16
post #8
post #3

It’s interesting to see my industry described from a different point of view. It misses the key point of the economics of subscriptions: a single up front fee is a disincentive to the constant maintenance that delivers the single biggest piece of value to the customer, that being the continued existence of the software. Instead it creates an incentive to add lines to the marketing BS on this year’s release and priori…

A subscription fee required for receiving updates for an application that you own seems fine. A subscription fee required to avoid that the application you are using will be disabled remotely seems unacceptable. The latter certainly does not create any incentive for the software vendor to improve the quality of their product and to fix its bugs. On the contrary, the latter business model provides a stream of revenue…

The second point just strands parts of customers on outdated versions - remember that time when loads of companies were running Excel 1997 or 2003 to their deaths to save costs?

Then anyone on Excel 2013 couldn't use any new features because they weren't backwards-compatible 10 years to some public sector organizations that refused to update.

Office 365 is so much better, I can actually send someone a file that uses LAMBDAs or uses PowerQuery and expect them to be able to open it.

Re: Spreadsheet Assassins – A short history of "software as a service"

#17

Thoma Bravo the “bridge trolls of enterprise software,” they are domestic terrorists if you ask me... because for the majority of people effected by them, its terrorifying. the way they operate is not in our countries/market best interest, but only the interests of a top few, who frankly include real global terrorists as members of the fund. The US should start to investigate PE, PE is crushing the economy under its…

I've been blaming MBAs for ruining large companies for about 15 years. More and more of them were minted, and true to their word, they really have gotten good at extracting every last dollar out of whatever a company sells. Now that small business owners are watching/listening constantly to small business gurus and hustle gurus, those businesses are screwing customers in ways I didnt see 20 years ago. I keep in conta…

> I keep in contact with many small business owners in construction and repair, and almost everyone now thinks that its better to get less work and just charge more.

I don’t see what MBAs have to do with that, it’s a tale as old as time: given the choice to have the same pay and more leisure time, most people will take more leisure time. The exceptions are probably mostly people doing intellectual labor, not physical labor like pouring driveways.

Re: Spreadsheet Assassins – A short history of "software as a service"

#18
post #11

Lovely; a monthly sub to an article talking about monthly subs. You have to realise I will never, ever, going to pay ‘thebaffler’ and especially an article explaining that everyone wants subscriptions in a site that gives me one article and the rest is a subscription.

More than "one free article"; I checked and TheBaffler seems to allow you read 4 articles(/mth?) before subscription-walling.

It literally says it at the bottom for me; from the start; maybe elsewhere it’s another number or it lies. Point stands no? Article writing about subscriptions wants a subscription.

Re: Spreadsheet Assassins – A short history of "software as a service"

#19
post #11

Earlier quoted context omitted.

More than "one free article"; I checked and TheBaffler seems to allow you read 4 articles(/mth?) before subscription-walling.

It literally says it at the bottom for me; from the start; maybe elsewhere it’s another number or it lies. Point stands no? Article writing about subscriptions wants a subscription.

Interesting; I'm in the US; where are you? Also, mobile/desktop?

(It literally doesn't say it on the webpage served to me; don't assume the same version is served to all countries)

Re: Spreadsheet Assassins – A short history of "software as a service"

#20

To me, Obsidian is a perfect example of how to get SaaS-revenue without making the user captive: All data is stored in an accessible form on the user hardware, and what you pay for is sync. X-user kepano (who is a/the creator of Obsidian) has some nice insights on this _file over app_ philosophy.

This is an effective, simple solution if the application doesn't have transactional constraints and authorization. The user is in full control of the data - and that's a good thing.

It becomes a bit more complicated if the data has to be in a specified shape and can only partially be authored by any individual due to authorization requirements. Having a single source of truth on a server is quite a bit easier to reason about and design in this case.

I don't know where Obsidian stands on this, but I assume that if it has collaborative features or complex data constraints it has to do some quite sophisticated stuff to make it work reliably.

Post reply on HN