What are your plans when end of life /support comes to Windows ten?

Switch to Linux and run virtual machines when I need to use Windows.

Right now I don’t quite have the drive to do it, but an end to support for Windows 10 would push me over the edge. I just can’t stand Windows 11, not even because of all the bullshit but just the way it mandates the UI structure - last time I tried it my dealbreaker was that you can’t just have it always display all taskbar icons, you have to manually force each one to show. If a new icon comes up, it will be hidden.

I’m sure I’ll be there with you soon enough.

/me Laughs in Windows 10.

I make little typos all the time, and often go back and edit things to change the shape of my comment. The backspace thing is a little thing, but it’s persistent and frequently annoying.

Also *fewer :p

It’s not really the keyboard though, the keyboard works fine everywhere else. It’s a poor implementation from the text editor that Jerboa uses, one that other keyboards have created a workaround for. But the issue is in the text editor.

It’s like when a website only works in Chrome, but doesn’t work in Firefox. It isn’t because Firefox is broken, it’s because the website doesn’t follow web standards and has only been tested in Chrome.

Good stuff hah. Thunder is in my trial group now anyway :)

Oh! Here’s the ultimate test: ^[1]

Can it handle Markdown citations???

Even the website doesn’t handle those quite right.

The links should scroll between the citation in the text and the definition at the bottom, while I actually wrote the citation immediately afterwards. The website scrolling doesn’t quite work, but it does at least place the definitions all together at the bottom.^[2]

View the source for fun.

Oh, maybe the website does handle it ok, it just doesn’t quite work on the first click. Subsequent clicks seem to scroll correctly.

It’s an absolute pain in the ass. When you press backspace once, the underline for autocorrect extends to the space before the word, then when you press it again it deletes the space, merging it with the word before. It will keep doing this over and over if you keep pressing backspace. You then have to go through and position the cursor just so in the middle of the word to add the spaces back - or, if you don’t notice it, you submit the comment and then have to edit it, which marks your comment and makes it dirty (lol, one thing I loved about reddit was the 3 minute leeway for edits).

Basically when you press backspace the underline for autocorrect extends over the space before the word, then when you press backspace again it deletes that space. Every other press of backspace will delete the space before, completely messing up the text when you’re just trying to make a minor correction. You then have the hassle of pixel hunting to get the cursor in the middle of the word where the space was to add it back again.

I hate this phrase because it assumes that copyright infringement was at one point the same as stealing - it never was.

Stealing is a crime, where you take with the intent to deprive. Copyright infringement is a civil offense where the original owner loses nothing.

I was tempted by GrapheneOS, my son used it for a while on his older Pixel, but I always resented all the diva drama from the devs. AXP.OS seemed like an easy transition, basically using the same ROM as my old phone (AXP.OS is a DivestOS fork).

Based on the Megathread, Connect doesn’t have an F-Droid repo.

UI preference is a key decider, imo!

Yeah others are saying it’s to do with the keyboard, or rather that other keyboards seem to get around the bug. However it’s only Jerboa that I have this issue with.

I’m using the standard Android Keyboard (AOSP), so it’s not something you would expect to have errors. Don’t really want to change as I’m used to it and have it set up for different nationalities (Greek for maths, couple other countries for their funky accented letters).

Yeah DivestOS ticks nearly all the boxes for me (eg call recording and custom gestures eg long press back to force close), however there were a few little niggles that custom ROMs have with other manufacturers - the camera is usually closed source so you can’t quite get all out of it, and also I was having issues with pocket detection where a message or call would turn my screen on and then it would either answer in my pocket or mess with the audio player on the lock screen. Not had any of those issues so far with the Pixel.

However curved screens suck balls, and the cheap screen protector I got is already cracked lol.

Looks like I’ll lean towards Voyager and Thunder, might give Eternity a go also. I had Voyager before but was sticking it out with Jerboa, we’ll see how I feel this time. Thanks!

Part of the reason for the move is upgrading from a Poco F3 to a Pixel 7 Pro (although I’m sad to lose the IR blaster). However I run custom ROMs, so I’ve been using the keyboard that comes with DivestOS and AXP.OS. Don’t really want to try another keyboard lol but others have said that might fix it.

I want it through an F-Droid repo so I can use the elevated priveleges I give F-Droid, such that I don’t have to approve each install.

Yeah I mean ultimately they should all end up with the same features, then it comes down to which UI you like the best.

Leaving us hanging…