Going somewhere doesn't mean it adds culture. Is anything new or interesting happening at the eagles games? Anyone gaining new incite or having revelations over the human condition? Seems more like people are just eating the same-old food and yelling at one another.
They literally are part of the culture. "The same-old food" is also culture. You are describing culture, and then saying "that's not culture". I think you're just using the wrong word for what you're trying to communicate.
The stadiums aren't contributing to that culture. They serve mass produced commodity food that's ubiquitous. I concede that hot dogs and the history behind them is culture, as are interesting new variations or applications. Though, continued sales at stadiums isn't adding to the culture.
Culture isn't history. We are constantly creating new culture. You don't have to like it. There's lots of new culture I don't like. But you can't redefine culture to mean "historic stuff, or stuff I appreciate".
One simple trick helped us a lot: we have a rules transpiler (fireplan) that adds a default "$other": {".read": false, ".write": false} rule to _every_ property. This makes it so that any new fields must be added explicitly, making it all but impossible to unknowingly "inherit" an existing rule for new values. (If you do need a more permissive schema in some places you can override this, of course.)
Our use of Firebase dates back 10+ years so maybe the modern rules tools also do this, I don't know.
What would really help us, though, would be:
1. Built-in support for renaming fields / restructuring data in the face of a range of client versions over which we have little control. As it is, it's really hard to make any non-backwards-compatible changes to the schema.
2. Some way to write lightweight tests for the rules that avoids bringing up a database (emulated or otherwise).
3. Better debugging information when rules fail in production. IMHO every failure should be logged along with _all_ the values accessed by the rule, otherwise it's very hard to debug transient failures caused by changing data.
Our experience has been very different. Our Firebase security rules are locked down tight, so any new properties or collections need to be added explicitly for a new feature to work — it can't be "forgotten". Doing so requires editing the security rules file, which immediately invites strict scrutiny of the changed rules during code review.
This is much better than trying to figure out what are the security-critical bits in a potentially large request handler server-side. It also lets you do a full audit much more easily if needed.
I'm no billionaire, but if there's a legal way for me to avoid paying a tax, of course I'm going to do it. Why should billionaires be held to a different standard? Tighten up the laws for everyone instead.
> if you want to reverse the car, you have to use on-screen controls!
So? If you're switching to reverse then by definition you're stopped (or nearly so) and can afford to take your eyes off the road. The control is no further than most cars' center tunnel-mounted gear levers. Plus it only has the two common drive/reverse settings accessible via the swiping action, rather than all the rarely-used options. (Do you know how many times I've shifted into Neutral or Low by mistake in an unfamiliar car...?)
That you can still look at your surroundings with the stalk and keep a tab on what people around you are doing.
Without the stalk someone can walk into a blind spot and you didn’t catch them because you were finding reverse on the screen.
The person next to you is getting ready to open their door.
Or simply you want to make a 3 point turn quickly without being stopped in the middle of the street fiddling with a screen
That would actually make them easier to spot, as they'd need to flip around for a breaking burn roughly equal to their acceleration burn, pointing their engines straight at us. (Assuming they want to stop by and say hi, of course. If not, then there's not much to worry about.)
If they intend to go straight through Earth at relativistic speeds (to establish a hyperspace bypass, perhaps?), then there's really not much we can do about it anyway. :p
Heartily seconded. Also don't forget the docs: Google Cloud docs are generally fairly sane and often even useful, whereas my stomach churns whenever I have to dive into AWS's labyrinth of semi-outdated, nigh-unreadable crap.
To be fair there are lots of GCP docs, but I cannot say they are as good as AWS. Everything is CLI-based, some things are broken or hello-world-useless. Takes time to go through multiple duplicate articles to find anything decent. I have never had this issue with AWS.
GCP SDK docs must be mentioned separately as it's a bizarre auto-generated nonsense. Have you seen them? How can you even say that GCP docs are good after that?
very few things are cli only, most have multiple ways to do things. and they have separate guide reference sections that can easily be found.
compared to aws where your best bet is to hope google indexed the right page for them.
wdym? As far as I see, it's either CLI or Terraform. GCP SDK is complete garbage, at least for Python compared to AWS boto3. I have personally made web UI for AWS CLI man pages as a fun project and can index everything myself if needed. Googling works fine. If you are not happy with it then ChatGPT is to the rescue. I honestly do not see any problem at all.
This assumes you're using a consumer Gmail account, I guess? If so, yeah, you're SOL. But I think as long as you have your owns domain you should be fine, even if you hook it up to Google Workspace for email, since you can always switch it to another provider. (And yeah, I realize this is not something civilians are likely to be able to figure out / do...)
Not necessarily. Speaking for myself, I like the convenience of SSO, and I generally trust Google to keep my account secured more than a random web site (if they even offer OTP!). As long as I know there's an escape hatch.
Same here. I have my own domain set as the main email address of my personal Google account (I have in fact deleted the Gmail one altogether, as I noticed that otherwise some websites would still pick the Gmail address over the custom domain one when using SSO). Not many people seem to know you can do this without Google Workspace, or that you can have a Google account without a Gmail address.
If I ever lose access to my Google account I can just set a password through the "forgot my password" feature (I've noticed this is often also the only way to set a password if you create an account through SSO with some websites, but it does work). The convenience of SSO with an escape hatch as you say.
> Also Mercedes is accepting 100% liability while their cars are in self driving
That's what I thought too, but apparently it's not that clear cut. Their manual says that the driver must be ready to take over not only when prompted by the system but also "due to obvious circumstances". It's not clear what that means — cue the lawsuits. https://safeautonomy.blogspot.com/2023/09/no-mercedes-benz-w...
Citation required.