3 ms·

Holy friggin crap. Can I buy a hardware timer, pls? I have to be reading this wrong - they can't even enforce the time budget for different tasks/threads under

Holy friggin crap. Can I buy a hardware timer, pls? I have to be reading this wrong - they can't even enforce the time budget for different tasks/threads under varied configurations? Don't nobody here know how to play this game?

munin 10y ago
> Don't nobody here know how to play this game? I guess all they need to do is hire "ArkyBeagle" from the comments section of hacker news, right?
- rhizome 10y ago
  Maybe! What do we know?
- deleted 10y ago
  [deleted]
- ArkyBeagle 10y ago
  We tried that. It didn't work out :)
Retric 10y ago
Real issue is different company's building different systems and then trying to integrate them after the fact. Chances are good that several systems are involved no one team has source code for even 1/2 of them. So, this is probably a reasonable trade off to prevent something else braking or massively delaying the project. Don't forget this is a weapon decreasing latency by 0.0001 seconds might be worth a lot of pain.
- aidenn0 10y ago
  They actually will have most of the source code for everything non-classified. However, they won't be allowed to change any of the software from other companies. This means getting a single bug fixed involves several con-calls with various levels of management at each company over the course of somewhere between two weeks and a few months. Double this at a minimum if the software wasn't developed in-house at the company that delivered it to you. In such an environment you very quickly get used to living with workarounds rather than bugfix. [edit] Oh, another thing I forgot that isn't universal, but is unfortunately too common. Dealing with managers after the bug is fixed asking why you spent time, and thereby the company's money fixing a bug in code that is the responsibility of another company.

3 ms·

Holy friggin crap. Can I buy a hardware timer, pls? I have to be reading this wrong - they can't even enforce the time budget for different tasks/threads under

by ArkyBeagle 10y ago

munin 10y ago
> Don't nobody here know how to play this game? I guess all they need to do is hire "ArkyBeagle" from the comments section of hacker news, right?
- rhizome 10y ago
  Maybe! What do we know?
- deleted 10y ago
  [deleted]
- ArkyBeagle 10y ago
  We tried that. It didn't work out :)
Retric 10y ago
Real issue is different company's building different systems and then trying to integrate them after the fact. Chances are good that several systems are involved no one team has source code for even 1/2 of them. So, this is probably a reasonable trade off to prevent something else braking or massively delaying the project. Don't forget this is a weapon decreasing latency by 0.0001 seconds might be worth a lot of pain.
- aidenn0 10y ago
  They actually will have most of the source code for everything non-classified. However, they won't be allowed to change any of the software from other companies. This means getting a single bug fixed involves several con-calls with various levels of management at each company over the course of somewhere between two weeks and a few months. Double this at a minimum if the software wasn't developed in-house at the company that delivered it to you. In such an environment you very quickly get used to living with workarounds rather than bugfix. [edit] Oh, another thing I forgot that isn't universal, but is unfortunately too common. Dealing with managers after the bug is fixed asking why you spent time, and thereby the company's money fixing a bug in code that is the responsibility of another company.