3 ms·
I often wonder about products like this. It seems to me that access solved many of these problems years ago then just faded away. I don't know why, I don't know
by xupybd 4y ago
I often wonder about products like this. It seems to me that access solved many of these problems years ago then just faded away. I don't know why, I don't know why these are better either. Other than being collaborative and in the cloud. Those are huge benefits but why didn't access carry on to the cloud?
I feel like I'm missing some understanding of the low code space.
I'd like to learn these tools one day to allow me to rapidly put together CRUD apps but every CRUD app I build seems to have some edge case that would not be a good fit. So I carry on the old fashioned way. I'm sure I'm wasting time manually plumbing data between the database and the front end but oh well.
- andyferris 4y agoI have a theory that SQL Server made so much cash that Microsoft didn’t want Access to eat its lunch. It could have made a lot of progress in the last 25 years even with a reasonably small team. Honestly something that could start as a local Access file and later be “hosted” on-premises for collaborative usage and later move to (e.g. Microsoft’s) cloud for wider usage/easy hosting would be useful to a lot of folk. The forms etc could migrate to HTML (rendered via local webviews / websites on a users browser).
- patife 4y agoRows isn’t for apps. It’s for spreadsheets proper. Just that Rows assumes 2 things: 1. you got to import data from your cloud tools (SaaS like GoogleAnalytics, BigQuery, Looker, Ads platforms,… and your own custom APIs). It’s hard to do on excel and sheets, not flexible and hard to automate. 2. You want to share spreadsheets in a way they render well on mobile. That’s why we made rows (im a founder)