all 11 comments

sorted by: hot top controversial new old
[–] 6 points 8 months ago*

As soon as I saw no networking, I knew TempleOS was coming

  • source
  • [–] 4 points 8 months ago (2 children)

    WtAF?!? So many questions, starting with WtF makes this "feminine?"

  • source
  • hideshow 2 child comments
  • [–] 3 points 8 months ago (6 children)

    As much as that doesn't sound very efficient, I admit having a single core would prevent so many multithreading related bugs or crashes. Sounds nice.

  • source
  • hideshow 6 child comments
  • [–] 8 points 8 months ago (5 children)

    A single core can still run multiple threads ...

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 8 months ago (4 children)

    Why would it? Everything still processes one at a time anyways...

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 8 months ago (3 children)

    So multiple things can effectively run at once. Otherwise, every piece of software has to be fully aware of every other piece's timing and resource requirements, which obviously can spiral out of control very quickly, and effectively locks out any possibility of an unplanned-for application running on the system.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 0 points 8 months ago* (last edited 8 months ago) (2 children)

    I feel like even without multithreading the services share processing power effectively. There might be some jitters and hangs, but doing things within specification won't produce any noticeable lag.

    It's kind of like the difference of if one process ran for 3ms or if it ran for 0.3ms 10 times.

    But we're getting off topic, now, yes multithreading is apparently (a very stupid) thing on single cores and therefor the bugs and crashes can still occur.

  • source
  • parent
  • hideshow 2 child comments