That totally threw me off. “Literally unplayable,” as they say.
That totally threw me off. “Literally unplayable,” as they say.
That makes sense. I’m also involved in localization efforts. In niche cases, it’s paid off to work with the clients directly on that. You get you a good balance between correctness and day-to-day usefulness.
Since ladder is mostly diagram-based it almost doesn’t need to be localized and isn’t jarring when you use non-English variable and function names with English keywords.
Apart from being strictly left-to-right.
If he worked in Germany, did he use English or German mnemonics?
If he worked in Germany, did he use English or German mnemonics?
Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.
Semicolon!
Shared with my favorite blind iOS dev. Should be a good laugh!
I also can’t get the printer to work.
OK, tiling window managers are neat and so are TUIs, but web pages are also supposed to work with keyboard only. On Windows, F6 will jump between different panels in an application - give that a try.
The key you’re talking about is the menu key, by the way.
Using a modern OS and the modern web with the keyboard only is essentially a solved problem, not only motivated by efficiency, but also to allow access to people with motor disabilities.
Coming at this from an accessibility… is there any reason the tab, arrow, scape, escape and enter keys would not suffice?
Is it about efficiency? Are Linux GUI apps not expected to be keyboard-only accessible by default?
Sounds like you may be interested in a certain manifesto.
Don’t mind me, I’m just picking the very best grains of sand to make my own silicon, like a real programmer (xkcd).
Interestingly enough, you also have amazon.co.uk, which combines the nature (commercial) and location served (UK), but in the opposite order.
But it could limit the usage of its TLD.
There’s a lot to talk about from this point alone, but I’ll be brief: having gone through university courses on processor design and cutting my teeth on fighting people for a single bit in memory, I’m probably a lot more comfortable with that minutia than most; having written my first few lines of C in 10 years to demo a basic memory safety bug just an hour ago, you’re way way ahead of me.
There are different ways to learn and gain experience and each path will train us in different skills. Then we build teams around that diversity.
There’s nothing like having your network go poof and knowing with 100% certainty that it’s your fault and you’re the only one who can fix it.
I threw together a quick image to ASCII conversion project to actually use a couple of concepts.
Sometime this week I’d like to make it not panic over every little thing. I feel like I should be shifting error handling left, but it’s not very natural for me, just yet.
I will say, the ergonomics for testing with cargo are excellent.
I said it’ll reduce friction, you said it might be easier. Looks like we’re in complete agreement, right?
My take on a summary: like C/C++, Rust can be relevant in a variety of use-cases and one could conceivably build a long-term career on it, while adjusting to market/technology interests.
Seems like a reasonable prediction?