skysight-inc/HackerNews huggingface dataset:
> In general, politicians poll their constituents and their platform changes to mirror what their constituents want in order to continue being re-elected

I find that in the UK the right-wing media tell everybody what they want, the BBC then takes that as rote and amplifies it. The officials then mirror that.

Take the immigration issue as a case in point to demonstrate (I am not going to argue the rights and wrongs of immigration itself so don't bother commenting, this is a meta-comment). The current PM talked about reducing immigration constantly as Home Secretary (mirroring the Daily Mail). As PM she has done the same. Recently a story came out that she tried to suppress reports that immigration was a benefit to the economy on multiple occasions. A recent report said that immigrants on average were more of a benefit to the economy than native Brits.

This seems to me nothing like mirroring public opinion, and instead they are trying to bend facts to fit the newspapers narrative, so they will get coverage.

I think we do need leadership from elected officials, otherwise 'public opinion' is lead by the press barons.
In the thriving mid-2000s, there was Trident (Microsoft), Gecko (Mozilla) and Webkit (Apple forks KHTML). Presto (Opera) and KHTML proper brought up the rear. Basically three major companies/organizations.

Today we have: Blink, Gecko, Webkit. Basically three major companies/organizations. Goanna (Pale Moon: old FF codebase) brings up the rear here.

Like before, one company takes a huge lead. It was Microsoft, now it's Google. The more things change, the more they stay the same.

The only thing that's changed for me is that I feel much more protective of the work Mozilla is doing with Firefox. I consider them vital whereas before, they were an option.

Note to Mozilla: stop playing around with borderline business practices that force users to question your ethics.

source, browser engines: https://en.wikipedia.org/wiki/Browser_engine
I see your point. But I think if we have more rounds of QE and use the money for UBI, we'll get to Japan levels of disenchantment for 20 years (or perhaps more because we have far more debt to repay).

What I would like to see is some bad actors really getting wiped out, our GDP reduce a bit, asset values go down. That will cost a few jobs in the beginning.

But, in some time deflation will reach a plateau (because everyone needs to buy food, but that's not as low as we need to get).

Once plateaued, it would allow savers and risk takers to start investing in businesses themselves (these are the guys today with non-speculative money but unable to invest in overpriced assets).

Ultimately, bad actors from 80s, 90s and 00s are still alive and still investing right now. If the moral hazard is always solved by inflation, guess how many more speculative bubbles we will have.
With the restricted diets, compliance is extremely hard to achieve in a lot of cases. If you go to social events, work in an office, etc., it will always come down to being offered restricted foods and having to forcefully reject them. For many folks food becomes a religious thing and they decide(maybe not consciously) they'd rather die than change.

Fortunately my issues to date seem to be controlled with heavy vitamin D3 supplementation, so I don't have to do a hard restriction on anything.
Do you not think that people who are doing this professionally as their career, spending their entire lives working, reviewing, and discussing this type of research, do not realize that there is a potential bias and do everything they can to address it? It seems like some of the people here believe that we've discovered something that the researchers don't already realize, and aren't already trying to address. It's kind of strange to me that you're attributing a simplemindedness to the experts doing peer review panels that is unrealistic.

It reminds me of the times when people who aren't programmers seem to make this discovery that there is such thing as technical debt, and that programmers should be focused on programming in a way that avoids technical debt ("these programmers should focus on writing maintainable code! Not just short term hacks"). It's an oversimplication of the situation that is not helpful.
You could also link to other tickets or Epics with "relates to" or "blocked by".
FreeRTOS TCP/IP Stack Vulnerabilities – The Details
Humanity's Largest Atom Smasher Takes a Pause, Will Wake Up Again in 2021
No, that's not right. First, there might not be enough demand for the most expensive places, only so many people can buy a 20 million dollar apartment. There's no magic power law that means that supply of housing works in a way that someone stepping up always makes a space for someone below. Also, the cost of a top end place could often pay for many many more lower end housing. Generally it seems easier to make a profit on expensive housing or whatever, because cost matters less in the final profit (that takes lots of discipline to make profits on more units of cheaper things generally).
You can find it on libgen.
They do test the blood, but the tests are not 100% accurate (no medical test like this is). Asking people helps reduce the need for these tests which helps reduce the accidents caused by inaccurate results. Give people an incentive to lie and these accident rates will go up. It's as simple as that.
Coinbase exacerbated the exploitation by only allowing users to buy one or two cryptocurrencies to get access to the broader crypto ecosystem.

1) This mitigates that.

2) Simultaneously allows Coinbase to collect commissions.

3) Allows Coinbase to stay competitive while other exchanges enter the US/European market with the ability purchase with US banks and debit and credit cards.
Sounds like they had no process to begin with, found a ticket tracking tool, made fulfilling tickets their process, and now blame the tool.
I've worked in probablistic data-linking quite substantially over the past ten years. See https://github.com/DJMelksham/IcarusDataLinkingSystem for example.

While the principal is broadly correct, in real life you've got to worry about a host of other things.

Firstly, while you can come up with a theoretical number of persons who are uniquely identified, its harder to establish who IS uniquely identified. This might seem like splitting hairs but its quite fundamental: imagine you knew you could identify 50% of the population uniquely, unless you know which 50% of the population, have you really identified anyone? Clearly knowing someone's sex, age and location gives me analytical information about them I can use to make predictions (a 5 year old female in california is going to be fundamentally different from a 85 year old male in alabama) but is it really identification yet and do we even need identification to make useful predictions?

Secondly, what you presumably care about in 'identification' is not 'single source' probability issues per se. In the real world what most people care about is multiple-source identifiability: not the odds of one piece of data uniquely identifying someone (just by collecting gender I might eventually uniquely identify someone in some remote geography for example), but the odds of uniquely identifying someone in TWO (or more) data sources that were previously 'unlinked', because that's what's required to expand your current information set (you didn't know this person was identifiable on two data sources, and now you do, so you can bring together more information than what you already held originally).

This second point is extremely important, because in the real world, you have to worry about transcription errors, recording formats, corruption, temporal changes and time, and scope of the two data sources. Most people do not get to work with total accurate census' of the population at two points in time in a population that doesn't change.

From my own practical experience, something like the zip code, sex and birthdate combination is powerful, and yes, you'll be able to uniquely identify some people with such information (especially in smaller geographical areas), but the practical rate will be far far less than 87%. But for many modelling purposes, it doesn't need to be spectacularly accurate to be useful anyway.
more difficulty is better - more protected network is. where efficiency will come from is better mining hardware and introduction mass adoption of the lightning network.
What are the value of a hammer if all the nails are crooked ?

That's not a really interesting question because:

- IRL, all nails are not crooked

- it's unlikely they ever become so

- we can make other nails

- we can use hammers in other contextes

- you can always make another hammer, or hammer-like tool if this one doesn't suit your need

- hammers are damn useful on their own, as a concept

- people still use hammers, so I guess it has value for them
Facebook, Dynamite, Uber, Bombs, and You
> Apple's official position is that you should be arrested if you do anything with "your" device that they don't approve of

No, it really isn't their official position.
China is doing well, really? Are you ignoring the literal billion of people living below the most abject standards for poverty in the West, or do you just think people outside cities don't exist?
And that is the main reason, IMO. Mozilla Inc. never wanted to do more with it.
I think the JS world might be particularly excited about async/await because other people just escape to threads when they don't want to block the whole thing on IO.

Both in JS or Rust, you don't gain anything just by declaring your thing to be async, or awaitable. Your function needs to be built around some kind of "primitive" that explicitly supports the "do something else in the meantime" mechanism. Using "await" on that thing lets your function piggyback on its support, but all your explicit, normal code is synchronously blocking as usual.

In Rust, I think it's a fairly established pattern to turn blocking code, where the blocking part is not some IO action that has explicit support for the futures mechanism, into a asynchronous, awaitable function by punting the work to a threadpool. That makes sense for CPU-bound work as well as IO done by libraries that don't support futures or things like disk IO where the OS might not actually have decent support for doing it in a non-blocking fashion.

I'm not sure if it's the canonical mechanism, but this crate seems to implement what I'm thinking of: https://docs.rs/futures-cpupool/0.1.8/futures_cpupool/
A scarf that I use to support my forearms. My doctor said that I was pressing to hard on the table with my forearms and pressed on the cubital nerve and that gave me the tingling sensation you describe.
Go at Google: Language Design in the Service of Software Engineering (2012)
Obviously the scale is huge, but conventional trains have inefficiencies.

Suppose the average rider's trip is 10 stops. At every stop where the rider does not get off, there is inefficiency because they sitting there, taking up a seat on a train that is stopped. You're not only wasting their time, you're also wasting train capacity.

The naive solution is to make the train longer. Which works, but it's costly because you also have to make the platform longer. In a subway system, that's expensive. And the worst part is, you have to do it for every station the train will stop at, even the ones that aren't as busy.

This is, of course, why express trains exist. Eliminate some stops and you reduce all these problems. But the more stops you eliminate, the fewer people can use the express (because it doesn't stop where they're going), so there's an unavoidable compromise.

In the days before automation, this was probably the best that could be done. But now that automation exists, new approaches are possible.

Since you no longer need a driver per train, you now have the option of making trains smaller. And it's also possible to group people together by starting point and destination. So in theory you could make every train an "express train", one with zero stops other than starting point and destination. No seats wasted on making people wait in a non-moving train while others get on/off. So you can eliminate an inefficiency that you never could before.

Of course, every train needs headway for safety reasons. More smaller trains instead of fewer larger trains means that's harder. So it's not without its own, different limitations. Maybe automation has fast enough reaction time (or other tricks) that can cut down on the physical space needed for headway.

Anyway, the point is that much smaller vehicles might actually increase efficiency, and this is what the Boring Company seems to be planning to do.
> Amazon is a monopoly.

Can you please back up this claim with some data? Certainly doesn't look as a monopoly on book distribution and online book sales from here.
I became aware of that after college, and think it is unfortunate. I couldn't recommend professors and programs that teach formula plugging rather than understanding.
I just want to encourage the practice of authors allowing everybody to read their books. Uploading it to libgen kinda defeats the purpose.
Over here: https://visalist.io/new-zealand/visa-requirements/netherland... it says "source: wikipedia", which is hardly "official", and may not be comprehensive.

The Wikipedia page is subtly wrong you get a "visa on arrival", not "visa not required". There are some important details left out too; for example one of the conditions for getting the visa is that you have booked flights out of New Zealand. I've heard stories of people not realizing this and having to book flights on the spot :-(

You can get a 9 month visa quite easily, but you need to apply for it (and then you can enter without flights out of the country).

There are probably many more pages where such details (or even more important details) are lacking; I just chose this one as I recently moved to New Zealand so I know a thing or two about the Visa requirements there.

It might be useful for a quick "hm, I'd like to go somewhere, what are my options?", but I would always check the immigration website for these kinds of requirements/details. And frankly, I don't see what this website adds over Wikipedia.
I was planning to build a visa site as well, and I also wanted to fill in the all the visa application forms online [1]. That's actually one of the main reasons that I built FormAPI [2].

I decided to stop working on this visa list / forms idea. I think I could make a bit money from ads (hotels, airlines, etc.), but I can't think of any subscription models, and I personally wouldn't pay any one-time fees just to fill out some forms. I think most people would rather use a pen than enter their credit card details.

It would also be far too much work to organize all of these application forms and stay up to date with visa requirements. I just wanted some passive income and wasn't ready to schlep [3].

But I think it could be done with VC funding and a team of salespeople and immigration experts. You need people calling or emailing embassies, or visiting them in person, and making sure that they know about these filled-in forms and are willing to accept them. I was also thinking that I would eventually build a SaaS service for every embassy, so that people could apply online and track their applications. Could start with filling out the forms, and then eventually digitize the process and cut out the paper. But I was worried about turning into another online visa agency where I was just a middle-man. That's a service business with low margins, and it would be easy to settle into that and get stuck there.

Anyway, it's a huge project, so it's not something I could do by myself. Also trying to sell software to government and immigration agencies is a really bad idea (from personal experience.) But maybe there's an opportunity here, so let me know if anyone is interested in working on that.

[1] https://www.visaforms.co

[2] https://formapi.io

[3] http://www.paulgraham.com/schlep.html
How many people can soak up that high priced unused real estate? Not that many. I expect there to eventually be a housing and infrastructure crash in China, but maybe they can absorb it because they are so large.
I hadn't considered it when I wrote my earlier comment, but I wouldn't be surprised to see O2 receive their own reputational damage invoices from their reseller networks (O2, Tesco, etc.) in relation to the problems.
CPUs do the physical calculation and the number of cores determines the number of calculations that can happen at the same time.

Software threads, from the OS to your application, run on one of these cores for a certain amount of scheduled time, then get switched out with some other thread. If threads are waiting on IO then they're not making much use of the time they get and are wasting CPU capacity.

An older approach is to just make more threads and switch them out faster, but this is very inefficient. Await/async is a way to let threads not get stalled by a single function and switch to a different function in that process that does have work available. It's basically another step of granularity in slicing CPU time within a thread.

The keywords do not force anything, they are just signals to the underlying software that it may pause and come back later if necessary, along with setting up state to track results. Some methods may still run all on the same thread if there's nothing else to do, or if the async result is already available and there is no waiting needed.

Most async/await is usually built on top of yield, generators, promises or other constructs that basically are state-machines or iterators.
> Road infrastructure costs a tiny fraction of rail infrastructure.

Not necessarily.

Rail is cheaper to maintain, and there is a huge opportunity cost of paving over a cities most valuable real estate to make roads.

The math on how large the streets would need to be in downtown Seattle to alleviate traffic end up with a giant % of downtown Seattle being torn down and paved over.

The Urbanist has a good article (https://www.theurbanist.org/2016/10/12/brt-is-not-cheaper-th...) on why light rail is cheaper than a huge freeway.

Rail can also have multiple tracks, it costs more, but amortizes really well.

Not having to intermix pedestrian, bicycle, and cars is another huge win for, well constructed, rail projects. Autonomous cars still have to stop at crosswalks! In urban cores, stop lights seriously cut into average MPH for a trip, and start shifting things into favor of rail.
The latest tokio has a work-stealing threadpools, so you don’t need to explicitly do this anymore, IIRC.
If it's trying to be an "official" site, then yes. I think it looks great, and those small things are easy to fix to not deter people.
Thankfully some services like Bandcamp sells DRM-free albums in FLAC.
People do that. Plus far more people do it 'indirectly' through options.
No it makes you start in an online pastebin env. It's the easy way for the tutorial writter, not the easy way for the learner.

I teach React regularly, I tried all methods. The only one that make people click is to make them use a flat html page and React.createElement() manually in it first. On their laptop. Offline. With no other tools than a text editor.

This way, you remove the magic, and when you bring it back, people make good use of it.

Magic is good for power users. It's a bad things as a beginer's tool though.
> Is there any benefit to making this [compute_pi_digits()] function awaitable?

If you introduce suspension points in that (e.g. every 100 computed digits), then you can co-schedule other tasks (e.g. a similar `compute_phi_digits`) or handle graceful cancellation (e.g. if a deadline is exceeded, or its parent task aborted in the meanwhile).
I lived in NY 2003-2006
> By building an application and putting it in the hands of the business as often as possible.

Just putting the application in the hands of the business is not enough, you need to ensure that you're actually delivering value to the business. You need pieces of functionality that you know the business values (and where both sides understand what the valuable thing is) - i.e. tickets.

> Thirty years ago I used a whiteboard.

> I never needed ticketing software to build software or to ship software.

I'm sure I could keep it all in my head, but I'd rather spend that mental capacity on more important things. That you found a whiteboard useful says that tooling can be helpful - and Trello can be more convenient than a physical whiteboard.
I'm not impuning the conclusion but the awful logic used to reach it. This is tentamount to saying, "a good meal of delicious food can lift one's spirits, therefore eating a rich diet everyday will make one happy!"
There is a chain of individual steps that need to happen to create the final product of hydrogen fusion, helium. One of the crucial steps is the production of deuterium from two protons. This step is incredibly slow and limits the rest of the chain. However if you skip the slow step and start by fusing deuterium and tritium you can have a much faster and efficient reactor.
That looks like fun! Thanks for the link.
Yeah, I was intending to refer to a time prior to the establishment of those conventions. Presumably those societies with right-to-left writing had independent mathematics with comparison operators. If they named them, there might be opposite conventions back then.
The silly thing about these kinds of tricks is that it shows they aren’t even thinking about why they’re being blocked. If it was just some simple text or an img tag, no one would block it and the ad would work without tricky markup. Since the typical ad is an obnoxious piece of trash though, I reserve the right to aggressively block anything I can. They will lose that war.
You are right.

I just came across this article which talks about using rational cubic trigonometric Bézier curves.

https://link.springer.com/article/10.1186/s40064-016-2544-3
Using "Create React App" as a beginer is the best way to have no idea of what you are doing, and make terrible decisions for what follows next.
Claim:

Many games can be implemented as a blockchain

Evidence:

Ledgers have been implemented as a blockchain

There you go. Now the burden is on you to provide evidence that it’s impossible for any game other than a ledger to be implemented as a blockchain.
Agreed, the few times we've tried moving from separate linked tickets to sub-tasks have been disasters. It doesn't jive with any of the tooling in Jira to try to have tickets be like 'mini-Epics'.
Genuine question, what does not too hot mean? Relative to what and/or when?
A lot of that "overpopulation" scaremongering is purely simplistic Malthusian nonsense. Consumption doesn't scale like that with population. Per capita, large families are more efficient. Besides, the population is predicted to hit a maximum of 9 billion, and the EU is aging rapidly which is a major problem. Instead of peddling unimaginative and lazy claims about overpopulation, people should focus on real issues like the glut of consumerism and the grotesque waste of very large quantities of food.
Hi! I'm the author of this blog post. This was fun to write: I've taken a bunch of flights in my lifetime, and was always curious what travel agents are doing when they book a flight, or what check-in agents are doing when they "can't find the ticket".
Three weeks? Are you employing non programmers to program?
They have to return investors' funds. Fine is on top of that. https://www.sec.gov/news/press-release/2018-264
It also gets you something where there is altitude gain.
Show HN: An app I made to eradicate child begging in my country at a hackathon
Developed countries where women control their own fertility don't have an overpopulation problem. Maybe we could help other nations reach those milestones?

But again, realistically, not enough time.
Not having the year in the title would imply we did.
I’ve written about this on here numerous times, it’s changed my life.

Here’s one of the threads where I mentioned it:

https://news.ycombinator.com/item?id=18573069