Comments by "" (@diadetediotedio6918) on "Mental Outlaw"
channel.
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
1
-
@thewitheredstriker
This is because nowadays the amount of low-level programming is infinitely less than the amount of high-level programming, which wasn't exactly like that at the time (and let's face it, C didn't last that long, most companies in the 2000s had a good part of their plastered systems made in Java and languages other than C, even banking systems used COBOL and not C, it's not like C The programming language), not to mention that in that era most of the systems we use today were being written.
Nowadays for a language with the ambitions of rust to prevail and become mainstream, it first needs to be effectively adopted, which effectively won't happen if we stop using it because it's not established (that would be a vicious circle), re-writing systems from scratch is simply impossible, the cost is gigantic and would be impractical for the overwhelming majority of corporations, hiring new programmers too, and even training existing ones would be costly, which is precisely why adoption is not so fast ( the fact that Rust has a relatively high learning curve doesn't help with that). In terms of stability, on the other hand, the language appears to have few bugs and it doesn't seem to be the case that it is static, it has an active community and people are willing to use it, think about what Linux itself would have been like if people never had given it a chance in the first place?
At the end of the day, it all comes down to cost, and it seems big companies are starting to look at Rust as more cost-effective than not using it (we're seeing movement in big companies like Amazon, and Microsoft itself recently, and even Dropbox has a significant portion of its systems written in the language), every new technology not established is a gamble until it isn't, which is why the world moves slowly (e.g. we still don't have IPv6 in, I would say, more than 50% of places in my country).
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
@happygofishing
No, it literally does. What you are even saying? This don't make any sense, are people crazy nowadays?
See, you, NOW, have the FREEDOM to pick a fork and stick in someone's else throat. You would obviously be violating the freedom of that person and his personal integrity, but YET, you have that freedom. Freedom implies freedom to not do something good as well as freedom to CHOOSE to do something good (in fact, if you don't have a choice there's nothing "deserving" or good in the action, you must first be free to make virtuous actions).
What those licenses mean is that you are ABLE to use the code in your own ways, this don't imply you WOULD, it also don't OBLIGATE you to do it. In fact, refraining from do so is MUCH more virtuous than just using copyleft licenses where you are obligated to it all together.
1
-
@z411_cl
This is not a good definition or conceptualization of freedom. If you take the freedom of people to do things, no matter how much time passes, it will still be less free than the alternative of [not doing it], the fact that you believe it is more free because it allows a specific property you want (in this case, the prohibition of releasing software without the source) don't make it less problematic over time.
I also don't think MIT, Apache or BSD are the pinacle of freedom, just so you know, I think a more free license would block things like suing people and allowing for all people to reverse engineer your code and even sell modified versions it (without using your name, obviously), it would be something that restricts only the truly evil things that most people can't fight against, like using the power of state to crush people down, but I don't think if a license like this is possible, I'm not a lawyer.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1