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

help-circle


  • They’re basically saying they won’t ship off data to be processed to anyone else. Apple server hardware will process it in data centers.

    There’s then a further promise that this hardware will be isolated from other things apple is doing, so that no other apple processes not related to AI will be able to see this data.

    So, for instance, some other AI company might cut a deal with Amazon, get a discount on AWS processing, and in exchange, let amazon snoop through the data being processed. Or, a company might use a cheaper process in an existing data center that isnt particularly secure, and just not care if its being spied on. I’m sure there’s more likely scenarios as well, I’m not a security expert, but apple is promising to thwart any similar thing, by promising the “cloud” for AI is a unique cloud, not just encrypted or whatever, but actually physically separate from everything else

    Its the equivalent of saying “this product won’t trigger your peanut allergy, we’ve built a facility that will never see a peanut, so cleaning procedures are easy and accidental contamination is impossible since this product is the only thing made in this factory.”

    These are still just claims though, not facts, so we’ll see.



  • In mint I can right click in a folder and reopen the folder with elevated privileges. That’s my primary, I assumed it was standard but if it’s not common I guess it’s a cinnamon thing. If so, maybe cinnamon is the desktop of choice for avoiding the terminal.

    I didn’t do my full diligence to the samba GUI thing, apparently. That’s a good catch.

    To salvage my argument, yumex has a GUI and extends yum, so while the instructions expect the terminal, I think it’ll be optional.

    I still recommend it to nobody, but someone who set out to avoid the terminal doesn’t have to fail.

    yumex, pip-gui, and aptitude give yum, pip, and apt GUI’s, respectively, so most anything that expected the terminal should be doable without it. All it costs is a bunch of effort troubleshooting GUI things or finding out one doesn’t display error messages and logs them weirdly or whatever.


  • Well if i double-click a file I’ve made executable, it will ask if I’d like to run it, and most software will have a github or downloads page that will give you direct downloads to the software.

    In other words, I can successfully install things like a windows user, I just have to go the extra step to open the file’s properties and make it executable with the GUI first.

    Apt is faster, and it’s also faster to do a direct download, make it executable, then execute it in the terminal, too. But I CAN do it.

    Config files can be edited in the GUI text editor, it’s just slower.

    To test my claim and prove your third point, this link is the repository for a samba GUI, found at https://www.samba.org/samba/GUI/. Specifically, it’s SMB4K, the first one.

    Convenient? No. Would it update automatically? No. Do I want to do it this way, or recommend it? Still no. But it does function.


  • So, you’re pretty much spot on with how emulators work. I also like using claymation to demonstrate it, like this. Your computer bends over backwards to give the game the exact environment it expects.

    What makes recompilation more than a simple script is the rebuilding aspect. I brought up claymation because it’s a great analogy for this, too. An n64 ROM is a complete set of characters, sets, and a script for a claymation movie. It’s I in one studio right now, and that studio is the N64, but you need this to be in your PC studio.

    First, you have to decompile your sets and characters. You take reference photos and rip out every tree in a forest set and roll each tree back into it’s own ball of clay, with its own reference photo each time. Every little clay cobble on a road, characters outfits, hair, limbs, you meticulously separate every piece of clay that Nintendo shaped, ball them up, and pack them. You now have a million little clay balls and reference photos for every one of them. You take these back to your PC studio. Thankfully, with these reference photos, your clay 3D printer (compiler) can return these balls into something very close to their original shapes, except there’s a bunch of little mistakes. One character’s leg is slightly thinner and longer than it should be, which messes up their gait when you re-film this, so you manually tweak the leg to be accurate. The cobbles don’t quite fit the same, they’re a bit smaller, but you have extra clay because of that so you just make more cobblestones. The road doesn’t look exactly like the original, but that’s fine. The trees, again, don’t quite fit right, but you’ve made similar trees in your studio before and you know those will work so you actually just use those as references instead of the originals. You get filming but this one scene just isn’t lit right, and you can’t figure out why, but you eventually figure out the N64 studio opened the blinds on their window to get natural sun in this shot, but your studio doesn’t have a good view of the sun at that angle, so you have to get a good lamp.

    You face a million little hurdles decompiling and recompiling. Its almost literally reinventing the wheel. Almost all the work goes into little details that almost seem unnecessary, but there’s so many that it’s absolutely necessary. I was watching a playthrough of a recompiled majoras mask earlier today, and the Dev of this project found his way there, too, and he said it took a few days to get majoras mask to decompile and recompile, and about a year to fix all those little details that in software become lag or new bugs. So the script guy isn’t really wrong when he said he could do it fast, but he definitely wouldn’t do it right.









  • The more the code is used, the faster it ought to be. A function for an OS kernel shouldn’t be written in Python, but a calculator doesn’t need to be written in assembly, that kind of thing.

    I can’t really speak for Rust myself but to explain the comment, the performance gains of a language closer to assembly can be worth the headache of dealing with unsafe and harder to debug languages.

    Linux, for instance, uses some assembly for the parts of it that need to be blazing fast. Confirming assembly code as bug-free, no leaks, all that, is just worth the performance sometimes.

    But yeah I dunno in what cases rust is faster than C/C++.


  • According to The arch wiki, x11vnc operates differently than some other servers and is not capable of going headless. You’d need the dummy plug.

    On that same page, though, it lists the alternative to x11vnc as Xvnc, and links to TigerVNC which is capable of going headless, and has an example config for going headless.

    I haven’t tested tigerVNC specifically, but it’s known, so I expect this is the solution to your problem.