skysight-inc/HackerNews huggingface dataset:
And who would that royal "we" be?

The "we" that doesn't have to pay rent?

The "we" for whom food is free?

The "we" whose student loans were paid off by someone?

The "we" that doesn't know that being homeless is, essentially, illegal?

The "we" that doesn't realize that there is no alternative to inclusion in the system of institutions?

Seriously, what do you think "exclusion" here is. The only way out is 6 feet under, otherwise you are still a part of the system, and the "struggle" is an inherent part of it.

This is where the socialists and libertarians agree, by the way. Except the Libertarians imagine there's a way to be sort of outside the system (while, somehow, still getting the benefits), and the Socialists aim to improve the system instead. Regardless, either would agree that the struggle of existing within the system is an artificial, and purposeful effect of the way the system was structured.
I wonder what is percentage? Is it still a mainframe shop? Last time I heard abd it failed is to become a consultancy firm with Pwc. What is ibm now?
Russian cyber criminals and other rich people often vacation globally. I didn’t check the defendant’s facebooks but I would be surprised if they have never visited the US.
Does this support the Dependanbot dashboard overview like on Github?
India's fanbase instantly reduced to zero.
Well, yes, you can do that, but Intel's Software Developer's Manuals are terribly written. They are good as references for details, but only after you understand the grand picture. Learning something new from them is quite a torturous process.
Promoted.ai (YC W21) Is Hiring an Apache Flink Expert
I've been looking for software that does this myself, but I don't think it exists.

There used to be a project, https://bazil.org/, that promised to do it. The website is still up, but it has not been updated in years.

The existing tool closest to what I envision is git-annex. It tracks what files live where, and you can sync single files or as much content as will fit on the local harddrive with a few commands. There is also git-annex-assistant for a more dropbox-like experience, although I haven't used it myself.
Darwin's lost microscope: the auction of a history-making 'box of brass'
A microservice runs as some (somewhat) privileged user, you may want some auth. Can everyone internally create sales tickets? Or can everyone just query them? If a team provides a library to run, and you run it, you still only run as whatever user you have access to.

Monitoring: it's easier to look at a stack trace, including some other team's external library, than a HTTP error code 500.

Deployment is certainly easier when you're just shipping code and a build. You don't have to faff around with the previous instance running, maybe having some active connections/transactions/whatever, needing to launch a new one. Maybe it's not hard overall, but less fun.
I wonder why no one ever talks about architectures in the middle between those two - modular monoliths.

The point in time where you're splitting your codebase up in modules (or maybe are a proponent of hexagonal architecture and have designed it that way from the beginning), leading to being able to put functionality behind feature flags. That way, you can still run it either as a single instance monolith, or a set of horizontally scaled instances with a few particular feature flags enabled (e.g. multiple web API instances) and maybe some others as vertically scaled monoliths (e.g. scheduled report instance).

I wrote more about that approach on my blog, as one of the first articles, "Moduliths: because we need to scale, but we also cannot afford microservices": https://blog.kronis.dev/articles/modulith-because-we-need-to...

In my eyes, the good part is that you can work with one codebase and do refactoring easily across all of it, have better scalability than just a monolith without all of the ops complexity from the outset, while also not having to worry as much about shared code, or perhaps approach the issue gently, by being able to extract code packages at first.

The only serious negatives is that this approach is still more limited than microservices, for example, compilation times in static languages would suffer and depending on how big your project is, there will just be a bit of overhead everywhere, and not every framework supports that approach easily.
> refuse to "act my age".

If you plan on having biological kids, that is not so easy. The risk of a pregnancy complications past 30yo rises a lot.
Planing the life around a timeframe where you get both financial stability and the youthful body to carry a child is extremely important, specially for woman.
I am on MacOS. The miniature in the desktop icon of the file shows "Hello World", but opening the file shows "Hello Apple".
As a child, I always want to play my sega mega drive in my house with my friends playing their mega drives in their house. When I was later introduced to the internet it just made sense to me.

Think about what you think the future would be like or how you would like it to be. Then see who is working on that right now.

For me, here's some things I think will be big in the future:

* smart screens - windows, mirrors showing information like weather and having 'Alexa' built into them.

* VR / metaverse(s)

* Bitcoin - it being the best proof of _work_ network
The answer is "both." This is very funny, very dumb, and how it's done, at the same time.
I think you're reaching too much trying to find some overarching patterns. The internet is distinctly not the cloud.
Haha, no that was missing. I mean all the features/loggers that were used in the project mapped one to one.
Bing is down in some regions. Is it also related to this outage?
Nope, that logo goes to https://help.sunsama.com/docs
The setup is not that relevant, what is relevant is how long it takes to get a match. And chess.com is much quicker at that.
I think we should be discouraging that kind of self-censorship for all but the worst words. Not only do people start to use it for ridiculous political posturing (e.g. "wmen" or "gmers") but it just makes what you're write ever so slightly harder to understand. And for what benefit?
So long as they keep the API available for apps like Apollo then I'm fine. Honestly that's the only way I browse Reddit now, but I can't help but feel weird when the only way to enjoy a site is to use something else entirely to view its content.
I have some major gripes with Xcode as it is now (though otherwise I find it to be quite good):

1. Startup time is too long. Often I find myself double clicking a code file in Finder to preview it only to be greeted with jumping Xcode icon. Riiiight, here we goooo, boss. Just 2-3 seconds, boss. It should open the file straight away, and then lazily load the rest of its frameworks if necessary.

2. Code editor is very bad with large files. Be it large JSON data, or C++ files from Unity's code generator, navigating and editing those is painful. Every typed symbol will incur a delay, every switch to different place in that file is noticeable too. This is by far the worst of all other code editors I used, but I get it, few people have to work with huge amount of text.

3. pbxproj format for project. Ever worked in a team where several people adding and removing files in their commits? Happy project merging then. Or rather, happy searching for a tool to auto-regenerate the project. This format has to go.
Are these threads necessary? especially when they're so common now. Don't want HN to turn into is-it-down.
> However, I still wouldn’t recommend microservices to a new team / org starting from scratch. IMHO microservices only make sense when the system grows so vast it cannot be understood in its entirety by a single person.

I wouldn't go that far. The problem is prescribing a stock design solution to every problem without even considering the problem domain or what benefits it will bring.

There are domains where this style of programming is an absolute benefit, even at smaller scales, and it's really nothing new either. A lot of the patterns in microservice design rhyme rather well with what Erlang has done for decades.
DevOps is a sad story both for devs and for ops. It was supposed to treat operations as a SW problem thus take away the toll and draw devs in. In reality for most places it either means that devs also do pipelines and operations or that operations were rebranded and are using "DevOps" tooling to do operations.
> 53 comments

Maybe, just maybe, it is an omen? ;-)
So is a kitchen knife, or a power drill, or a chainsaw, all of which can be bought in any hardware store or supermarket without special documents. There is a certain measure of simply letting people take personal risks that should be plausible and allowed in adult life. Antibiotics I can understand, because the resistance one creates within themself from improper use can affect others very badly. Likewise for opiods, which can cause people to lose personal control or coherence in situations such as driving down a highway at 100+ km per hour. For many other medications, the damage will be personal, and the choice should be as well. Your argument falls flat in the face of so many other things that you would also have to ban without written permission if prednisone or birth control pills were one of your baselines for prohibiting personal risk. Also, yes I know that prednisone is dangerous. I've been using it intermittently for a long time. I don't think anyone should have the right to treat me like a child on something so easy to learn responsibly.
Can you elaborate on the vice part? My mental image of Japan in that period is pretty conformist. Which kind of vice was rampant?
That's a fallicy. You've optimized for one use case, but you've made everything else more complicated as a consequence.

Deploying a single monolith is faster than deploying 10 microservices, especially if you find yourself in the model where your microservices share code, you've ended up with a distributed monolith instead of microservices.
That's probably fair enough in many cases, but it should be doable to make the display togglable; and some handwriting is very enjoyable.
Twitter really depends on who you follow. I've no idea how I got to the point where I have an interesting feed and attempts to follow the same process on Instagram have so far failed.
Maybe it's that brain worm that I got from staring at too much assembly, but I actually find that part of the Intel manuals to be quite approachable.

Even to get a general overview, the introduction section I linked seems fine?
So since a 10-sigma event could result in a 200-yr old person, there is no real limit?

There is no hard limit, but clearly the age distribution drops suddenly (for developed countries) at 70.

There are a bunch of single points of failure in our body -- the heart, the liver, the spine, the major blood vessels, the trachea, etc.

There's only so many 9's that those components are built to last for, and they ALL have to work!

FYI: I agree that "Leading demographers ... 122 years" is an incorrect statement.
> Unvaccinated people under the age of 60 certainly do not put any significant pressure on ICUs

However:

"Ohio Gov. Mike DeWine a day earlier warned of a “startling” rise in Covid hospitalizations among young people."

https://www.cnbc.com/2021/09/22/unvaccinated-covid-patients-...

"I’m treating more and more young, unvaccinated people in ICU"

https://metro.co.uk/2021/11/10/most-covid-patients-i-treat-i...

"We're seeing younger people, unvaccinated, who take up around 75 percent of the intensive care beds and that's not just here, that's nationally."

https://www.bbc.co.uk/news/uk-england-gloucestershire-594054...

"90% were not fully vaccinated, with most tending to be on average six years younger than patients admitted to ICU who are fully vaccinated"

https://www.bartshealth.nhs.uk/news/almost-90-of-patients-ad...

"Young people in ICU with Covid almost exclusively unvaccinated and some are dying"

https://www.independent.ie/irish-news/news/young-people-in-i...

Why do you call this "a blatant lie and demonizes people" ? - that's strong language, and would need some justification.

"blatant" means "very obvious", so what is very obvious about it?

What I'm very obviously seeing, is not what you claim to be very obviously seeing.
Sounds a bit like a Chinese room: https://en.wikipedia.org/wiki/Chinese_room

> Suppose that artificial intelligence research has succeeded in constructing a computer that behaves as if it understands Chinese. It takes Chinese characters as input and, by following the instructions of a computer program, produces other Chinese characters, which it presents as output. Suppose, says Searle, that this computer performs its task so convincingly that it comfortably passes the Turing test: it convinces a human Chinese speaker that the program is itself a live Chinese speaker.

> Searle then supposes that he is in a closed room and has a book with an English version of the computer program, along with sufficient papers, pencils, erasers, and filing cabinets. Searle could receive Chinese characters through a slot in the door, process them according to the program's instructions, and produce Chinese characters as output. If the computer had passed the Turing test this way, it follows, says Searle, that he would do so as well, simply by running the program manually.
Anyone on an iOS device using Reddit that doesn't have this application is missing out.

I've said it before, but old.reddit.com and Apollo are the only methods I use to browse the site. If either dies or the API becomes private/non-existent then I'm out.
Been a while Ricardo, I still remember that old WebAudio talk with the guitar. Thanks a lot for sharing MDX here, it looks quite neat indeed.

I think that the main difference between what I was showing and MDX is that MDX is the JS ecosystem, and you basically get JavaScript only. In those Pollen/Racket based setup, you get languages beyond Pollen and Racket. For example, I can write my own language specialised to describe TTRPG adventures. It doesn't need to look like Racket, or behave like Racket. It can be a whole new language. And I can still plug it into my blog because Racket allows you to mix and match Racket-based languages.

With MDX, from my very brief read of their website, you'll create a JSX components and insert it inside a Markdown document. You're limited to Markdown documents and JSX components, which let's be honest is probably enough for most cases if not all of them.

In the end it is about what the blog authors want to use. There is no point in using something one doesn't like, that will make writing a chore. If I was doing a JS-based blog, I'd certainly would look towards using MDX.
It really doesn’t matter what it ‘is’ or if it makes sense to speak of things in moral categories. There are plenty of ‘tools’ that are/should be restricted, from guns to Tucker Carlson.

It can obviously have some effect on the so-called ‘real world’, or people wouldn’t pour money into developing & using it. It would be a unique feat to be powerful with no chance of any of the effects being harmful.

From there, it’s just arithmetics: what harms and benefits do we expect with what probabilities, and how does this change depending on the distribution scheme?
"These anti-suicide fans might be the answer to a crisis in Kota" - https://www.deccanchronicle.com/lifestyle/viral-and-trending...

~2% of suicides in India are from fans. You probably go higher looking at just the cities. "Ligature material in hanging deaths: The neglected area in forensic examination" - https://www.sciencedirect.com/science/article/pii/S2090536X1...

> institute in India removes fans

The current title is pretty clickbait, they are changing from ceiling fans to wall mounted fans. Not removing all fans. Suicide by ceiling fans is an acknowledged problem. This prison is developing anti-suicide fan tech as well - https://www.abc.net.au/news/2021-03-17/ceiling-fans-removed-...

In the ultimate irony, covid which is causing this is better protected against with ceiling fans than wall mounted fans.
> It's a lot of code, but it's not a lot of logic.

The exact reason why I compare microservices to OOP ;-)
New York City bans natural gas in new buildings
> but use some assembly tricks to ensure there is always valid memory available after the end of the buffer

Isn't rounding up your buffer's size an allocation technique rather than "as assembly trick"?
This is somewhat intended, though. Also, for intercepting the logs you need _a lot_ more access than for an unauthenticated RCE and that database might not actually be accessible from the outside.

It's not cool, but far less severe than the original issue.
https://archive.md/tNkyV
It’s funny, csv files are so common and yet many mainstream languages don’t even attempt a decent parser baked in. I think dotnet has 3-4 different ones and as I recall they’re all pretty slow.
Thank you. I had previously re as the citizenlab report, but didn’t realise that Indians were targeted as well.
I am a Russian citizen, so no problem here, but funnily, I have no idea what Russian rules for crossing the border are now because last time I was abroad was in 2019. But judging by my friends' posts on social media, crossing in an out of Russia by plane is a non-issue, it's crossing into other countries that's complicated.

But then even if you are admitted into the EU, you would be considered non-vaccinated for any place that requires a proof of vaccination, and from what I heard there are many such places.
And we all know that salary and title are the true measure for one's happiness and fulfillment.
Thank you for this as this is exactly how its implemented in a recent project of mine.

I didn't want to put unneeded information in the first post but here i have some space ;)

What I ended up doing was:

- two sqs queues, one for processing one for failures after 3 tries

- the go backend reads from its queue and the message contains a json object with all the information needed for pdf generation

- the backend posts the file back to the "internal api" of the application, which saves it in s3 and also sets processing to true which means the user can go and download it.

This results in:

- my pdf generated the way i want it (sorry i dont actually make stardust)

- the queues are only reachable through the assosiated iam roles

- if a job failes it will be added to the failed queue, which sends me an email

- if i recieve an email by the failed queue, 90% of the time i have found another edge case

- since the message already contains everything that i need to build the pdf, my edge case has just defined itself

- for the postback i supply an api token that is only valid for that one file

All this means my client has total flexibility in deployment.
I really can’t tell how serious you are. I’m too aware that what you describe often is exactly how it works in practice. It’s just that very few admit it in public. :)
>How is 122 ANYTHING other than a random number?

It is a random number. They could have lived to 122. But 0 have been shown to live to 150, and we're most certain 0 lived to 200 or 500.

There being a natural limit doesn't mean that "largest age found" is the limit. It just means that there's a natural (e.g. cell based) process that kills people with increasing certainty as they age, with a measured cap around 120 years or so.

Whether that can tomorrow or historically been found to be 130 or 150 in some random human that gets/got to be ultra-old doesn't mean it's not statistically more than appplicable to the 99.99% percentile of humans, or that there's no "increasing natural death certainty" with a limit towards 100% as people age.

>Just because all of your data points show the same thing, doesn't make that thing true.

It surely makes the thing statistically true (this is what happens most commonly), and points to processes and factors making it so.

>Oh, your set is all human lives ever recorded? Meh... Doesn't mean a thing. Your set is too small.

Huh? "Too small" compared to what? One that would include humans in prehistory or pre-modern-registries that might have lived more? (And we do know that they lived less too, even if they're not recorded, from the bodies/bones/etc. records we have).

Rather, the dataset is huge, and (after 20th century or so, where globally registry records are kept) close to exhaustive. Statistically if anything it's much more than required.

>To me, it is self-evident that there is no natural limit to human lifespan.

Sounds more like a wish than a self-evident truth.

>If anything, the existence of a natural limit should require proof, not the lack of it.

People die, lifetimes of billions have been shown to be capped, both in nature (pre-historical living) and civilization (modern life, diet, etc).

That points to a natural limit. And there are similar numbers/caps for all primates and mammals anyway. That's the very definition to a natural limit.

That doesn't mean an absolute limit, or a specific hard number (like "122") just a limit based on current evolution. E.g. if we modify humans genetically or whatever we might be able to overcome it. But as it is, there absolutely are natural processes towards limiting life span at play and there is a clear cap measured. That's not even contestable.
The dynasty of Han collapsed and was divided into three kingdoms. After many years of war, one of them finally defeats the other two and it becomes united. This pattern is replayed again and again in the history, and possibly in the future.
No, what you’ve listed are all reasons for shorter lifespans.

There are other reasons for longer lifespans, but you’re implicitly saying all of them combined are not enough to counter the reasons you give.

Now, I’m not certain either way about the broader social impacts — I personally very much want to live longer, and yet I am also aware that my personal interests are not always aligned with group interests, e.g. tragedy of commons, Nash equilibrium, prisoners’ dilemma — but it is extremely unlikely that any negative consequences are perfectly balanced to positives either personally or collectively, so I am absolutely certain that the one thing we should not do is leave lifespan as is.
I like the part where the blog mentioned certain malloc() library will break under ASLR (i.e., jemalloc, PartitionAlloc).

Arena methodology of malloc() design should have been implemented with ALSR enabled.
Caveat: I am really not qualified to discuss the nuances (because I have never used microservices so the little I know is based on reading a bit on those here and on other online forums).

"Single writer multiple readers", yes, this is what I would probably use, but yet again, wasn't the "promise" of Microservices being able to work in total isolation?

If I have one table (e.g. "Customer") which is written by one specific microservice and read by a dozen or more... what happens when I decide that I have to change the schema because the current representation of "Zip Code" is not adequate anymore because, I dunno, we started dealing with UK customers now?

Lo and behold, I have to change code in 13 Microservices - the one actually writing to it, and the 12 more that only need to get the data to show or print or convert to JSON or whatever... ¯\_(ツ)_/¯
I think you are right, and I think health officials and politicians basically want society’s immune system to be on high alert for a long time.

I have no idea scientifically how good an idea that is. Second shots have a higher risk of myocardiatis, what about third, fourth, fifth? At what point can you let go and rely on T cell immunity?
Downvoters don't realize that all fiat currencies go to zero in less than 100 years. This knowledge should be more common.
Scientists unveil drug discovery tool to screen more than 11B compounds
It’s impossible to understand the future with 100% certainty, ergo illogical.
Bank of England: UK interest rates hiked to 0.25% to combat surge in inflation
Thanks! Updated accordingly.
Identity Theft Is Not a Joke, Jim
Bootstrap5 Tutorials