skysight-inc/HackerNews huggingface dataset:
Kotlin and Swift are both currently encroaching on Go's server-side use cases. For example, Go's star feature, goroutines, has recently been cloned by Kotlin. They are at least as equally pleasant to program in, and they're hitched to major client platforms which means they improve faster and will definitely have a pool of trained developers in the long term.
I completely agree! I think the narrative would then become “rich and greedy big pharma gets rich selling legal narcotics to addicts”
6000 troops isn't alot
>take the seed of this κάνναβις

Thought it was strange that such an ancient word would closely match what we call it today... The etymology page on wikipedia credits that term as the origin of the modern word.

- https://en.wikipedia.org/wiki/Etymology_of_cannabis
> After a couple of years of massive frustration with the entire direction of the "devops" segment,...

> Kubernetes represents the complete "operationalization" of the devops space.

It's funny that I have all the exact same concerns and misgivings as you, but the exact opposite feeling (ie reactionary bias) of where it has come from :)

To me in my less charitable curmudgeonly cynical moments (using when tracking down a Docker or Kubernetes problems), it feels like "ops" was overrun by talented but inexperienced devs adding too many layers of abstraction too quickly CADT style funded by large valley tech companies and VC money. And constantly changing them as fashions come and go. It's like the React ecosystem having a go at Go.

For all the faults of the culture of slower moving traditional systems software written in C etc, we didn't run into so many issues with the level of bugginess or with tooling that gets abandoned/replaced before we've even finished evaluating it. It's like Go has done for systems software quality what PHP did for web software.

To be fair Docker is maturing now, and Kubernetes itself has too now, but the gap between the now relatively stable low level functionality of core kubernetes and what app developers need at a higher level is a gulf of churning crap.
Treat everyone the same. My local bar recently got in trouble for allowing people to smoke weed on the patio. Meanwhile there's someone shooting heroin in the parking lot.

If you commit property or violent crime you go to jail. Rehabilitation services should be made available there.
Less than 10% of prisoners are in private prisons - getting rid of private prisons would have little impact on support for the drug war.

https://en.wikipedia.org/wiki/Private_prison

Which isn't to say that public sector unions and companies that supply material to prisons, or built prisons don't all support polices that incarcerate more and more people. (For example, the CA prison worker union spends more on political lobbying than all other labor unions in CA.)
https://en.wikipedia.org/wiki/California_Correctional_Peace_...
Mac Pro 2019 – What we know and what we’d like to know
"This opioid chrisis stems from doctors carelessly prescriping pain medication and patients"

Yes, so think of what would happen if you could buy opioids willy nilly, wherever.

So yes, thanks - even with 'intelligent actors' in the system, it's also a problem.

FYI - the crisis is definitely not just 'doctors' - it's a whole assembly of problems. Doctors can be misinformed, patients can be demanding, regulatory issues, pressure from drug companies.

Apparently America is getting better at prescribing fewer opioids as well, so this is good, but 'getting smart about how to prescribe opioids' (which is good) is one part of the 'war on drugs'.

As for medical uses of Fentanyl, super, that's great, all for it if there's legitimacy - but it's again it's going to 100% have to be 'a controlled substance', ergo, people arrested for smuggling quantities, which they will, ergo, 'war on drugs' continues.
How would you prefer it be implemented?
> These cannot run at the same time as the output of one feeds into another one.

This precludes parallel processing of individual packets, but does not prevent concurrent processing of packets.

Plugin A accepts a packet, processes it, outputs it. Plugin B accepts a packet from A, processes it, outputs it. Plugin C accepts a packet from B, processes it, outputs it. [...] Plugin G accepts a packet from F, processes it, outputs it.

Everything is serial so far. Got it. Here's the thing though: Plugin A processes packet n, Plugin B processes packet n-1, Plugin C processes packet n-2, [...] Plugin G processes packet n-6. Now you have 7 independent threads processing 7 independent data packets. As long as the queues between plugins are suitably small you won't introduce latency.

The mental model here should be familiar to anyone in the music industry; each pedal between the instrument and the amp is a plugin, each wire is a queue. Each pedal processes its data concurrently (but not parallel with) with every other pedal.

It's relatively common in game development for AI/physics to generate the data for frame n, while graphics displays frame n-1. (there's a natural, fairly hard sequential barrier separating physics from graphics, and there's a hard sequential barrier when the frame is finally shipped off to the GPU) Especially on consoles that have 8 core CPUs but each core is really slow. PS4/XBoxOne use the AMD Jaguar architecture, which was the mobile variant of Excavator. The single core performance of these CPUs are absolutely atrocious, but the devs make it work for latency sensitive activities like gaming.

> Data travelling from one core to another could mean additional performance loss.

Only if it is evicted from the L3 cache, and the 3950X has 64MB of it. That's over a second(!!) of latency at 16 channel+192kHz+32 bits/sample audio.

Speaking of channels, that seems like a natural opportunity for parallelism.

I get that legacy code is legacy code, and a framework designed to run optimally on Netburst isn't necessarily going to run optimally on Zen 2. (or any other CPU from the past decade) But this is an institutional problem, not a technical one. It sounds to me like somebody needs to bite the bullet and make some breaking changes to the framework.
The problem may actually be compliance requirements. SOC2/HITRUST/SOX all mandate the removal of admin rights from computers, mandate an approval process w/ manager approval. Regulated industries, especially banking have more security-related compliance requirements causing a lot of the pain.

Unfortunately from a security perspective devs and system admins are probably the highest risk targets since they typically have access to servers and admin rights. At the very least they have source code an attacker could analyze, and likely have access to external services.

The reality is that compliance, security and usability are often in direct conflict that can only be solved to make everyone happy with significant work.
I mean, until they realize they did, right? [0]

Like I said, there's a place for those systems. Redis in particular is close to my heart. But many devs hear "NoSQL" and think "Great, I love JSON! Who cares about SQL, SQL is for fogies!"

I have little doubt that the staff at places like Google and Facebook are qualified to weigh the concerns and choose the system that works best for their use case. The concern is about the rest of us, and the rapid proliferation of experimental systems developed for internal projects at MegaCos whose demands make any off-the-shelf system untenable.

The fact that Google or Facebook release a project essentially as an academic exercise doesn't mean that it should come anywhere near mainstream use. People see "Facebook" or "Google" on the front matter and want to be like the cool kids on the block, hardly realizing the quagmire they're plunging into.

MongoDB gained prominence by claiming massively improved write performance and encouraged devs to switch off real databases for a system of record and then, woops, it turns out that "write performance" is sans-`fsync`. That's sort of fixed now, many years after the controversy, but they still built the entire NoSQL story on the back of that deceit.

As an autodidact who detests formal schooling, I hate to say it, but sooner or later, there is going to need to be some type of vetting/licensing at play here, both to stop the mindless proliferation of "grab anything Googly" and to hold those who engage in predatory behavior accountable.

[0] http://hackingdistributed.com/2014/04/06/another-one-bites-t...
> Obviously it is my responsibility to keep those bytes away from you.

If you're in your home changing and accidentally leave a window open, I shouldn't be watching you through binoculars. Whether it's bits and bytes or images or sounds, it doesn't make any difference, we're ultimately trying to avoid various types of harm.

And that means you're right in that it is your responsibility to be prudent because people will do bad things, but at the same time it's also my responsibility not to intentionally spy on you. Though, that shirt has to go.
At my small startup we tried using Google Drive as a Dropbox replacement a year or two ago. We are paying for Google apps so it made sense to try they're Dropbox-like service, and it had some seeming advantages too. We found it to be a lot less reliable than Dropbox in most senses. UI is worse, error handling is poor, you may easily end up losing data. Not worth it. Now we pay for Google apps for gmail, and for Dropbox for file sharing. Which btw has become a lot better now that there is cloud sync available in the pro subscription (not only in the business subscription), they raised the price from $10 to $12, but I'm so happy that I have been able to recover some much needed disk space in a convenient way!

I agree with the issues with the Mac OS client burning too much CPU/battery, I've learned to live with that as an inconvenience, since otherwise, it works great by fulfilling the top priority you want in a service like this: it is reliable.
Actually it would be either ASCAP or BMI that enforces this fee. When I owned a small restaurant, I had to pay for the privilege of playing CDs over a stereo.
So you have enough intuition to criticize this drone toy as being "designed by dudes" and not palatable for girls, but have zero intuition about how the game can be changed so your own daughter would enjoy it better? Do you realize how unhelpful that is?

From your own words, it sounds like your daughter enjoys being aesthetically creative rather than technically competitive. In which case, why are you bitter about a drone company being a drone company?
I don't think you realize just how big 64 bits for the network address is. It's one of those things where the scale is so large it's outside of normal human experience and we just can't hold it in our minds. There is no danger of running out of addresses for hundreds of years unless we decide it is necessary to give every single atom in the Earth its own /64. Even then we would have plenty of room to spare in the address space.

It's just an absurdly large number. Giving out a few thousand to anybody who asks will never be a problem until humans have literally filled the galaxy.
I have always been intrigued by your service, and will probably try it at some point for a smallish setup for important data, but whenever I think of backups in the TB range, it gets way out of budget (even after accounting for borg or other discounts). Do you have any plans to compete on pricing with other popular cloud/storage providers? I understand that this is a different product for a different audience.
Timestamps are adjusted by the second-chance lobber; see https://news.ycombinator.com/item?id=19774614 and https://news.ycombinator.com/item?id=11662380. You can think of the modified timestamp as the re-up time, though it's a bit more complicated than that.

The best way to see which came first is to look at the post IDs: 20167106 < 20169125. Or, look at pages other than the front page or /item. For example: https://news.ycombinator.com/submitted?id=cdepman. Those always show the original timestamp.

Sorry for the confusion, but it's the only way we've found to balance the various concerns that apply there.
The API is there, but is there a stable MongoDB Operator? ( https://github.com/Ultimaker/k8s-mongo-operator ? https://github.com/mongodb/mongodb-enterprise-kubernetes ? )
I don't know, I'll go and read up on it more.

The feature leaves me 'meh'. I don't find slices as awesome as everyone is always saying, especially without negative indices.

I guess part of it it that it isn't always clear to me when you're dealing with a slice, or an array, or whatever.

I know, when it's confusing, there's always some reasonable sounding explanation after the fact, sure, but the whole thing feels like a confusing mess.
Alternatively you could have completely open interests in public correctional officers unions. Over 90% of prisons in the US are public and their employees are at least as highly motivated as any investor to lobby for more punitive laws and they can vote.
Supporters of a dishonest leader are mostly well aware of the dishonesty (pity the few victims that actually fall for it, because they're most likely to be the eventual casualties of a catastrophic resolution). For them, the lies function as a shibboleth which allows mutual recognition and cooperation through the pretence of a shared counterfactual.

An amusing example is when people complain about 'virtue signaling' - almost everyone engages in this, but because the word virtue has moral connotations it is projected onto people who make moral arguments and superficially appears consonant with and a critique of their behavior, when actually the underlying purpose of the complaint is for people who ostensibly object to virtue signaling to recognize and team up with each other by shared recognition of an in-joke. That is to say, pejorative use of the term 'virtue signaling' is an instance of covert virtue signaling.
They're a useful tool for understanding the mindset of the original developers, but as you go "up" in the layers, the division of responsibilities becomes more and more arbitrary, with a very sharp uptick after "layer 3".

But more importantly, the notion that routing and forwarding "belongs" in IP, because that's the layer 3 protocol --- that's just false. There's no validity to it, and lots of systems have built overlays with layer 3 function on top of UDP (which in the "layering" model is a "layer 4" protocol, but is really best thought of as an escape hatch with which to build any new system you want on top of IP).
For one Elixir is very slow compare to Go.
I mostly agree... I used to work for a classic car website, and in that case, we dealt with a LOT of comment spam, and scams that were out there. A lot of it is actually individual people, doing actual work to get past. We also did see a lot of custom bots, etc. It took a few different approaches and even recaptcha wasn't always the best option, but it did help with most of the non-scam traffic.
What value does k8s offer a traditional stack on a single node?
> wasting all the land

The waste exists only because we deem those locations as sacred. Otherwise, burying is the most efficient use of resources.
Movistar+ has a F1 channel
I hit quite a wall of cognitive dissonence when I read their enumeration of a "middle future."

Transparent? Human-time-focused? maintainable? Those properties aren't true of the present, nor have they been true for any large swath of human history that I'm aware of.

What's odd about this is that I agree with the crux of their statement, most futurism is focused on the extremes, and the sheer mundanity of how the "current future" has panned out often isn't well captured. However, I don't find their alternative persuasively different, and it seems to fall prey to exactly what they're criticizing ala utopianism.

I think fundamentally my issue is that a human centric view of the future seems as utopian as anything else they describe, vs a more realistic view to my eyes (and why dystopias resonate with me), driven by the same incentives that have, do, and will for the forseeable future continue to motivate us: Increased growth, rate of return, and efficiency, focused in the areas that most benefit those with incumbent power.

So rather than just saying "they're wrong let's all be pessimists" let me transition this into an open question. How do we realign incentives such that the article's aspirations are more reflective of where we see corps investing their effort? (This probably is a total rathole for even one of their enumerations, ala transportation, but it's where my head is at when I read this.)
For example, recently released IK Multimedia T Racks Tape Machine collection. One instance of the plugin takes about 15% of one core. In a large project this is a lot and you need to think where to use it or use freezing. Then you have a suite of plugins by Acustica that use a variant of dynamic convolution (volterra kernels) to simulate equalizers, compressors or reverbs. Virtual synthesizers like Diva in pristine mode and enabled multi core can also take a lot of resources. You really need to budget what to use where so that it won't break up - which is a skill in itself, that hopefully in the future won't be relevant as much.
Several of the key members have shifted focus but there's still a core IPFS team. But we're still spread quite thin.

We're still paying down years of documentation debt but there has been quite a bit of progress:

* Expanded https://docs.ipfs.io/ with a concepts section.
* Tutorials https://proto.school/#/
* A ton of work on libp2p specs (https://github.com/libp2p/specs/commits/master) along with a full time documentation writer.
In one of my ex-companies I worked with, we had a newbie coder who was just getting fascinated by Kubernetes. Unfortunately, every project this person touched would be left half-way by him and he'd move on to another project.

This company invested around $1 million into a very new Saas product that had a lot of potential. Now, I'm an old school guy. I like systems where I don't touch devops. The cost for such Paas is usually high, but it saves a lot of my time, which I value more than money (and it is valuable, in many cases). I advised the management to use something like AppEngine which is freakin' awesome for such kind of large scale projects.

Unfortunately, this newbie coder was management's pet. They bit the bullet and went on with his advice to use Kubernetes instead. The system randomly failed, they spent tons of time doing devops and microservices on what should have been a simplified monolith. The development time elongated to almost 2 years. By this time, there were competing offerings in the market for much cheaper.

This costed an entire team's morale, which lead to missed deadlines and product launches. This lead to many missed opportunities. For instance, there was a HUGE client we were demo'ing this Saas product. It failed spectacularly on a relatively light load (I've hosted Rails apps on AppEngine that can handle FAR better) and we lost that product and the client.

It was still not too late and I insisted on management identifying the root cause to switch to a managed Paas stack given how resource constrained we were. But this newbie coder turned it into a political situation ('mine vs yours'). I tried various ways to resolve this, but it didn't work out.

As a result, I said 'fuck this, I'm out of here' and I quit. In less than 3 months of my departure, about 10 people quit including one of the senior managers. In about 6 months, the company shrunk from a double digit to single digit company. The company almost went into bankruptcy.

The company lost its $1 million investment. Everyone left. The product development was put on indefinite hold. Finally, this newbie coder left as well. The founders had to rebuild their companies from scratch.

Co-incidentally, I went on to become an AppEngine consultant. I'm able to run unbelievably large monoliths in production, with almost zero downtime for 3 years in a row simply because I chose to avoid devops, and most importantly infrastructure complexity. I pay more, but it easily is worth my ROI. Most of the time, microservices aren't required and we can get away with a simplified monolith. And if you can get away with monoliths, you probably don't need Kubernetes.
"Personally I think it's a bit harsh,"
Wright says, "every fix is different
and they should allow for some
flexibility in their deadline."

As far as I can tell, (1) this is a denial-of-service bug, not a privilege escalation or remote root exploit, i.e. a low-severity bug; (2) it is unlikely any code depends on the infinite loop triggering, meaning this fix doesn't call for great architectural upheval; and (3) the deadline was already extended to 91 days, rather than the usual 90.

If you'd give out deadline extensions for this bug you'd give them out for almost any bug, so you may as well not have deadlines at all.
China Tiananmen square incident, the local military wouldn't get rid of protestors. The government had to get military further away to do it.

With Hong Kong, the government can't do it as the country is too small. The only option is Chinese military. If you say the Chinese military is there, then a massacre is inevitable.
Why was this downvoted. Seriously rare earth is a totally a non issue.
"All enterprise software competes with Excel. All productivity software competes with emailing things to yourself."

https://twitter.com/pavelasamsonov/status/110653418815977881...
It's an overused phrase but there really are two Americas. Can you imagine your life without broadband or cell service? How would you function? That's reality for large swaths of rural America.

Even here in Michigan you can get an hours drive away from Detroit our largest city and experience it. These same people only got electricity in the thirties because of a federal program.

https://en.wikipedia.org/wiki/Rural_Electrification_Act

It's long overdue that we offer rural broadband as part of an infrastructure bill.
ChernobylMaps – Free PDF Maps of Chernobyl and Other Places in Exclusion Zone
Storing your addicted+homeless population in a prison is not only inhumane, it's not effective. And just moves the costs elsewhere. (And often increases them, since incarcerating someone is not cheap. Where will this money come from?) The problem has been swept under a rug, not actually solved.
That I agree. I was just correcting the view of the parent comment, which was wrong on its own.
It's not crazy to give you another PC or two.

Corporate IT can admin the box for corporate training PowerPoint gunk. You get another box to run what you have written, and maybe another to run the development environment. Those don't go on IT's network. You can run a private LAN around the office, not connected to the outside world, in which you break things as you please.

This solution is even good enough for people who are intentionally dealing with malware.
I ride every day in SF and I gave up on Scoot. There are too few of them. A lot of them are out of service. It’s not even worth checking the app.

I would like to see more scooters. There is a shortage of scooters and ebikes in the popular Caltrain <> downtown route.
but exposes to who?
"Beside, the concern about "hard drugs" used recreationally, are the same as with alcohol. "

They are not, though.

Weed (not a hard drug), sure.

But meth, coke and opioids are not very much like alcohol at all really.

I can see legalization of folks chewing on coca leaves maybe, i.e. something like coffee ... but beyond that ... I don't think it's going to work in any regulatory environment.

The 'liberty' it provides the few who can a) handle their stuff and b) have safety nets (i.e. middle and upper class) is not enough to warrant the terrible effects it will have on others.

These things are already a problem in some workplaces: construction, truck driving, because of the intensity of competition etc. - loosening the bounds just creates more problems.

I do think we should decriminalize, but I don't think that our little party at Burning Man is worth the damage that it will wreak in other places.