The real deal y0

  • 0 Posts
  • 103 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle
  • Im not saying you are defending them, youre just missing a lot of stuff that happened around ai and nvidia in your comment and whatever genai we have now isnt all because of nvidia. That its locked to nvidia is because of what they did before ai hit public eyes.
    Current genAI also has not much to do with nvidia besides programs being based on cuda which uses nvidia’s tensor cores for neural processing. From a technical standpoint, nothing ai has to do with nvidia, they just played smart ( and unfair ).


  • Youre missing a lot of events in that timeline tbh :p
    Nvidia forcing developers to use cuda enabled hardware, hard locking their tech to their hardware, the crypto boom of 2016 and 2020, …

    Theyve done a lot of stuff to gamers and datacenters over the past years that made them as powerful as they were when gpt3 hit the public eye.

    Me? Im stearing far far away from them. I dont support that business at all.










  • Pre-locked bootloader times ive had multiple android devices be passed to me that were malware infected that changed the rom in a way that even a factory reset would not remove the malware. Locked bootloaders made it so the rom needed to be signed and unaltered on boot, fixing this. Root access also means apps can use and access api’s in android that it normally cant, changing settings and things inside android it shouldnt. What do you think happens when malware comes in? :p

    Imo, i agree what you said. bootloaders should remain locked but you should be able to somehow, in the bootloader, be able to add the os’ signature/keys to the bootloader’s trusted stuff like how secure boot on a pc keeps os signing keys and verification stuff inside the tpm.

    This way you can install lineage os for example, tell bootloader to trust it, and lock bootloader again so nothing can be changed anymore.
    I wouldnt take this from user input, as that is controlable by malware, but rather come from the OS itself. Maybe even during installation, idk




  • This is a very complex topic that is very hard to draw the line on.
    As a technical person who follows hacking and security news i can understand google introduced the api and warnings, as phones are getting hacked and unlocked bootloader or root can be abused to keep your malware going, and has been abused in the past.

    But as a user of fairphone/lineageOS, who tells google, apple, meta, … all of them to fuck off when i can, this scares me. The lockdown of devices can and is going too far. Hell, i even consider samsung’s android ui changes to be going too far, as it changes a shit ton of stuff and really is not a stock android experience. It locks users in their environment…



  • 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