> It was once routine for me and others I know to be prescribed hydrocodone for conditions like painful seized muscles, root canals or severe strep throat. We were apparently all in the ~80%+ who used it as intended and…
> I believe systemd-resolved, however, is one of those components that is entirely optional, and which nothing explicitly depends on... Yet. Wouldn't be the first time some "optional" component became mandatory.
GP is clearly right. What's the point of going "that's just your opinion" on every fact he mentions?
Scala developers can do whatever they want or need at compile-time.
> The systemd network stack is entirely optional and intended for scenario where you can't afford/don't need the 'fatness' of NetworkManager, just because it's there, doesn't mean you have to use it. Currently.
Jesus, it took me way too long to realize this was about online classes, not virtual classes in languages. :-)
Yes, exactly, which makes the claim even more baffling. Sure, they can just reimplement all their Java dependencies, but if they have to implement e.g. collections anyway, they could just have designed a better API in…
Isn't pure Kotlin a much more unlikely scenario than pure Scala? Kotlin devs certainly take pride at every opportunity of how much Kotlin piggybacks on Java, cf. collections. I think you can't have it both ways, having…
I have seen plenty of libraries using null to indicate an error. If this wasn't the case, as you allege, then why do Kotlin devs act like it's such a big deal? Why add a language feature for something that isn't even…
I think this comment shows a very fundamental lack of understanding how different languages handle errors. In Java (and Kotlin) -- ignoring the topic of exceptions as an alternative -- errors like "missing value" are…
> It was once routine for me and others I know to be prescribed hydrocodone for conditions like painful seized muscles, root canals or severe strep throat. We were apparently all in the ~80%+ who used it as intended and…
> I believe systemd-resolved, however, is one of those components that is entirely optional, and which nothing explicitly depends on... Yet. Wouldn't be the first time some "optional" component became mandatory.
GP is clearly right. What's the point of going "that's just your opinion" on every fact he mentions?
Scala developers can do whatever they want or need at compile-time.
> The systemd network stack is entirely optional and intended for scenario where you can't afford/don't need the 'fatness' of NetworkManager, just because it's there, doesn't mean you have to use it. Currently.
Jesus, it took me way too long to realize this was about online classes, not virtual classes in languages. :-)
Yes, exactly, which makes the claim even more baffling. Sure, they can just reimplement all their Java dependencies, but if they have to implement e.g. collections anyway, they could just have designed a better API in…
Isn't pure Kotlin a much more unlikely scenario than pure Scala? Kotlin devs certainly take pride at every opportunity of how much Kotlin piggybacks on Java, cf. collections. I think you can't have it both ways, having…
I have seen plenty of libraries using null to indicate an error. If this wasn't the case, as you allege, then why do Kotlin devs act like it's such a big deal? Why add a language feature for something that isn't even…
I think this comment shows a very fundamental lack of understanding how different languages handle errors. In Java (and Kotlin) -- ignoring the topic of exceptions as an alternative -- errors like "missing value" are…