This is really cool!! Some thoughts followhttps://twitter.com/asyncrs/status/1206574783250468864 …
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
This is why the separation of concerns between executor, reactor, and middleware is so important: we *should* have many different runtimes optimized for different use cases
One library cannot be the runtime for every use case. Runtime authors should try to pick a particular target user, and other libraries should be written to be abstract over different runtimes
May I ask why this approach isn't necessarily ideal for soft real time systems? Is it because you no longer have control over when your code may be passed over to a different OS thread?
More abstractly i think it makes the latency of individual tasks less predictable (in exchange for overall better throughout and maybe better average latency depending on the workload)
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.