Why not usa.gov or something similar? From a geographical standpoint, America refers to the entire landmass of the Western Hemisphere, which is made up of North America and South America.
You would have a point if it were called "america.com". But ".gov" is reserved for the US government, so it would be redundant for such domains to specify "USA" in their name.
Though I do wish it were called chat.gov or america-ai.gov or something else actually descriptive of what it is
Because it isn't america.geography, it's america.gov, and everyone who isn't playing dumb knows exactly what government that refers to.
Not to mention the only context you ever hear people using America to refer to both South and North American continents is people complaining that it should be only used in this way.
Ah yes, American Exceptionalism. USA is the best and that's why they reserve the right to the word America. And also to Greenland. And Cuba. Probably Venezuela. Middle-east. Hmm...
I worked with Astra for two weeks and the output was really bad compared to Opus. It made so many wrong decisions within C++, Go, Python and Typescript code bases. My college made the same experience and we moved back to Claude.
I dump my thoughts and a short draft of my message, mail, ... into one of the big LLMs and let it finish my work. Quite happy with the results and I can concentrate on the real tasks. I don't like writing and I am happy with the speedup... Get real work done and enjoy the rest of my time outside in nature.
Might end in a new bcachefs fork beeing included back into mainline. If companies sponsor a few fulltime devs working on the new fork, we finally might have a stable enterprise ready CoW filesystem.
Thought about a real fork going in its own direction. I would love to use bcachefs in all our products. But the current state does not qualify for usage within enterprise environments. Any ideas how to get that fixed? How many core developers are present? Any fallback plans, ...? How to help to get there?
reply