3 ms·

Based on this, I'd love to brainstorm here on HN about what a next-generation Excel could look like, one that keeps Excel’s core strengths without expanding int

by wslh 2y ago

Based on this, I'd love to brainstorm here on HN about what a next-generation Excel could look like, one that keeps Excel’s core strengths without expanding into database like features found in tools like Airtable. Here are a few ideas: 1. Clear Separation between UI/UX and Backend: By separating the user interface from backend processes—perhaps as a module or library—Excel could maintain its clean, familiar interface while supporting more complex calculations and data handling in the background. This concept is somewhat akin to “Microsoft Excel Services.” 2. Multi-Language Formula Support: Similar to how VSCode supports multiple programming languages, Excel could allow users to choose between languages for cell formulas. Many users are comfortable with the current formula syntax, but it feels outdated, and even Google Sheets has (obviously?) largely replicated this old model. Allowing for different languages, while keeping the Directed Acyclic Graph (DAG) structure, could enable more advanced and flexible workflows. 3. Enhanced Data Types and Representations: Cells or groups of cells could support stronger data types, richer formatting, and custom representations, like embedded charts. 4. Integrated Data Connectivity: Excel could come with built-in tools to connect to external data sources and export data in structured formats, perhaps managed with an external orchestrator. I know you can do this with Excel and some other tools but I would like to just mark a cell and indicating that it can be consumed in a specific endpoint. 5. No artificial limits to the number of columns and rows.

kjellsbells 2y ago
6? Explicit versioning of spreadsheets, eg a Commit to GitHub button. 365 saves continuously but doesnt have the mental step of making you record what changed. Along the same lines, diff for spreadsheets that supported diff-by-value and diff-by-formula. 7? Beef up the recommended pivot tables. Not to jump on the AI bandwagon, but any table that has Sales$ and dates is ripe for suggesting sales by qtr, week etc. Let the AI inspect the table and make suggestions. 8. Beef up the programmability. The Record Macro feature emits VBA but the code is very literal (eg it sees you move to row 12345, and records that, not understanding that what you mean is 'move to the last row') and the IDE is primitive. Fold in copilot experience to the IDE, modernize the UI, and allow macros to be integrated with github instead of buried in some personal.xlb file that is all too easy to lose.

by wslh 2y ago

kjellsbells 2y ago

6? Explicit versioning of spreadsheets, eg a Commit to GitHub button. 365 saves continuously but doesnt have the mental step of making you record what changed. Along the same lines, diff for spreadsheets that supported diff-by-value and diff-by-formula. 7? Beef up the recommended pivot tables. Not to jump on the AI bandwagon, but any table that has Sales$ and dates is ripe for suggesting sales by qtr, week etc. Let the AI inspect the table and make suggestions. 8. Beef up the programmability. The Record Macro feature emits VBA but the code is very literal (eg it sees you move to row 12345, and records that, not understanding that what you mean is 'move to the last row') and the IDE is primitive. Fold in copilot experience to the IDE, modernize the UI, and allow macros to be integrated with github instead of buried in some personal.xlb file that is all too easy to lose.