Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Sicherheitslücken (CVE)USN-8797-1: GStreamer Base Plugins vulnerability(21.09.2026 um 20:05 Uhr)
Sichere ProgrammierungYou can build HTML emails with Tailwind CSS(21.09.2026 um 22:15 Uhr)
Sichere ProgrammierungDEV-Part-1-Backend.md(21.09.2026 um 22:24 Uhr)
Sichere ProgrammierungWhat It Actually Costs to Serve a 1M-Token Model in Production(21.09.2026 um 22:33 Uhr)
Sichere ProgrammierungHow to Check an Agent's Diagnosis Before It Touches Production(21.09.2026 um 22:53 Uhr)
Linux Tipps & HardeningWhat if Spotify was self-hosted? I think I got pretty close.(21.09.2026 um 22:33 Uhr)
Linux Tipps & HardeningSandboxing on Linux(21.09.2026 um 22:45 Uhr)
Sicherheitslücken (CVE)USN-8797-1: GStreamer Base Plugins vulnerability(21.09.2026 um 20:05 Uhr)
Sichere ProgrammierungYou can build HTML emails with Tailwind CSS(21.09.2026 um 22:15 Uhr)
Sichere ProgrammierungDEV-Part-1-Backend.md(21.09.2026 um 22:24 Uhr)
Sichere ProgrammierungWhat It Actually Costs to Serve a 1M-Token Model in Production(21.09.2026 um 22:33 Uhr)
Sichere ProgrammierungHow to Check an Agent's Diagnosis Before It Touches Production(21.09.2026 um 22:53 Uhr)
Linux Tipps & HardeningWhat if Spotify was self-hosted? I think I got pretty close.(21.09.2026 um 22:33 Uhr)
Linux Tipps & HardeningSandboxing on Linux(21.09.2026 um 22:45 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

Another Web Spreadsheet App?

About five years ago, I was building a spreadsheet-based web application with SpreadJS. It worked well for most scenarios, but over time I realized the biggest challenge wasn't rendering spreadsheets. It was helping people manage…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

About five years ago, I was building a spreadsheet-based web application with SpreadJS.



It worked well for most scenarios, but over time I realized the biggest challenge wasn't rendering spreadsheets.



It was helping people manage hundreds of Excel files that were almost, but not exactly, the same.






What was painful?




  • Users already had hundreds of Excel workbooks, and asking them to migrate to a new format was simply unrealistic.

  • Most workbooks shared the same structure, but each customer had made small manual changes over the years.

  • We kept building more tools to simplify their workflow, but every new feature meant another button to learn.

  • Most spreadsheet components are designed as UI libraries. That architecture makes background tasks(like auto-saving) surprisingly difficult.






My philosophy



The root problem was that businesses expected spreadsheets to behave like structured systems, while Excel was designed as a personal document. Every workbook became a slightly different source of truth, forcing backend systems to constantly validate, clean, and interpret the data.



I believe organizations should be able to define a contract for their spreadsheets. Users still work in the familiar Excel experience, but the workbook follows a well-defined structure instead of relying on conventions.



Once a workbook has a stable contract, it becomes much more than a document. Software can reliably access its data, automate repetitive tasks, and process thousands of workbooks without fragile scripts.



Finally, every business has its own workflow. It's impossible for a spreadsheet application to include every feature every team needs.



I like the philosophy behind VS Code: keep the core simple, and let extensions adapt it to different use cases. I believe spreadsheets should work the same way. Instead of building every workflow into the application, users should be able to extend it with their own business logic and automation.






Five years later



The company eventually shut down, but the idea stayed with me.



I open-sourced the project, which only included a formula parser and an OOXML parser, and continued working on it during evenings and weekends.



For a long time, it felt like an endless marathon. Every feature uncovered three more waiting to be implemented.



AI changed that. It didn't replace the engineering work, but it dramatically increased the amount of work one person could accomplish.



Today, I finally feel the project has grown into what I originally envisioned.






What I've done?



At the foundation is a set of Rust libraries that provide the core spreadsheet capabilities. They support features such as formula calculation, OOXML compatibility, undo/redo, and workbook manipulation.



Building the engine separately was important because spreadsheets are not just a user interface. They are also data and computation systems that need to run independently from the frontend. This architecture makes it possible to perform tasks such as background processing, automation, and server-side integration.



On top of the engine, I built two concepts to solve the problems I described earlier: Block and Craft.



A Block defines a stable structure inside a workbook. Instead of treating a spreadsheet as an arbitrary collection of cells, a Block describes what data exists, how it should be organized, and how software can reliably access it. Users can continue working with spreadsheets they already understand, while applications no longer need to depend on fragile cell coordinates.



Craft is the extension system built on top of this foundation. Inspired by the philosophy of VS Code extensions, Craft allows organizations to add their own business logic, automation, and workflows without modifying the core system, using JS.



I built a factory-simulator game(craft) to demonstrate how Block and Craft work together. If you play it carefully, you might be able to find some special formulas, that help you refer cell by (table name, key, field)! Isn't it cool?



Actually I have a lot more to share. If you're interested in this project, star it please!

Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Another Web Spreadsheet App?

Thematisch verwandte Begriffe: Another, Spreadsheet · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-45381 | Tautulli is a Python based monitoring and tracking tool for Plex Media S…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick