3 ms·

> What's Slack doing compared to a full (if primitive) OS and userland? Connecting to the internet.

• coldtea 10y ago
  Who'd new a few network sockets (support for which the TempleOS guy could write in his sleep his one hand tied) were such CPU beasts...
  • staticassertion 10y ago
    Who said anything about CPU? Slack's going to make DNS requests, multiple TCP requests most likely. That's network IO, multiple orders of magnitude slower than reading from disk - which is (at most, it may just read small file from disk and unpack in memory - I don't know) what TempleOS does. Slack's app has to display images, render scrolling, respond to network events, store and load application state like your preferences and theme, etc. Assuming it does these things - I use the web client. Slack also has to support multiple operating systems, so it may make technology choices around that. It's really not hard at all to see why Slack would be much slower than an OS that basically does nothing to boot up. It's not hard at all to see why Windows, which supports tons of hardware, would be larger on disk and slower to unpack as it boots - lots of drivers and services need to start up to support all of the things that make it not TempleOS.
    • coldtea 10y ago
      >It's really not hard at all to see why Slack would be much slower than an OS that basically does nothing to boot up. You seem to underestimate what TempleOS does and overestimate what Slack does. We had apps 10x more complex than Slack (with network IO et all) in 1995 -- and they run faster. Now using the web stack for Slack desktop might very well be a business decision (and a good one at that), but it's one of the worst performance decisions you can make.