• 0 Posts
  • 114 Comments
Joined 2 years ago
cake
Cake day: August 19th, 2023

help-circle








  • I’m very open to being an early adopter of mobile Linux phones. I’ve been unable to because of a couple of factors. I last seriously checked about half a year ago so take this with a pinch of salt.

    • Limited support for specific models. This means that the phone will work as a computer but won’t have the correct drivers for gyro, sim and whatnot.
    • Lack of extensive driver support. Phones turn off components to save power, this was not supported the last time I checked and halves the battery life compared to stock android.
    • Waydroid support incomplete. Many apps will work but some apps will bug out. Waydroid also has performance issues so it’s not as good as WINE for example.
    • Not big enough community. A lot of models are maintained by a single dev that checks in every blue moon.

    To get a Linux phone to be competitive on performance we’ll need to get driver APIs and component lists open sourced so it’ll be easier to gather the appropriate info and make drivers.

    There has been tons of progress though, Gnome and KDE have really strong touch support now and the apps scale decently.

    It’s coming but now fairphone is the only phone that openly supports Linux mobile distros and is open sourced.





  • I also had issue when I was working on a pycharm project back when I was on windows. During setup it asked me “What’s your name?” and my name has a cheeky accent which Windows was decided should be the name of my Home folder. Home folder also has appdata and whatnon so which the build system didn’t expect to have a an accent in the folder path.

    I ended up having to create a different folder and link to it then move all the path configurations to that folder link just so I could get imports working.


  • I use Jetbrains IDEs now for 5 years, I’ve used VSCode, Sublime, Atom, Vim, Neovim but I feel like Jetbrains IDEs are just better if you have the RAM to run it.

    1. It’s a setting.
    2. Doesn’t happen
    3. Doesn’t happen
    4. Searchable actions, just search for “encoding” in this case.
    5. That’s an LSP/project mismatch usually just a setting. Most things are supported but worst case you can remove the error.
    6. Happens if you run out of RAM or open a very large file.

    So it’s not all bad, but comes with a lot of good such as “invert if statement”, “use template strings” and “extract method” thingies along with a load of plugins.





  • Don’t get me wrong, I still write more than 98% of code by hand and of course, I can write those functions myself in 30m myself but I can get it in 60s with the AI. LLMs can write code to that does parse - > model - > map - > format with only one or two easy to fix bugs.

    It’s in the very niche cases where it’s just tedious to write something out that LLMs actually work. “Write an API client that uses [library] that handles these requests/responses” comes also to mind as something that would work.

    I’m using now also to learn react native where I get bugs I’m very unfamiliar with and SO doesn’t give me a good answer.

    I’ve also had decent success at having it review my code with “how would I further optimise this code” and it gives me some pointers and then writes buggy code but the approach is correct usually and I can implement it myself.