I’m using whatever the stock keyboard is on Google Android. Since we’re on the topic, I’m open to suggestions. Especially if I’m going to re-train to swiping inputs.
It’s hard to pin down anything specific as an example. If I had to sum it up, its usually where I want to use a long word with a common root for others. There could be eight or so different ways to go for auto-completion, but my choice is seldom in the top three.
I’m going to just take a guess: Most people who have a problem with autocorrect type each letter individually by pressing each letter?
Possibly. I’m in that group, for what it’s worth.
Then there is/was this feature that resizes key hitboxes on the fly, based on prediction. I’m unaware if that’s still a thing, but at the time, it absolutely screwed with my thumb-typing muscle-memory in the worst way. Until I learned about this, I was convinced that I was just garbage at hitting the keys, then I started seeing it mis-register keypresses when I looked closely.
From all that I think I see the problem. These systems are compromises for a huge range of different users and communication styles. So it’s going to be pretty mid for a lot of folks until (people like me) move to the middle where the software wants people to be. Were it not for the sake of clear, personalized, and expressive communication, I’d be on board with that.
Is it just me, or does autocorrect paper-over the fact that touch-screen keyboards are kind of garbage?
For me, turning off autocorrect reveals how hard it is to be both accurate and precise with key presses on these things.
Real question is: how many smaller cars can I fit inside it?
It’s a feature, not a bug!
So… which one of you is going to ask Randall Munroe if this is plausible or not? Disregarding the the obvious frozen-butt problem, of course.
It pushes your code to be very tree-shaped
This is basically where my learning took me. I had to develop this notion that there was a preferred directionality to ownership and data flow, like “grain” in a piece of wood. Everything is easier if you go with the grain. “Tree-shaped” works too, since it basically is the call graph of a (single threaded) program.
The point where I realized all this was when I tried to do a very Python/JS-brained thing: return a closure from a function. The moment you try to “curry” values into the closure, you have to “move” them to solve for ownership, lest you bring timelines into the picture. Which isn’t always what you want in a generic and reusable function. And sure enough, the standard lib and other popular libraries want you to pass a closure to functions instead.
This was my experience too, until I learned a few things.
Box, dyn, and Rc.dyn) isn’t really necessary a lot of the time. Identify where you absolutely need it and solve everything else through other means.&). Instead, try to re-think your structs and functions using composition and clone/copy instead. It’s less efficient, but it’s easier to optimize a running program, too.enum, match, if let, and ? are weird, but are where you get the most leverage in the language. Try to master them.derive[...] is a first-class feature with a lot of standard lib support. Always use this to make your custom types mesh with the standard lib more seamlessly.if and match are expressions, not statements! You can use either block to evaluate to a single value, useful in composite expressions like let. Example; let x=if y>20 { y } else { 0 }; Or use them to return values from functions (w/o need of a return statement).I will say this: for me, learning rust was 80% un-learning habits from other languages.
People tend to not like it when they have to change habits, especially if those took a long (and painful) time to acquire.
In this particular case, this is the same complaint Go faced with its form of explicit error handling. And Java, for that matter.
Honestly, Rust does a killer job of avoiding checked exceptions and verbose error hooks by way of the ? operator, and requiring all possible match branches to be accounted for. If you embrace errors fully, by using Result<> and custom Error types, your program gets a massive boost in robustness for not a lot of fuss. I recently learned that it gets even better if you embrace enum as a way to define error values, and make sure it implements useful traits like From and Display. With that, error handling code gets a lot more succinct, permitting one to more easily sift through different error values after a call (should you need to). All of that capability far exceeds any perception of clunkyness, IMO.
The fact that this probably doesn’t even optimize to a lookup table just gives me pain.
It’s basically the UI equivalent of this:
Yes, it’s a fully-functional date picker and also deviously, wildly, uncomfortably outside of aesthetic norms. Also, there’s a lots of fun, invalid combinations of input outside of the usual “February 30th” shenanigans.
Why yes, that’s my birthday: the 32nd of Septunepril. What’s the problem?
Thanks. I hate it.
Do we really want “The time my AI bang-maid turned out to be a lethal combat robot” as a light novel? Because this is how that happens. (assuming it hasn’t already)
Well, Temporal Investigations only cares if you move at a negative speed. And causality just flippin’ breaks down and ends the universe if you move instantaneously. Everything else seems to be fair game. So… mostly nobody?
::cue Spongebob music::
340 million years later
I was going to reply to this with yet more Nick Cage overreactions, but the man is just a font of stuff like this. There’s literally too much to pick from.
Robin of Sherwood is actually a pretty good show. They did some fun things with the lore, and it’s a pretty cozy watch overall.
Yup. At the same time: a messianic hero rises to lead the chosen people.
They’re literally incapable of imagining anything else. Otherwise, we’d have radically different outcomes from all this.
It also didn’t take long for the aftermath to become racially charged, either.
As it turns out, the folks most impacted by hurricanes and other weather events (e.g. flooding) are people of color. So, sending FEMA late to these sorts of things just reeks of malicious compliance.
My pet theory here is that the RNC likes having a populist for election purposes and someone who is culpable that can be ejected if needed. In this case, culpability has to fall outside range of a self-pardon or any presidential immunity. I think the civil cases qualify for that, but I’m not sure.