<pedantry>For English language text letters are 1 byte when encoded in UTF-8 (which is how essentially all text is stored and transmitted these days).</pedantry>
Though it probably balances out in your final answer since you’re not counting spaces, punctuation, formatting, or other markup.
refusing to follow semantic versioning standards that are designed to essentially account for that is pants-on-head stupid.
Seems like it would be a bit hard to follow a versioning scheme that it predates by almost 20 years. Lua 5.2 even predates semver 1.0.0.
Before semver there was basically no standardization in versioning schemes and the meaning that semver applied to version numbers basically didn’t exist (at least in my experience) before it came around. Everyone just kinda had their own meaning for what version numbers meant.
I’m a fairly experienced Rust Dev (I’ve been paid to write it since 2014). I’ve never use Tauri, but damn it looks complicated.
If your goal is learning rust, I’d suggest learning on something simpler. Avoid complicated “ecosystems”, anything super macro heavy, or async in general. Go write code like you’re a college freshman. Duplicate code, call .clone() and .unwrap() with wild abandon. There’s no reason to throw all the hardest parts of the language at yourself all at once.
If your goal is ending up with a GUI application, I don’t really have advice for you, I’ve never figured that out myself.
That’s kinda, at least historically, been Nintendo’s whole thing: https://en.wikipedia.org/wiki/Gunpei_Yokoi#Design_philosophy
Thanks!
I would imagine it’s just some sort of really basic shim driver to get a communication channel between the controller and steam, then from there everything just goes through steam input.
That’s the kind of choice you make when you need to just get ‘it’ working. IIRC when the deck, its input depended (more?) on the steam client too. I’d imagine that they’ll finish the slow part of the process eventually to make the controller work more generally too.
The store page said 3-5 business days for the early orders and 6-10 for the later orders.
FWIW, I was getting the same checkout error as everyone else for half an hour while trying to buy with steam wallet credit.
I got one and will try to post to this community with my thoughts after I receive it.
The dpad is also my biggest worry with it.
What did you do to upgrade your deck dpad? I would love to do that to mine too if it works well and isn’t too loud.
Nah, hugged nearly to death in a minute, but my order went through at xx:31. But I think I was pretty near the end before they went OOS.
Edit: in the US, sounds like the EU might have lasted a bit longer?
If it makes you feel better, I was on desktop (web) (and mobile and when I was getting desperate deck, lol) and my order didn’t go through until xx:31. I think it really was just random.
Also switched to 6-10 days in the US at some point.
Gratz!
I had money in my wallet too and got the buy button about 1 minute early, but still got stuck in the “There seems to have been an error” loop until my order went through 32 minutes later.
I don’t even think it’s that, I had preloaded wallet credit my payment was failing too.
Eyy, finally managed to get one. Right before they went out of stock.
Ditto all of this.
There are no good decently priced domain registrars at the moment. Even porkbun is just a cloudflare reseller now. The only downside of going with cloudflare is that don’t let you use your own nameservers (at least that was true the last time I checked a few years ago), but if you don’t already know that you want that, you probably don’t need it.
Lemmy makes the /c/ format into a link to the community in my instance, FWIW.
🤷, embedded device manufacturers were really bad at software back then. I honestly don’t remember the details anymore.
Yeah, to be fair, there was an issue getting string.h to work (so i could just use strstr) with the vendor’s shitty toolchain, that took me talking to an engineer at the vendor, and the dev who wrote that was out of our Taiwan office. But also, my first fix was just doing a sort of sliding-window check, manually checing for s[0] == '\n' && s[1] == 'C' && s[2] == 'o' &&..., which was gross, but much more correct.
It’s not just those specific licences, it’s: