Comments by "Ralphie Raccoon" (@Croz89) on "Fireship" channel.

  1.  @SirCharcoal  FPGA documentation is often pretty terrible though.
    4
  2. I used PyCharm for a while because you could get a lot of plugins for it. There was even a really good LaTeX plugin, so you could write academic research up in a Python IDE. But compared to VSCode it is much, much slower. Even something like a VCS commit and push was so much quicker in VSCode, and start up was always a pain, I'd be waiting a good couple of minutes before I could edit anything. And VSCode's LaTeX workshop extension isn't bad, through it still lacks some features of the PyCharm extension, that was ridiculously comprehensive.
    2
  3. Some devs: "lets rename it to something much more offensive".
    2
  4.  @janelain8611  I think it's more the fact they had to be perfectionists. Hardware capabilities were very limited back then, you had to make things as optimal as possible to squeeze out every ounce of performance. Nowadays outside of very specific niches, nobody needs code to be as efficient as possible. And of course it's important to note that women were not doing all the work (though not to diminish their achievements). The men were designing and building the hardware, for the most part. Computer hardware was far less standardised back then. It was very much a collaborative effort between the sexes to create the computer systems used for the moon landings.
    2
  5. Amazon Q? I'm just waiting for the Star Trek jokes.
    1
  6. ​ @yurrwithme The most ignored rule on stack exchange. Everyone knows taking it to chat is just a way to kill the conversation apart from a small group of users having an argument.
    1
  7. Sounds like Airbus recently.
    1
  8. TeX/LaTeX is notorious for this. One error can cause a cascade of unrelated errors, because the typesetter spits out something invalid, which then causes the typesetter to produce something else that's invalid, and so on and so on until you get to the top layer.
    1
  9. If you really want to go into hardware, FPGA programming with VHDL/Verilog could be an option. Problem is it's so specialised and so unlike anything else you will do, that there's not that many transferable skills.
    1
  10. Now I'm imagining a malevolent AI with a valley girl accent.
    1
  11. It's cheaper than a MyRIO, that's for sure. Though it's not really powerful enough for some more advanced automation and robotics tasks.
    1
  12. Doesn't run ads? Sure that's not do true nowadays... seen some crypto nonsense on there recently.
    1
  13. To be fair, it kinda was in the early days, computer architecture was much less flexible and more limited, you had to build the hardware around the problems you wanted to solve a lot more. That changed with more general purpose computing later on.
    1
  14. I'm slightly disappointed that my boy from the Goofy Movie didn't show up when "powerline" was mentioned.
    1