vitalus

Is it possible to modify the car to disconnect from the remote Tesla service and keep the 90 firmware on there? What critical functionality of the car would you be looking at losing, other than updates?

Is it normal for unionization votes to have this kind of opposition? 56.6% doesn't seem like an overwhelming majority, so I'm curious to see how it plays out for all of the employees there.

It would be interesting as well to know how/if the vote was drastically different based on role - it sounds like this was a company-wide vote, which would necessarily include many more roles than just software engineers.

I understand that Kubernetes is a complex project, but I struggle to see how this comment adds to the discourse.

For those that do need a solution like Kubernetes, charts like this are helpful, and the knowledge requirements certainly aren't too steep relative to comparable platforms.

What about Kubernetes makes it especially worth going in and commenting that you don't have a use case for it, in a thread dedicated to Kubernetes? Would you make similar comments about other platforms/libraries/technologies that you, for whatever reason, don't have a use case for?

I definitely agree with you - my team switched to an "ephemeral cluster" model which allows us to very quickly spin up an entirely new cluster and drain traffic to it as needed.

It's something that we've ended up implementing on our own with a lot of Terraform, but that's had its own obstacles and is something of a small maintenance burden. I'll be taking a look at sugarkube!

Definitely can sympathize with you on this, having spent plenty of time myself fighting some clusters that ended up in a broken state, and trying to get them going again.

I think that this pain is sometimes more severe in the context of automated provisioning tools out there and the trend towards immutable infrastructure - folks tend to not have the know-how to dig in and mutate that state if need be.

It's really important to have a story within teams, though, about either investing in the knowledge needed to make these fixes, or to have the tooling in place to quickly rebuild everything from scratch and cutover to a new, working production cluster in a minimal amount of time.

Adopting any piece of technology just because it's a fad or otherwise trendy is rarely a good justification.

It sounds like the primary reason you're deciding to move away from it is because you don't face any of the problems that it's there to solve, rather than it being an operational burden.

I think that the "Even in JavaScript..." comment was written with the idea that race conditions might not be present/possible in single threaded environments, such as JavaScript...I read it as "Even in a single-threaded environment, such as JavaScript..."

I don't think that most folks would hold up JS as some sort of gold standard of language design, and it doesn't seem that the author is doing so here.

- Simple DNS based service discovery

- namespace separations between resources

- optimized resource utilization and container scheduling

These are the biggest 3 for the smaller orgs I’ve been a part of

Seems hard to get enough users to make this worthwhile at any given bar - people have to adjust their "out at a bar" time to include checking into a dating app.

The right growth strategy here seems a lot more localized - targeting specific bars/nightlife districts and seeding from the ground up. Can't get any useful signal from 10,000 users if they're all spread out across North America.

I say that after seeing this app promoted on HN a few times now - probably not a super effective growth channel.

The sensor reading could have just as easily been 24 degrees rather than 70 and caused the same crash w/ the author's proposal.

Not saying or excusing the failures that led to this crash, but it seems like an oversimplification of the needed solution to suggest that ridiculous data be thrown out, with the benefit of hindsight being used to determine where the threshold of "ridiculous" is.

I'd be interested in seeing a license that better accomplishes the goals cited as motivation for moving to this license, that would hopefully also avoid the flaws mentioned in this article and throughout the comments.

Is there an example of such a license?

Could this type of license even be created in an enforceable way?

Bystander cellphone footage is often used as evidence in courts, at least in the USA.

This comment seems to imply that all court admissible video evidence comes from trusted chains of custody and thereby trusted sources, which isn't necessarily the case.

I don't agree with the "journalistic process being hacked" as being the only line there, as it implies some deliberate power play by bad actors which would omit said integrity.

It seems plausible that it's more along the lines of "journalistic process being broken" for this type of article, that all parties might be acting in good faith and that there is some level of misunderstanding.

Curious about the 24h-48h burndown...could it potentially be longer for you guys or is there some mechanism in place to force disconnection (and thus risk a spike) after some TTL?

In practice you probably would want pretty thin proxy layer as you said, which is then forwarding requests to other services as needed...but you would still need to re-deploy this proxy layer, and would thus need a similar solution to the one proposed in the article.