The real deal y0

  • 0 Posts
  • 118 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle















  • As a software developer i know what iterative development means, its in our blood and brains ( or at least it should be ). Simulations can indeed only get you so far, and i agree sometimes you have to make things and take a plunge. However, and i would like to be really wrong here so correct me if im wrong, but other companies like nasa, do not just shoot shit up in space and hope for the best. They arent allowed to do so for a reason. They test and calculate everything very rigoursly to make sure itll hold up as expected. From thruster power, resistance to continues extreme heat from reentry, …
    All of that they do here, on earth, before shooting anything up into space. Otherwise things like the rover on mars would have needed like 20 tries instead of 2.

    These are things that looks like spacex is just throwing out the window.
    To take it back to software development, they are doing an iterative development ( which is very good for what they are doing! ) but their testing before production/release of software is so basic theyll just see how it responds out there. Thats a huge nono to me if youre going to end up crashing all those rockets in the sea killing a shit ton of nature in the process. Sometimes the means dont justify the costs to me, and this is one of them. Yes, the booster catching was nice to see ( eventhough it nearly ended badly ) and its idea is very good and needed, but the way to get there is…messy.


  • Specially this. How space x handles failures is a very hard nono in my book. “But we test in the field” is what space x says, and as a software developer its like saying “we test in production”.
    Yes youll get something use able faster, but its way way more costly in the long run and is nasty in between.
    My arse they cant test this stuff on earth. We have simulations, models, calculations, test, everything. Yes, things can and will sometimes still fail when going in production ( in flight ) but you want to lower the risk of it failing cause its costly as fuck.

    They dont seem to care though.

    Also, im not saying what they are building towards is bad, it really really isnt, but their methods is… Bad



  • DacoTaco@lemmy.worldtoOpen Source@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    edit-2
    4 months ago

    Their source code repo contains a copy of libogc for wii/gc builds because they were annoyed at us. And i do mean a copy. Not a reference, or a sub-module, a full on copy that they build before building the wii/gc executable.

    Their own issue, as long as we dont get reports of their broken shit…

    Then there are the multiple times they cloned emu repos and butchered them into cores. Or the fact they force the core interface on emulators making them bad.

    Retroarch is a nice project from a far, but the closer you look, the more you see huge ass cracks in the project, held down with duct-tape