great deep dive into the Amen break. this video is from the yt days of yore, nice to see the yt algo still propping it up.
61 karma · joined December 7, 2017
great deep dive into the Amen break. this video is from the yt days of yore, nice to see the yt algo still propping it up.
> 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.
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.
[0]: https://community.spiceworks.com/scripts/show/4378-windows-1... [1]: https://community.spiceworks.com/how_to/148624-how-to-clean-...
^^ 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.
Thus I'm sour on Helm, I'm rooting for Kustomize. [1]
[0] https://github.com/kubernetes/kubernetes/blob/master/cluster...
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.
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)
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.
Almost a decade later, possibly the cops on the beat shakedown situation has improved but general man on the street economic conditions are not improved in Tunisia. It is not apparently (yet) a success story.
I'm unsatisfied with the cassava and acorn stuff. I get that metabolism is externalized and I get that once it is a cultural practice then that's just how it is. I struggle with envisioning the part in between where the processing is newish and becoming a practice, especially in regards to something like the cassava toxin that doesn't happen until decades later. How does a processing strategy sustain in those early iterations? Versus the animal husbandry practices, they have more immediate results that seem less vulnerable to biases making false causation. I think I struggle with the making sense part of it, what I got from the book is that considering cause is a luxury won by doing it "because I said so".
I had this discussion recently about 'security' with regard to X-Header versus ?query=param. Either it's http all plaintext on the network or it's http with tls all cyphertext on the network. Every bit in the http request and response is equivalent - verb, path, headers, body, etc - agree?
You could represent the card number as cyphertext in the request body, that's a good practice regardless of tls, but of course don't roll your own crypto. You could put that cyphertext in the path as well but if the cyphertext isn't stable that makes for a huge mess of paths.
You could make a case for trad 'combined' access logs situation with the path disclosed in log files. I can appreciate keeping uris 'clean' makes it safe to integrate a world of http monitoring tools, I would make this argument. In the case of the card represented in a stable cyphertext it's kinda cool to expose it safely to those tools.
Anything else?
>In retrospect, it should have been obvious that hypertext transport over line printers just wasn’t a good idea.
What's annoying about helm is many cases would be fine as plain yaml template macro without any cluster state but many public projects are packaged as helm charts so to use them off the shelf you need to go full helm. Thankfully it's not too difficult to use helm template.
2K Games is the premier purveyor of fine video game entertainment. My team is growing and has some open positions for software development and technical product management. We build services for game developers, we make components that go into the games and services that support the games. On the game side it’s mostly C++ and on the service side it’s Java and Python.
Lead Software Engineer https://chp.tbe.taleo.net/chp04/ats/careers/v2/viewRequisiti...
Principal Software Engineer https://chp.tbe.taleo.net/chp04/ats/careers/v2/viewRequisiti...
Software Engineer https://chp.tbe.taleo.net/chp04/ats/careers/v2/viewRequisiti...
Associate Technical Product Manager https://chp.tbe.taleo.net/chp04/ats/careers/v2/viewRequisiti...
My name is Tim Lynch and I'm the devops wretch, please contact me directly if you are interested in learning more about us, email me first name dot last name at our domain.
Timely, here's antirez on this topic when Redis was announced on HN ten years ago [0]:
> There are a lot of projects similar to Redis in Erlang actually: http://www.metabrew.com/article/anti-rdbms-a-list-of-distrib...
> Apart from speed what I like of C for this kind of projects is the self-contain-ness and the fact that most developers that may help in the development are probably able to read/write C but not Erlang.