skysight-inc/HackerNews huggingface dataset:
I think your comment is probably tongue-in-cheek but I still want to throw my support in with the person you replied to.

The longer I've been at the company I'm at, the less interested I am in how cool something is and the more interested I am in the least effort possible to keep the app running.
I am a solo developer (full stack, but primarily frontend), and Kubernetes has been a game changer for me. I could never run a scalable service on the cloud without Kubernetes. The alternative to Kubernetes is learning proprietary technologies like "Elastic Beanstalk" and "Azure App Service" and so on. No thank you. Kubernetes is very well designed, a pleasure to learn and a breeze to use. This article seems to be about setting up your own Kubernetes cluster. That may be hard; I don't know; I use Google Kubernetes Engine.

For others considering Kubernetes: go for it. Sometimes you learn a technology because your job requires it, sometimes you learn a technology because it is so well designed and awesome. Kubernetes was the latter for me, although it may also be the former for many people.

The first step is to learn Docker. Docker is useful in and of itself, whether you use Kubernetes or not. Once you learn Docker you can take advantage of things like deploying an app as a Docker image to Azure, on-demand Azure Container Instances and so on. Once you know Docker you will realize that all other ways of deploying applications are outmoded.

Once you know Docker it is but a small step to learn Kubernetes. If you have microservices then you need a way for services to discover each other. Kubernetes lets you use DNS to find other services. Learn about Kubernetes' Pods (one or more Containers that must reside on the same machine to work), ReplicaSets (run multiple copies of a Pod), Services (exposes a microservice internally using DNS), Deployments (lets you reliably roll out new software versions without downtime, and restarts pods if they die) and Ingress (HTTP load balancing). You may also need to learn PersistentVolumes and StatefulSets.

The awesome parts of Kubernetes include the kubectl exec command which lets you log into any container without almost any setup or password, kubectl logs to view stdout from your process, kubectl cp to copy files in and out, kubectl port-forward to make remote services appear to be running on your dev box, and so on.
Automatic Job Postings Data Extraction API
universal more-or-less free _access_ to basic (generally good in my opinion) care. But that doesn't include dental or prescriptions (with some exceptions/subsidies), for most people. It's surprising to see them list it as a significant part of someone's budget though. Perhaps I'm not old and sick enough (yet!) to relate :).
Umm.. that's not really true.

Most userspace memory allocators are based on mmap(). Using sbrk() is legacy. The slab allocator (Bonwick, 1994) is the dominant algorithm (both in userspace and the UNIX-like kernels), although there are various flavours and somewhat different implementations of it. Since it uses fixed-sized allocations under the hood, they are nicely packed in pages. Those pages can be released with munmap() once there are no used blocks. Sure, depending on the application and workload, allocations can be become quite distributed amongst the pages over the time, but that is a separate problem.

Also, as another comment states: madvise() is also an option, but it doesn't reclaim the virtual address space. On 32-bit systems VA space exhaustion can be a problem, especially with "modern" applications.
Interesting idea. Install a few cameras at general aviation terminals, international tax attorneys, beauty surgeons, parliament, etc.

When a big Swiss private bank moved into new premises in a skyscraper in Hong Kong, there was a rumour that they had one unmarked elevator avoiding the building lobby, directly from the underground car park to a private lobby within the bank, for UHNWI. Let’s Clearview there, too!
Yeah, that's a means test and breahes the "universal" principle.
Bikeshedding is the absolute worst.

I've been very involved in (local) party politics.

There are legitimate reasons why people despise parties, politics, policy, campaigns, planning, etc. Because it sucks.

And there are some people who LIVE for the knife fight. Living incarnations of the Simple Sabotage Field Manual.

http://www.openculture.com/2015/12/simple-sabotage-field-man...

Of course this happens in all organizations, to varying degrees.

I've struggled to come up with mitigations. Some have worked pretty good. Briefly. Like JADs (joint application development). With an enforcer playing Bad Cop.

Codifying better governance in bylaws and codes of conduct can also help, a bit.

But the moment you stop pumping energy into the system, things revert to the Tyranny of Structurelessness.

https://en.wikipedia.org/wiki/The_Tyranny_of_Structurelessne...
Restarts should go into your reporting too.

Erlang seems to take the opposite approach. Processes are cheap, when one wears out you dispose of it instead of trying to fix it.
This might be a bug rather than a feature for a lot of people. Many people want humanity to concentrate in urban areas because it is better for the environment. Others complain about urbanites' tax dollars paying for rural roads (which is effectively the scenario you're describing, even if those tax dollars are labeled "UBI" and routed through rural citizens' bank accounts first). Still others see rural Americans as their political adversaries.

(Note that this is just an observation; not a value judgment)
A Falcon 9 has a LEO payload capacity of 22,800kg in expendable mode, something SpaceX does not like to do. The largest payload mass they've carried to LEO was Starlink-2 at approximately 15,600kg (60 satellites at 227 kg each).
(outside of GP's reply) Generically, life is messy and unpredictable, never put all your eggs in one basket. Your cloud server is sitting on a physical hyp which will need maintenance or go down, or even something in your VM goes wrong or needs maintenance. Using a basic N+1 architecture allows for A to go down and B to keep running while you work on A - whether that's DNS, HTTP or SQL etc.
If you intend to tax away all the advantages of providing additional housing supply, I’d expect smart landlords to not increase housing supply.
Hence GP's comment about solving at the regulatory level. Housing is artificially supply constrained.
Are your friends up at 1am because they're excited about what they're doing?
Once you configure the kubernetes network layer with whatever hosting platform you’re using, it’s really not difficult to administrate. It’s funny to me how much kubernetes hate there is on hn.
>Health care yes, housing, no. It's possible to build more housing to meet demand, or for people to move to balance supply/demand vs. prevailing wages. Or to have a smaller home or more room mates.

Why do you think healthcare is constrained? The same way housing supply is constrained by zoning regulations and stuff, healthcare supply is constrained by slow diffusion of IP, restrictive immigration policies, inadequate numbers of medical school and residency slots, and restrictive occupational licensing for day-to-day medical care.

It is possible to expand access to care to meet demand, but in the USA we have a system that prioritizes high fees for doctors and hospitals, high returns to student loan providers (medical school debt), and high returns to health insurance providers above access and supply.
Speaking of wrong metrics, another anecdote:

I used to work for an ISP. Some genius high up in the support management chain decided that tickets were taking too long to resolve, and the touch rate was too high. So they implemented a way to measure how many times a ticket communicated on before it was resolved, and somehow turned that in to what they called a "conversion percentage". Percentage of what was never expressed.

The result, naturally, is that customers started talking to a void. Tickets took longer to resolve because the support engineers would waste time not asking clarifying questions because that would hurt their conversion percentage. Customer dissatisfaction soared.

A week or two after it went live, some engineers in the NOC team figured out that if you took a ticket, resolved it, and then re-opened it, you'd hit a 100% conversion rate, regardless of how you then communicated on it. Slowly but surely that started spreading through the company and things pretty much got back on track and customer satisfaction returned.

When I left, they were still tracking that conversion percentage, even though every support engineer was now taught during on-boarding that the way to handle a ticket was to resolve it and re-open it. Firmly on its way to becoming "it's just the way things are done"
I recently started investigating Istio, and though it will probably be an unpopular opinion here on HN, I honestly don't understand why it's not a core part of Kubernetes.

It's amazingly simple to configure, the docs are pretty OK, and the benefits seems huge. Mutual TLS within minutes? BAM, done. Don't worry about cert rotation, Citatel does that for you.

Block all egress, and whitelist what you need? Like, that's a killer feature! Also, the inability to do 90-10 canary releases with plain K8s baffles me. With Istio? Simple...

I don't know, I'm sure I'll find the pains of Istio in the coming months, but in my dev cluster, it looks amazing.
Ask HN: LinkedIn Jobs sucks for remote roles. Who will disrupt them?
Thanks for reading and for your careful analysis. My perspective lives in the last paragraph of the post and I'll let that stand.
You can definitely create new cards in the official mobile app (for iOS).
This part of the article is about shifts for assembly workers:

So Musk is making the machine to make the machine. Musk has brought lessons learned from Tesla’s assembly line so workers do not burn out. They will work three 12-hour days and then have a four-day weekend. Then they’ll work four 12-hour shifts with a three-day weekend. Thus, with four shifts, the Boca Chica site can operate at full capacity 24 hours a day, seven days a week. SpaceX is throwing in hot meals every three to four hours, for free.
A lot of people rely on friends as non-monetary resources. If I get locked out of my car right now I'll call a family member to bring me a spare key. If my car is acting up I have a friend that will look at it for me. I do a lot of tech support in return, not necessarily in exchange for other services in a direct way. It's just being part of a community. At least in my world (midwest US) I cannot imagine moving to an unfamiliar area as a form of resource management. I think this probably gets more extreme the more your financial resources are strained.
It's not that hard to use Kubernetes and it makes the developer's life easy. It's very easy to deploy helm charts and even though that there are many gotchas and complex things, if you want to deploy something simple, it is easy and completely doable to do it even solo.

(rant)

After over 10 years in development I've done and used literally all the things people complain here a lot about: Virtual machines, Single page apps, docker, microservices, FP and the list goes on. Even though I've struggled, I feel very lucky to be able to try all those things and it's a joy to use and I've shipped shitloads of great code that is making a lot of money to a lot of people and improving businesses in general.

I don't mean you need to use K8S or even like it, but there is definitely developers which know their shit very well, and can also make great Single page apps using more than 3 different JS framework, also write good backend code and so on. And also enjoy all of this and make companies definitely successful. It sickens me a bit how so much posts of this kind get a lot of attention and could be replaced by "yes, software, like everything in life, is complex!!!11". I think the article itself is completely shallow to actually touch the difficulties there is with using kubernetes and is mostly useless information. There are at least 10 posts with a better and more structure criticism, but it's just because it's cool to complain about new things, it gets automatically traction in HN(which used to be a place where people like new things...).

So... yes, you shouldn't use K8S everywhere(also applies to everything...), but it is the new thing(well, not really new...). Should we just talk about Apache mod_php? It's natural that people want to try new stuff and actually enjoy working with software. Not everybody sees everything as problems. "Now you have eight problems, hehehehehe!!11".

Am I the only one that found this post completely useless and at some degree, toxic?

(/rant)
Indebted to the Tech: Market Volatility and Trading Systems at PEAK6
Also docker-compose doesn't have zero downtime deploys which might be a deal breaker depending on your application.
Not only that, I also require "offline" time to relax otherwise I become very weird emotionally and I start dreading everything.
Well yeah, if someone says, "would ending this program cause you to change or cancel current plans?", I would say yes in the hopes that it would encourage the program to continue. Free money is nice.
Sorry you weren't first. https://news.ycombinator.com/item?id=22491627
Correct. You can (super¹)linearly increase launch mass by adding fuel. The rocket equation hits when you're trying to go farther, rather than more massive.

¹ Superlinear because tank mass scales with a lower exponent than tank volume.
Ask HN: Is there a Craigslist-style anonymized email forwarding service?
Is there a Saas or open source tool that lets you add a craigslist-like anonymized email forwarding service to let users on a site email each other without publishing their real email address? I saw that a now-defunct service that did this called maskedmail, and I was wondering if there is anything comparable that exists now.
Tax settlement is done once per year. Monthly UBI both feels different and is practically different in terms of helping people have money throughout the year.
> In 1992 Tim Berners-Lee created three things, giving birth to what we consider the Internet. The HTTP protocol, HTML, and the URL.

What we call the web, surely? I appreciate we conflate the two, but in this context I think that's what was meant.

And it's really the URL (URI, IRI, URN...) that makes the web. An amazing thing.
That would be interesting. Not the Trojan horse you’re thinking of... but using it instead for good. One of the downsides to f@h is you aren’t compensated at all for your contributions. Now obviously that’s not such a big deal, since you’re ostensibly doing something altruistic for society and your fellow man/woman.

However... if you put a real cryptocurrency behind it and coupled proof of work to solving real scientific issues... that could bring a lot more compute into the cluster.
> If people wanted to save, why wouldn't they do so privately?

The "why" is complicated, but the "they generally don't" is not.

> Isn't a democracy supposed to reflect what the people want?

People wanted slavery, segregation, Jim Crow, etc. There aren't many pure democracies out there as pure mob rule isn't super awesome in the long run.

Alaska's dividend is particularly odd given they were proposing 40% budget cuts to the state university system recently in order to keep the fund payouts up.

https://www.reuters.com/article/us-alaska-politics/deep-budg...

> Dunleavy, who took office in December and is an outspoken supporter of U.S. President Donald Trump, has called for major cuts in higher education, health care and other social programs as he pushes to sharply raise the annual oil revenue dividend that Alaska pays to nearly every state resident.
Lol. This is a near commodity tech. Heck I built a Rube Goldberg version of this to identify when the UPS guy comes, and I’m a 0.10x developer.

There’s already multiple shady companies that share fixed and mobile LPR. The social media integration isn’t required for this tech — it’s distracting hype.
ASL19 (https://asl19.org/en) | Toronto (Onsite) | Systems Programer (https://asl19.org/en/systems-programer/)

ASL19 is a development, media and design lab building technology for social good. We work bypassing internet censorship, countering misinformation online and holding power to account.

You'll earn a competitive salary while helping make the internet more accessible for people and work on open source projects for social good.

We are looking for a systems programer to join our team (https://asl19.org/en/systems-programer/) We Offer:

- Competitive salary and benefits

- All the hardware you need

- Catered lunch and healthy snacks

- An open culture that welcomes innovation and independence

Email us your CV to: apply at asl19.org
I’m glad there are experiments like this actually happening for any amount of time. It would be great to see the experiment run it’s full course, but it’s maybe more surprising to me that it got funded, rather than that it got cancelled. Thinking about how contentious and political funding can be for things we know we need, like schools, it’s not very surprising that something expensive and not 100% required ends up on the chopping block.

What do you think it would realistically take to be able to fund UBI (or other experiments) without running the risk of being cancelled? How could it be set up so that next year’s political opponent doesn’t have the ability to axe a project to make themselves look good?
I saw it all the time when I was commuting out to the burbs from the city on 90. Every day when I was coming home, I always got a little excited when I saw it had finally incremented! Then I would feel sad about it because of what that meant. It was strange, I had some weird desire to see the number continue to go up, apart from the clearly tragic context. In a way, quantifying it like that kind of abstracted away the human element. As the cliche goes, those who lost their lives became just another statistic. If they had put the name of the last person killed, that might have driven the point home more effectively, privacy issues aside.
I usually set a time limit of how long it takes for me to make a decision

Once I write something I don't go back to fix it until after its done
Canadian here, the supply of housing depends on which part of the country you're talking about. As far as I've heard/seen the supply of housing is generally increasing with demand in most parts of the country - some of my relatives who live in a small town a couple of hours from Toronto were saying the town is getting its first block of apartments.

However, the moment you start looking at Toronto, Vancouver, and to some extent Montreal and Ottawa, the trend no longer holds. The populations of Torcouver are going up far faster than supply is able to increase, for a variety of reasons including the cost of building, regulations, NIMBYism, etc. The problem is further exacerbated by demand-side issues driving it up, such as speculation leading to housing sitting empty and illegal AirBNBs keeping units from being rented.
I totally agree with "you can't just replace availability with pagerduty" if you're dealing with stuff like pacemakers. But that's not what most startups do.

I believe that too many engineers worry about "what if a million users sign up tomorrow" and plan a system that will handle that (which also happens to be fun and tickles all the right places), which takes a lot of time and money and manpower instead of building something that works reasonably well and worrying about building the "right" solution when they're beginning to actually grow rapidly. I'd much rather hear "our servers can't handle the load, there are too many users signing up" than "when we're done here in six months, our system will be able to handle any load you throw at it".

I wouldn't say that it's a no-go (there absolutely are situations where it makes sense), but it often looks like premature optimization.
“It does avoid dealing with the root problems in some sense, but it's certainly elegant.”

Yes it’s an avoidance of the real problems. Basically a nice looking pipe dream.
Another option is to use jemalloc[1] instead. Better performance with threads.

It'z possible to use via .so injection with ld_preload.
>The problem with this argument is that it proves too much. It's true of anything that causes the poor to have more money.

Lower unemployment would be associated with a greater availability of goods and services, so that would get it out of the trap. Higher wages would also be associated with a supply increase if they came with increased productivity, but if you raised the minimum wage then prices of low-end products might actually go up. Of course, the typical supply and demand picture predicts both an increase in price and an increase in volume if the demand curve gets "richer," so you are not entirely off the mark, although your argument is not valid.
So, request budget to move the app to a cloud VM / container, and work out the security issues, etc. The latter will be expensive, but the RPi deferred the cost. Bean counters like deferred costs.

Then, ask finance to figure out the billing. It costs about $5 / month to rent a raspberry pi equivalent, but multitenancy might reduce that.
More "tax dollars" going to rural roads because more people live there is incomparable with a policy maker deciding that more budget should go there.
They are currently not primarily working on the rocket, but in the production process.
My team wrote an analyzer to prevent use of DateTime.Now and enforce DateTime.UtcNow instead. Helps us prevent weird time bugs. Neat stuff. The code for it took me a while to get used to, lots of strange looking syntax and types.
A solution in search of a problem is how I class Kubernetes.
Here in Finland the UBI discussion is completely different from what is in the US. Here UBI hast to come in addition to housing allowance, free healthcare and education.

Realistic UBI would be roughly the size of minimum guaranteed pension.

The cost: Microsimulation models have shown that it can be cost neutral.

In current systems effective marginal tax rates are higher for poor people than they are for the middle class or the rich in both US, Finland and probably most other developed countries. UBI or negative income tax or something similar is needed to solve this problem.
Many startups are not as resource efficient. The ones I am familiar with spend 50%+ of their MRR on cloud costs.
So sqarql rdf should stick to it's limited application space and let more generally applicable graph technologies go their own way
High demand != foreign (read, chinese) investment.
A lot of the poor that qualify for benefits can already get equivalents through family or friends if the program were not offered. If we just give cash, they're likely to spend it on other things and combine expenses where possible.
Good Hygiene? erm... what?
Using data science to predict the best place to launch a cafe in London
I used (many years ago, with Mnemosyne) spaces repetition on CS and AI history. It is really useful to have this extra context available during my normal activities. It allows me to see modern development in a historic context.
So provide a basic income, but also shift some (or all) of the costs of those externalities onto the individual. Your basic income stretches farther if you choose a lifestyle that makes more efficient use of it.