skysight-inc/HackerNews huggingface dataset:
How Big Oil and Big Soda Kept a Global Environmental Calamity a Secret
That's what I thought too. It looks cute, but I normally turn down any animation delays I can. After the first dozen times it just becomes annoying.
To use different phrasing, what you're saying is that you want people to be poorer. Please understand that I don't mean this as a personal attack on you, your beliefs or philosophy. But from a different perspective, that really is what you're saying. Do you really want to say that?

Perhaps a better alternative is: a good goal would be to allow people to have more while using less natural resources and polluting the environment less. While certainly difficult, I'd hope that advances in efficiency (such as more automation) could theoretically allow this!
My fastrebase script is even better[0].

[0] https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...
Create a SpringBoot, Flyway project in a couple of minutes on GitHub
You're not differentiating between an iterative design process, during which failures are expected, and a monolithic one where the end product is final. When Starships blow up, Musk can build new ones and try again. When the probe crashed, that was the end of the mission and there was no more Mars Climate Orbiter. It was a one-off. This is a common problem in spaceflight.

The Webb Space Telescope is another example. If it eventually does launch and something goes wrong, we'll have paid >$10 billion for absolutely nothing. These aren't trial and error because the designs are never improved based on the errors. They're just scrapped. SpaceX works in a fundamentally different way.
> WTF is folding?

folding@home is a protein folding[1] simulator.

> Why not just say, HELP US FIND A CURE?

Though their work helps others find a cure, they themselves are not looking for a cure. Their contribution is only to help understand these things better by simulating the proteins folding.

I'm not saying this to downplay their work, but to explain why referring to folding and not to curing makes more sense. I imagine that it may even be the case that not all their work is with the aim of helping find cures.

[1] https://en.wikipedia.org/wiki/Protein_folding
Load balancing--and yes that can become a source of failure too.
I agree, not least because I can't see how to define 'obscurity' without it also being a basic explanation of encryption.

(Good) Encryption is a (secure) mechanism for obscuring data, surely?
The dirty secret of virtually every k8s setup--every cloud setup--is that the cloud providers' stuff is simply too good, while at the same time being just different enough from one another, that the impedance mismatch will kill you when you attempt to go to multi-cloud unless you reinvent every wheel (which you will almost certainly do poorly) or use a minimal feature set of anything you choose to bring in (which reduces the value of bringing those things in in the first place).

"Vendor lock-in" is guaranteed in any environment to such a degree that every single attempt at a multi-cloud setup that I've ever seen or consulted on has proven to be more expensive for no meaningful benefit.

It is a sucker's bet unless you are already at eye-popping scale, and if you're at eye-popping scale you probably have other legacy concerns in place already, too.
Charles XIV John of Sweden
most likely using martian soil as a radiation shield. Either built up in mounds around structures, or by tunneling under the ground (boring company?)
Linear history.
I've been focusing on reading, but it looks like there is interest in writing too. The HN API doesn't support writing, so the username and password has to be stored. It's important that reading keeps working even if HN changes their backend in a way that breaks writing. I'll think about it.
I'd be willing to bet in most workplaces, about 20% of the workforce is dead weight - especially those in the management chain.
You're forgetting about growth. Is UBI possible today? Probably not.

Quick googling (so take my numbers with a grain of salt but my point is to illustrate not be exact) says US economic growth the last 10 years has been ~45%. If that trend continues today's $3 trillion budget could be $4.5 trillion in 2030 - UBI starting to look much more possible. Another decade of 50% growth and the budget is $6.75 trillion in 2040 -- UBI seems absolutely possible. Sure there's population growth to consider as well, but you get my point where at some point the math works pretty well.
Like others have said, cross that bridge if/when we get to it--there's no sense in incurring the Kubernetes cost now because one day we might have to switch to Kubernetes anyway.

It's also worth noting that Fargate has actually gotten considerably cheaper since we started using it, probably because of the firecracker VM technology. I'm pretty happy with Fargate.
> Developing technology for surviving outside Earth's atmosphere contributes to advances in sustainability tech.

Good point, thanks.

> It also opens up huge amounts of clean energy resources.

Sustainability research is making it clear that we already have an abundance of clean energy resources here on Earth. If Mars does indeed flood the market with cheap clean energy and makes clean energy the overwhelmingly obvious choice, then I agree that will be a net win. But the problem doesn’t appear to be a resource scarcity issue here on Earth so I’m unconvinced that the solution is more resources.

Also, what clean energy resources are you referring to specifically? We essentially need something that can be substituted into our existing fossil fuel infrastructure. Mars provides something like that?
Also, he probably has other debts, and this process will sort out who gets what (since not everyone can get the full amount they are owed).
Agreed - I've found that Anki really helps to recall underlying facts, but if I didn't grasp a concept well outside of Anki, it's not helping with A-HA moments.
If so, why is everyone else so far behind?
"Born in Pau in southern France, Bernadotte joined the French Royal Army in 1780. Following the outbreak of the French Revolution, he exhibited great military talent, rapidly rising through the ranks and was made a brigadier general by 1794. In 1810, Bernadotte was unexpectedly elected the heir-presumptive to the childless King Charles XIII of Sweden, thanks to the advocacy of Baron Carl Otto Mörner, a Swedish courtier and obscure member of the Riksdag of the Estates."

"Upon the death of Charles XIII in 1818, Charles John ascended to the throne as the first monarch from the House of Bernadotte. He presided over a period of peace and prosperity, and reigned until his death in 1844."
That's already assuming that overtime is paid which is not the case in the vast majority of cases.
Agreed. The momentum of welfare service providers alone would see to that, with somewhere around a million US workers having a vested interest in keeping their jobs as gatekeepers/facilitators, vs "everyone gets a check" covering what they control access to. Should UBI be enacted, the very same system would agitate to provide specialty services on top of UBI for special cases, building pretty much the same bureaucratic structure as exists now.

UBI simply redefines $0 income to a higher number functionally equal to $0.
I'm no designer.. but the new logo looks horrendous. From the few design principles I do know, it appears they took all of them and did the exact opposite. If they wanted to stick with flat design, they could have easily repurposed their existing logo without beveling/lighting to achieve what would likely be a much better result.
This problem is tricky with three doors but if you imagine playing the same game but with 100 doors instead of three, then the result is very clear.
Show HN: Vanilla Doom on linux
Preprint: https://osf.io/6mcu3/
For what it's worth, I keep everything in a single deck. I never stop reviewing stuff and "interleaving" makes learning more effective than "blocking" (studying things in blocks). Source: Bjork et al 2013 (https://www.researchgate.net/publication/231610455_Self-Regu...)
Often when I encounter (startup) teams using this git-flow inspired strategy there definitely are things going on with master that shouldn't be. For example:

Feature A is in staging ('develop'), but can't get into prod ('master') yet. However, the opposite is true of Feature B -- a customer needs it now and timelines get changed by sales or management (your largest customer needs it now). It conflicts with something in A and can't go into staging just yet (another team needs it). So that feature branch needs to go straight into master without hitting develop. The whole deployment infrastructure was designed on the (false) assumption that develop is always deployable to staging, and master to prod, rather than being able to quickly deploy and test feature branches at whim. So now we've diverged between master and develop a bit, and while we could still get our way back to a "clean" git-flow at this point pretty easily, if you're not careful this can keep compounding. I've seen it compound for months, and personally have wasted days trying to clean up conflicts that set in because teams I'm consulting for weren't careful.

It's easy to have an inexperienced startup team make these git-flow based decisions early on, get stuck with them for some time, hit rapid growth, and then get themselves into a messy place.

My point is sure, use it if you have pretty steady release and deploy schedules. But if you're deploying dozens of times per day you need to design your infra and CD strategy to handle it. Typically I've seen teams with fragile deploy strategies they've adopted due to assumptions they made from starting with git-flow.

So why even do it? There are simpler strategies like GitHub Flow that force a team to design a deployment strategy that accepts that feature branches can be tested in a real environment, and master can always be delivered (or rolled back).
Two load balancers using either keepalived or bgp anycast.
My Machiavellian side says that they have dirt on you now and know they can use it at any time. If anything, more dirt is then better, as it creates more leverage for them in the long run.

Still, Hanlon's Razor applies, and you boss is more than likely just telling the truth.
living under big shields perhaps?
> You can wait years for services

*in some rare cases
Agreed that there's additional margin we can get with less restrictive zoning, but land is ultimately supply constrained. More importantly, high-quality (previously defined as arable, now defined as "close to good jobs/services") is certainly constrained as a matter of physical distance.
The simpler solution is to just impose a tax of a given rate and pay out all the money it generates as a UBI. As economic productivity increases over time, more revenue is generated and we can pay out a bigger UBI, which satisfies the intuition that minimum standard of living should increase as overall productivity improves.

If that amount is below some standard of living we wouldn't wish on our worst enemies then we can worry about it (i.e. raise the tax rate). If it's somewhat more than that but nonetheless we have a reasonable tax rate, so what? If the economy is doing better in ten years and that allows someone living on a UBI to be able to afford broadband when they couldn't before, is that supposed to be a problem?
A lot of the problem with using Kubernetes is it appears to be the only option for running microservices in a cloud environment. People choose it because they think there's no other option (and they're somewhat right). But there's Nomad, DC/OS, Docker Swarm (for a little bit anyway), ECS, GKE, etc. That's still not a ton of options, but there are options.

That's just microservice orchestration. That's a small part of the totality of things needed to implement a full-out SDLC. You can't just build Kubernetes and think you're done; your code will need to integrate into a lot more stuff, and you'll end up writing 10 layers of glue because that's just how many use cases you have to support.

And it's weird that all that glue doesn't use standards. I mean, we have TCP/IP & RPC & REST, we have pipes & filehandles, we have the OCI specs. That gets us to a point where (at most) half of the stack of an architecture is portable and interoperable with any system following those standards. But then there's every other component of the architecture that connects all the pieces together, meaning you're writing glue that will only work for one implementation. Change your implementation, and you have to change your glue, and probably more stuff.

I think a lot of that non-reusable glue could be erased if it all followed standards, such that the configuration and operation of each part followed a standard interface, set of data types, etc. Tools and libraries could just "talk container orchestrator" or "talk load balancer" or "talk object storage" or "talk secrets management", and virtually any component could be integrated into any other, by virtue of either a system-wide or application-specific configuration.

You could argue we have something like that now with a "kubectl file" or similar, but that's not only still platform-specific, but other tools don't speak it, so K8s has to do everything, because it's the only thing that speaks its language (config file/backend data store/IAM/secrets/roles/etc).

Rather than resign ourselves to those limitations, we could bundle everything in an implementation-agnostic standard way with standard interfaces. The exact same configuration (as code) could be used to run the same complete architecture on a dozen different platforms, because every component would speak the same language and handle all the other components in the same ways. The backend services could all translate the standard based on how they were configured, such that generic instructions are then translated into implementation-specific actions. You could really write your architecture once and run it anywhere, without the caveat of "anywhere on this platform only".

I feel like we're not talking about doing that because we keep getting caught up in "Fuck, Kubernetes is pretty hard" conversations. Yeah, it's hard; building and operating an 18-wheeler is hard. But what about the roads? What about the gas stations? What about the containers we put on the trucks? All that stuff is standard, and so we don't have to worry about what implementation of gas station or road we use. I feel like we still don't have those things in the cloud, and it's just weird.
If they are able to do this by creating the dataset just by scraping public social media web images, and having a facial recognition algorithm in place, whats stopping anyone else to do that ?
The new logo looks more top heavy somehow. When there was a dark ring the logo looked balanced, now it looks like the center of gravity is off and the logo wouldn’t stay upright if placed on a table.
I don't understand the new VW logo, either. What benefit is there to have the characters touch the upper part of the circle, but not the lower part?
Tend to agree. Worst one I've ever seen in a VMS is something like "Province's governor <Name> wishes you merry christmas". (Not in the US).
E – object-capability programming for distributed, secure, and robust software
Luna is a feminine noun in latin. So, lunicula.
Are most people getting their laptops seized?
No top down surveillance would be my preference and it isn't that hard to imagine really. Certainly you can get the impression that people currently don't really value privacy, but if it is taken from them, there will be quite a sudden interest.
Let's just assume you've described the perfect solution.

Now, how do you make it actually happen?

What steps can you take to go beyond making theoretical comments on a online forum, to having a working experimental version handling calls on my Android phone?
Since we already have the productivity to grow and make all the necessities of life, why are we worried about maximizing degree to which we work for more luxury goods?
Your link leaves out the study of the Alaska Permanent Fund
https://www.nber.org/papers/w24312
I believe it's left out because it contradicts the premise - it found more people actually looked for work because prior to the Alaska payment they were too poor to venture far from home.
"China can now produce 1.6 million test kits for the novel coronavirus per week. The test delivers a result on the same day. Across the country, anyone who goes to the doctor with a fever is screened for the virus: In Guangdong province, far from Wuhan, 320,000 people have been tested, and 0.14% of those were positive for the virus."

The US needs to implement this yesterday. The most concerning thing about the outbreak is we really have no idea how many cases the US actually has. Fewer than 500 people have been tested across the country.
From my personal point of view, basic income SHOULD disincentivise work; it's a boost for society, health, well-being, children, etc.

Because in the current economy, a lot of people have to work unreasonable hours, multiple jobs, and have all people in a family work to make ends meet, at the cost of personal health and well-being, personal time, having children at all or having more children, getting married and buying a house, etc.

Right now I'm stressed because I'm earning less than I spend, my girlfriend is stressed because she doesn't have a job yet and due to personal reasons may find it hard to get, keep, and work enough hours at a job, etc. If she earned a basic income we'd be out of the woods already. If I then also earned one on top of my job we'd be VERY comfortable.

(And keep in mind I would already pay for both of our basic incomes through the income taxes I'm paying at the moment. I'm happily paying taxes because other people paying taxes put me through college and into my current job)
Design by committee... Never works.
Lol. I've been using k8 for 5+ years and am currently interviewing for more 'traditional' sys admin roles. The number of traditional problems I don't have by running even a small k8 cluster has become even more obvious as I go through the process. For every alternative you may suggest, I can point out dozens of problems you can run into that are solved with k8s. Just like any other operations tool, yes, it takes time and effort to learn...that's why sys admins exist. I always find these posts by non-sys admins humourous. Devs often have so little respect for the knowledge base required to maintain a stable, secure, scalable, and flexible system. It ain't nothing, no matter the tool you use.
Cost Matters: Why Lambda School should have a lower success rate than college
Seconded.

I mostly read for pleasure (and occasionally for work). Even for work, I don't tabulate what I read. I read a lot of paper books too, where uploading stuff is not practical without a lot of fuss (OCR?).

I love reading. And yes, I forget a lot of stuff. But if I had to go through all this whenever I pick up a book, I'd simply stop reading.
These are vastly more artistically satisfying than the OP, and most other GAN images that are presented as art. That's a great statement about process mattering as much as result (or is that just my POMO talking?)

Thanks for sharing this.
> Maybe it's just the thing that tries to fill the volume. Because otherwise it's displaced by a different one that does it faster.

This sounds like parasite logic to me. We can do better. The fact that I can even conceive thoughts of doing better is all the proof I need to know that we can do better. That’s what vision is about.
> If you can't answer them, then it is because you fear their answers.

Or they object to the obvious answers and rather strike out emotionally. How dare you sir!
The question is not whether the transparent society is inherently good or free. The question is, which is more compatible with freedom:

- total surveillance, of everybody by everybody

- surveillance only by authorities, of the rest of us

The book's premise is that these will be the only choices. The premise may not be correct. But if you start from it, clearly total transparency is better than the alternative.
You can do custom study of all the cards.
> Three year. Would you quit your job, and move somewhere cheaper if you knew the money will run out after three years, and you'll have a three year gap in your CV?

Short-term thinkers vs. long-term thinkers
Isn't that serverless, ie. AWS Lambda?
IBM cancels its biggest event of the year over coronavirus fears
> It actually gets worse than that. Those passwords were shared by the entire team and posted on the group’s intranet. IRC chats published during the trial even revealed team members talking about how terrible their infosec practices were, and joked that CIA internal security would go nuts if they knew.

ouch! can't claim ignorance if you joke about how much trouble you could get in...
This study was in 2018 updated in 2020 - does not cause decline in work by recipients.
https://www.nber.org/papers/w24312
The C10K Problem (1999)
Memory allocators for manual memory management could return memory asynchronously in a separate thread as well. The call to free() is only required to update some internal bookkeeping in the memory allocator's internal data structures. A separate thread could easily monitor when the data structures that hold raw pages from the OS are completely free, and return them to the OS.
I really admire this guy. His energy, his resilience, his improvisation. Had my life gone a bit differently, this could easily have been me. But I can't help but think: what could have he done with his smarts and his drive if he didn't have to spend every day on securing the very basics?
While digital technology led designers to prefer flat, modular and responsive elements, this does not explain why contemporary interfaces and brand designs have started to address adults as if they were kids: breaking down complexity, colourful design, big typography, and animated animals or things with friendly faces.

This just jumbles so many different things together. Animated animals might be associated with children, but colorful design or breaking down complexity has nothing to do with childishness. The subway map is an obvious counterexample.
Land is supply constrained, which causes housing to cost more in urban areas because constructing taller buildings costs more. But the limit on housing supply even in urban areas, absent restrictive zoning, would be that construction cost at any plausible level of demand.

We know how to build 100 story buildings but there is no place on earth where you can find a hundred square miles of nothing but 100 story buildings.
If you're not trusting stuff to sit static without a human near by you probably wouldn't let it hurtle down the road with the same.