Comments by "justanothercomment" (@justanothercomment416) on "Linux has Real-Time now. What the fart does that actually mean?" video.

Been used for this stuff for ages. Real time simply means guaranteed worst case latency. Many people believe it means fast. Real time usually means lower bandwidth in exchange for increased reliability to maintain the worst case latency. Common example of where real time make sense is audio processing. Thus the birth of Jack audio server. Heck, I've even seen RT Linux used with CORBA for real time flight control avionics. As well as radar processing. Real time doesn't have to mean embedded nor specifically embedded processors. It simply means one has a worst case latency requirement.
32
Not sure why, but two of my detailed replies were removed. Yatub absolutely stinks for good discussion and information. Difficult to imagine a worse place.
14
@Winnetou17 You understand the actual market share is drastically under reported? And Windows market share is drastically over reported, which has the effect of further reducing the overall percentages for Linux? Linux actually has desktop share on par with MacOS. The Year of Linux desktop came and went years ago.
11
@Winnetou17 For example, Win over counts by millions. They count installs which no longer exist. Including ancient installs. The result is Win is massively over represented.
8
@Winnetou17 Most Linux installs are not counted. And methodology is known to be inaccurate with very conservative reporting. Making Linux installs under reported.
7
@Winnetou17 The point being. W's installs are frequently counted when they should not. And L's installs are frequently not counted when they should. And Many L (majority) installs count as W installs.
6
@Winnetou17 Provided a detailed reply. We'll see if yatab allows it.
5
@Winnetou17 Looks like they nuked my reply. I'll see if I can sneak some stuff in tomorrow.
5
@Winnetou17 Just based on these facts which are trivial to confirm, which way do you believe the install counts slant in reports vs reality?
5
@Winnetou17 Additional indirect market data reflects Linux desktop installs are roughly that of MacOS. Easy to see why.
5
@Winnetou17 Interesting. The most meaty part of the reply is removed again.
5
@Winnetou17 I'll let you figure out why yatub doesn't want you to know.
5
@JPs-q1o I still remember when SMP was new to Linux and it had the Big Kernel Lock.
5
@SterileNeutrino I can't point you at anything specific, but the way X11 works makes it especially difficult. Wayland is likely to further improve things there.
5
@Winnetou17 I invite you to investigate for yourself. If you spend much time researching you'll quickly confirm and agree.
4
@PayterX Because M pays people to not support L. And W is the primary platform preferred by three letters. YT has no issue in getting free stuff associated with L. But that doesn't in any way imply they support its ecosystem on desktops.
4
@MyAmazingUsername You are completely correct. They've marked me.
4
@vitalyl1327 Correct. Latency is simply the delta of event/signal/datum to handling that event/signal/datum. Remains true regardless of the time scale (pS to years).
4
@xlerb1637 By definition, a higher priority task should starve lower priority tasks. That's why they are prioritized accordingly. If one shouldn't starve the other they should have the same priority. Priorities basically says I want the higher priority to run even if a lower priority task wants to. That's why it's higher priority. It's more important it runs than the lower priority task.
3
@YellowCable Lower latency is the entire point of the preempt code. But Linux does in fact have an RT scheduler. Making it an RT kernel. One can split hairs on soft vs hard, but Linux is factually an RT kernel so long as it's appropriately compiled.
3
@autohmae Correct. It used to be things like MMUs and large memories and storage were scarce. These days they are common. As is multicore.
3
@Winnetou17 You have to do the research yourself. For example, Win over counts by millions. They count installs which no longer exist. Including ancient installs. The result is Win is massively over represented. As most computers running Linux come installed with a Win license, this is counted as a Win install. Again, over representing Win installs. Even best case, this results in a Win + Linux install count, which still over represents Win installs. Keep in mind Win installs are subsidized so it's almost always cheaper to buy a Linux computer with a Win license which is never used. My last five computers all fall into this category. As is the case with most Linux users. Most Linux installs are not counted. And methodology is known to be inaccurate with very conservative reporting. Making Linux installs under reported. Just based on these facts which are trivial to confirm, which way do you believe the install counts slant in reports vs reality? Additional indirect market data reflects Linux desktop installs are roughly that of MacOS. Easy to see why. Sadly, many people misunderstand and mireport Valve's (Steam) user surveys. These represent a tiny subset of Linux installs and their report reflects the minority of users which game and use Steam. Their counts do not represent actual Linux vs Win installs. But pay attention to how these stats reflect upon what I'm telling you. I invite you to investigate for yourself. If you spend much time researching you'll quickly confirm and agree.
2
@Winnetou17 As most computers running Linux come installed with a Win license, this is counted as a Win install. Again, over representing Win installs. Even best case, this results in a Win + Linux install count, which still over represents Win installs. Keep in mind Win installs are subsidized so it's almost always cheaper to buy a Linux computer with a Win license which is never used. My last five computers all fall into this category. As is the case with most Linux users.
2
@Winnetou17 Sadly, many people misunderstand and mireport Valve's (Steam) user surveys. These represent a tiny subset of Linux installs and their report reflects the minority of users which game and use Steam. Their counts do not represent actual Linux vs Win installs. But pay attention to how these stats reflect upon what I'm telling you.
2
@lolilollolilol7773 And scheduling algorithm.
2
@BillinSD Three letters just got aroused.
1
@rezah336 Sure. Liability. If your medical pump misses an interrupt which halts the pump, and creates an overdose, who pays for that? This is just one example. QNX and VxWorks are very popular and their pricing reflects the reality of liabilities and support for their products. Not to mention, someone has to port to new hardware and new peripherals. I've played with QNX. Thought it was pretty cool. Used VxWorks for P95 radio, including the entire init process. Something I did was used at NASA for rover testing. And I also do embedded development, in addition to some phone stuff on the application processor side. The RT world heavily overlaps with the embedded world but it's not exclusively so. As nez rightly points out, many applications within the embedded world (most?) use no OS at all. Even still, for many non mission critical apps, there are many RTOS solutions available (example, FreeRTOS). Cheap hardware (couple bucks) is available to play with much of this.
1