>Suddenly, the field has begun to bloom. A small cluster of startups have in the past year released spreadsheet products
All of which are subscription based SAAS. Maybe I am showing my VisiCalc oldster roots, but I want my document related tools to be pay once / run locally.
I long for a computing world where the free tier is run-in-a-browser-on-someone-else's-computer and the paid tier is run local and native.
Every day I think about how Microsoft Access allowed otherwise not-so-tech-savvy users to, with just a little training and practice, build a complete relational database for their entire business, supported by a relatively sane GUI and a way to build forms and reports with very little (if any) 'code'. I have no idea what small companies are using nowadays, but I think there has to be some untapped middle ground somew…
There are still lot's of folks using Access. For those of us in the Linux space, we can use Libreoffice Base and script it with python. I once built for a local business that needed to join the computer age using this. Then about a year+ the owner's relative came to the business and decided that it was too old school and to get it redone as a web app. Needless to say, the owner is not too happy with it, took too long, cost too much both to develop and run and has more errors. He lamented to me about it when I was in town... The issue is the world has moved on from local/native apps.
>Suddenly, the field has begun to bloom. A small cluster of startups have in the past year released spreadsheet products All of which are subscription based SAAS. Maybe I am showing my VisiCalc oldster roots, but I want my document related tools to be pay once / run locally. I long for a computing world where the free tier is run-in-a-browser-on-someone-else's-computer and the paid tier is run local and native.
The best startup ideas are creating one part of the O365 system (usually Excel) and monetizing it separately.
Warning: I'm a founder working in the spreadsheet space, so take the rest of my this comment with a (large) grain of salt. I've written before [1] (HN and elsewhere) about how I think spreadsheets are the most popular programming paradigm ever, we just don't talk about it much. As this article mentions, there are many ways we can push this forward. I personally think the most powerful low-code spreadsheet tools we ca…
You need the commercial license to disable telemetry? That's... new.
Microsoft Access is, of course, still around. It would be great if there were a solid way to develop a database, forms, and reports in Access and then deploy it to the web. If you've ever had to work with someone else's Access database, it is unusual to see a reasonably normalized relational database. Most people are much more comfortable with the single flat file of Sharepoint lists.
For stuff at the scale of a small Access database, does the normalization (or lack of) end up being a big deal? I get that there are real advantages, I'm just wondering out loud whether they are universally applicable/important to small scale databases.
Probably matters as it relates to data quality mostly
Excel users tend to do a far better job of data storage, analysis, and forecasting than most of overpaid SaaS-reliant "modern data team" (Data Engineers, Data Analysts, Analytics Engineers, Data Scientists).
>Suddenly, the field has begun to bloom. A small cluster of startups have in the past year released spreadsheet products All of which are subscription based SAAS. Maybe I am showing my VisiCalc oldster roots, but I want my document related tools to be pay once / run locally. I long for a computing world where the free tier is run-in-a-browser-on-someone-else's-computer and the paid tier is run local and native.
Sadly it feels like single purchase software is on its way out. All the momentum is toward SAAS.
Microsoft Access is, of course, still around. It would be great if there were a solid way to develop a database, forms, and reports in Access and then deploy it to the web. If you've ever had to work with someone else's Access database, it is unusual to see a reasonably normalized relational database. Most people are much more comfortable with the single flat file of Sharepoint lists.
For stuff at the scale of a small Access database, does the normalization (or lack of) end up being a big deal? I get that there are real advantages, I'm just wondering out loud whether they are universally applicable/important to small scale databases.
That's a good question. For an honest and complete answer, I'd have to remember the messes I've seen and it's been a couple decades now, so I don't. But simply, everything in setting up forms and reports is more convenient if you have real relations as opposed to a bunch of columns like "supplier1, supplier2, supplier3...".
>Suddenly, the field has begun to bloom. A small cluster of startups have in the past year released spreadsheet products All of which are subscription based SAAS. Maybe I am showing my VisiCalc oldster roots, but I want my document related tools to be pay once / run locally. I long for a computing world where the free tier is run-in-a-browser-on-someone-else's-computer and the paid tier is run local and native.
The best startup ideas are creating one part of the O365 system (usually Excel) and monetizing it separately.
Ironically, O365 is $7/month with max rows = 1m+ and spreadsheet.com is $9month for max rows = 10k.
>Suddenly, the field has begun to bloom. A small cluster of startups have in the past year released spreadsheet products All of which are subscription based SAAS. Maybe I am showing my VisiCalc oldster roots, but I want my document related tools to be pay once / run locally. I long for a computing world where the free tier is run-in-a-browser-on-someone-else's-computer and the paid tier is run local and native.
Sadly it feels like single purchase software is on its way out. All the momentum is toward SAAS.
As a greybeard, I have seen plenty of old ways become new again. It's hard to predict when the next shift will be or where it will go, but it will shift.