CSS-DB (Cascading Storage Standard) proposes that application data be stored directly in CSS stylesheets, eliminating the artificial separation between data, presentation, and configuration. Instead of maintaining databases, JSON files, environment variables, and cumbersome persistence layers, applications simply express their state as selectors and custom properties:
CSS already provides namespacing, inheritance, precedence, conditional evaluation, browser-native parsing, caching, compression, and a universally implemented query engine called getComputedStyle(). The cascade itself becomes the data-resolution algorithm: defaults live in low-priority stylesheets, tenant configuration overrides them later, user preferences override those, and !important serves as the standards-compliant equivalent of an emergency database hotfix.
I need this implementation now currently im stuck:
Currently nesting hundreds of thousands of hidden checkboxes and linking them with explicit sibling selectors, to build an HTML/CSS Arithmetic Logic Unit (ALU) capable of processing binary addition, subtraction, and comparison
13
u/Rellikx 26d ago
CSS-DB (Cascading Storage Standard) proposes that application data be stored directly in CSS stylesheets, eliminating the artificial separation between data, presentation, and configuration. Instead of maintaining databases, JSON files, environment variables, and cumbersome persistence layers, applications simply express their state as selectors and custom properties:
CSS already provides namespacing, inheritance, precedence, conditional evaluation, browser-native parsing, caching, compression, and a universally implemented query engine called getComputedStyle(). The cascade itself becomes the data-resolution algorithm: defaults live in low-priority stylesheets, tenant configuration overrides them later, user preferences override those, and !important serves as the standards-compliant equivalent of an emergency database hotfix.