@thanatos @Vexatos First off, you're already giving me the fact that you're worrying for a specific OS and processor. It turns out Windows has its own C runtime, it's just that it always comes with the OS.
Conversation
Notices
-
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Monday, 11-Jun-2018 18:13:53 UTC Xerz 💗 [UNMOVED]
-
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Monday, 11-Jun-2018 18:14:51 UTC Xerz 💗 [UNMOVED]
@thanatos @Vexatos (just like Windows also comes with some version of .NET btw, and I don't think you're complaining about that even when st
ff like C++ software depends on it) -
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Monday, 11-Jun-2018 18:15:00 UTC Xerz 💗 [UNMOVED]
@thanatos @Vexatos (just like Windows also comes with some version of .NET btw, and I don't think you're complaining about that even when stuff like C++ software depends on it)
-
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Monday, 11-Jun-2018 18:18:51 UTC Xerz 💗 [UNMOVED]
@thanatos @Vexatos Basically, C tries to minimize the friction of having a runtime, by making it small enough, with the least changes, as readily available as possible. That's why most devs don't even know that there's such a thing as C runtimes. But oh boy they are, and they can surprise you in peculiar ways if you don't know that.
-
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Monday, 11-Jun-2018 18:22:07 UTC Xerz 💗 [UNMOVED]
@thanatos @Vexatos You can do the same with any other language, or even go further. For instance, you can have a Java OS or even a Java processor which uses JVM bytecode as its instructions (there's been a few, and I think Qualcomm processors have some!). So it's rather not a language thing (not even depending on whenever it's compiled in the traditional sense!) but an *implementation* thing.
-