skysight-inc/HackerNews huggingface dataset:
> Omicron has an 87% lower fatality rate.

That is likely due to so many people being vaccinated or recovered.

If you dropped Omicron on the world population in the middle of 2019 I strongly doubt it would be any more mild.

> A lot of the deaths occurring right now are still from patients that were infected by the Delta variant weeks ago.

I guess natural immunity isn't as consistent as vaccination though (which produces exactly zero shock amongst the world's virologists and epidemiologists) and also suggests that Omicron isn't intrinsically mild at all.
Perhaps the most angering part is that both Google and Apple will greenwash the issue away as during product launches (which is where all attention is) where they will emphasize how very sustainable they are.

That's the tactic to get away with piss poor aftercare. It's time for regulation and I mean harsh regulation. A product should be supported for as long as the reasonable duration of its hardware life cycle.

I have 7 year old smartphones that still work just fine. So you're going to be delivering support for a long time, even up to a decade.

Unwilling to do it or technical excuses? No problem. Refund the phone. I have a working paid device, you broke it. It's not my problem that your security model is like Swiss cheese. It's your defect, not mine.

Battery replacements are to be made dead simple as it always was before. This is actually a key reason why people needlessly buy a new phone.

All reasonable repairs should be possible to be carried out anywhere, including by the customer themself. You're going to document the process and supply the components.

You may think of this as an angry extreme rant, but I'm serious. The point is that the pain should be put where it belongs. When you make a crappy product, the producer should feel it, not the consumer. This creates the incentive for the producer to create a product that doesn't break down so easily. Likewise, producers are a much larger factor in sustainability compared to a consumer, so they should drive it.

Speaking of security, it's laughable that in a digital society, we accept that everything requires forever frequent updates otherwise its insecure. What does that tell you about the foundation of our computing? It's garbage. Yes, I know, "programmers produce bugs", "hackers are creative", but that's an explanation, not an excuse.
Nobody gives it to them. 5-year-olds have sufficient intelligence and dexterity to get into all kinds of things, but don't necessarily know not to eat/drink/play with it, etc.
The number doesn't mean anything really, give me the access control and we can have a thousands times more in a week.
But their traffic lights are red, being the traditional "STOP", or caution, etc...why would that be chosen to be applied to something increasing?

And apparently chart-decreasing is blue, again opposite correlation to use in traffic lights, meaning "go"
I'm no fan of NFT (non-fungible tokens) crypto and do not now, never have, never intend to own any, but, and maybe part of Web3, am guessing at some useful purpose -- a convenient, low overhead, way to move many small amounts of money to pay for Internet usage.

E.g., Sam runs a Web site and wants to charge each user some small amount, say, $0.001 up to $0.10, including users in foreign countries, for each visit. Sam is eager to let his users pay with some major NFT.

Joe wants to use Sam's site and other sites with such a charging technique so buys in whatever fiat currency his country uses, say, $10.00 worth of some NFT. Then Joe uses Sam's site and pays with some NFT money. That NFT tokens can be divided into many parts is crucial here.

Once a day Sam converts all his NFT revenue to dollars (or whatever fiat currency is used in his country).

So, net, the money flow is from Joe's fiat money to $10.00 WORTH of some NFT to Sam's revenue in NFT to Sam's revenue in his fiat money.

Point 1: The NFT is held by Joe and Sam for only a short time and is used only as a convenient way to move many small amounts of money.

Point 2: Neither Joe nor Sam cares what each whole token of the NFT is worth.

Point 3: Investors who want to speculate on the long term value of a NFT tokens have risks from "unknown unknowns".

Point 4: If each of 1 billion people do what Joe does, hold nearly all that NFT, and on average hold only $10.00 worth, then we have an estimate of the maximum the investors can make.
Or magically find a way to stop tracking that metric.
I so wish these articles would give a 101 on how to make an old-school, decentralized website. So many of us want that, but just have no idea where to begin anymore (and I made websites in the late 90s....) Love these articles, tho. The more the better.
Gaming console computer technology was very different to PC. The last unique one was PS3 Cell (but also RSX by Nvidia). Now they are just PC or smartphone based.
SoundCloud experimented with something called Ask years ago. I was one of the users they selected to answer spoken questions from the public with my voice.

https://blog.soundcloud.com/2011/05/16/this-week-in-tumblr-5...
Scroll down to Wednesday. Users could have their own branded domain ala Bandcamp or Tumblr, mine was http://ask.hammyhavoc.com. Quite a few celebs of that moment got on board with it.

People hit an 'Ask' button in their browser, it uploaded their voice, I got it, I responded with mine, it got shared out on Twitter, and tagged anyone involved, which led to more interactions. Was pretty cool. Similar to Google's Cameo concept that they just killed off. Had a fancy UX for the era.

The questions and answers got archived on the subdomain and were accessed via SoundCloud's API.
I'm waiting for Web 3.11 for Workgroups. At least it will be useful for something.
> Not everything is a conspiracy. Sometimes it’s just useful to have a word to describe a particular architecture. In this particular case, “monolith” isn’t even disparaging, so if Big Microservices we’re trying to disparage monolithic architectures, why wouldn’t they use a term with a negative connotation?

This isn't the reality on the ground. Where I currently work, "Monolith" is absolutely used as a pejorative by those advocating for microservices.
Where in the South are you living, Marseille?
I know what a straw man is, but you just naming the term doesn't constitute an argument. Maybe a more clever person than myself could have intuited what you believed was an example of one, but I couldn't.

Russell's teapot is a new one to me. It seems you're position (correct me if I've misunderstood, or don't since you don't seem interested in the conversation anymore) that since we don't have definitive proof that we can't trust these third parties, it's wrong to distrust them. I'm too paranoid to buy that. If I can't verify, then I don't trust. Good luck with your better things.
> Never use SELECT * within the context of an application, as column additions or removals can break the app.

Use a dictionary cursor, or some other method to convert whatever is returned into a hashmap like so: https://dev.mysql.com/doc/connector-python/en/connector-pyth...
Alan Kay defined object-orientated programming as having messaging, state hiding, and late binding. I think the ship has sailed on the last one, but the first two properties hold true for at least all the object orientated languages I'm aware of.

A closure lacks messaging by default, so it's not an object. You can certainly make an object from a closure, and in an object orientated language a closure may be itself represented by an object; but responding to messages is not an inherent property of a closure.

It's not useful to say that all languages have all features; the line has to be drawn somewhere. Being able to theoretically write an object system for a language doesn't make the language object orientated.
Companies whose bottom lines are affected by GDPR are screaming that it's too difficult to understand and apply. Many HackerNews, especially for some reason North American ones, are parroting what they hear in this echo chamber without giving it a glimpse of a thought.

I think we underestimate the power of PR way too often.

Last I've read GDPR itself it's been way clearer than any of the Terms of Service written by the very same companies who complain that GDPR is too incomprehensible.
I'd love to move on, but they're filling up the fucking hospitals.

I have 80 year old parents who need medical care and can't get it right now.
I was accepting to your criticism and then exploring it from a different angle. Your comment is needlessly hostile, it's not going to make me more receptive to your opinion.

Perhaps write from a place with less "preconceived conclusions" about the other commenters motives next time.
I frequently use foobar2000 on Linux just because of the Discogs Tagger plugin:
https://www.foobar2000.org/components/view/foo_discogs
The other great feature is a very nice spectrogram which helps me to easily spot tracks which were converted from a lossy format to a lossless one.
I wish the source code was open sourced so that a Linux port could be made without the need to run it via Wine.
>So that CEO bonus costs ~$0.13 per salad sold. [...] but that seems like a lot. I doubt the CEO's value is irreplaceable.

The flaw in this analysis is that you think chipotle only sells salads. They obviously don't. At least based off my experience most people order burritos/bowls, not salads.

Here's my analysis: per wikipedia, chipotle has revenue of $5.586 billion in 2019. If we divide CEO's salary by that, we arrive at 0.68 cents per dollar of revenue. According to wikipedia, chipotle doesn't franchise, so we can assume that's all food revenue. Assuming a salad that costs $10, that's 6.8 cents of CEO comp per salad sold.
There weren't treatable diseases in medieval times, even if you were king. You either recovered on your own, or you died.
Red is almost uniformly a more-left/pro-labor political color outside the U.S.
I’m going to be contrarian and honestly say I have no issue with Gmail’s spam filter. Works really well for me.
pkexec is a setuid binary because pkexec is just a sudo-alike that uses polkit for authorization.

> a scheme of having a privileged service that acts on the requests of unprivileged processes

That is precisely what polkit is!
> A governments that governs inconsistently is not necessarily illegitimate.

Fair enough, I suppose legitimacy is in the eyes of the beholder, which happens to be itself.
You can have a look at https://github.com/sonyxperiadev/kernel
They're paying for it.
But they weren't directed to accommodate those use cases, even though those people existed.
Once per 3 years?!
The Polygons of Éric's Chahi Another World
If you'd like to grow tree collard / tree kale varieties yourself, check out Project Tree Collard:

https://www.projecttreecollard.org/

They grow great in California (and places with a similar climate), producing harvestable leaves year round.
Write barriers in the Go garbage collector
>In Japan, the country where the first emoji sets originated, red is traditionally used to represent increases in the value of a stock.

I don't see it necessary to make a correlation to a stop-light's color coding. You could also argue why anything hot is colored red while cool is supposedly blue.
Just because a device stops receiving security updates does not automatically mean its instantly unsafe to use. Unless you are a high profile target or a serious exploit comes out you can probably safely still use that device for quite awhile. If you want to be confident in your security then that might require some extra steps on your part monitoring what exploits are being released but with a hugely popular device like the Pixel I doubt that is very difficult. Tons of people are going to be using them regardless without any thought to security.

That being said this whole 3 years of security updates is of course totally stupid and we deserve more. And manufacturers look to be realizing this. But if the rest of the phone hardware wise is also on a similar obsolescence cycle then is software updates the real problem here?

Our devices are becoming more and more disposable in many ways and we need to target the root of the problem - if you can easily replace your battery and your 5 year old phone still does everything you need then there will be much more consumer demand in turn for longer software update support.
Concave Hulls in JTS
1) "knowledge proof" : proving that you have some information . E.g. suppose I claim that a graph can be colored with only 3 colors. I can prove that I know a coloring for the graph with 3 colors, by presenting you with that graph.

2) "zero knowledge" : Suppose I want to prove to you (or at least, give you very strong evidence) that I know a 3-coloring for the graph, but I don't want to give you any information about how to color the graph with 3 colors.

This can be done in a way where I first randomly permute the 3 colors, and then commit to a particular coloring without showing you anything about it (e.g. I give each node on the graph a random salt, and show you the hash of (the color and the salt appended) for each node ), and ask you to pick any two nodes of the graph. I reveal the color and salt for those two nodes, and you can check that they make the hash I said they did. If the two nodes are connected by an edge, then the colors I give have to be different (if they are the same then my proof is invalid and you shouldn't believe my claim that I have a coloring of the graph with 3 colors.)

By repeating this process many times (each time I randomly permute the colors/names-of-the-colors, and make a new commitment about each node), and each time you choose a random pair of (adjacent) vertices, then, if I didn't actually have a coloring of it with 3 colors, there's a high chance you would eventually find that the pairs you asked me to reveal, have the same color. So, if we keep doing this, and I'm telling the truth, eventually you should have strong evidence that I have a coloring for it, but without you getting any information about that coloring (other than that it is one) (because by permuting the colors each time, the only info you get about the nodes you asked about, is that the colors are different, which is already implied by it being a coloring.)

So, that would be a zero knowledge proof that I know how to color that graph using only 3 colors, with no 2 nodes having the same color.

(of course, the thing with coloring graphs is just an example, one which is relatively easy to give a protocol for.)

3) "non-interactive" : accomplishing the same sort of thing, except instead of us sending many messages back and forth like in what I described above, instead, I just do one computation (using the knowledge I have), and then I give you the output of that computation, and you can check that with some algorithm, and the algorithm says "yep" if I gave you a good output, and "nope" if I gave you a bad output, and, if I had the info I claim to have and used it for the input to my computation, then you will always get the result "yep", while if I don't have the info I claim to have, then the probability that I succeed in giving you a good output, one which would make your program say "yep", is negligible.

__

Hopefully that helps make the idea more clear?

You might be wondering why this idea is applicable to cryptocurrency stuff?

A number of reasons. Being able to prove that you have some information that satisfies a given property, without revealing the information, is fairly powerful.
Muscle is good to a point, it is very easy in our high calorie high protein diet to put on way too much muscle. It is little better than fat, especially with the way heavy weightlifting distributes it.
Not good enough, as 'select *' can in any event introduce ambiguity that is fatal to query processing.
> It didn't "just work" in a lot of cases, for any sane definition of that phrase.

I was thinking about this the other day, and how Apple's departure from skeuomorphism made a lot of "just works" analogies a lot more dilute. I've never been particularly fond of Apple's design chops, be it from 2008 or 2018, but there's something to be said about how digital Corinthian leather and wood textures makes a person perceive a device. It also made their design philosophy fairly straightforward: if you're designing a digital bookshelf, it should work similarly to a physical one. There was no ambiguous frosted-glass layer of UI, nor "lickable" candy buttons littering your experience. It was just... functional. Modern Apple seems pretty disinterested in that stuff though. Relative to the rest of the tech industry, they're the same clowns in a different circus.
I think most people are salty about your comment because they fail to see the subtle difference between:

1) "Everyday you should ship something"
2) "At the end of each day you should be able to tell your line manager in a clear and concise way exactly what you did; if you can't you've done nothing."

2) does not mean ship code: you could have spent 12 hours thinking and reading code. But if you can explain i.e provide a daily update, then you have actually done something, and not spent a day on slack sending memes.

i've had days where I did nothing but read code trying to understand a bug, and then my whole contribution was 1 line of config or 2 lines of code. But I have a clear achievement: I understood an area of the code much better and i have a fix.

Having daily updates to your manager also forces you to not slack and work on the most important problems: otherwise you might be tempted to work on sth fun but not mission critical.

At the end of the day, people should do as they wish.
> long chain inulin and resistant starch

Any references to suggest on these?
I don’t see how anyone conceivably can compare getting nearly 8 billion individuals to follow COVID orders where failure only requires 1 individual leaking the virus compared to a select few people who can launch nukes who all have to agree to go ahead with it and use that comparison to try to make a point.
In the US today a bushel of wheat (60 pounds) is worth $7.50 and contains about a month's worth of calories, for about half an hour worth of the average American's labour. Chinese factories produce widgets for pennies.

Under that definiton either both the 24th and the 22nd centuries are post-scarcity or neither are.

Trekonomics writer Manu Saadia has a much better definition:

"Post-scarcity is not so much a matter of material wealth or natural bounty, but an organizational option for society".

https://en.wikipedia.org/wiki/Trekonomics
You are right. Those who got "natural immunity" from Delta had no protection from Omicron. But how Omicron is structured, they get natural immunity from Delta and many other variants.

https://youtu.be/PYLbJ0H8zdc
Neil Young tells Spotify it can’t have both him and Joe Rogan anymore
Myocarditis Cases Reported After mRNA Vaccination, December 2020 to August 2021
You're proving his point, there are also people with good/bad intentions working in "web2" and everywhere for that matter.

Don't criticize the tech, criticize the individual bad actors, like you did with Theranos.

One of the main talking points "web3" critics yell is "scams!", like they don't exist elsewhere.

If you do want to criticize the tech, leave the moral crusade out of it and say technically what is wrong with it, so we can have a technical debate about the feature in question.
Well, Theranos was a fork of existing, well-understood blood testing methodology. It was a house of cards built out of lies and falsehoods in order to enrich the founder and associates.

Exactly like crypto often is.
Strengthening identification is a non-starter until the US has something similar to the GDPR, and the surveillance industry has been massively reigned in. Right now it's a feature that the average person balks when asked for personal identifiers like social security number, otherwise things like grocery store discount cards would insist on positive identification. If we had a universal smartcard for ID, imagine having to swipe it for every single fucking transaction.
I don’t disagree, there is of course a body of knowledge, which rapid churn implies that we are accreting that at a good pace.

And yet, despite all this, no better treatments that amphetamines have been found for so many cognitive disorders.

100 years old drug, and to prescribe which you don’t even need to know how much the brain weighs.

What is the use to the laity of all this research, if half of the time the answer is stimulants, the other have is SSRI?

I think we will be seeing the most promising area in sleep, because it’s so underserved and you can collect a lot relevant data inexpensively and un-intrusively.
"Writing a web browser for today's web appears to be a technological challenge comparable to a level 5 self-driving car."

Only when the "constraints" are that the browser must support all "standards" produced by some committee where most if not all memebers are employees of the few browser vendors or other "tech" companies heavily invested in the web. Perhaps that is what is meant by "today's web".

I use a netcat and similar TCP clients and a text-only browser on today's web and this works quite well for mine own purposes. Non-commercial use. Basic tasks like sending GET and POST requests, downloading pages and other resources and reading them. Using the web as an information source. I would be willing to bet these programs are "more secure" than the "modern web browser". They are certainly less complex.
Ask HN: How much did your bonuses decline in value?
Most people here work in big tech so I wonder if anyone is willing to share how much the recent sharp decline in tech stocks has affected their TC.

I am interested in % but $ is also aceptable.
And then there's Korea, where every party is re-created every few years. In the past decades liberals tried green, yellow, and (currently) blue. Conservatives had blue, red, pink, and now back to red.
> I think annotating microversions would get tiresome fast. I think the right way to think of this is that you put in a single version number like 1, and then only ever change that if you need to do backwards-compatible changes that cannot be handled by clever hacks in the runtime.

Thanks good idea, I just changed this to remove the microversions. If we use SemVer, then before `1`, we'd hold versions compatible to the 0.X, and then to the X.
The shuttle had plenty of military missions, and most are still classified.

No, we never got the Vandenberg polar launches we were promised.

And I don't think anyone anticipated just how quickly miniaturization and automation were going to advance when it was designed in the 70's or even as missions began in the 80's.

Even autopilot was a controversial cutting edge technology that was excluded because of the focus on human centered missions.

But back to military- it's not a coincidence that Hubble fit so perfectly in the shuttle cargo bay.

(Hubble being a spare keyhole spy satellite body, with borrowed mirror fab tech.)

But it would be interesting to know just what else the military had in mind, besides their not-so-secret ambitions for militarized manned space stations.
It’s pretty straightforward. In a monolith everything is in the same memory space, so the payment system credentials and routines are available to the whole monolith. In a microservice architecture, one service can’t access the memory or routines of other services.
Within 30 seconds, more like 15. No problem.
But we've got far more developers now, and by large, we aren't producing more capable software than we did 20 years ago. It's gotten very complex, but that is by large just a failure to keep things simple.

Spotify is slower to launch on my Ryzen 3900X than my operating system, and lacks many of the basic features that WinAmp had in 1998. Now you're thinking "Aha! But WinAmp just played mp3s, it didn't stream over the internet!", Yes it could. It was also by large developed by one guy, over the course of a couple of months.

I don't know where this superior developer productivity is going, but it sure doesn't seem to be producing particularly spectacular results.