skysight-inc/HackerNews huggingface dataset:
Once you start to see both Kustomize and Helm as a templating language, then you'll realize that Kustomize doesn't cover many use cases and is intentionally limited in scope. There is a reason almost every major project in the Kubernetes ecosystem has a Helm chart, but not a Kustomize configuration file. That doesn't mean that Helm doesn't have it's issues, because their implementation of Go templating is constrained, and Go templating is challenging in itself; however, it does a lot more than Kustomize can offer and covers a significantly larger amount of use cases than Kustomize patch files.

Kustomize is great for getting a job done quickly if you don't mind some duplication of code and effort throughout your projects, but Helm is ideal for managing dependencies and templating across a large amount of projects where you may want to re-utilize other charts.

I think it is ideal to not just discover these tools by reading about them, but actually start using them and spend a few hours trying them out and testing what they can and can't do.
If everyone did this, in the limiting case, no one has the ability to investigate and repair actual bugs until the point where the application can only crash every 10 ms and does nothing but get continually restarted.
Assuming you don't count side effects like running out of memory, assignment is definitely idempotent. It is, of course, not immutable. Now, it is completely possible to implement a non-idempotent assignment if you want. For example, if you wrote an assignment function that returned true if the value changed when you assigned it, or false if it didn't, then that would not be idempotent.

And, of course, you could be nit-picky about side effects. For example, a language might implement assignment such that the first time you assign a value, it allocates the memory and the second time it simply overwrites the memory. That's obviously not idempotent. However, you could make similar arguments for a lot of compiler optimisations: they can take an idempotent function and make it not idempotent when viewed from outside the context of the source code.

While there is some value in considering those issues, it's a bit self-defeating as well. You take a useful abstraction and throw it away. I think it makes sense to have conversations like: is this idempotent from the context of the source code? Running out of memory when you assign to a variable that's allocated on the stack is not something anyone normally prepares for (and if you do, then God help you ;-) ). The concept still provides value to the conversation, which is the reason for having words in the first place. You may prefer a different word, but if it's going to be used in every single case I would question the utility of the redefinition.
> Rent control rewards the entrenched people who were lucky enough to find a unit early, at the expense of everyone who came later.

And market housing rewards well-paid, rich professionals at the expense of everyone who isn't pulling in a FAANG salary.

Neither is a 'fair' distribution of shelter - that much is true.

> The victims of rent control are everyone who is pushed out of the city -- or those who cannot move there -- because of how rent control makes building rental units unprofitable.

If you remove rent control tomorrow, there's going to be no shortage of immediate, acutely suffering victims of that political decision. Forgive me that I have more sympathy for those individuals, then some nebulous group of 'People who, for whatever reason, really want to move to SF, and can afford a $2,800 apartment, but not a $3,400 one, so they don't move to SF.'
You have an opportunity to practice second order thinking in regards to using second/third order thinking here.
Please do not spread falsehoods.
Yep, it is full of bullshit corporate PR and crisis management. This story has just begun. FAA and Boeing hopefully will be held responsible. I don't hold my breath to see criminal charges for Boeing management, but this time, I wouldn't be completely surprised, if it happens.
People in their formative years see technology so clearly. Each generation invents something that changes things in ways people wish they could relive. Past the change, you can’t see things the same.
Cloud spanner seems awesome but has a base price of $740/mo, doesn’t seem to autoscale, and doesn’t support a mysql or postgres interface.
If your buddies work in finance, they should tip as much as they want (50%? Why not?). The poor restaurant workers need the money a whole lot more than they do.

The financial services industry has been skimming gajillions of dollars off the whole economy. Might as well pay at least some of it back to folks doing honest work.
sure and what if 20 percent feel strongly the opposite way but cant say anything or else they will be bullied by the 1 pct and called bigots and fired like damore?

I'm sure 1 pct of people are white supremacists but we don't listen to them just because they whinge
Indeed, the whole press release brings to mind a couple of points from "Engineering a Safer World" which, if you're interested in this stuff, I can't recommend enough[0].

In the section "Questioning the Foundations of Traditional Safety Engineering":

Old Assumption
Most accidents are caused by operator error. Rewarding safe behaviour and punishing unsafe behaviours will eliminate or reduce accidents significantly.
New Assumption
Operator error is a product of the environment in which it occurs. To reduce operator "error" we must change the environment in which the operator works.

And:

Old Assumption
Major accidents occur from the chance simultaneous occurrence of random events.
New Assumption
Systems will tend to migrate toward states of higher risk. Such migration is predictable and can be prevented by appropriate system design or detected during operations using leading indicators of increasing risk.

In the press release we see both the "operator error" and "random events" hand-waving. Regardless of the fiduciary duty of this man, this is just not good enough.

[0] Open Access PDF: https://mitpress.mit.edu/books/engineering-safer-world
Managing Kustomize configuration files is even worse in most regards, and you are likely to have a significantly larger amount of Kustomize files than Helm files, especially if you create a common chart and use dependencies correctly within Helm.
Show HN: MySellerBot – A contact form that tries answering questions on its own
Contact forms are slow for the customer and burdensome for support teams.

MySellerBot is a smart contact form that uses AI to suggest answers.

Solved queries get no tickets made/emails forwarded for them!

Try our demo: https://mysellerbot.com/demopage?acc=VhTObzUMAYfCzqimWBlKZgMdUDrnIFnKolFeIQEL&intent=CkTJnsDuNV&img=https://static.toiimg.com/photo/64428999/Vivo-NEX.jpg
huh. on one hand, this is awesome! something like this should be fantastic for things like citus’s columnar storage - a pluggable storage system can be a huge boon. on the other hand there have been some bugs popping up on pg-bugs like the parallel queries that look a little questionable. hopefully no negative impact for anyone upstream while everything gets hammered out. context: i’m The maintainer of a fairly popular pg extension

editing to note that the bugs popping up have nothing to do with this, just the hope that it doesn’t become ... overwhelming
Right.. so now your developers don't need to understand how to configure and tune open source directory services and RDBMS's and in-memory caches... they just need to understand how to configure and tune a cloud-provider's implementation of a directory service and RDBMS and in-memory cache..... ?

If you think using a cloud "service" out-of-the-box will "just work" your scale is probably small enough that a single server with the equivalent package installed with the default settings is going to "just work" too.
You hit it right on the head. MV needs to be a lot denser. But the city council, much like other bay area councils, likes things just the way they are. After all its the supply constraints that have made existing residents rich, why would they want to fix the area's housing problem all by themselves?
Apple is literally famous for doing free warranty replacements for people who don't actually qualify. There's thousands and thousands of stories of this sort of thing over many years. Forgive me for not believing you when you say Apple is conspiring to defraud customers out of warranty replacements.
Unvaccinated student loses in court after suing health dept during outbreak
Of course they would have tried to land after getting the plane under control. They didn't have airspeed or altitude under control, and were following the checklists they were supposed to be following. IAS Unstable tells them to leave thrust high and flaps alone to avoid a wing stall.
changing the zoning laws is really hard when you have people in the hotel industry spending huge amounts to not only keep it the way it is, but make it even more restrictive. Cities are fining airbnb, using code enforcement to put huge leins on property owners who try to accommodate low income housing in neighborhoods... 20 yeas ago most places didnt even have a "code enforcement".. its a racket. all it does is raise rent higher
I agree. I live in Mountain View and all for building more density and more townhouses, but the number of townhouses in the articles is less then the number of apartments in each of the new developments. Unless I am missing something, I don't understand how decreasing the number of housing units is helping the area.
It sounds like you are dreaming of it tough. To make such a strong statement. It is like saying all corporations end up like Theranos or Enron eventually.
Economists do a lot of research and disagree with each other violently. So I will not take your links as any proof that regulatory capture is an inevitable end. Yes it is concerning that it happens but there is absolutely no reason to believe it is the fate of all.
An Explorative Guide to the Google Cloud Certifications
AWS status page is notorious for not indicating there is an issue either at all, or until well after the event began.
I disagree. I think if you took a reasonably fit marathoner (approximately 3:30 time on a flat course) and compared them to someone who only does mild exercise every day, the marathoner will come out as far healthier.

I think this because to be even a mediocre marathoner, one needs to exercise with about the same frequency as the control person. But one also needs to work diligently on a large peripheral system like flexibility and mobility, recovery routines, stricter diet controls such as counting calories, macros, ensuring proper vitamin/mineral uptake, strength work with lifting, etc.

Sure, a mild exerciser can be relatively healthy, but the real difference is that the marathoner has challenging goals to accompany the systems for building health; whereas the mild exerciser only has the systems and easily accomplishable or even no goals besides "being healthy".
> having your password in plain text on the hard drive

That's not necessary for git. git has a facility called git credential that can allow it to cache the password (or other piece of information) for a given period of time[1]. So, when you use git send-email, it will prompt you for the the password.

[1] https://git-scm.com/docs/git-credential-cache
Those are gross, immoral people.
I didn't start off criticizing AWS; just large companies in general, based on my experience with them, and extrapolating it to AWS based on my experience with the one issue, combined with reading things that sound like the same pattern of people having to debug big company's software, and it's hard when you can't see anything.

On this specific issue; I worked with sales support, and also looked on their forums; and found things like this: https://forums.aws.amazon.com/message.jspa?messageID=721247

Which says 'yes, we know there's a limit; no we won't tell you what it is' and ignores the elephant in the room, that apparently if you reconfigure the network rules, the problem evaporates.

Excuse me for not banging my head against the wall or watching random videos from third parties. Actually, I only know there's a way to avoid this because I complained about it for a long time in HN threads, and finally, some lovely person told me the answer. In the mean time, I had continued my life in sensible hosting environments where there wasn't an invisible, unknowable connection limit hovering over my head.
I wanted so much to like this. The evolution of SirHat (better name :) is entertaining, and never leaving the cmdline would be great! And I was on board until encountering this type of tedium:

Find the message ID to reply to.
Don't stress too much about getting
this step right, but it's a nice
Courtesy for the people receiving
your patch. On the mailing list
Archives, look up the latest email
In your thread and expand "Details"
to find the Message ID. Copy this
for the next step.

IMHO, needing to lookup email header IDs for each patch revision is an insane and terrible workflow! (At least, compared to gitbucketlabhub.)
I live in Mt View, and I can tell you that a rallying cry of anti-development people is "Do you want Mt View to become Tokyo?"

There is a large contingent of people who own single family homes who want to keep things exactly as they are now. They vote in elections. The contingent of people who DO want development largely doesn't live here, so they don't vote. There is no constituency of people who will live here in 10 years when we have higher density!
You wrote “The point is with a managed service, none of your problems will be with the service.”

What deathanatos wrote sounds awfully like problems with the service to me.

I don’t think S3 taking 100+ seconds to respond to a GET request can be solved by orchestration alone.
Not the original commenter, but my team uses CloudSQL MySQL. It's not too bad. It's pretty performant, but we've run into some weird issues surrounding replicas.

As far as I know, MySQL 5.7 is as far as they go and like PostgreSQL, they don't support point-in-time recovery. Also, perplexingly (at least as of a year ago?), deleting the instance deletes all backups associated with it, so there's an opportunity to accidentally blow away all your data. I'm sure Google can recover it, but you'll have to submit a support ticket for that.
Yes that was a mistake. It did get the person who had the original lunch with Pocket off the hook though.
user.js files are awesome for Firefox. You just specify a list of preferences which then are applied every time you start Firefox.

(And here's a popular preconfigured user.js https://github.com/pyllyukko/user.js )
Is this really a thing though? I would be surprised if I find someone that's able to deploy a spark cluster for a production application and at the same time doesn't know that is not a good solution for their problem.
The unforunate part of this idea is that both conditions will have to be tested in order to determine which of the two were better, meaning we'd have to try slavery, genocide, rape, or pretty much anything really. This system doesn't work because there are some things we know are wrong without having to attempt them at least once.
So for those who are curious to know more about this:

https://www.sfgate.com/technology/article/bell-labs-larry-lu...
As someone else commented, the huge size of Go executables is down to a design decision to include a map of functions for panic reporting. There was a whole discussion on this recently on HN.

I don't know why the grandparent was downvoted. Go binaries are not small and the claim that this is a "small" single executable is untrue.

Hopefully the Go team will give us a flag to decide for ourselves whether to optimise for executable size or initialisation time. I know I'm fed up of uploading 50Mb files over dodgy wifi+vpn connections to update my server.

(edit fix repetition of design)
No. Brave is collecting money on people's behalf without their consent.
It's impotence for people living in Deutschland
I don't agree with the original article at all, but I find this comment quite ironic. Almost no European except for the very rich is thinking about owning a 6000 square foot house, it's just not a priority. But it doesn't surprise me that an American would. And I think that difference is illustrative of the American vs European narrative the author is alluding to.

The aspiration of owning a 6000 square foot house probably costs the American a lot of things the European _would_ value: not having to be so career-focused to make enough money, not having to take on as much debt, living in a higher-density urban area which makes other things mentioned in the article possible (taking the train, going to cafes, casually stopping for groceries, all the while being surrounded by other people)...
Bear in mind that they're at low altitude and the pilot is busy supplying maximum pull on the yoke, and therefore likely unavailable to help crank a stiff trim wheel.
Maybe a little overstated to avoid getting into subtleties, but I stand behind the point.

Yes, it seems the plane is probably mostly flyable if you kill the MCAS system (which is the only reasonable step to take in a two sensor system when they disagree). But

- The plane no longer handles the same, you definitely need to be alerting the pilots, and put this change into manuals and training. This isn't just a thing you should silently do in software and expect not to kill people.

- The plane no longer meets the FAA rules for the class under these conditions. Maybe that's acceptable because it is an error state, but I think that meets the definition of a "workaround" and not a "fix".

- At least one of these planes took off when one of the sensors was known to be bad from the previous flight (as I understand it). I can only assume that they don't do that when something critical to the handling of the plane is broken. This is another process bug that needs to be fixed before a software workaround might be acceptable.

I don't see any way to interpret this other than "the hardware didn't work as we thought it did", which leads me to say "hardware bug", even if you can maybe work around it with process, training, and software changes.
A quick search indicates Mountain View has a population of 80k and Tokyo has a population of nearly 14 million.

SMH.
Even though I don't like it, I normally just start one of those "focus" playlists from Spotify. It's harder for me to concentrate if I listen to something I actually like I guess.
At the risk of repeating myself, it's in the epilogue of the same episode as OP: https://news.ycombinator.com/item?id=19579575
The collect money on someone's behalf, without that person knowing. It's a scam. It would be like me taking money on behalf of you. Only I wouldn't tell you. And now someone thinks they are paying you by going through me.

Seems like a scam.
I don’t think it’s a failed login attempt since I received a one-time code. Also, this is the same email I get when I try to login.
I was under the impression that weight and the ability to carry more rounds into combat was a bigger driver of the original 5.56mm development, not recoil.

Given the rapid growth in hard armor that can take a few 5.56mm rounds before failing, I wouldn’t be surprised to see militaries shift more towards a 6.5 or 7mm cartridge with a hardened steel penetrator.
I do use a VPN but I was not accessing the site, I was watching a movie when I got the email.
The datasheet (i assume you mean the register mapping) is linked at the bottom of the article.
> AWS was a hell of a lot better than anything you could come up with unless you're literally at Amazon scale

AWS is a hell of a lot better than most people here can come up with for solving AWS specific set of problems and priorities. But those problems and priorities generally do not match the problem space of the people using it exactly.

For example, AWS has a lot of complexity for dealing with services and deployment because it needs to be versatile enough to meet wildly different scenarios. In designing a solution for one company and their needs over the next few years, you wouldn't attempt to match what AWS does, because the majority of companies use only a small fraction of the available services, so that wouldn't be a good use of time and resources.

AWS is good enough for very many companies so they appeal to large chunks of the market, but let's not act like that makes them a perfect or "best" solution. They're just a very scaleable and versatile solution so it's unlikely they can't handle your problem. You'll often pay more for that scaleability and versatility though, and if you knew perfectly (or within good bounds) what to expect when designing a system, it's really not that hard to beat AWS on a cost and growth level with a well designed plan.

Edit: Whoops, s/dell/well/, but it probably works either way... ;)
J. J. Thompson (who discovered the electron) said this about 100 years ago:

If you pay a man a salary for doing research, he and you will want to have something to point to at the end of the year to show that the money has not been wasted.

In promising work of the highest class, however, results do no come in this regular fashion, in fact years may pass without any tangible result being obtained, and the position of the paid worker would be very embarrassing and he would naturally take to work on a lower, or at any rate a different plane where he could be sure of getting year by year tangible results which would justify his salary.

The position is this: You want one kind of research, but, if you pay a man to do it, it will drive him to research of a different kind. The only thing to do is to pay him for doing something else and give him enough leisure to do research for the love of it.
There is no present just a discrete plank scale time that you can be ignorant and call it arrow of time, or be present and try not to fall in the illusion of continous flow.
Great tutorial. You may want to add a section about using git-format-patch to allow one to see the emails on disk and using git-send-email with those files. You may also want to add a caveats section about certain email providers.

In my experience, any Microsoft Exchange/O365 server will most likely mangle the email server side (introducing quoted-printable encoding characters or changing the message-id field. Gmail will require that you enable insecure application access in order to use git-send-email. If you don't do that, then using git-send-email will result in a authentication failure error (which you can see if you use the --debug flag).
> their responsibilities lie with their shareholders

This is the "shareholder value" theory, modern economists successfully brainwashed the population with. It became popular during the 1980s, "greed is good" times. It's just an ideology disguised as a science. The purpose and structure of modern corporation hasn't changed in the last hundred years or so. In 1950s and 1960s the public good, among others, role of corporations was wildly accepted. What changed is the ideologues who became more vicious and took complete control of the narrative.
VGA Museum
Ruby on Rails CVE-2019-5418 – Payload to dump session signing keys in production