Nope: it surprised me too, but we did a small survey and unless you’re a nerd, anything not ending in either com or your own nation’s TLD structure is considered dodgy and/or hard to type (.co being a notorious case — people type .com instead).
This is mitigated slightly by the fact that people don’t use URIs much any more and even if they do they usually type something into a search bar or chat bot which DWIMs what they typed anyway.
I once worked for a U.S.-based company called Doe Products, Inc., which it commonly abbreviated as "DPI." When the web started becoming relevant, DPI hadn't managed to get either doe.com or dpi.com so, instead, it got dpi-doeprducts.com. All of this happened before I arrived and began handling DPI's website-/domains-related stuff. I always chafed at that unwieldy URL, especially due to its often-problematic hyphen, so I was happy when we did manage to get doe.us. However, the execs soon quashed that satisfaction when they told me, no, we can't use that URL because people will think they have to type "doe.us.com" (!?!); and I never managed to convince them otherwise.
Indeed, the standard domain I use for my mail is family-name.org. And so many people do try familyname.org.com that when I have to give my mail address over the phone or in a shop I just say familyname.com
it's not that they can't afford to buy one. it's that they're not available. and now a lot of other tlds have gained traction so it's now reasonable to consider others.
I would assume that for most foo.ai domains, foo-ai.com would also be available. So it’s more about naming preferences, and sometimes lack of imagination for coming up with an available name.
"non-starter"? In a URL? You mean URLs and not domain names? Why are these "non-starters"? What is special or wrong about hyphens? Do you avoid clicking these for moral reasons? You do understand that they are perfectly legal anywhere, and acceptable in the character set by all RFCs? What makes them so odious to you?
once you have built up a trust in a model/harness/setup/workflow and you’ve been hitting enter for months straight then Auto Mode is appealing.
i found initially it would hang on some commands (moreso on subagents and moreso when first rolled out) and then roll past the hung command sometimes forgetting about it entirely. which wasn’t cool.
but after dialing in subagent permissions and probably some updates from anthropic Auto Mode is great. i still don’t always do it. but after reading this article just switched my current 12 panes to Auto.
could you help me understand the appeal of running everything in tmux? i use tmux if i have long running scraping/db backup or restore, or something similar.
it seems like an awesome thing to geek out on.
but i keep claude code sessions running for days that sometimes get interrupted that are easily resumed. without the tmux latency or giving up aspects of rendering.
I haven't experienced any latency in tmux, so I'm not sure what you're experiencing. For rendering, you may have to change your `TERM` value in your shell.
Tmux is highly keyboard driven and I hardly use any graphical applications outside of my browser. My workflow is basically the same regardless of whether I'm using Linux, macOS or Windows because my workflow lives in the terminal. If I close the terminal, I can continue the session and I can SSH into the machine from another machine.
It's also got a rich plugin ecosystem and is available on pretty much any package distribution. You can also preprogram your layouts if you always do your layouts the same way.
i was an early vagrant user, a long time tf user, and 3 year nomad/consul user. but have moved on. cf now for aws & gcloud cli in scripts for gcp. and eks/gke instead of nomad.
