• 2 Posts
  • 163 Comments
Joined 1 year ago
cake
Cake day: February 19th, 2024

help-circle



  • Hm, the the absolute least scary option would be to try it out on a live bootable USB. That’s not difficult, it’s the first step before installing pretty much any modern distro.

    The second least but slightly more technically advanced would be to get a second hard drive and install Linux on that completely separately from your windows install. The technical part here is your BIOS will have a default boot drive and will boot from there on start up, so you would need to interrupt the boot and select which OS you want.

    I personally went with the second option, as dual booting from the same had drive is a minefield with windows, as they have a tendency to wreck the Linux boot part. But when I swapped, I set the default boot to my Linux hard drive to get in the habit of using it, and if I ever need anything from windows nowadays (only VR) I select that on boot.






  • Edit: I reread your message, and I missed the double negative in your sentence. Did you mean games never run better with DLSS?

    That is odd. DLSS should definitely net you a handful of frames. Games often run better with ray tracing on and DLSS on quality vs native without ray tracing, sometimes doubling it. Some newer titles I find are only playable (at the very least 60 fps) because of DLSS (which is a whole problem in and of itself). I absolutely prefer running without any sort of temporal AA because of smudges and ghosting.






  • I read it as “you type a URL in the address bar, we’ll take you there. You want to search for something using the search bar? We got you, we’ll forward your search to the search engine of your choice. All free of charge.”

    It’s just worded in such generic legal wording it makes you gag. But them pointing it out so explicitly just makes me more suspicious lol. I think it’s fine for now, just another wall of text to keep an eye on for any future modifications.




  • I agree kotlin can be a cool language sometimes. And I’m sure it’s been a more gradual journey if you’ve worked with it while it’s been evolving. But man, jumping in at Android 10/11 having to remain compatible with 7 (we’ve moved up to a minimum of 10 now thankfully) with how much background services and file storage permissions changed right around that time was an extreme headache to work around.

    But I definitely prefer C#'s async/await Tasks than trying to wrap my head around all the various coroutine scopes, runBlocking and all that jazz. I know they are very similar concepts, but there’s just something with coroutines that isn’t clicking in my head.


  • Android is the worst environment I’ve ever worked in. Concurrency? Use Threads! No wait, we got handlers and loopers now. Oh wait sorry, we’re doing coroutines this year.

    Now let’s do DI with Koin. But ooh google released their own version with Dagger, but oh no! It’s clunky to use, so well slap some more stuff in top and call it Hilt!

    Networking, persistent storage, UI, permission flows, any other API they have follow the same pattern of new shiny thing, oh it didn’t turn out very good, here’s a new thing to replace the old. Congrats, every blog and SO answer is now outdated. Even the build system has gone from Maven to Gradle in Groovy to Gradle using Kotlin.

    And don’t get me started on Android Studio itself. The worst IDE I’ve ever touched. Any changes to the manifest and now you need to manually sync the project. Be prepared to create a shortcut to gradle’s cache folder for easy deleting whenever it shits the bed.

    Fuck Android development, I hope I’ll never have to touch it again after this job.