skysight-inc/HackerNews huggingface dataset:
I just think that it's silly to boycott someone's videos about the a launch vehicle just because they work in missile testing. Especially when you consider the heritage of launch vehicles in general, and the Saturn V in particular

The Saturn V's F-1 engines were originally designed for the Air Force. Would you boycott a video about the Saturn V made by someone who actually worked on the thing, because they worked on a part of the Saturn V when it was still a military project? I feel like that is a ridiculous purity test.

The Titan series of ICBMs, with light modifications, was a workhorse for America's civilian space program. The Atlas, Delta, and Minotaur families of rockets were also originally ICBMS. AFAIK the only deaths from the Titan II were industrial accidents, which can happen just as easily for a civilian rocket program (although silo conditions did exacerbate the accidents). I don't think it's fair to say that someone who worked on testing the rocket contributed to those deaths— if anything, competent testing should reduce the number of accidents.

I won't go too much into the less wholesome background of the Saturn V, which had multiple former Nazis in leadership positions, all of whom had previously worked on rockets like the V-2. The head of the Saturn V program office even gave up his US citizenship in the 80s as part of a deal with the government to avoid prosecution for war crimes and abuse of prisoners during the Holocaust. I don't understand why someone would be willing to accept that, but not accept involvement from a random test engineer at Redstone Arsenal.
" But the success of US tech companies is certainly notable."

One of the funniest statements ever following an assertion of empiricism.

The left's idea of "leading" is always amusing. The left in the socialist paradises in Europe will keep depending on US technology and posting on sites created by US innovation. At least until they depend maybe on China and then they won't even have the choice to practice evading their own country's speech laws.

The leftists in the US will just keep abusing the privileges they are afforded by those who keep them in luxury because that's just what they do. The system is good to them that way.

I'll now go "wage slave" so I can afford to travel to places that produce old buildings you visit.
This is not price negotiation really at all because uber can and does kick people off the platform for not accepting rides. https://www.businessinsider.com/how-uber-drivers-get-deactiv...
How many people cheering this are still paying the plumber that fixed their toilet a year ago a salary?
Nobody is stopping them from being independent drivers with their own customers. For example, I do this for with regular drivers for airport rides that I originally met on the app.

Uber is a matchmaking service that comes with certain rules and objectives so the marketplace works better for everyone, and flexibility to work when and where you want is usually most important.

Perhaps we need a 3rd category to account for this kind of work.
More like: "If people voluntarily choose those jobs then doesn't that mean that any alternatives that aren't even worse have been replaced with ones that are even worse, because the government allows such replacement?", actually.
> Jogging around would not provide the same benefits as a proper strength training program.

it is not the tax payer's responsibility to provide a proper strength training program for those who cannot afford it themselves. It is the tax payer's social responsibility to provide a service when said service is important (like healthcare) but is difficult for the poor to fund themselves.

Exercising is important, but it's free to do, so should not require a tax burden to provide anything of this nature for the poor. Health care cannot be free (nobody works for free). Therefore, it's important for the tax payer to fund it.
... which is why you never see any other companies with "electric" or "electronics" in their name.
Ah, modern art.

https://imgur.com/JxOzgTM
> There is no free market of proposals

Drivers are free to accept or decline any ride requests around them. How is that not a free market of proposals? Pretty much every driver I met used multiple applications, Uber, Lift, Juno. I don't know whether or not any Uber drivers would stop for someone just flagging a cab on the street the old fashioned way.

> Uber sets the terms and conditions

There are always terms and conditions. If your handyman needs to do something to your power circuitry, he had better be a licensed electrician. The catering that puts icing on your cake, better pass a health inspection. And your cab driver better have a driver's license. All of these are pretty much take it or leave it restrictions.

> it would have to allow drivers and riders to post proposals, set their own terms and prices and freely select from available offers

No taxi service I know of works this way. Because you want your fares to be at least somewhat predictable and your incentives are aligned very different from driver's incentives.
> rebase is already a big no-no in any sort of distributed development

You are ill-informed on this subject, and I have a proof-by-existence.

Sun Microsystems, Inc., used a rebase workflow from the mid-90s all the way until the end, at least for the codebases that made up Solaris (OS/Net and other consolidations), and it did so while using a VCS that did not support rebase out of the box (Teamware, over NFS). It was essentially a git rebase workflow years before Larry McVoy created BitKeeper, and even more years before Git was created, and even more years before the rebase vs. merge workflow controversies.

When I was at Sun we had ~2,000 developers on mainline Solaris. The rebase workflow worked fantastically well.

Large projects had their own repositories that were rebased periodically, and team members would base their clones on the project's clone (known as a "gate").

Large projects' gates would get archived for archeological interest.

All history upstream was linear. No. Merge. Commits. (We called them "merge turds", and they were a big no-no.)

Solaris development was undeniably distributed development.
Visual Basic pre-dates Delphi. Remember VB6 was the 6th iteration of Visual Basic and VB hadn't really changed that much since at least Visual Basic 3 (which was the earliest version I used).

I always thought Visual Basic got unfairly mocked because it was a fantastic language and framework for non-computationally expensive workloads.

Delphi, on the other hand, I struggled to enjoy. I really wanted to love Delphi because Pascal was one of my favourite languages but Delphi just didn't gel with me and it's hard to explain why. However Hejlsburg was also the author of Turbo Pascal and that achievement alone deserves to put him in the history books in my opinion.

It's also worth noting that your Apple/Jobs comment should probably acknowledge Steve Wozniak instead.
I often append forum, reddit, whirlpool, etc to a search to avoid the content farms. I think it will hold out for a while longer.
> important distinction is that typically GC iterates over something (incurring a cost of O(N))

During _collection_ and N is size of live set, so divided by allocation the cost is amortized and can safely considered as O(1) much like appending a dynamic array where costly O(N) resize is amortized over N appends.

Typically GCs allocate via bump a pointer allocation which is actually faster then what pretty much all of libc malloc implementations would do.

> C++ case iterates over nothing (incurring a cost of O(1)).

Not quite, take a look at jemalloc paper for instance:

https://www.facebook.com/notes/facebook-engineering/scalable...

A lookup to get the metadata for this specific allocation could be anything from O(1) to O(lgN) depending on size and malloc strategy.
IIRC there are already some analogous uses in mining - there the track following is a bit easier, but has similar dedicated use simplification.
CQ (Cultural Intelligence) may be more important than IQ or EQ (2017)
> As many have mentioned here already, $72/mo most likely a rounding error on workloads kubernetes is designed for.

There are _many_ reasons to use k8 beyond just workload scale and that amount per cluster per month isn't anywhere near a rounding error for many deployments.
> This is great feedback, but clusters should be treated like cattle, not pets. I'd love to learn more about why your clusters must be so static.

Clusters often are not "cattle". If your operation is big enough, then yes, they might be. Usually they aren't, they are named systems and represent mostly static entity, even if the components of said entity change every hour.

Personally, I'm running in production a cluster that by now had witnessed upgrades from 1.3 to 1.15, in GKE, with some deployments running nearly unchanged since then.

Treating it as cattle makes no sense, especially since on API level, the clusters aren't volatile elements.
>It is basically what whole world do

It's not what the whole world does. Many companies gasp start charging for something right away! They're entire sales pitch was that it was free. People made decisions based on that which are not so easy to turn around.

It's a legal form of bait and switch and it's hardly accepted as an ok thing to do by consumers.
... "from the data we have so far."

There are still a lot of unknowns, as stated in the media briefing.
The title is just one of those many points made.
> I've never run a rebase on purpose in my entire life

While it's great that you've found a branch strategy that works for you, I would hesitate to take recommendations from anyone who doesn't rebase their patches. Then it's just an elaborate way of doing cvs style development.

Which there is nothing wrong with of course. That works great for many people. It's just not what git does best.
Thanks for the input, you do bring an excellent point. I wouldn't agree that they are equivalent though, one is formed specifically to give the impression that it's never disadvantageous, while the other isn't. Parentheses aren't used to bring essential information, which in this case, it is essential.

This is why I would have less problem with the second one. I would still precise that some of theses benefits aren't really a choice, they are tax break that just happens to be offered because of your income, so sure if you already went beyond that income, you aren't on that government benefit... but at one point you weren't beyond that income and you did made less money once you went beyond.
Interesting... i wonder what the data is to back up that assertion?

Another interesting tidbit in there was that very few cases (1%) appear to be totally asymptomatic, and that most infections apparently start showing some symptoms after a couple days. So there are a few assertions in total that seem to depart from what was previously understood, at least through mass and social media.
This is a different point that the one I made.
I'm self employed. I really strongly prefer it. I don't want to be an employee thanks. Yet my government (UK) are also trying to ban it (IR35). Why is it so hard for people to understand: I prefer cash to "secure employment", I'm old and mature enough to make that decision?

I didn't even know I was this right wing...
Ideal Free Giveaways to Promote Your Startup
Finally! We've been wanting something like this for a long time.
> at which point the vehicle has no way to prevent a robbery

What a novel problem, truly unique to society. Goodness wonders how society protected stage coaches back in the 1800s.

Perhaps with deputized armed tax-payer funded civilians, tasked with investigation and law enforcement?
This is my experience too, anything non-trivial quickly becomes an absolute mess, even the trivial things often have bad defaults. A few years ago I looked into using it as a build system for .net projects but ended up tearing my hair out on even the simplest things like removing directories or recursively copying html files: http://flukus.github.io/powershell-is-a-joke.html
That's because humans are the main cost, like I said, and no amount of software is going to make them go any faster.

If there's really such a better execution to be had then Atrium was in the best place to find it. Yet it didnt.
What else does a typical attorney need to use that would make a meaningful difference?
I guess I need to start migrating my clusters, then. $73 per cluster on my prod, dev, QA, and test clusters is a significant increase for me. Looks like Google is doing their best to kill off GCP - https://www.cnbc.com/2019/12/17/google-reportedly-wants-to-b...
When you are doing things that operate on unstructured text and files you will probably get a more concise script with bash most of the time. As soon as you do anything beyond that with structured data or complex processing (e.g you fetch a Json from a web api, filter some properties in it with a regex, save the result as xml, send the xml to a program, parse the output using some complex logic,...) then the powershell is way more powerful.

You might say it’s more a tool that shines in the cases where you’d already give up on bash and use python or something else instead, because you need some libraries, some structured error handling etc.
Like every "special offer for startups", it's a vulture waiting for funding round to close.
Got to see the Seti Burst computer rack at Arecibo in December along with a lot of other stuff. Glad to have that memory.
He says he's posting videos of himself playing the piece, which means he owns the copyright of his performance.
Just eat cake!
acute food shortages would make growing food more lucrative than growing khat. there is probably something else going on
This is a good one too, subtle: https://imgur.com/3uo8VyJ
How to Instrument UserLand Apps with EBPF
Since you actually did some research and posted a link I will go along with those numbers.

>We estimate Intel’s total server die cost at $162 per good server chip while AMD costs about $108 per good server package.

EPYC is 8 Die + an IOD, assuming the massive IOD of ~420mm2 only cost $10 ( That is suggesting GF are selling 14nm / 12nm Wafer at ~$1.2K, even under the AMD WSA with GF would likely not be feasible ), that number suggest the cost per Compute die would be ($106 - $10)/8 = $12, which is again off by quite a bit. Compared to equivalent die size cost of Intel, which is not even accurate because intel do not require the 65%+ Gross Profit Margin from TSMC and it is on an older mature node. And its yield are too pessimistic, we do not have any numbers from Intel on defect per mm2, but taking a guess from Nvidia's massive ~800mm2 die isn't too far off.

So again, let's assume both of those numbers are "relatively" correct. Do you think $62 would matter for an Intel® Xeon® Platinum 8280 Processor with Recommended Customer Price of $10K? Or the same die they are selling at the lower end for $3K?

While it would definitely be good to have those $62 as profits, the reality is on the server market its advantage is relatively minimal.

The bulk of the benefits of Chiplet approach is that you can reuse one or two designs and have it deployed across the whole range of market from Server to Desktop. As design cost increases with Pure Play Foundry such as TSMC this is extremely important for Fabless Design company like AMD, it cost them hundreds of million per design variation. Intel would have that problem down the road but it is mostly migrated for now because all of their design and fabs are in house, and would not cost them as much.

And since the original post was specific to ARM and Server, which has a different market dynamics in cost, you have less R&D as compared to x86 market. In ARM you are paying for IP price on the N1 core and some Interconnect, and those cost of Spread among all ARM players. Hence the conclusion of Chiplet is everything isn't as clear cut and why I said it is too narrowly focused.
"No time to die" was postponed. Probably an "uh, oh".
the conjunctiva of the eye is different tissue than optic nerve. there is fat, connective tissue, and muscle surrounding the eye.
I was making a general point; I favour outdoorgearlab for example. But far more often, forums seem to provide more "real" and practical advice.
I find that Instagram stories, being ephemeral (they disappear after 24 hours) have done a lot do reduce the impact of "instagram perfection". You get to see a bit more of people's real, everyday lives.

You're right that you miss things if you don't check it at the right time, but that's ok, you don't have to see everything.
My only beef with rebasing is that it seems to fail much more often, whereas merges will usually do the right thing. I realize this is git-specific, but rebases have still given me much more trouble than merges.
In my opinion the problem with GitFlow and a lot of other git workflows is you end up holding a bunch of state inside of your git branches which is hard to decipher, complicated to manage, creates work for people ( with merge conflicts, and managing feature branches that need to be merged ), and is capable of losing progress.

My solution: USE FEATURE FLAGS. Keep the list of features and refactors you want deployed in a format that is easy to audit and reason about.

I like the Microsoft branching strategy: https://docs.microsoft.com/en-us/azure/devops/repos/git/git-...

Basically:

* Create feature branches.

* Merge into master when the feature is done. For long lived branches: Don't keep them around. Merge them into master and put them behind a feature flag.

* Deploy to environments using release branches.

* USE FEATURE FLAGS. Do not hold state in your github repo/branch merge status. Do not control features and refactors inside of your git branches, only merging the code you want to be deployed. Instead, put them behind feature flags and activate them using code.

There is a good book on the topic of feature flags titled "Effective Feature Management" that is a good overview. Feature flags do not have to only protect features. You can put refactors behind feature flags as well, or really anything.
Unfortunately, even if they switch to dynamically started clusters, the latency of spinning a new cluster is much higher than the latency of adding a bunch of preemptible nodes to existing node pool :/
I've never had such a steady stream of seemingly conflicting data before.
Why do your utilities needs to be distributed? We have our own well, and generate our own solar power. Transportation isn't a big concern because the kids walk to school, we grow food, and I work from home. With the mix of animals and crops we grow, there is a full ecosystem that supply our fertilizer via composting. Our waste is reduced because we use less packaging, and even food waste goes to the chickens and becomes our egg supply.

Those counter-points notwithstanding, your larger point is still valid -- but you are bringing in a pile of assumptions.
Skyresponse – Cloud platform for intelligent alarm management
It's a good point, HN thinks after 60 years of sucking and being useless Augmented Reality (AR) is going to go exponential this year!

But then someone in the Valley did beat a hell of an old Taxi institution exponentially.
Mis-classification of employees is very common in the U.S. for tech, if you work on a company laptop and work a full time schedule for 1 client, you're likely mis classified.

Similarly, many nannies and cleaners are mis classified.
I'm continually surprised that we don't have a clear delineation between extensions that "do" something—maybe relying on well-known third-party SaaS APIs in the process—and extensions that exfiltrate your browsing data.

99% of extensions don't need to send the URL anywhere without the user clicking to activate them; nor do they need to send the whole content of the page to a server, ever.

You know how macOS now has a capability-model for apps, where it sometimes says "X wants Y, and it's been denied it; you can go into System Preferences to manually give it Y"? That tends to neatly fix the "99% of apps don't need Y" problem, by increasing the friction to getting Y to the point that users won't generally bother unless the whole point of the app is Y.

I'd love to see that implemented for browser extensions—or, in fact, for individual tuples of {extension, trigger, data, third-party origin}.

In the sane case, that'd look something like: {Instapaper, on click of the extension's button, current tab's URL, instapaper.com}

It'd be pretty clear, just from looking at one of those entries, whether it's something that contributes to the functionality of the extension or not. Extension authors would undoubtedly write "installation instructions" urging users to enable these; but if the instructions say to enable a stanza like {MalwareExt, on page load, sends everything it can, to badserver.info}... well, even the most guileless user would think twice, no?
The website has one of the worst scroll bars I've ever seen. Some people just mistake minimalism with minimizing things.
This is important, because lots of internet commentators are just going with the most alarming possible statements: 28 day incubation periods, people can get infected twice, airborne transmission, asymptomatic transmission. These assertions are all based on outlier cases, sometimes even single cases, observed during the fog of war. Even if these accounts are correct, they aren't the typical case, which is what actually matters for policy and prevention.

The typical case has been well-known for months: most people get fevers, the incubation period is usually a few days, and most transmission is from symptomatic cases and via droplets. The WHO has collected stats from tens of thousands of cases and they've been straightforwardly pointing in this direction the entire time.

There definitely is a serious problem, but misinformation helps nobody, even if its spreaders are well-meaning. For example, I've seen a lot of people take the inflated statements ("28 day incubation period!!") to mean that stopping the spread is completely impossible, while we have seen by example that it isn't.
> I don't agree with Cory Doctorow on everything

Honest question, why this qualifier? Nobody expects a human to agree with everything another person says.

Is it unfashionable on hn to agree with this Cory guy, whoever he is?

EDIT: For anyone else wondering, he seems to be a writer.
>I don't know what I would have done had they continued to dig in their heels.

Either they would sue you or the claim would go away.
That model tends to break down as soon as you need more than one development branch.
Even things that have science are largely ignored - one I always shake my head at - oracles for ethereum. Proved many years ago - there can't be an oracle. Ethereum developers - we'll build oracles so the transactions are guaranteed.

No doubt there will be arguments for how oracles for ethereum are different, and so on
I am usually searching it for Australian-specific house-related info (sealing concrete was a recent search). I don't know many other Australian sources that have a broad range of content. There are some reno forums which have solid subject matter experts too.
Beige Book: National Summary
In practice, the cert-manager team has made breaking changes in probably close to 1/3 of minor releases (which is really fine pre 1.0, IMHO), there has been comprehensive guidance to lead users or cluster admins through upgrading, that walks through exactly what steps are needed, and followed well does not interrupt your cluster's service in any way.

It's not dark magic, it might make building off of it in the form of integrations prohibitive, but they have done a great job making sure users can upgrade one release to the next.

It is a little bit of a treadmill, but it certainly beats manually renewing certificates!
But the overpayment is optional, you can stop it at any time if it becomes inconvenient. Whereas as long as your mortgage balance is outstanding you are legally required to make the monthly payments.
My plumber is an actual independent worker, setting his own rates, having his own clientele and free to organize his work as he sees fit.