tlynchpin

warning, completely pedantic pet peeve.

> Note all dates and time in this blog post are in Pacific Standard Time (PST).

But the incident was during PDT. Just use UTC or colloquial "Pacific time" or equiv and never be wrong!

My heart goes out to these people. I can imagine how much sustained terror they were feeling, stare hard and harder at your terminals and still nothing makes sense.

Apple is well regarded for their strategy. I don't find it very credible that Apple is reacting here, it seems apparent that they would anticipate substantial negative reception.

So this delay is preordained in the strat, right?

But Apple is only human and has had its share of monumental wtf, so this is just a huge gaffe? The spyware team didn't know about iphone 13 launch? This seems incredible.

There is some n-dimensional chess at play here. I feel like a popcorn munching audience member who is actually a pawn in another dimension.

RIP grafana

^^ this is not a good contribution to HN, not much substance. (edit)

Many people who use Grafana will see this news and will stop planning on using Grafana and start planning on doing something else. That has nothing to do with Grafana, that is a common reaction to AGPL.

In theory, AGPL is fine under circumstances blahblahblah. In common practice in commercial settings (in my experience), GPL is poison and AGPL is radioactive poison.

CGNAT block is popular in private k8s as overlay network address space because often the enterprise network already claims rfc1918 blocks. I'm not sure how close to the line that kind of usage is but I suspect it is SHOULD NOT. Speaking of, I probably should not even post this comment as it will now be indexed and served in search results, further contributing to the corruption. Alas, it works.

No refunds for canceling KubeCon registration after November 4th.

This has happened to me with Firefox. Thankfully there is Waterfox.

Recently this came up in discussion with a software developer who was overly concerned with openssl certificate minutiae. I advised the only durable solution for his concerns is a method to change the entire implementation, not only the certs.

This is what I'm talking about wrt bitching and moaning, in summary you tried to use ES but you didn't rtfm or didn't know about jvm tuning or didn't scale test and found out the weekend is a bad time to come up to speed on those, you had a bad time several times, plus you slashdotted yourself with monitoring; then you did a custom implementation for your vertical use case which didn't have the rtfm problem because you wrote it, but also only satisfied your case as opposed to the wide applicability of ES. Ultimately cool story bro because ES is freely available for anyone to use (many people do this) and modify (some people do this too) and your alternative is unknown.

What are the fundamental flaws of ES and what alternatives avoid those flaws, or how do you propose ES could address those flaws?

For example:

- "Algolia is so much better because it is a managed service." (hey whatsup ycombi)

- "Solr is also lucene but necessarily requires significant customization to the workload which avoids the common ES problem of it appearing to work so well out of the box that people neglect the details until it becomes an incident."

- "ES fundamental flaw is that zen disco mcast nonsense, people please stop being clever using mcast it never works in practice because igmp snoop". (hey whatsup we out here using ES since a while now)

If someone would say that on HackerNews then they would expect to hear "citation needed".

Anecdotally what I hear is a bunch of bitching and moaning about ES yet it clearly does work and has generally all of the difficulties of any CAP problem. This indicates to me that ES is addressing a Hard Problem and to the extent that it is long lived and quite popular, it's likely not substantially worse than any reasonable alternative.

Please tell us what you view as ElasticSearch fundamental flaws and give some proposed alternatives either as revisions to ES or entire other solution components.

"Install a decent terminal emulator" - this is the big problem for any command line experience on windows. What do you suggest?

AboveNet built out a datacenter in a mostly derelict mall in the middle of downtown San Jose. At the time the irony of ecommerce servers in an abandoned mall was fresh and surreal.