Better yet you can configure gitignore globally for git. I do this mostly to avoid polluting repo ignore files with my editor specific junk but *.key and similar can help prevent accidents.

https://git-scm.com/docs/gitignore

Right, but AI is not the only way they’re doing the data collection.

It’s promotion-driven development at its finest.

It probably won’t be profitable in rural areas to begin with.

Linux ISOs obviously

Enterprise enjoyers today:

It’s been a long road, getting from there to here.

That’s exactly what Half Life 3 will be.

But not from a knowledge engine. It makes sense if some rando just spouted off a date from the top of their head but this is the former world leader in knowledge capture and search.

Fair enough! I definitely read this around the time 5g was coming around but apparently I was misinformed.

IIRC, 5g is a much nicer generation for the carriers than for consumers. It can be more easily deployed with microcells on light poles vs requiring the tall cell towers. There’s ultra-wideband, which is definitely faster, but plain 5g is roughly the same, just easier to roll out.

I microwaved my phone and the battery level hasn’t gone down at all since.

Sandpaper remote, coming right up!

These situations are almost always self-inflicted. If someone else hacked Google Cloud this badly then you’d likely have heard it from them first. And they probably would have done something significantly more destructive if their goal was harming Google reputation.

Unprecedented only means there’s no precedent. This just hasn’t happened before at this scale.

But here, the API is open and I can run my own copy and train my own LLM same as anyone else. It’s not one asshole who decides to whom and for how much he’ll sell the content we all gave him for free, so he can justify his $193 million paycheck.

I can get behind his Twitter handle.

I’ve had exactly that in my personal slack space since OpenAI announced gpt3. He’s helpful and hilariously accurate.

Samsung will add extra AI so their next ad will be employees being crushed into single device.

Plus you have plenty of time to tumble once or twice while your large codebase compiles.

The real primary benefit of storing your relationships in a separate place is that it becomes a point of entry for scans or alterations instead of scanning all entries of one of the larger entity types. For example, “how many users have favorited movie X” is a query on one smaller table (and likely much better optimized on modern processor architectures) vs across all favorites of all users. And “movie x2 is deleted so let’s remove all references to it” is again a single table to alter.

Another benefit regardless of language is normalization. You can keep your entities distinct, and can operate on only one of either. This matters a lot more the more relationships you have between instances of both entities. You could get away with your json array containing IDs of movies rather than storing the joins separately, but that still loses for efficiency when compared to a third relationship table.

The biggest win for design is normalization. Store entities separately and updates or scans will require significantly less rewriting. And there are degrees of it, each with benefits and trade-offs.