2 ms·

Why do you need to use CSS specifically? macOS built-in Terminal.app has had transparency (even varying transparency for focused vs background windows) for yea

Why do you need to use CSS specifically? macOS built-in Terminal.app has had transparency (even varying transparency for focused vs background windows) for years. Edit: oh, maybe you were being sarcastic? It's been a long day.

agumonkey 9y ago
yeah, I was. I understand the appeal of having html/css hyperdynamism everywhere. And at the same time I don't want to pay the price to the point that I prefer living in lotech linux land. I value frugal over potential flexibility these days. I told that often, but the other day I booted win9x (on a pentium 3 or less, some MB of ram, maybe 64) and ran an old copy of turbo pascal 7 (dos). That thing was flying. It had 80% of what I wanted (including, hear this, ascii shadowed floating editing windows.. talk about overfancy) and used zero resources. Today to have that kind of interactions you'd need a somehow recent quad core and 4GB+ of ram. All that mostly for a bit of eye candy (css may be of some use to decorate tokens/entities to give additional info, but I rarely see that).
- pantulis 9y ago
  Oh, Turbo Pascal had those Turbovision-powered ASCII shadowed floating editing windows in 1993 or so, and it flied on a 386 CPU... the P3 would be a screamer for that ;)
  - agumonkey 9y ago
    Thanks for that input, I was very curious to know about performance on much older hardware. This makes TP's worht even higher. 600kB total .. can you believe that ?
    - pantulis 9y ago
      Turbo Pascal had more tricks, it could compile to memory (at least in version 5, if memory serves well). Mind you, not a RAM disk, it could compile and run a MSDOS .COM file from memory itself. Following the filenames during compilation was difficult, as they passed so fast (20Mhz 386sx with 2MB). The compilers and IDEs from that era were truly pieces of art. I also remember TopSpeed Modula-2 that also included its own task scheduler for real time DOS (using clock interrupts, I guess).

agumonkey 9y ago

yeah, I was. I understand the appeal of having html/css hyperdynamism everywhere. And at the same time I don't want to pay the price to the point that I prefer living in lotech linux land. I value frugal over potential flexibility these days. I told that often, but the other day I booted win9x (on a pentium 3 or less, some MB of ram, maybe 64) and ran an old copy of turbo pascal 7 (dos). That thing was flying. It had 80% of what I wanted (including, hear this, ascii shadowed floating editing windows.. talk about overfancy) and used zero resources. Today to have that kind of interactions you'd need a somehow recent quad core and 4GB+ of ram. All that mostly for a bit of eye candy (css may be of some use to decorate tokens/entities to give additional info, but I rarely see that).

pantulis 9y ago
Oh, Turbo Pascal had those Turbovision-powered ASCII shadowed floating editing windows in 1993 or so, and it flied on a 386 CPU... the P3 would be a screamer for that ;)
- agumonkey 9y ago
  Thanks for that input, I was very curious to know about performance on much older hardware. This makes TP's worht even higher. 600kB total .. can you believe that ?
  - pantulis 9y ago
    Turbo Pascal had more tricks, it could compile to memory (at least in version 5, if memory serves well). Mind you, not a RAM disk, it could compile and run a MSDOS .COM file from memory itself. Following the filenames during compilation was difficult, as they passed so fast (20Mhz 386sx with 2MB). The compilers and IDEs from that era were truly pieces of art. I also remember TopSpeed Modula-2 that also included its own task scheduler for real time DOS (using clock interrupts, I guess).