I have absolutely no idea why pivot tables would die before spreadsheet software. If people are using spreadsheet software, of course pivot tables will be useful. So to put my stack overflow hat on, it's asking the wrong question. Its entirely a matter of whether or not spreadsheet software has a place.
Looks like LLM-written article. It does not explain why Pivot tables never die. Also, somehow this page completely messed up my browser history - I could not just click the back arrow to navigate back.
You can also read here, in case that works better: https://www.ssp.sh/blog/why-pivot-tables-never-die/. And it's definitely not LLM written. And I tried to answer the why in the chapter "Why Pivot Tables Endure":
> The enduring power of pivot tables is their robustness, simple usage, and fast, interactive response. It's the Lingua Franca of data if you are not fluent in the language of SQL or Python. A common language everyone understands: the top management, domain experts, and developers. It's an interface to data; it's the first no-code interface. Instead of the multidimensional query language MDX or the newer DAX, people can use a simple drag-and-drop interface. It democratized data analysis.
>Also, somehow this page completely messed up my browser history - I could not just click the back arrow to navigate back.
It seems like the page updates the page url every time you scroll to a new section, which means you end up with 10+ history entries for the page if you scroll all the way through. To exit out of the page you'd have to click back 10+ times to go through those history entries. Google maps does something similar, where it adds a new entry to history every time you pan, which means your history is polluted with entries for google maps.
No this does it worse, try actually backing out through it after scrolling down, when I tried it went back to the beginning of the current section but then I couldn't get any further back than that so it's adding more entries each time you go back.
I can't find it now (would appreciate a link if somebody has one), but "pivot table" I believe was the name for a process where you would follow the intersecting points on a multi-equation graph that would represent the maximal value.
Essentially you have some maximal resource, i.e. money, and you are trying to figure out how it can be used most effectively under several constraints (don't have to be linear).
I remember distinctly having the calculate them by hand in an A-level math exam in the UK.
I think a major fault in the article is the minimization of the impact Improv had on the Pivot Table concept. Much like Numbers twists the spreadsheet paradigm into independent tables on a page instead of tabs, Improv twisted the spreadsheet into everything is a Pivot Table (or Excel Table). And it was first written for NeXt workstations before being ported to Windows. It was a radical departure from Lotus’s previous products and they never realized what they had in it. Microsoft capitalized on that lack of imagination by incorporating much of the functionality into the existing spreadsheet model.
This website hijacks my back button. I just loaded it and scrolled half a screen and every time I clicked back button on the mouse it added another history object to the stack.
Since this article successfully got me to look at an example using their software and get to the edge of their funnel, has anyone used Rill and can comment on its utility vs just using Excel which I already have or something else?
Pivot tables rock! I wouldn't be surprised if they were studied mathematically and proven to be somewhat capable of everything you might want to do in the context of tabular data processing.
It is the best, but also the very very worst in so many ways.
There are all sorts of data that are nearly impossible to get into Excel because of the ways that it tries to turn everything into a date. There has been so much silent data corruption because of random misfeatures that were added decades ago and now they will never back out of the system. The string OCT4 amongst a column of alphanumeric identifiers will get changed into a date, silently, on import, and it's nigh on impossible to find out how to import without that silent conversion. It's better to write your own Python code to get data into Excel than to use its built in foot guns.
That can be turned off (easily Googled), or as mentioned, doesn’t affect proper import using Power Query. Also, if you control the data format and know Excel is the intended target, you can just output your CSV so Excel won’t do that (put =“ and “ around text columns).
For any spreadsheet which are updated by refreshing source data such as CSV output from other systems, PowerQuery is what should be used and is very effective.
What are the web search terms you use to find to turn this off? Most people have not been able to figure this out, with the help of the web or in the application itself.
The typical windows user is not going to be accomplish a successful import, except maybe by whatever the heck PowerQuery is.
I wish more people stop hating on Excel. It's an incredible tool with cool stuff baked in (Python support, PowerQuery, etc.). Just because some people misuse it as database or it doesn't scale well beyond a couple of 10k rows does not make it a bad product. For 90% of daily office tasks it's just fine.
> Just because some people misuse it as database or it doesn't scale well beyond a couple of 10k rows does not make it a bad product.
It's not just that making it a bad product. Those are minor annoyances when compared with it trying to keep your data hostage in opaque formats[1] and exfiltrating your data to the cloud[2].
I don't think it's as bad as people make it, and certainly we can't blame non-technical users if they like it, for many tasks it's the only tool that's simultaneously usable by normal people and powerful enough.
It suffers from trying to do too many things at once, though. Excel 3 is enough for those use cases without being a complete nightmare for everyone else. Electronic spreadsheets as a concepts are genius, it's the implementation I hate.
Too many at once? Apparently, you can insert Python code into Excel now, which then gets executed into whatever Azure's equivalent of lambda is. I was recently introduced to someone at work who vibe coded an entire Python application in it and burned through their teams worth of cloud credits.
But using a spreadsheet to store data is completely reasonable. We delude ourselves as technically experienced people when we imply otherwise. When Excel fucks up data (perhaps the most unforgivable sin in all of software) with unexplainably bad defaults and UX for auto-formatting (i.e. "trying to be clever"), it's absolutely out of touch to point the finger at the end user.
The recent releases with new functions are great, there's a lot that can be done in a format that both pervasive and familiar. And Power Query is indeed a useful addition.
I'm a BI engineer, and I always convince people to use something else. But when I need to calculate my finances, and does not fit into Obsidian, I find myself using Excel again too :D Great product. Maybe not so much if you need to align on financial numbers - as everyone has their own truth :)
The advantage of Pivot Tables is they are interactive, but (modern) dynamic array formulas are better in cases where you are producing a static result.
Why would either of them die when they are some of the greatest tools ever invented and there is nothing better for the typical use case?
I have absolutely no idea why pivot tables would die before spreadsheet software. If people are using spreadsheet software, of course pivot tables will be useful. So to put my stack overflow hat on, it's asking the wrong question. Its entirely a matter of whether or not spreadsheet software has a place.
It's the best tool I never want to work with.
Looks like LLM-written article. It does not explain why Pivot tables never die. Also, somehow this page completely messed up my browser history - I could not just click the back arrow to navigate back.
You can also read here, in case that works better: https://www.ssp.sh/blog/why-pivot-tables-never-die/. And it's definitely not LLM written. And I tried to answer the why in the chapter "Why Pivot Tables Endure":
> The enduring power of pivot tables is their robustness, simple usage, and fast, interactive response. It's the Lingua Franca of data if you are not fluent in the language of SQL or Python. A common language everyone understands: the top management, domain experts, and developers. It's an interface to data; it's the first no-code interface. Instead of the multidimensional query language MDX or the newer DAX, people can use a simple drag-and-drop interface. It democratized data analysis.
>Also, somehow this page completely messed up my browser history - I could not just click the back arrow to navigate back.
It seems like the page updates the page url every time you scroll to a new section, which means you end up with 10+ history entries for the page if you scroll all the way through. To exit out of the page you'd have to click back 10+ times to go through those history entries. Google maps does something similar, where it adds a new entry to history every time you pan, which means your history is polluted with entries for google maps.
No this does it worse, try actually backing out through it after scrolling down, when I tried it went back to the beginning of the current section but then I couldn't get any further back than that so it's adding more entries each time you go back.
That web site is impressively terrible.
This is a better article if you are interested in the history of Pivot Tables: https://qz.com/1903322/why-pivot-tables-are-the-spreadsheets...
Discussed here:
The pivot table, the spreadsheet's most powerful tool (2020) - https://news.ycombinator.com/item?id=37820877 - Oct 2023 (192 comments)
I can't find it now (would appreciate a link if somebody has one), but "pivot table" I believe was the name for a process where you would follow the intersecting points on a multi-equation graph that would represent the maximal value.
Essentially you have some maximal resource, i.e. money, and you are trying to figure out how it can be used most effectively under several constraints (don't have to be linear).
I remember distinctly having the calculate them by hand in an A-level math exam in the UK.
Are you talking about linear programming. https://en.wikipedia.org/wiki/Linear_programming
Specifically the Simplex algorithm
Demo of Lotus Improv https://www.youtube.com/watch?v=TbsfvdZXE7s&t=205s
Linear optimisation? Ie. The excel "solver"
* maths exam...
I think a major fault in the article is the minimization of the impact Improv had on the Pivot Table concept. Much like Numbers twists the spreadsheet paradigm into independent tables on a page instead of tabs, Improv twisted the spreadsheet into everything is a Pivot Table (or Excel Table). And it was first written for NeXt workstations before being ported to Windows. It was a radical departure from Lotus’s previous products and they never realized what they had in it. Microsoft capitalized on that lack of imagination by incorporating much of the functionality into the existing spreadsheet model.
This website hijacks my back button. I just loaded it and scrolled half a screen and every time I clicked back button on the mouse it added another history object to the stack.
Yup. Messing with my back button is an immediate fuck off.
The foundational premise that pivot tables went away somewhere seems flawed; they've been going consistently strong as long as I've had a job.
Pivot tables are available on LibreOffice as well: https://help.libreoffice.org/latest/en-US/text/scalc/guide/d...
They are in most spreadsheets and many databases now. Even Sheets and Numbers and Oracle SQL etc... maybe just without the same UI.
Microsoft copied the basic concept from Lotus, and Borland also copied it etc...
Since this article successfully got me to look at an example using their software and get to the edge of their funnel, has anyone used Rill and can comment on its utility vs just using Excel which I already have or something else?
Pivot tables rock! I wouldn't be surprised if they were studied mathematically and proven to be somewhat capable of everything you might want to do in the context of tabular data processing.
I wish more people explored Excel. Not just spreadsheets. But MS Excel. It is the best piece of software that came out of MSFT.
It is the best, but also the very very worst in so many ways.
There are all sorts of data that are nearly impossible to get into Excel because of the ways that it tries to turn everything into a date. There has been so much silent data corruption because of random misfeatures that were added decades ago and now they will never back out of the system. The string OCT4 amongst a column of alphanumeric identifiers will get changed into a date, silently, on import, and it's nigh on impossible to find out how to import without that silent conversion. It's better to write your own Python code to get data into Excel than to use its built in foot guns.
That can be turned off (easily Googled), or as mentioned, doesn’t affect proper import using Power Query. Also, if you control the data format and know Excel is the intended target, you can just output your CSV so Excel won’t do that (put =“ and “ around text columns).
For any spreadsheet which are updated by refreshing source data such as CSV output from other systems, PowerQuery is what should be used and is very effective.
What are the web search terms you use to find to turn this off? Most people have not been able to figure this out, with the help of the web or in the application itself.
The typical windows user is not going to be accomplish a successful import, except maybe by whatever the heck PowerQuery is.
If you import with PowerQuery you can explicitly specify the data type for each column.
I wish more people stop hating on Excel. It's an incredible tool with cool stuff baked in (Python support, PowerQuery, etc.). Just because some people misuse it as database or it doesn't scale well beyond a couple of 10k rows does not make it a bad product. For 90% of daily office tasks it's just fine.
> Just because some people misuse it as database or it doesn't scale well beyond a couple of 10k rows does not make it a bad product.
It's not just that making it a bad product. Those are minor annoyances when compared with it trying to keep your data hostage in opaque formats[1] and exfiltrating your data to the cloud[2].
[1] https://blog.documentfoundation.org/blog/2025/07/18/artifici...
[2] https://superuser.com/questions/1903431/how-to-stop-excel-36...
I don't think it's as bad as people make it, and certainly we can't blame non-technical users if they like it, for many tasks it's the only tool that's simultaneously usable by normal people and powerful enough.
It suffers from trying to do too many things at once, though. Excel 3 is enough for those use cases without being a complete nightmare for everyone else. Electronic spreadsheets as a concepts are genius, it's the implementation I hate.
Too many at once? Apparently, you can insert Python code into Excel now, which then gets executed into whatever Azure's equivalent of lambda is. I was recently introduced to someone at work who vibe coded an entire Python application in it and burned through their teams worth of cloud credits.
When Python in Excel was announced I was initially pretty excited until I found out that it executes in Azure.
WHY wouldn't Microsoft just run it in the local interpreter on the machine?
> WHY wouldn't Microsoft just run it in the local interpreter on the machine?
Probably to tighten vendor lock-in.
Excel is fantastic. I love it.
But using a spreadsheet to store data is completely reasonable. We delude ourselves as technically experienced people when we imply otherwise. When Excel fucks up data (perhaps the most unforgivable sin in all of software) with unexplainably bad defaults and UX for auto-formatting (i.e. "trying to be clever"), it's absolutely out of touch to point the finger at the end user.
> unexplainably bad defaults and UX for auto-formatting
Agree. Soooo many leading zeroes have been striped from ZIP codes.
Equally as bad is no visual indicator to distinguish formula cell from static cells. Easy to silently overwrite formulas with a careless paste.
The recent releases with new functions are great, there's a lot that can be done in a format that both pervasive and familiar. And Power Query is indeed a useful addition.
Is Python is still a metered cloud runtime?
I love Excel. In some ways it is similar to Jupyter Notebooks: great for exploration, horrible for using in production.
It can be great in production, like any tool it depends on the nature of the task.
Tangential: Timeless post I go back and read through periodically: https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
I'm a BI engineer, and I always convince people to use something else. But when I need to calculate my finances, and does not fit into Obsidian, I find myself using Excel again too :D Great product. Maybe not so much if you need to align on financial numbers - as everyone has their own truth :)
MS Excel is good because it has Lisp inside. Does Pivot thing contain Lisp?
Why do you think Excel has LISP inside? What would that have to do with Pivot Tables?
1. The datatype.
2. Idk, just asking.
shameless plug - online pivot tables: https://www.seektable.com o_o
With _array formulae_ you can live without pivot tables, to a certain extent. They would auto-refresh, too...
The advantage of Pivot Tables is they are interactive, but (modern) dynamic array formulas are better in cases where you are producing a static result.
Why would pivot tables ever die? That's just like saying line charts never die...