Yeah thru hikers avoid roads like the plague. Judging by his route he could've walk a lot existing trails. Go southbound on Great Divide Trail and Continental Divide Trail, then somehow cross Mexico and central America into Andes, there you can follow Greater Patagonian Trail all the way to Tierra del Fuego. The European part can just reuse Trans European Alpine Route, then cross Black Sea and take the Transcaucasian Trail, afterwards maybe the work in progress Snow Leopard Track? It's gonna be a lot more difficult but definitely beats highway walking.
Yes, in fact if I have the opportunity to walk these trails I would take it in a heartbeat. I am sorry but you really have to thru hike to understand it. Being tired and hungry all the time is the least concern
I personally haven't found any keyboard that works better than gboard. And exactly because it's the only keyboard that just lets me type in two languages without having to "switch", and it does that well. Right now my spacebar just says "NL - EN" and it lets me combine Dutch and English just fine.
From my experience it is much worse than it used to be 5 years ago. I have been writing English, French, and to a lesser extent German on an iPhone since ~2008. Initially, the dumb autocorrect would just correct to the closer word in the dictionary corresponding to the current keyboard, but over time it would pick up more and more words I used regularly. At some point around 2018 or so, it was nearly flawless. I think it changed the dictionary depending on the language or the sentence, because I had different suggestions for the same mistyped word in the same document. Also, I assume that by then my personal dictionary was quite extensive.
And then they bragged about a new machine-learning improved keyboard and it went downhill. First, all keyboards became monolingual, which was a 10-years regression. And even in that language, it was very flakey. They added multi-language keyboards somewhat recently and it got slightly better, except that for some reason it changes the keyboard back to the English-only one regularly for no reason I can see.
It is maddening. For a couple of years it was fantastic.
And that’s not the worst. On the Apple Watch not only is the multilingual keyboard completely broken, but worse than that: if you change the language of the keyboard by long pressing the space button it shows the new language, but the autocorrect proceeds to just ignore it completely and autocorrects everything as if I were typing in the system language rather than the one I selected.
And contrary to the iPhone you can’t even disable autocorrect! This + the super-aggressive autocorrect of watchOS (the screen is small after all so you are likely to make a mistake and we better fix it automatically!) makes it an absolute NIGHTMARE to type on an Apple Watch in multiple languages. Your only option is to use speech to type because that one for some reason works when you change the language whereas the keyboard doesn’t care.
Edit: the language switch bug on watchOS seems to have finally been fixed on watchOS 26.1. The bug was already long present on watchOS 11, so not something that watchOS 26 introduced.
Completely agreed. Apple seriously regressed the multi-lingual experience. They probably have a model per language. If you have to mix languages in a sentence, well, good luck!
I just want to talk to the folks who made the language switching logic so complicated instead of just a constant rotation like desktop IMEs. It seems like they expect the user to remember the previous language or prioritize languages in a clear order, but did it not occur to them that I might switch languages chaotically (A->C->D->B), keep it there, then hours later when I forgot what $previousLanguage was and press switch, I might as well be spinning a roulette?
> And exactly because it's the only keyboard that just lets me type in two languages without having to "switch", and it does that well. Right now my spacebar just says "NL - EN" and it lets me combine Dutch and English just fine.
I can't stand keyboards that do this - especially those that don't let you turn it off. If you write in another language that doesn't use the Latin alphabet, you end up with nonsense suggestions - common English words like "the" or "and" will get replaced with obscure words in another language that just happen to sound vaguely phonetically similar. I almost never switch languages mid-sentence when typing, and yet the keyboard can't seem to grasp that.
This. I use romanian, english and turkish at the same time. Sometimes goes sideways because we mix a lot of words in english and romaninan in the same sentence, but it's ok. No other keyboard comes close.
Multilingual typing is a godsend. I did have to tweak settings though, like disabling the "suggestion strip" (because sometimes I'd be typing fast and accidently click the GIF button, then an image, which in many apps sends it immediately without a draft which was extremely annoying).
Does Pixel somehow have a good keyboard? I use GBoard and find it atrocious: for English it's ok, but it doesn't know basic declensions in Czech nor Polish and autocorrects them to something nonsensical. This happens every time I try to type something, so I avoid writing on the phone.
It's the age of LLMs! Language has been solved! LLMs are great at both Czech and Polish. This problem is orders of magnitude easier. Why doesn't my keyboard even know these words exist?? Is there an Android keyboard that actually... knows basic forms of basic words?
Do you have an example? I type in Polish in GBoard regularly and haven't noticed too many anomalies (although I do have the right language pack installed, and the keyboard is set to it, and I "add to dictionary" occasionally).
what do you mean by this specifically? iOS (and I'm guessing Android) both have dictionaries. I can select a word I've entered and look it up in nearly any text area.
> Does Pixel somehow have a good keyboard? I use GBoard and find it atrocious
I use Google Pinyin Input. Since it was discontinued in favor of (the much worse) GBoard, I have to keep a backup of the apk and sideload it onto new phones.
Google does not appear to think of input methods as something that should be convenient for the user to use. Not sure why.
Humans writing tests can only help against some subset of all problems that can happen with incompetent or misaligned LLMs. For example, they can game human-written and LLM-written tests just the same.
First, the "good practice" argument is just an attempt to shut down the discussion. God wanted it so.
Second, I rather keep my dependencies outdated. New features, new bugs. Why update, unless there's a specific reason to do so? By upgrading, you're opening yourself up to:
- Accidental new bugs that didn't have the time to be spotted yet.
- Subtly different runtime characteristics (see the original post).
- Maintainer going rogue or the dependency getting hijacked and introducing security issues, unless you audit the full code whenever upgrading (which you don't).
It's true that you can satisfy the audit just by running dependency scans and updating the ones that come back vulnerable. Unfortunately, in a lot of ecosystems, that ends up looking the same as keeping all your libraries updated.
You can instead document exceptions for why all those vulnerabilities doesn't apply to your app, but that's sometimes more trouble.
> In the last years writing SQLAlchemy or Django ORM the teams I was on would write queries in SQL and then spend the rest of the day trying to make the ORM reproduce it.
Ah yes, good times! Not Django for me but similar general idea. I'm not a big fan of ORMs: give me a type safe query and I'm happy!
reply