skysight-inc/HackerNews huggingface dataset:
I get the feeling K8 is the modern PHP. Software that's easy to pick up and use without complete understanding and get something usable. Even if its not efficient and results in lots of technical debt.

And like PHP, it will be criticised with the power of hind sight but will continue to be used and power vast swaths of the internet.
If someone is unhappy about not being listened to and their response is to burn down half a neighborhood in my city maybe there was a good reason we weren’t listening to everything they had to say. They don’t seem interested in reasoning, only in taking what they want by force.

The armed protesters in Michigan were being jackasses but afaik they didn’t start looting or committing arson (or even hurt anyone for that matter). There is no equivalence here, it’s just as much a bullshit “both sides” argument as the one trump made three years ago.
Very unlikely. That would be suicidal publicity at this moment.
Ongoing discussion here: https://news.ycombinator.com/item?id=23352785
As I said in another comment, the importance of the change doesn't lie in a narrow look at the changed component. It is formally about the overall balance of rights, responsibilities of citizens and police/military[1], and less formally about trust between the two and the overall climate we want to live in, as a country.

If you make a given police enforcement mechanism cheaper, it will be used more. What does that do to your average person's sense of privacy/fear/trust? What kind of relationship do we want to have between citizens[2] and its government?

[1] That line is being blurred.

[2] Not subjects
LPD was awesome for sending a file, as-is, to a pre-configured printer. CUPS is awesome for changing things on the fly, like color vs. black-and-white or two-sided printing, or for giving clients enough information about the printer that they can automatically configure the correct driver.
The context for this is also that although Democrats wanted Obama to use executive orders to advance their agenda, Obama understood that future presidents would use his use of executive orders as precedent for their own--regardless of to what party they belong.
Honestly, at least with GKE, hosting applications on managed k8s is not that complicated, to the point that I don't think it is a poor choice even for small teams who might not need all the bells and whistles of k8s. That is, so long as that small team is already on board with CI and containers.
You keep implying that the schools are doing their best in a trying time and deserve sympathy. Sure, that's fine. They're not acting in bad faith. But they aren't acting fairly. If the reason you went to a school was it had a cool robot building program, and you don't get to build any robots, that's clearly not what was offered to you. An online college is not worth the price of an in person college and it is very, very unfair to these students who are paying fortunes to get them. Much more unfair to the massively indebted students than the bureaucratically overbudgeted schools.

Employed engineers working remotely is a really bad analogy because engineers are paid to be available on an ongoing basis. Contract workers are a much better fit. If they were a contract worker, contracted to complete a specific task, and they don't complete the task... they don't get paid. COVID or otherwise. There is a wealth of pretty reasonable legal literature of settling disputes over partial completion of work.

> "While closing campus and transitioning to online classes was the right thing for Defendants to do, this decision deprived Plaintiff and the other members of the Classes from recognizing the benefits of in-person instruction, access to campus facilities, student activities, and other benefits and services in exchange for which they had already paid fees and tuition."

Note things like "campus facilities". Obviously 0% of that thing that they paid for was provided. And it should be reimbursed.
I was expecting this one before I clicked: https://xkcd.com/1252/
It is not so much the platform as the general internet medium. It lends itself to narcissism. Humans are more gratuitous when speaking to another in person. More attentive to inflections, reactions, emotions, etc.
Alpine Linux 3.12.0 Released
> After many years of litigation, on April 25, 2019, ruling from the Northern District of California for Jewel v. NSA concluded that the evidence presented by the plaintiff's experts was insufficient; "the Court confirms its earlier finding that Klein cannot establish the content, function, or purpose of the secure room at the AT&T site based on his own independent knowledge."

> The ruling noted, "Klein can only speculate about what data were actually processed and by whom in the secure room and how and for what purpose, as he was never involved in its operation." The Court further went on to discredit other experts called upon, citing their heavy reliance on the Klein declaration.
And what about all the other people caught in the dragnet? Most of whom presumably did nothing. These people have no idea if they are also being surveilled. I mean, who knows what else the government is doing "while they're there."

There are smaller aerial drones that could be used, which would capture the same relevant footage, without the potentially miles-wide dragnet. That's my main objection here: innocent people shouldn't have to give up their rights because the government can justify it. A good justice system would do their best get the minimum amount of information necessary, in order to protect the innocent.
Unrelated, but did you hear that 5G causes coronavirus?
I don't see the problem, just reject the special privs for twitter and treat it like a publisher. It should be fairly simple, either you do not moderate at all (and your not responsible for whatever people say on your platform) or you moderate and therefore you publish. It aint that hard. Twitter clearly moderates, that's fine, so it should be treated as a publisher, not as a public 'facility'. Simple.
I meant they might be so closely related that you want them share the same caption and figure number and everything.
The simple answer is that Kubernetes isn't really any of the things it's been described as. What it /is/, though, is an operating system for the Cloud. It's a set of universal abstraction layers that can sit on top of and work with any IaaS provider and allows you to build and deploy applications using infrastructure-as-code concepts through a standardized and approachable API.

Most companies who were late on the Cloud hype cycle (which is quite a lot of F100s) got to see second-hand how using all the nice SaaS/PaaS offerings from major cloud providers puts you over a barrel and don't have any interest in being the next victim, and it's coming at the same time that these very same companies are looking to eliminate expensive commercially licensed proprietary software and revamp their ancient monolithic applications into modern microservices. The culimination of these factors is a major facet of the growth of Kubernetes in the Enterprise.

It's not just hype, it has a very specific purpose which it serves in these organizations with easily demonstrated ROI, and it works. There /are/ a lot of organizations jumping on the bandwagon and cargo-culting because they don't know any better, but there are definitely use cases where Kubernetes shines.
Whoa, did I get Nat's attention? Prepare for a brain dump!

- Keyboard shortcuts: I’m always triggering these by accident. There’s no easy way (AFAICT) to block or disable them. My browser and OS already define a bunch of keyboard shortcuts. Please don’t steal existing shortcuts for non-standard uses.

- “Mobile” view: this hides so much it's nearly useless to me. (And the desktop view is a pain to use on my phone when I want to check one little thing.) 100% of the reason I use GitHub today is because -- by default, with no action required -- it displays the (entire) README, and the list of files. That’s what GitHub is.

- “?w=1” has always been one of the most useful features of GitHub. It’s completely hidden, hard to use (it messes up my browser history), and easy to forget.

- Releases/Tags: this page has only Next/Previous, no page numbers. If you want to get to an old release, you have scroll down and click "Next", and then repeat that dozens of times. “git tag” is fast (right?), so I’m not sure why normal pagination is missing here. Other GitHub lists have it. (Oh, I just found from poking around that "Subscriptions" also has only Previous/Next. I think that one's new.)

- “Issues" attachments: only a handful of file types are whitelisted, and it excludes 10 common ones I want to use (not just videos). I’ve never been able to figure out why. Is there some security issue we're avoiding by making people rename their .csv files to .txt before uploading them?

- "Issues" email responder: I see people send attachments here, and it silently drops them, instead of attaching them to the issue, or sending them a response that it doesn’t accept attachments via email. I’m tired of talking people through this. At this point, I wish I could turn off the email responder entirely, because it’s more trouble than it’s worth.

And finally, my Completely Unreasonable Requests:

- DOM stability. For example, when I'm not logged in, there's that giant "Create your own GitHub profile” banner, with the confusing “Dismiss” floating over a busy background, near the weird icon that looks like it might almost be a close button but isn't. I guess you have to always upsell, but nothing on github.com seems to ever have a stable DOM class/ID, even when there’s no reason to change it, so I regularly have to edit my user stylesheet to fix or block things I don’t want.

- “Issues" are the only major part of a GitHub project which aren't repos, so there's no easy way to back them up, or use them offline, or query them from a shell, or ... The GitHub docs always suggest some third-party API-based method for backing up Issues, and I've never gotten any of the free ones to work, and I shouldn't have to pay someone else to retrieve my own data. (The cynic in me guesses this is GitHub's primary mechanism for lock-in.) It feels like GitHub is a 2000's-era version control system, with an SVN-era bug database.

Thanks for listening to my ramblings!
Pricing is similar to the Segment.io model, you pay for the number of accounts, in chunks of 10k.

You get the most value when you do more transactions, so that's why we don't charge for that, we don't want companies limiting what they to with Decimals to save money.

Also important to note is that this is not one more layer in the payment cake taking a percentage of your revenue, the pricing is based on API usage, with no relation to your revenue.
ah, thanks! hadn't seen it.
Here's an interactive website for trying the system out https://lewiscarrollresources.net/gameoflogic/demonstrator.h...

Does anyone know if this graphical reasoning system something Lewis Carroll invented himself?

It looks like he also wrote a sequel book, about how to turn the system into a game: https://archive.org/details/gameoflogic00carruoft/page/28/mo...

Unfortunately it hasn't been digitised as well as OP
That's pretty ridiculous considering that RPI's endowment isn't that big, so it's not like she could justify from fundraising.
Such a weird way of putting police reaper drones into context.
If you are bought in to GCP and plan to stay there, then maybe not much. OTOH, Anthos would allow you to do easier migrations from on-prem, support hybrid workloads, or consolidate multi-cloud clusters including those running on say, AWS [1] if you like.

1. https://cloud.google.com/blog/topics/anthos/multi-cloud-feat...
I get what you're saying, but the flip side of it is that such actions are aiding, enabling, and abetting a crime (in this case, a large number of crimes). The "protect yourself from bodily harm" bit is what enables these rioters to avoid dispersing and ceasing violent destruction of property. And it is obvious from numerous tweets from various DSA and antifa handles that these two groups are very much amplifying and glorifying destructive rioting. This is real material violence, not theoretical violence, and therefore Twitter needs to shut it down if they have a problem with theoretical violence that they think Trump's tweet glorifies.

Calling police "violent" for wanting to stop blatant opportunistic theft and terrorist behavior (e.g. deliberately cutting gas lines to create big explosions) is a stretch. I would call the initial policing incident that tipped off the protests violent, and I would call the destructive rioting violent (as opposed to the initial peaceful protesting). Both acts deserve condemnation and consequences in my view.
Tapping the barometric altimeter (and other pressure sensors, but altimeter the most) had been driven hard into me and my friends when training on gliders. Can get you hundreds meters difference lower, and suddenly you find that yes, you're lower than you thought.
Yes, people ought to do a side by side comparison of a new user learning to K8S v AWS v GCP before claiming Kubernetes adds more complexity than it returns in benefits.

Remember the first time you saw the AWS console? And the last time?
It's not, if you on the other side.
We can have a discussion without the pitchforks I this forum.
Typically you are laundering cash; electronic systems do not help here since all the means of depositing the cash into the system are monitored.
Ars longa, vita brevis ...
What's with the negativity in the comments? all tesla shorters or is it a factory opening fallout?
Of course they do. People hoard any time they expect the price to go up — even the most unregulated markets have speculators.

You also hoard whenever goods have storage costs associated with them and you have excess capacity. Hoarding is how you collect rent on your grain silos, warehouses, freezers, oil tanks, etc. You either hoard yourself, or you contract out the capacity to others who want to speculate without the capital expense of building their own storage.
Chef and from what I heard, since I didn't use it, Puppet are declarative, but since their DSL is really Ruby, it is really easy to introduce imperative code.

Ansible uses YAML, but when I used it few times it felt that you still use it in imperative way.

The saltstack (which also uses YAML) was the closest from that group (never used CFengine, but the author wrote research paper and shown that declarative is the way to go, so I would imagine he would also implement it that way).

If you truly want a declarative approach designated from a ground up, then you should try Nix or NixOS.
The thing with selective enforcement is that then anyone with claims against Twitter can claim that their moderation attempts are all in bad faith, because they are selective - thereby opening them up to libel.
Exactly. That's a great way to put it. A bunch of Bash glue reimplementing what Kubernetes already does. Poorly.
Having a little bit of discipline is all that's needed.
The high-road leads to Trump agreeing with you that we need to prevent the spread of fake news to protect society. Then, as the duly elected leader sworn to protect society, he takes on that solemn duty and tasks the agency he controls, the FCC (the entity usually tasked with controlling media content), to make sure that all fake news and entities peddling fake news are permanently squashed so that they will not interfere in the upcoming election.
The goalpost was placed wrongly, likely by accident. It's rather obvious the problem are the people with a $2k credit card who want to profiteer off a crisis, of whom there's much more than the ultra-rich, and who have much stronger incentives to buy up the supply.

> allow supermarkets to raise the prices.

That would just price out anyone without $2k credit.
1. Managed, on AWS ECS -- it was not that difficult to set up using AWS services (Aurora for the DB, ElastiCache for Redis)

2. Freedom. We generally use PythonOperators but it is not uncommon to run containers as well. I agree with pyrophane, setting up containerized operators really is a non-trivial and far from straightforward to test locally. Still, it seems worth doing, particularly if you do not want various execution to affect one another.

3. Again, echoing what pyrophane said, a custom solution is needed for anything that's more than a couple hundred bytes in size. There even exists (now mostly abandoned) plugin that allows you to streamline the whole process: https://github.com/industrydive/fileflow Writing directly to something like S3 is almost always sufficient in combination with passing the path for the file from one task to another.

Having said that, I would encourage you to try it out, even if the setup may sound daunting at first. If you can model your tasks as DAGs whose graphs are known in advance, I would argue it almost always makes sense because you get many things "for free" that were not mentioned before: logging, backfill, standard handling of connections/secrets and a ton of metrics in a nice UI that helps a lot with the visibility part.
>Lots of people repeat catchy sayings without even knowing and endorsing who originally said them or even what those sayings originally meant.

This I disagree with, particularly since he doesn't have to consciously "know" or acknowledge anything explicitly for him not to understand the basic import of the statement.

I don't think anyone's saying he's capable of giving a brief one paragraph statement for an SAT question concerning Civil Rights activism in mid-20th century Florida, cause biases and prejudices don't need that much formal verification to commerce
It doesn’t have to be this abstract, though. This will likely change in the next 20 years.

Consider the move from horse drawn carriages to vehicles.

It was an acceptable risk that anyone might be permanently disabled due to being kicked in the head or trampled by a horse.

This might be a horse you are simply walking past. Or one that is spooked and running down the street. The owner of the horse beared little to no responsibility.

Now it is largely acceptable, to permanently disable or kill someone due to a mistake or some form of common negligence while operating a vehicle.

It is almost not a crime to accidentally run someone over. This is “normal” or “not intentional.”

In the future, it will seem insane to have allowed so many people manual control over multi-ton vehicles.

Just as it does not make sense that a horse would be tied up outside Trader Joe’s and due to a spook permanently disable you as you exit the store.

It will seem so primitive to have such loose controls on cars that if you chose to drive a manually controlled car killing someone will likely be seen as dangerous enough of a choice that a person would be held liable for manslaughter.
> setting it up kind of feels like I'm trying to earn a PhD thesis.

Are you following "k8s the hard way"? I've never had this problem; either:

`gcloud container clusters create`

Or

`install docker-for-mac`

And you have a k8s cluster up and running. Maybe it's more work on AWS?
NSA: Russian govt hackers exploiting critical Exim flaw since 2019
Kubernetes is popular because developers want names on their CVS. A couple of shell scripts will get you anywhere.
Why do a comparison? K8S runs on AWS and GCP. They have managed services for setting up one. If you know K8S as a developer, then you simply consume the cloud K8S cluster.
Kubernetes makes impossible things merely hard, but at the expense of also making normal and easy things hard.

The system becomes so complex that most people screw up simple things like redundancy, perimeter security and zero downtime updates.

I've seen all of the above from very bright and capable people.
The DMV is a whole different kind of crazy.
I've been using Kubernetes exclusively for the past two years after coming from a fairly large Saltstack shop. I think traditional configuration management is flawed. Configuration drift _will_ happen because something, somewhere, will do something you or the formula/module/playbook didn't account for. A Dockerfile builds the world from (almost) scratch and forces the runtime environment to be stateless. A CM tool constantly tries to shape the world to its image.

Kubernetes isn't a silver bullet of course, there will be applications where running it in containers adds unnecessary complexity, and those are best run in a VM managed by a CM tool. I'd argue using k8s is safe default for deploying new applications going forward.
ISAs (income sharing agreements) can land you into deep shit
Practices like income sharing set up the possibility of an actual human stock exchange.
With income sharing, financers stand to make money from and assert further control over human experience. Effectively this is a debt for equity swap and It'll not be a very fun bubble when it pops.
I got a bit disillusioned with k8s and looked at Nomad as an alternative.

As a relatively noob sysadmin, I liked it a lot. Easy to deploy and easy to maintain. We've got a lot of mixed rented hardware + cloud VPS, and having one layer to unify them all seemed great.

Unfortunately I had a hard convincing the org to give it a serious shot. At the crux of it, it wasn't clear what 'production ready' Nomad should look like. It seemed like Nomad is useless without Consul, and you really should use Vault to do the PKI for all of it.

It's a bit frustrating how so many of the HashiCorp products are 'in for penny, in for a pound' type deals. I know there's _technically_ ways for you use Nomad without Consul, but it didn't seem like the happy path, and the community support was non-existent.

Please tell me why I'm wrong lol, I really wanted to love Nomad. We are running a mix of everything and its a nightmare
Not a problem if the drivers are written to be easy to forward port. But that's not the approach that embedded BSP's generally take.
Twitter does not want to be a publisher, because then lots of people will sue it for libel and other nasty stuff in twits.
I don't think this is right. The reason I say that is because for the most part, teams new to k8s aren't building and managing their own clusters, they are using a managed solution. In that case, an application deployment only need be a few dozen lines of yaml. Most teams aren't really going to be building deep into k8s, and it shouldn't be hard to deploy your containers to some other managed solution.
I'm a longtime fan of your comments and you've shaped my POV on many things. I am a religious reader of https://news.ycombinator.com/threads?id=rayiner

You normally have the facts on your side, or else you make generous and clear concessions. What is happening here? You are saying such incorrect (or confusing) things.

In point of fact, Democratic presidential candidates began to lose in Southern states because of integration well before the 1970s. Formerly-Democratic Southerners splintered from the Democratic party for explicitly segregationist reasons, and carried several Southern states under a third-party banner, in two different presidential elections (1948 and 1968).

(One of them, Strom Thurmond, is a direct counterexample to your argument that the Civil Rights Acts were not a "precipitating event for politicians switching parties." At least according to Wikipedia, he switched his affiliation to Republican because of the 1964 Civil Rights Act.)

Is this, like, something you haven't read about yet? Or do you have a strong argument that explains the above, which I don't get yet?
Answer has to include implementation details. No credit if your answer does not reference iptables.
But languages are easy, there is the whole field of PL theory to draw from. If you're randomly throwing things together like Lerdorf was, there's a missed opportunity.

But what is the universally regarded theory that k8s contradicts? I don't think there is one.
I thought it was pretty insane yesterday when I read a YC-backed recruiting company was using Kubernetes. Absolutely insane. It's become the new, hottest, techiest thing that every company has to have even when they don't need it.