The only times I encounter vi (and so not sure what version, but likely barebones Linux), it doesn't indicate whether you are in insert or normal mode. So I immediately install vim (once possible).
Is that something you just get used to, or was I using some weird vi?
I always assume I am in normal mode unless I am actively typing. If I stop to think I ESC. Then, when I gave thought, I know what I need to do next.
So for me there isn't really any time of looking at the screen and not knowing. And if there ever was some ambiguity I would reflexively hit ESC to get to a known state.
So, not sure it would bother me. But my editor does give me an indication of whether I am in normal, insert, visual, visual block, or Emacs mode.
$1100/m for an outsourced engineer… am I missing something? That’s far too low. Even juniors in South America tend to ask for at least double that number before factoring in the DeepSeek cost.
I thought the same thing. The author's reference point for LCOL developer seems a bit outdated. With what we pay our teammates in Colombia, the model pushed out to 22 months before crossover.
I have one page with my full history of text messages, full transcription of all voice messages, contacts information connected with every number, and I can search everything. I can configure which of my phones ring.
And, possibly most importantly to me right now, my current phone has only a data connection and I make and receive calls using the Voice app. I think SIP eats too much battery and data and doesn't work well for wifi<->lte switching, but it's been a long time since I used it much.
I'm not sure what the OP does, but at least for me I find myself chained to Google Voice for SMS 2FA use because it's basically the only phone number provider that cannot be exploited with a sim swap attack (same deal with Google Fi). And while I don't necessarily trust Google, their account security is leagues ahead of anyone else imo.
I previously looked at jmp.chat but they didn't really inspire confidence on the security front.
My use cases include 2FA and I like the added security that Voice provides, but it's not really added security, it's just moving the risk from your cell provider to Google. IMHO, Google does security better than the cell providers do.
I like the muti-platform integration of Voice. I use it on my iPad, on my Android phone, and mostly from my desktop. It works well on all platforms.
When I'm at home, I mainly use my VoIP phones. GV forwards to them, and they spoof my GV numbers when I make outgoing calls.
I like the spam text and call protections that GV provides. I believe they're partnered and integrated with Nomorobo.
I also have jmp.chat. It has capabilities that GV doesn't have, but it's not well integrated. (I use Cheogram on my Android phone, but there's no easily usable client on my iPad, or my desktop.)
I noticed Claude Sonnet 4.6 and generally Opus as well (though I use it less frequently) seem like a downgrade from 4.5. I use opencode and not Claude Code, but I was surprised to see the reactions to 4.6 be mixed for folks rather than clear downgrade.
I'm regularly switching back to 4.5 and preferring it. I'm not excited for when it gets sunset later this year if 4.6 isn't fixed or superseded by then.
Opus 4.6 was definitely a mixed bag for me. Overall Id probably prefer 4.5 but only just barely and I stay on 4.6 just for the "default" nature of it. But if 4.5 is unchanged vs what Ive had on 4.6 lately then 100% I would move back to it. Ill have to test that
They kinda added window positioning with Tahoe -- there are things I like more about it than Rectangle (resizing), but I found that it was janky enough I switched back to Rectangle.
I rarely use the Dock, it's somewhat eye candy I leave up, or add stacks for folders that I use, but typically for keyboard action I reach for spotlight (cmd+space). Now, spotlight occasionally shitting the bed, that's another issue...
Definitely not Wayland related, or so I doubt. I'm on wayland and never had any issues, and it's a TUI, where the terminal emulator does or does not do GPU work. What led you to that conclusion?
> On Linux, some Wayland setups can cause blank windows or compositor errors.
> If you’re on Wayland and the app is blank/crashing, try launching with OC_ALLOW_WAYLAND=1.
> If that makes things worse, remove it and try launching under an X11 session instead.
OC_ALLOW_WAYLAND=1 didn't work for me (Ubuntu 24.04)
Suggesting to use a different display server to use a TUI (!!) seems a bit wild to me. I didn't put a lot of time into investigating this so maybe there is another reason than Wayland. Anyway I'm using Pi now
That issue points out that it is probably a dependency problem.
The other problem is that they let a package manager block the UI and either swallow hard errors or unable to progress on soft errors. The errors are probably (hopefully) in some logs.
A dev oriented TUI should report unrecoverable errors on screen or at least direct you to the logs. It's not easy to get right, but if you dare to do it isn't rocket science either. They didn't dare.
Is that something you just get used to, or was I using some weird vi?
reply