skysight-inc/HackerNews huggingface dataset:
That's awesome you know lots of languages, well done. It's not necessarily about what's the best backend choice, it's about getting shit done as efficiently as possible. For the vast majority of projects, you're never going to reach any type of limitation in Node performance, that you may or may not be suggesting. I'm not sure why you're so hung up on the front impacting the back, it impacts MY workflow. I don't have to switch gears, and look up documentation on how to do x y or z in this language, when I already know it in this language. Do you use arrays? Variables? Any basic programming structures? There is plenty of overlap.
I remember vividly a conversation with a developer whose proposed rollback was that we just move the data to a temporary table. And when our customers call us and ask where their money's gone, do we tell them it's safely in a temporary table?
What's "often" however? I think it happens often enough to doubt direct link between dollars and votes, at least absent hard data proving it.
It's the inverse square (not a root), because the surface of the planet is two-dimensional. Think of moving a projector screen back and forth. For a fixed aperture angle, the area projected upon will grow quadratically with distance, so the intensity (inverse area) grows inverse-quadratically.
A __surface__ it projects on to (that absorbs or reflects) is effectively 2D
light intensity scales with (distance)^2.
Microsoft announces Visual Studio 2019
Wow, thank you for this. Scroll reverser did the job.
Unchained Capital Raises $3M to Lend Fiat to HODLers
no worries; that makes sense and I agree with you.

(it's strange that my question resulted in downvotes).
Interesting fact - "Lobster was also commonly served in prisons, much to the displeasure of inmates. American lobster was initially deemed worthy only of being used as fertilizer or fish bait, and until well into the 20th century, it was not viewed as more than a low-priced canned staple food."

Perception is key.

[1] https://en.wikipedia.org/wiki/Lobster
Oracle recently had Apple pull an app from the App Store because it had the word JavaScript in the name. So they are vigorously defending the trademark.

https://news.ycombinator.com/item?id=16862949
Vint Cerf on the 6th Anniversary of World IPv6 Launch
I don't think that's true. If you are using bash or chef to interact with the cloud then k8s can replace those with a much cleaner model.

My biggest fear is helm becomes chef cookbooks
T-Mobile is bringing its long-range LTE to Puerto Rico
It would be iiiidns4tor because, while base-32 is commonly implemented with capital letters, the onion service ID is lower cased.
Things I Regret About Node.js – Ryan Dahl
I use sublime text, it is lightweight, it has many plugins, it is fast and works great on Ubuntu 16.04.
It is very useful if you want to make your devs not client or server but both. This works well in many organizations that i have seen: developer is responsible to build feature from ground to top - this speeds up things a lot.
Because, although it’s only one of many factors to consider, brevity matters.
I don't have much practical experience with Kubernetes but I think one argument is that there are other alternatives to it that might give equal or better productivity gains for a lot of people.

For example Azure App Service or equivalent from the other vendors. You don't have to manage a VM.
The need to secure repos was identified by Karger in MULTICS evaluation. It was a requirement in TCSEC security certification. A great summary of issues is below by David A. Wheeler:

https://www.dwheeler.com/essays/scm-security.html

On top of yours, the OpenCM and Aegis programs attempted to meet some of these requirements. Most ignore them. Big, blind spot in software security.
They didn't just "not mention specs". They mentioned someone asked a hardware spec related question, and then said something along the lines of "I'm not falling for that trick question."

That's waaaay worse than just silence in my opinion.
From a speed standpoint, I'll say the obvious thing, "it's architecture dependent".

For thousands to tens of thousands of users, most folks need data center with 1+n nodes (w/ larger diminishing returns at 8 nodes). There's a few tips and tricks with that, like pointing CI/CD tools to a smart mirror instead of the primary instance and only mirroring specific build projects. Putting smart mirrors in the same physical location as a primary instance could also help reduce the impact of CPU-intensive requests like git fetch or clone.

Another common issue is apps/plugins. Bitbucket 5.9 added a way to get app diagnostics so infra folks can see if there's a long-running process or other weirdness. Vanilla Bitbucket needs about a 1gb heap (java) and with apps, you want around 4gb (give or take).

If you want a longer read to share, this still has some good info despite being 2~ years old: https://developer.atlassian.com/blog/2016/12/how-we-built-bi...
In response to recent elections, I have a friend who decided to counter hate with love and began volunteering in prison. Mostly, it's prayer groups, bible discussions and the like. His strength is something I value, and something I'm not sure I can replicate.

It reminds me of a time when I went to a school in Philadelphia for foster children. These children were between foster homes, generally because they were abused in previous situations. Some of these kids were borderline feral; one, who had been set afire by previous foster parents, was one of the most balanced and normal kids I ever met. Probably, much like hospice care for the workers in this story, that experience has stuck with me.

I don't have any real comment, just that I hope these inmates find peace. Both the caregivers, and the cared for. I'm glad both are there for each other.
I could throw the "you'll know it when you see it" but I'll try not to!
1. You have a large amount of underused hardware/VM 's you want to cluster.
2. You have an eloborate microservices system with a dynamic service discovery mechanism.
3. You have the above over many regions / teams.
4. All your services are mostly stateless.
5. Your team of rockstar ops engineers are building their own crappy version of Kubernetes just to deal with the engineering challenges your business faces.
Performance reviews are a form of legal ass coverage for companies. Their purpose is to re-enforce the notion that there are rules and that everybody is treated equally and have a paper trail to back that up. This paper trail may be used for defending choices for promoting certain people and not promoting, or worse firing, certain other people. They are a formality if nothing is wrong but in case something is wrong, it can be key in e.g. lawsuits or other forms of conflicts. Of course the sad reality is still that e.g. women get treated unfairly in a lot of places and that your mamager's bias or their relation with their peers play no small part in how you get treated. It's far from perfect as a system.

The bigger the company the more likely it is to have very elaborate ass coverage when it comes to these things. So, keep in mind that it might be less about you and more about them when you are having that conversation. They are required to have that conversation with you. It's not optional; it's a box that must be ticked.

However, performance reviews are not necessarily a bad thing and I've had some great managers give me great advice. I would just add that a good manager would not wait until the review if things aren't going great and some of the best managers I worked with made a point out of doing regular one on ones. Coaching happens outside of performance reviews. Performance reviews are also your opportunity to speak up. I once pointed out that I had nothing but good reviews but no recent raise. It went up the chain, they checked their records, and I got my raise. It was a modest one but it felt important to me. These things work both ways.
> You probably don't need the cloud either, but everyone recognizes that it is a productivity gain.

Care to quantify that? Because we don't use the cloud (in fact, in my current role, we don't even make use of virtualisation for production infrastructure) and we have no issues with productivity. Or rather, let's be a little more honest, we have no issues with productivity that would be solved by a move to AWS/Azure/$_some_other_cloud_provider.
As a non-JS dev, it is kinda boring update for me this time. But I am excited when looking at the preview updates, such as the new settings editor and grid layout.

I hope the new UI for settings would also applies to extension settings. It is quite cumbersome to set up extension at the begining.
>"Facebook swap 80GB of DRAM for 140GB of NVM. The lower latency of NVM is therefore compensated for by the higher hit rate from having a larger cache."

Should this be "the higher latency of NVM"? I'm assuming the comparison is to DRAM and not Flash in this sentence. Or am I misunderstanding something?
We work in a busy business park, 10 minutes from the warehouse, where UPS freight comes by and loads an 18 wheeler every day full of packages from a neighbor. They used to arrive at 2-3pm daily but we are now their seemingly last stop. Dropping packages off at 5pm to a business just doesn't work.

All of my examples are for work locations. Residential is always a shit show, but business customers should be held to a higher standard considering they have operating hours that are standard.
I worked at a place that was deploying K8s as I was leaving and my experience was that K8s was complicated and no one knew exactly how to use it or why we should use it, other than it seemed to be what everyone else was doing. I didn't notice any operational improvements over our prior system (which was largely ad hoc), but the kinks may have been worked out by now.
NY State Dept of Financial Services approved the trading of a privacy coin
If you click the "web" link in the HN header, it will bring up a search page, and I clicked on the wsj.com link and got thru the paywall just fine.
I see a lot of value in Kubernetes. For one thing I don't want to wake up at 1 AM if one of my node goes down and brings down with it important containers. If I scaled the environment with excess capacity then Kubernetes should start up new pods on the remaining nodes.
Well this isn't correct either. It's not fully automated in the sense that doors are still operator controlled. LIDAR is completely unrelated and is used for asset management rather than signalling.
It took some time to get used after moving from Atlassian Stash (which works quite well for code reviews, imho) to Phabricator/Arcanist. Still consider the latter inferior to Atlassian tools.
> Yes. They use your banks credentials and scan the accounts. It is really awesome.

Interesting. Is your bank OK with you handing out your web bank login to 3rd party?

I found it strange how LinkedIn could trick people into handing over their email password. But the web bank login..!?
I strongly disagree. I've built a couple in house PaaS type systems in the past with various degrees of success on more classical tech like straight up EC2 using a variety of Terraform/Ansible/CloudFormation/Scripting but the dev experience has always been painful compared to Kubernetes.

Developers really love working with Kubernetes. It doesn't take a lot to get started and if you're not doing anything too crazy it is a huge productivity boon IMO.

Where things get hairy is persistence, but that's the case regardless of Kubernetes or not.
Not quite. "Completing the square" is an algebraic step; the argument is geometric (translation of the parabola). One can learn how to complete the square (symbolic manipulation) and be completely unaware of the geometry.

If you never learned the algebraic trick, would you invent it when solving this problem? It's not immediately clear from the algebra that a quadratic polynomial ax^2 + bx + c even can be rewritten in the form a(x-Q)^2 - R.

Conversely, while this technique involves algebra that amounts to completing the square, it exhibits a general technique.

If you want to say "..and that's just a special case of..", homotopy continuation methods[1][2] -

- because the idea here is transforming the simpler polynomial x^2 - C into a more complicated one, and seeing what happens to the roots.

[1]https://en.wikipedia.org/wiki/Numerical_continuation

[2] https://en.wikipedia.org/wiki/Numerical_algebraic_geometry#H...
It's amazing how hard it is to make something secure when considering side channels. Almost any bit of information can be used to extrapolate more - just consider this type of power-based attack, timing attacks, meltdown/spectre, CBC padding oracles, etc.

Plus, suddenly people are pumping millions (or billions) into private keys on little devices, it is amazing.
If you're invoking the early 20th century you're looking too far back. You might as well look back to serfs working 6 days a week dawn until dusk year-round for their lord and say "look how good we have it, our modern problems are insignificant" even if people are legitimately suffering today. Or go back 20,000 years and talk about how hard it was to be a nomadic hunter/gatherer. Standards go up over time.

There was an incredible period of American prosperity starting after World War 2. Good work was plentiful, wages were high, and the middle class prospered- the American dream was alive. That's slipped away from a huge segment of the population. Cost of living shoots up while real wages remain stagnant. We have cheap luxuries that previous generations couldn't dream of but that doesn't mean that many people aren't living paycheck-to-paycheck or fighting to keep their house or running up credit card debt to stay afloat. Outside of our tech bubble, Americans are struggling when they didn't before.

Meanwhile, capital compounds exponentially. People see their quality of life decrease relative to the average person while they work harder than ever, and they see the rich's quality of life increase relative to the average person while their money works for them. It's hard to live every day in that system and not think that there's a problem.
I think the recommendation is not to use another orchestration service, but to keep the infrastructure simple and not use any orchestration or service discovery at all.

Adding service discovery and container orchestration will probably not make your product better. Instead it will add more moving parts that can fail to your system and make operations more complex. So IMO a "containerized microservice architecture" is not a "feature" that you should add to your stack just because. It is a feature you should add to your stack once the benefits outweigh the costs, which IMO only happens at huge scale.

Most people know that "Google {does, invented} containers". What not so many developers seem to realize is that a Google Borg "container" is a fundamentally different thing from a Docker container. Borg containers at Google are not really a dependency management mechanism; they solve the problem of scheduling heterogenous workloads developed by tens of thousands of engineers on the same shared compute infrastructure. This however, is a problem that most companies simply do not have, as they are just not running at the required scale. At reasonable scale, buying a bunch of servers will always be cheaper than employing a Kubernetes team.

And if you do decide to add a clever cluster scheduler to your system it will probably not improve reliability, but will actually do the opposite. Even something like borg is not a panacea; you will occasionally have weird interactions from two incompatible workloads that happen to get scheduled on the same hardware, i.e. operational problems you would not have had without the "clever" scheduler. So again, unless you need it, you shouldn't use it.

I think the problem that Docker does solve for small startups is that it gives you a a repeatable and portable environment. It makes it easy to create an image of your software that you are sure will run on the target server without having talk to the sysadmins or ops departments. But you don't need kubernetes to get that. And while I can appreciate this benefit of using docker, I still think shipping a whole linux environment for every application is not the right long-term way to do it. It does not really "solve" the problem of reliable deployments on linux; it is just a (pretty nice) workaround.
How is the quality and stability of AMD chips lately? Although I've always purchased AMD chips everytime I upgraded my desktop, the segfault problems reported with Ryzen made me cautious about further upgrades (on Piledriver now).

Are the latest Zen/Zen+ CPUs stable enough now, or should I wait for Zen 2?
Heroku is still amazing indeed. Our team recently moved all Node.js based systems from AWS to Heroku and it has given us a tremendous productivity gain and reduction in complexity. Before we made that decision we spent about 8 months experimenting with K8s, only to discover it actually made things way more complex for us and reducing productivity without any clear benefits.
Every instant the sun emits a certain amount of energy. After 1 second that energy is spread across the surface of a sphere 4pi(c)^2 big. After 2 seconds it's spread across a the surface of a sphere 4pi(2c)^2. And so forth.

Or another way to look at is that that at a certain distance from the sun all the energy leaving the sun is passing through a sphere that grows that same way.

EDIT: Thanks to grn for pointing out I was confusing the constant of a sphere's volume with its area. Fixed.
MIT CSAIL hardware graph accelerator device
It's not even likely they're in the same repo when working with Node (although possible). The context switch between apps is one cost you have to pay (surely your backend will differ from frontend in architecture). However, the costs of switching languages is higher. Golang / JS conventions are very different. It is possible to share some common libs front end / back end (lodash, validation logic, etc) and that helps too.
And my understanding is generally that your bank will disclaim liability for any "fraud" that occurs due to you intentionally and willingly sharing your credentials.
Go Atlassian. So much better.
Organizational Skills Can Significantly Impact Your Success [video]
> .. " kill 6 tonnes (6.6 short tons) of cockroaches at a time with heat and extracts the essence from them."

Essence? What the hell is a cockroach essence?

> “The effectiveness of cockroaches has been tested by the bodies of our ancestors and proven by lab experiments,” Geng said.

What lab experiments? Which ancestors?

> Geng said kangfuxin ye, made entirely from cockroaches, can cure oral and peptic ulcers, skin burns and wounds, and even prevent stomach cancer.

I really hope people don't take this as a preventative measure for stomach cancer.

All of that within a few paragraphs, the amount of bullshit in this article is incredible. While I'm sure mashed up roach guts is probably not the worst thing for you, the claims in this article are unsubstantiated and just don't make any sense.
> Ok, then please point me to an authoritative source where this is described

There is a brief Reddit thread with sources available[0]. The initial post sources DoD transcripts of a post-exercise interview[1], and although this doesn't go into the missile weight issue it directly mentions that active air defense was turned off on the real-world ships in the simulation and they were unrealistically geographically constrained due to rules about shipping channels as they were operating in active, crowded seas.

Regarding the issue of unrealistic missile weights, please read the "rebuttal"[2] and subsequent discussions regarding why the missile setup was unrealistic.

Note: At the time of writing, I freely admit I am unable to source a reliable entry on the motorcycle teleportation bit, so I may be mislead on the matter. I have to get back to work, but will provide more additional sources if and when I can find the time.

[0] - https://www.reddit.com/r/CredibleDefense/comments/4qfoiw/mil...

[1] - http://archive.defense.gov/Transcripts/Transcript.aspx?Trans...

[2] - https://www.reddit.com/r/CredibleDefense/comments/4qfoiw/mil...

> because I can't just take your word for it.

I have to take a moment to point out that you have not provided an authoritative reference for your claims. The Wikipedia entry itself merely cites newspapers quoting Van Ripper, and doesn't even mention criticisms which seems rather suspect. In fact, there is a giant warning at the top of the article stating that the neutrality is suspect.
I did not know you could get dirt cheap USB oscilloscopes
You're conflating so many things it is difficult to know how to respond.

Life + 20 is a completely different class of sentencing than the ones in the Wikipedia list. I don't see a large distinction between re-sentencing or not. The end result should still be 20 years, no? "Life without parole + $X years" is functionally equivalent to a "whole life order" in the UK.

The extremes in the list are of two classes:

1. Mass murderers, serial murders, or others who have gone on large crime sprees. These generally carry life sentences without parole. So, they cannot be indeterminate no matter how many years are tacked on, unless they have a successful appeal of all convictions that result in life sentences.

2. The indeterminate sentences you're talking about. Generally speaking, these are pretty egregious, violent crimes with many victims or the same victim over a long period of time. In many cases, the convicted could have received a life sentence, or one would have been mandated depending on the crime and the state.

But this isn't common by any stretch, except on TV crime dramas. A problem is the giving of life sentences to nonviolent offenders (e.g. California's three strikes law). Also problematic is the stacking of charges to compel plea bargain, which is exacerbated by cumulative sentencing. But "Life + 20" is just, effectively, a life sentence with a different label.
​Buildah 1.0: Linux Container construction made easy
They aren't even close, shrimp have actual soft flesh and tissue. The only characteristic I can really see them sharing is they have an exoskeleton.
Any particular background on any of this you might recommend?
We do the latter, and I am currently reading this thread to gain ideas.

Please, if anyone has ideas about what a good performance management SaaS would look like - share!
Wired and Wireless AV System
My team runs a grand total of 1 server, 1 daemon and up to 5 concurrent batch jobs. Sometimes we bring up 1 extra server for experimentation.

It is handy to not break the bank and use GKE autoscaling for the batch jobs. Surely we could setup some batch job manager over some raw VMs, or maybe spend some time to select and learn to use yet-another AWS service.

It is handy to go to the GKE "Workloads" page and see how many servers are currently active, using how many pods. Surely we could pull that off with raw VMs, but it would take me a few minutes extra / a brittle script to pull it off.

Do we _need_ Kubernetes? No. It makes us more productive? Yes. Am I confident that in the next assignment I'll be able to reuse my skills, regardless of what VM provider they use? 90% yes, pending EKS becoming usable.

Echoes of "you don't need C, just use Assembly, it's simpler and faster" from early '90s gaming industry.
> Currently needs to be an EV certificate though.

"currently" sounds like that might change in the future. I thought the CA/B forum was pretty much opposed to non-EV certs for .onions. Is that not the case? What is the potential use case for non-EV certs on a .onion?
As someone from the UK I find a lot of this hilarious, our employment laws are strict as fuck, unions are optional even in unionised businesses and no one gets fucked over if you don't join