If you set up the nonguix channel you need to add the nonguix substitutes, or else it will compile whatever nonguix packages you're using from source, including the kernel, which will take forever.
Also, the nonguix substitutes server is currently down for ipv4 users but someone has set up a mirror at nonguix-proxy.ditigal.xyz, so you can use that instead.
They also might go with a compute puck. That would allow them to offer a cheaper option which streams from your PC and a more expensive one that works by itself.
Pretty sure they are close to final. It's disappointing, as they look like a big step down from the Index controllers, but it seems like seamlessly emulating a gamepad is important to them.
I'm not sure. I remember seeing an example in the docs, but I can't find it now. Actually the docs in general are a lot less opinionated than I remember them.
One thing that I did find is that the ion shell document mentions that it isn't a posix compliant shell because they would have had to leave out a bunch of features.
This is true, but the differences go even further than that. Redox is intentionally non-posix-compliant. This means that userspace programs written for posix operating systems may or may not need patching to even compile.
Part of the philosophy of Redox is to follow the beaten path mostly, but not be afraid of exploring better ideas when appropriate.
I blame C++. When these kernel hackers hear about how they should switch to this shiny new language that's going to make their code so much cleanser and more manageable, I don't blame them for thinking it's all bullshit. It was last time.
I finally watched the talk today and that wasn't what I thought he meant. What I thought he was getting at was that the rust parts of the kernel interact with lots of other modules written by people who don't know rust. When those C modules change their semantics in ways that break the rust code, they can't go fix it because they don't know rust. In fact, whenever they make a change, they don't even know if they broke some rust module, because they don't understand the rust code well enough. And this is something that everyone is going to have to live with for the foreseeable future, because you can't force all those other kernel hackers to learn rust.
It's the same idea, and may even share some assets, but it's specialized to VR. It's kind of similar to the way that steam input and SteamVR input have the same basic purpose but are separate systems.
Besides the Steam Link device and the Steam Link android app, there's also an app with the same name on the Quest store that lets you stream SteamVR games from your PC.
There are already libraries like clap that allow the developer to specify all their arguments including short and long variants and description strings. I think some of them will automatically generate --help based on the specified options. I could imagine a library that takes the same specifications and makes an interactive menu or a tui form out of them. It's an interesting idea.
Haskell is typed and has a repl.
If you set up the nonguix channel you need to add the nonguix substitutes, or else it will compile whatever nonguix packages you're using from source, including the kernel, which will take forever.
Also, the nonguix substitutes server is currently down for ipv4 users but someone has set up a mirror at nonguix-proxy.ditigal.xyz, so you can use that instead.
I find the Quest 3 to be about the same as the index comfort wise, maybe a little better.
It would be weird if they offered steam link for Quest but not for their own hardware. Stranger things have happened though.
They also might go with a compute puck. That would allow them to offer a cheaper option which streams from your PC and a more expensive one that works by itself.
Did they just take Gabe follower's tweet and pad it out into an article? I don't see any actual reporting here.
Pretty sure they are close to final. It's disappointing, as they look like a big step down from the Index controllers, but it seems like seamlessly emulating a gamepad is important to them.
This looks really fun.
I've got a galago pro that's a little over five years old now, and I'm still pretty happy with it.
Doesn't Kobo use Adobe DRM? I don't see how that's much better than Kindle.
I have a bunch of books from both stores, and Google too. The downloading and DRM removal process was about the same for all of them.
You can friend me for a code if you don't have one yet. My username is Octorine.
I'm not sure. I remember seeing an example in the docs, but I can't find it now. Actually the docs in general are a lot less opinionated than I remember them.
One thing that I did find is that the ion shell document mentions that it isn't a posix compliant shell because they would have had to leave out a bunch of features.
I wonder if someone's working on this from the other end. Like, instead of porting mrust from gcc to tinycc, port rust 1.79 from 1.78 to 1.1.
This is true, but the differences go even further than that. Redox is intentionally non-posix-compliant. This means that userspace programs written for posix operating systems may or may not need patching to even compile.
Part of the philosophy of Redox is to follow the beaten path mostly, but not be afraid of exploring better ideas when appropriate.
I blame C++. When these kernel hackers hear about how they should switch to this shiny new language that's going to make their code so much cleanser and more manageable, I don't blame them for thinking it's all bullshit. It was last time.
I finally watched the talk today and that wasn't what I thought he meant. What I thought he was getting at was that the rust parts of the kernel interact with lots of other modules written by people who don't know rust. When those C modules change their semantics in ways that break the rust code, they can't go fix it because they don't know rust. In fact, whenever they make a change, they don't even know if they broke some rust module, because they don't understand the rust code well enough. And this is something that everyone is going to have to live with for the foreseeable future, because you can't force all those other kernel hackers to learn rust.
It's the same idea, and may even share some assets, but it's specialized to VR. It's kind of similar to the way that steam input and SteamVR input have the same basic purpose but are separate systems.
Besides the Steam Link device and the Steam Link android app, there's also an app with the same name on the Quest store that lets you stream SteamVR games from your PC.
I was about to write this exact comment.
Even if I hardly ever play standalone, it's nice to have the option.
Also the ability to wander around an arbitrarily large play space is nice too.
There are already libraries like clap that allow the developer to specify all their arguments including short and long variants and description strings. I think some of them will automatically generate --help based on the specified options. I could imagine a library that takes the same specifications and makes an interactive menu or a tui form out of them. It's an interesting idea.