But in the age of AI, it seems like chasing the popular thing takes precedence to good practices.
1,183 karma · joined October 9, 2011
But in the age of AI, it seems like chasing the popular thing takes precedence to good practices.
It's too powerful and there are too many of its implementation details exposed to the user.
The fact the business gives away free compute is irrelevant and more a discussion of their marketing budget.
Given that there are usually _zero_ people rallying in Lansing, this is notable enough for the local newspaper.
What spaces are you in that you see this??
This is also simply not true: we have so many examples of horrific dog bites, with normally-well-behaved animals, well-meaning owners, etc.
A tool like https://github.com/tummychow/git-absorb has been on my to-try list for a while, but for now I do it by hand.
@mitchellh seems to rely on the Ghostty feature to dump scrollback to a file, and edit/search over that.
I found it a bit too inconvenient when using remote systems frequently, though. (If I'm missing a trick, I'd love to use Ghostty! But I'm just not a fan of multiplexers.)
Here we see the basic steps of modeling a complex system, and how that can be useful for understanding behavior even without knowing the details of every component.
So...where does that leave the Zed team? If existing LSPs aren't good enough, that's not a Zed problem: they're building an editor, not LSPs for your favorite language.
I'm not counting something like C++ where there's effectively no "packages" to speak of.
There's Guava and its Preconditions class[0] that is approximately as terse and I find to be more helpful than everything-is-an-AssertionError.
[0] https://guava.dev/releases/14.0/api/docs/com/google/common/b...
I understand the benefits of dependency injection, but to be totally honest I'm more likely to take the Go-style approach of wiring it all up manually, even if it's a bit of extra boilerplate. The indirection and abstractions built up in DI frameworks is rarely worth it IMO.
> The data shows it’s not just an incremental improvement; it’s a demolition.
Complete with extra bold to emphasize the second half, sigh.
"Sharing with a third party" because you have phone backups enabled is very different from streaming live or uploading to social media, like most are actually discussing here.
I know you consider it pseudoscience to force creating your own cards, but I do find premade decks result in a lot more leeches. How do you avoid them when relying on these thousands of auto-generated cards?
initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no
I think it's more likely Safari these days just ignores this, because of the very problem OP complained about.Why is this such a concern to you? At some point, everything has _some_ risk, and this feels like you're putting a lot of guilt on someone else for making a medical decision they deserve to make on their own.
I imagine Cloudflare and AWS were on a Chime bridge while this all went down, they both have a lot at stake here.