Youtube comments of (@Onyx-it8gk).

  1. I think what he's actually trying to say while being diplomatic is that software has become overengineered and unnecessarily complex.
    186
  2. I'll be honest, this is a seriously impressive language by an absolute giant in the field. To oversimplify a bit, it has the safety of Rust, the performance of C, with the syntax of Python.
    164
  3. It really goes beyond just personal privacy. This feature basically makes Windows unusable for any type of enterprise environment. What if you deal with proprietary code, company bank accounts, network passwords, protected health information, pretty much any type of info that needs to be kept private. All that is completely up for grabs now just by one machine getting hacked.
    37
  4. Forcing C devs who aren't familiar with Rust to merge Rust PRs that are non-idiomatic and in Greg K-H's words, look like magic, is a surefire way to put malware into the kernel.
    16
  5. It's very refreshing to see people taking this issue seriously and coming up with innovative solutions, rather than simply writing it off as a "skill issue". Now, off to check out Vale
    15
  6. LLMs will never be able to replace human developers, but it's being used to create a sense of job insecurity, which in turn will lead to accepting things like reduced pay and benefits, and poorer working conditions.
    13
  7.  @I_Am_Your_Problem  Microsoft troll
    12
  8. I'm the person who posted that to Reddit, which is where I'm guessing you found it bc you uploaded this the next day. I don't agree with you ideologically or philosophically, and in fact I don't have a problem with Rust in the kernel per se. The reason I posted that is because I felt like some disclosure was in order regarding the big tech forces pushing Rust in the kernel bc people say things like, well Linus wants it in there. But to me it was very clear there were powerful forces working behind the scenes that were pushing for it, and my suspicions were confirmed by what Ojeda said. And as someone who values libre software, and given the history of those specific big tech corporations violating the GPL and other treatment towards libre software, it did certainly pique my interest and I felt like a public service announcement was necessary.
    12
  9. Yeah, it could probably give you a brain hemorrhage too.
    11
  10. ​ @Xevion Rust 1.0 is only ten years old. Calling it a 19-year-old language is a bit of a stretch.
    9
  11. Rather convenient it was a null pointer dereference and now it's instead just a logic error, because, well, if it were in fact a null pointer dereference it put on display for all the world to see how dangerous C/C++ are and highlights the fact why we need to move to memory safe languages. Crowdstrike and major software companies would basically be peer pressured into switching to Rust, et. al., which would cost billions for industry to actually do. Now it's just nah, nothing to see here, just a logic error. Whew! That was close! Now we can continue to run on decades-old legacy code!
    9
  12. ​ @vendetta.02 If you're trying to say Linus wrote this, that's incorrect. This was written by the lead developer of Rust for Linux.
    7
  13. Open source is mostly just a way for business to extract free labor out of programmers.
    6
  14. "Free as in free beer" means you don't have to pay for it. It's free as in cost. "Free as in free speech" means you have access to the source code AND you can modify the source code if you wish to make a different/better program.
    6
  15. @alelondon23  Almost 20 years on and Nim still doesn't even have native ARM/Aarch64 support. It's a community-oriented language that's not well suited to serious production deployment at scale. It's cool, but I wouldn't even consider it for a serious system.
    5
  16. Not everyone is that boring that we want to hear about the same thing 24/7 365
    5
  17. Omg, I love Gleam! Kris, can we please have a update with Louis!!! It's such a cool language that brought me into the BEAM ecosystem, and it's come so far and the community around it is awesome!
    3
  18. People are still going to need to learn how to program to not only use this tool effectively, but also to review and audit the code being produced. Having critical code infrastructure being produced by AI without a serious level of audit would be a huge mistake.
    3
  19. This is very true. If you want to look into this further, all of these labels AI was trained on were provided by humans, specifically thousands of underpaid people in India.
    3
  20. C, Linux, native integrated packages, mutable systems, these are all out of date. We have to design software and systems that are proactive rather than reactive. That means an operating system written in a safer language, like Rust, an immutable file system that can not be arbitrarily changed during runtime, and containerized applications.
    3
  21. @jordanjohnson714  To be clear, I didn't actually say "learn Haskell", meaning it's necessary to grok Hadkell, bc you're right, that's a BIG ask. What I did say was spend some time in a functional language, i.e. learn how to solve problems in the functional style. There are plenty of other functional languages besides Haskell that are easier to learn. When Graydon designed Rust, he pulled heavily from functional concepts, and in fact the first Rust compiler was written in OCaml before it was bootstrapped in Rust. At its heart, a program is a proof. Rust's correctness and safety mostly comes from its functional roots.
    2
  22.  @jordanjohnson714  I would seriously recommend Roc. It's far less "academic" and way more practical in its design.
    2
  23. People still use Windows? Wild!
    2
  24. SDKMAN! is on point 👍👌🙌
    2
  25. I really do appreciate your videos, but the new generations have a different learning style. They gravitate towards engaging, interactive and responsive learning materials. 1000-page textbooks really don't fit into that anymore.
    2
  26. > Open Source (OSI definition) = "no one has control over it". Correct, EVEN its own creator. This is what has allowed big tech to leech off of developers. French fries is a bad example, because McDonald's didn't create French fries. A better example would be the McFlurry, because McDonald's actually created it.
    2
  27. ​ @horusfalcon I'm not exactly sure of the point you're trying to make. If you're just trying to make the point that the McFlurry is proprietary, yes, of course, but that's really beside the point here. I was trying to stay within the parameters of the original comment. It's clear they don't really know anything about open source licensing and software. I'll try to explain why McDonald's to French fries is a poor and misleading example. French fries are an abstract concept. No one could ever patent or make proprietary either the name or concept of French fries. Tying this into software, no one could ever patent or make proprietary the concept or name of "image editing". We do not need open source licenses to protect that. The original comment is like say we need open source licenses to protect the general concept of image editing software. A specific piece of software, let's take GIMP, is a concrete creation, like the McFlurry. Any piece of software is a concrete creation, not a generalized or abstract concept. In that sense, any specific piece of software has the relationship of McDonald's to McFlurry, not McDonald's to French fries. Open source licenses are not used to protect generalized concepts, like French fries. That's like saying we need open source licenses to protect the general concept of an operating system kernel. No, specific licenses are designed to protect specific creations, such as the Linux kernel, not the concept of kernels in general.
    2
  28.  @RenderingUser  I personally would agree with the second part. I'm not saying Rust is rocket science, and I'm not against it, I'm just saying for me personally it has not been easy to learn and people who say anything is easy to learn can only speak for themselves.
    2
  29.  @TrevorSullivan  Btw I do really like your Rust series! And Lua. I've watched both. You're a great teacher.
    2
  30. Can you please try not to give your audience a seizure when you decide to make a video? You need flash warnings on your videos.
    2
  31. ​ @albertoarmando6711  Yes, learn C and assembly before anything else if you want to be a systems programmer.
    2
  32. Smalltalk! Alan Kay is one of my favorites! Not only is he a brilliant programmer, but also a brilliant educator! On a side not, you really have to get Sean Baxter on to talk about Circle. It makes C++ memory-safe like Rust. Far more promising than Carbon or CppFront.
    2
  33. There are biological limitations to this type of technology. I'll give an example. When a heart surgery patient goes on bypass, their blood is circulated by a perfusion machine. The longer their blood circulates through said perfusion machine, the more it breaks down. They can only remain on bypass for a few hours, then the risk of permanent brain and organ damage sets in. This is because our blood does not like to circulate through anything other than living tissue, i.e. arteries, veins, etc. Circulating through all of the plastic tubes causes it to break down. A similar thing happens with tissue-computer interfaces. You'd have to be pumped full of antibiotics and other serious drugs to arrest this process for these devices to work long-term.
    2
  34. This comment is pure gold 😂🤣
    1
  35. Jumping straight into Rust from, say, C or Java is usually a mistake. Rust borrows heavily from the functional paradigm, so you definitely want to spend some time in a functional language first, bc Rust is essentially the melding of the imperative and functional styles. I promise, you will pick up Rust much, much faster and understand it better.
    1
  36. ​@bm1259 Most drivers think they're better drivers than they actually are. That's not meant to be personal. It's often hard to take full advantage of Rust unless you have a strong background in computation, so things like the lambda calculus and type theory. I know Forest has a CS degree, but most people coming to Rust are web devs who don't have such fundamentals. The way you solve problems in Rust is completely different to C, C++, Java, etc.
    1
  37.  @scitechplusexplorer2484  You can lead a horse to water, but you can't make them drink.
    1
  38. @Lykkos-321  Here's a quote from the new TIOBE report: "Lots of eyes were on Rust and Kotlin this year. Did they live up to their promises in 2024? Rust is still getting more popular. Despite the amazing speed of Rust programs, its steep learning curve will never make it become the lingua franca of the common programmer unfortunately." I'm trying to set people up for the best success. It's the advice someone wishes they would have taken. Maybe not you, but someone.
    1
  39. These people are so enthusiastic about trying to put us all out of a job.
    1
  40. You're confusing libre (free) software with open source. The two are fundamentally different. So-called open source was created to co-opt the free software movement.
    1
  41. Gleam is fun Rust!
    1
  42. Can you do a breakdown of run0 for Linux released with Systemd v256? It's supposed to be safer replacement for sudo. Would be nice to have an explanation of the internals.
    1
  43. Talk about job security 😂
    1
  44. The whole world runs on unsafe legacy code and capitalism is too cheap to correct its mistakes or invest in new technology.
    1
  45. I love C, but it's true that C/C++ are definitely on their way out for critical production code in the software industry. They're still great for teaching, though. But there's no doubt the software industry is undergoing a major shift to memory-safe languages like Rust. We've had over 50 years to learn and improve on C. We have better, safer tools available today. Let's not treat a programming language like a religion. Programming languages are just tools.
    1
  46.  @DeveloperVoices  Awesome!
    1
  47. ​@ABaumstumpf You're not understanding the point. French fries are a concrete concept just like a car is a concrete concept, but Ford cannot license "a car". Chevy cannot license "a car". Ford can only license the Ford Focus. Chevy can only license a Chevy Corvette, etc., etc.
    1
  48. ​ @ABaumstumpf I'll try and explain it another way. Chips are a specific dish, too, but it's too abstract to be controlled. Lay's cannot copyright nor have any control over "chips", just like McDonald's cannot copyright nor have any control over "French fries".
    1
  49. ​ @horusfalcon Gotchya. Sorry, things always get lost in translation.
    1
  50. All the white collar jobs about to go down the drain 😂 welcome to the working (soon-to-be non-working) poor
    1
  51. ​ @ItsDreamplay If R4L was pushing the Linux Foundation to provide paid Rust training for the C developers, I'd take it a little more seriously. When a professional software team has to learn a new language, like Rust, they bring in professional trainers. The Linux kernel is far too important for this not to be seriously implemented. If big tech wants Rust in the kernel so bad, they need to step up to the plate and pay for proper training. Let's have THAT discussion.
    1
  52. @ItsDreamplay  I already said what I have to say on that subject. I'm moving on. This is my comment and I'll say whatever I want to about whatever. You're trying to win an argument, I'm trying to provide better solutions.
    1
  53. I constantly hear from the Rust crowd that Rust is easy to learn for beginners. Well, it's not been easy for me, and I have a 3.8 GPA. Am I an idiot or an outlier? Neither. The truth is, no one can say X is easy to learn. You can only speak for yourself.
    1
  54.  @TrevorSullivan  As someone who first started with C, I personally would completely disagree. To me, C is far simpler. Again, we can only speak for ourselves.
    1
  55.  @RenderingUser  Will do
    1
  56. Insert Crocodile Dundee meme
    1
  57. I'm willing to bet that the people who have had their lives destroyed by drunk drivers fully support this technology.
    1
  58. This is why we need more development and adoption of Servo.
    1
  59. Pretty much every problem encountered by modern society can be summed up with one word: GREED
    1
  60. Ada is mostly used in the defense industry. It's never gone mainstream.
    1
  61.  @OCTAGRAM  Programming is going to look a lot different in 10 or 20 years. AI will be writing the majority of code in a specially designed language tailored specifically for that, which means it probably won't be human-readable.
    1
  62. The only real solution is new licensing. Well, these licenses already exist, so in that sense it's not like they have to be drawn up from scratch. But they're essentially fair-code licenses that restrict the use of the software in such a way that it protects the project from having their lunch eaten by big tech and ensures long-term success. The SSPL is just one example.
    1
  63. Billionaires aren't looking forward to the "End Times", just a population reduction of about 50% to 80%.
    1
  64. I'll tell you what's going to be great is when another newer, "safe" language comes out, "safer" than Rust, and they cram it down the Rust cult's throats and accuse them of "blocking progress" and "being stuck in the past". I'm going to pull up a front-row seat for that one 😂🤣
    1
  65. ​ @RomanAvdeevX You obviously don't know anything about Rust for Linux because complete memory safely isn't the goal, nor is it even possible in the kernel. Drink some more kool-aid.
    1
  66. Habsburg AI 😂 Never heard that before, but I get it. Basically inbred.
    1
  67. Next time you make a video, can you please not put all the flash transitios in everywhere. It's just flash, after flash, after flash. Some people have epilepsy and photo sensitivity medical conditions. Thank you.
    1
  68.  @lawrencemanning  Yeah, bc Redox OS is such a space and RAM hog.
    1
  69. It's often said that FDR "saved capitalism" by implementing some modest social reforms. It's probably more reasonable to say he saved capitalists from themselves, because they'll just take, and take, and take until there's nothing left for anyone else.
    1
  70. You didn't make the connection between the shake and Soylent Green, a 1970s dystopian sci-fi where the shakes are made of people 😱
    1
  71. Really, Lex? 🙄 JP is anti-intellectual and transphobic.
    1