The version of Debian it shipped with had a bug where I couldn’t install any software updates without deleting some random lib64 directory. Once I did that, everything was fine.
Neat, I’m still running the stock Android but I’ll try. How long ago did you do that? Is your fix documented somewhere?
No doubt NVIDIA is peddling AI as they are financially depending on it now.
Now from claiming something is powerful and even used to actually shipping code on something low level and benchmarkable like (GPU) drivers I have doubt. I imagine they can say they use AI there to rephrase comment and it would “technically correct” but beyond that I’m still skeptical.
Regarding chip design, AI has been used for decades … if you consider routing to be AI. It’s not generative in the modern sense, it’s not using LLM, but it’s automated a process.
To me it’s the typical Harvard Business School playbook. C-suite repeat keywords they read in their peer most popular magazine, they aggregate in a document they call “strategy” they lower down the chain of commands people “execute” that because they must, thanks to KPIs.
I’d love to hear it from an actual engineer working on drivers but I imagine it’d be hard to get a honest opinion with NDAs and all.
Thanks for providing all the sources!
Source please
Sure, but FWIW I play from AAA to indies and it “works” as in no bug, no noticeable visual glitch.
I don’t benchmark from my driver version to the previous one on Windows or Linux or a price point equivalent with AMD hardware, I just play. I don’t think anybody gain much from checking performance benchmarks before playing a game, at least I can say for sure to me that’s not part of the fun.
I would notice if something was blatantly wrong e.g 50% performance hit, but I wouldn’t if it’s 5% hit. I don’t really care for it as it doesn’t affect my gameplay. Like I said, it’s from a casual player, not a pro player nor a game tinkerer.
Working “better” on Windows means nothing to me. Either I can play and I’m happy or I can’t (which never happened) then I’d be disappointed and potentially check why.
PS: I’m also a developer of XR content so I’m relatively confident I’d spot any significant problem.
No idea, I’ve been playing “normal” games and VR games with my NVIDIA card for years now on Debian and… it just works. It just keeps on working. Maybe people are hardcore tinkerers that mess with specific options but me, I just play and I’m happy with it.
Of course, in fact you do not have to change right now, or even next month. Instead you are in a great position when you already have a device because it means you can take the time you need to prepare for a transition without any rush. The problem IMHO is … if you repeat the cycle. If in few years, or whenever you do change phones you say, again “Switching isn’t necessarily easy or doable for everyone” while having done nothing to change your situation.
Please, don’t rush a change and make it painful. Take the time and use the resources you have… but do something, even if a small thing, to go where you want to be. Do not stay stuck in a place you do not even enjoy.
Honestly… I come from iOS, using for nearly a decade. Yes that stuff is secure, yes that stuff is (or at least was) stable, yes that stuff is slick to the point of being a status symbol… but DAMN does it suck for interoperability!
Every success of bringing the Apple ecosystem to interact with anything is just so ridiculously hard… for in the end bringing very little.
Do yourself a favor, switch to (deGoogled) Android to enjoy KDE Connect, adb, scrcpy, etc just working out of the box, copying normal files the normal way, however you want. Try “just” Linux if you can’t but on mobile that’s not for everyone.
Again, I celebrate this success and all ways, e.g. iSH or Homebrew, that help to tinker, manage, work with Apple hardware but honestly I suggest ignoring it entirely. Just rely on software and hardware that actually provides the bare minimum to be interoperable. Not this.
Instead use this, and iSH, Homebrew, libimobiledevice, and the rest to transition AWAY from that locked ecosystem.
FWIW rsync also works on mobile phones and VR standalone HMDs, via e.g. termux or ish … so it’s really on working fine on… pretty much anything with a terminal and a connection really.
Warmly recommended.
Also if you need more than solely the last version, check rdiff-backup.
Became quite trivial, e.g. took me 15min to get CopyParty on a Debian on a Banana Pi running RISC-V https://mastodon.pirateparty.be/@utopiah/115332958192905605 and staying headless performances are fine.
Yep, that’s the point of https://lemmy.ml/post/39238406/22339896 but it’s “just” an FPGA though "Precursor - Mobile, Open Hardware, RISC-V System-on-Chip (SoC) Development Kit "
Ah… but then that’s not enough, you need to insure that the supply chain itself is 100% free! For example if you are using an Intel CPU, how can you verify it does what it says it does?
Enter precursor.dev ! Check this out if 100% free is not enough for you.
PS: honestly do what makes pragmatically your world, and that of the ones around you, better. Hopefully it is toward free software but IMHO if you have more agency with usage (which yes does overlap significantly with this) then it’s a powerful step to keep on doing so.
yet to get my first. I had been considering the Meta Quest 3, but Meta.
Perfect then
You can also run kiwix-serve to provide offline Wikipedia, StackOverflow, Project Gutenberg and more. Even on a very basic device search works as indexing is well done.
Remove the battery.
One should hope, and the tinkerer community, me included, is eager for both of these features.
Regarding new content I posted https://www.uploadvr.com/valve-isnt-currently-working-on-a-new-vr-game/ countless times because to me that’s maybe the biggest bummer. I have several headsets so I don’t need “yet another one” that is roughly equivalent. I need something genuinely different. A flat SeamOS (no immersive features to KDE Plasma) is boring but understandable, no new content from the quality only Valve (unfortunately) seems to be able to produce makes me think I’m not in rush. Just like hand tracking or WebXR we can hope for surprises but it mostly shows it’s considered a thin terminal for Steam, nothing more, and I have already few of these (thanks to Alvr, Wivr, CloudXR, but also just Steam streaming).
At uni I logged on a thin terminal that would then connect to a computer with hundreds of users.
You think of your computer as a desktop but in a reality it can be a lot more than that. Hundreds of users could simultaneously use it without bothering you (assuming resources are sufficient).
Obviously that also means you shouldn’t be able to see or edit files from other users
You, like most of us to be clear, are just using it in a very very limited way.
It costs pragmatically nothing to keep this model working and it seriously limit usage to remove that. Now if you do want, you can autologin and skip all this but at your own risk.
TL;DR: a desktop is just a server with a screen, mouse and keyboard, nothing magical about it. If a server can handle hundreds of users, so can your desktop even if that’s not how you use it.
There is a mix of very precise issues with very detailed examples but also a thread of not being “comfortable” which makes it challenging for me to make practical suggestions.
If that’s OK I’d suggest to start with the top 5 problems you have then I, and hopefully others, can give potential paths forward.
One generic advice though the learning curve might feel threateningly high but I’d argue it’s if you consider this a short term adventure. If you think about the next year or so, discovering the intricacies of a distribution or shortcuts for a desktop environment look like a bad investment of your time. If now you consider this, especially as you mentioned managing servers for years, relying on WSL, etc a long term investment. If you imagine than in 10 years, heck even 50 years, console, servers, VR headsets, desktop, phones, tablets… all run Linux (which to be clear basically is the case now, even before the Valve recent announcement) then it’s a totally different dynamic. I don’t mean “behind the scene” kind of things, I mean today you can use adb shell on your standalone VR HMD, on your video projector, on your phone, etc. You can also have the console on your Mac laptop. It doesn’t make learning easier, it’s just a lot more motivating IMHO.
Also on that topic, my “trick” is to write down notes. It can be actual notes or just my ~/.bashrc or ~/bin in a more pragmatic day to day solutions. They do add up, day after day, years after years. Each challenge once overcome can be composable and a new opportunity to do more.
What kind of use case for Super over meta do think I’m missing? Like I said if I do meta-e I get in KDE Plasma the file explorer, Dolphin, isn’t it also the behavior you get?
sold my OG Ergodox
I basically forced myself to use it and it was a good transition from the Microsoft Sculpt but now that I’m a 3x6 I don’t want to go back ;)
Transition is always tricky and I find that NOT having a project to rush on for few weeks at least is what I need.
Had one from the start and also had a reMarkable 1, 2, Pro and e-readers with e-ink. I did discuss all that before so feel free to check my comment history. You can also check related prorotypes at https://fabien.benetou.fr/Tools/Eink including for the PineNote.
Now on your questions :
Last time I check it didn’t run well enough (basically CLI only) so I’m still on their stock Android OS. Worked great. According to other comments it seems fine now and I’m familiar with
KOReaderand a bitXournal++so I’ll try again.Easy, I didn’t do anything ;)
Well in my case yes but again Android, so if you are familiar with it, e.g.
adbthen it’s easy.Fine but power management kind of sucks so it will not go to sleep properly and thus waste battery. It’s also heavy so honestly I wouldn’t travel with it.
Again, I did share on Lemmy quite a bit. I do warmly recommend it if you are a tinkerer who doesn’t travel too often. If you are a minimalist who wants to get things done then IMHO reMarkable is better.