skysight-inc/HackerNews huggingface dataset:
The video event annotations or filenames described in the article sound like what you might get out of a company culture that allowed the previous behavior to go largely unpunished.
There's the function coloring issue: https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...

Where your sync functions have X considerations and your async functions have separate Y considerations - BUT, async/await sugar makes these widely different behaviors look nearly identical - so you get "clean" sync code aesthetics on your asynchronous code and are sort of on your own when tracking the behavior of its implication.
> Was spinning up a bunch of OS threads not an acceptable solution for the majority of situations?

It's worth remembering that this is still a very acceptable thing to do in some cases. And spawning OS threads is sometimes easier to write and easier to read, and easier to reason about than async code.

Just because async is in the language, don't feel like you need to use it everywhere.
I find rust to be too hard to use for it to ever become huge
> saying they're unexpectedly dark strongly implies you didn't think someone of that ethnicity was capable of being a software developer.

Everything is blue if you wear blue tinted glasses

I live in a city where I expect everyone to be expectedly dark, and anyone that come near to my white shade is very unexpectedly light

If I go to the pale end of the country, any darker skin would be unexpected, no matter the job title and no matter the IQ level

No unexpecting person should be liable for your projected meaning on surprising turn of events
Is that even math? I can accept that but it's not a very satisfying answer.

And almost anyone playing the lottery can tell you the chance of winning a jackpot is very low!
> So... don’t use first-class functions so much? It’s a systems language, not a functional language for describing algorithms in CS whitepapers.

Then maybe it was a mistake to adopt an async paradigm from functional languages that relies heavily on the idea that first-class functions are cheap and easy?

(FWIW I think Rust was right to pick Scala-style async; it's really the only nice way of working with async that I've seen, in any language. I think the mistake was not realising the importance of first-class functions and prioritising them higher)
I guess the next step of the argument would go something like "we can formalize certain forms of interesting* knowledge in the relationships among prime numbers, which are infinite" (e.g. Godel's work). After which point we can get into a very long conversation about what constitutes "interesting" and what constitutes "knowledge" .

It would certainly be a feat to formalize any of this, and we'd still be debating definitions and assumptions if we could formally prove anything.

> Learning the next thousand thousand prime numbers is not very interesting if you already know the first few million, and of very limited practical use.

Maybe your intuition here is right but my hunch is that if you were able to prove this conjecture, it would absolutely blow the socks off the mathematics community.

I look at it as a Pascal's Wager w/ regards to knowledge: either there's more to know that we don't know we don't know, or there isn't. If there is, we'll likely only find it out if we believe there is more knowledge to uncover and spend our time trying to uncover it.

My overall hunch here is that a lot of our current knowledge is constrained by our mental semantic structure, which is bounded by the working set of objects we can mentally manipulate at an instant in time. That set is probably O(10) for most of the population, and likely O(100) for everybody. We can increase the number of semantic objects we can operate on by working on them temporally using logical rules, but those rules themselves are bound by this O(100) limit, and so on for any meta-rules.

I would find it very surprising if all interesting things that could be stated were relationships between O(100) semantic objects, however abstract.
I miss pwn4ge like this, but even this was kind of weak because they didn't do anything funny and also damaging, must be both

all we've gotten this decade were super quiet "state-level actors", and uninspired trolls

I want the "for the lulz" ASCII art pros dropping MIDI music while also pillaging corporations and leaking secrets

make a festival out of it.

I think its coming, a hack that incorporates the best of the latest hacks. Like making a docker disk image of content that was leaked, so that all the other hackers (including the original hacker) have plausible deniability and don't violate the CFAA
> Batteries will never have sufficient capacity to delivery any meaningful amount of storage.

What physical limit prevents this?

It would be expensive, but cheaper than building nuclear power plants, especially the breeder reactors that would be needed for a fully nuclear world economy.
I started again to use RSS and Atom feeds last week.

I used to use facebook as an aggregator, but its curated list has become too poisoned since the pandemics and "political outbreaks" that followed. The algorithms noticed that I've been (automatically/inadvertently) interacting too much with such content, and decided to focus on that in order to keep me hooked.

Facebook and other platforms profit by subtracting value from society. I ask myself if that will stop someday.
The author admits that they needed Arc/clone in a footnote. So I think the more interesting title would be to rehash/interpret this as “Why asynchronous Rust is too hard”.

Having played with this a bit recently, I think folks are going to end up:

- assuming Tokio (now that it’s 1.xx)

- mark nearly everything as async

- push callers to use rt.block_on to wait for an async function from non-async code

I definitely miss the easy concurrency of golang the author refers to (more so in the colored functions post), particularly since AFAICT, tokio is basically going to become the default assumption. So Rust is technically pluggable here, but won’t be in practice. Does that mean that embedded folks end up having their own !tokio that they prefer? Maybe! But they’ll get locked out of the “assume tokio” ecosystem.
Oh, fuck. Cloudflare aside, Okta is huge for enterprise SSO throughout our industry. I can hear our infosec group having kittens as we speak.
Their staff on Reddit deny it and claim we are bound by different TOS
> anything where you want to pass functions around.

You should read the article! The author goes into this in fascinating detail.
Which are absolutely insane numbers compared to very similar societies all around the world. I doubt there is some sort of truly unique illness doing rounds only in America.
A little gem for anyone that is bored
Anyone able to weigh in on what "at scale" means here? Just "N number of records" where N is larger than is tenable by manual curation?

What about generating realistic amounts of data for performance testing (millions of records), and pushing that to shared database servers, or making it available for developers to populate their local databases? Are there best practices for this?
All my groupmates were and most of my doctoral committee are from Russia/Ukraine (the remaining member will be from China) but only one has non-North American (USSR) PhD
Renewables CANNOT replace nuclear OR fossil fuels. It's literally impossible based on current or any near-term technology.

We are being told on the one hand that climate change is an existential threat to tens (hundreds?) of millions of people. Oh but actually we can just refuse to decarbonize our energy production because maybe someday 10, 20, 50 or 100 years from now there's a true "green" renewable energy I guess.
Has anyone managed to actually get hold of the paper?
Title misspelled "both adults"
Why is a sales employee enabled with access to the surveillance footage of the home office? It's not trust-inspiring.
So, basically workflows where the cloned code gets run as root without further inspection anyways.
I don't think any of this is actually a reason why async rust doesn't work. The function color problem is a bit overblown, it hasn't broken nodejs yet either. Most code is sync, sync can call async and vice versa, and the ecosystem hasn't come tumbling down yet (since most Rust isn't whichever async application runtime for web apps is currently in vogue - its a systems language after all).

Either way there are bigger function "color" problems in Rust.

If you want a target for criticism in async Rust, it should be the lack of easy conversion from generators to async functions (and back) and the cognitive difficulty of implementing a custom executor.

I also think the tangent on closures is nonsense, closures are syntactically and semantically complex because closures are hard to keep safe without a garbage collector. Reference radioactivity is a feature, not a bug.
"The best time to plant a tree is 20 years ago."

I'm not convinced there aren't hidden costs with wind and solar, such as finding the land to put them on or the complexity of storing energy for night time usage or cloudy days or lack of wind etc.

What I do know is nuclear is able to power our collective needs just fine, day and night, RIGHT NOW and all we need to do is build the fucking things. So, let's build them...now.

Renewables are still an unknown, nuclear is not, and I'm not comfortable staking the future of the planet on "wellll, it will probably be fine in 10 years."
Ask HN: What should Apple do with the Apple silicon Mac Pro system architecture?
What do you think they will do?
I'm facing this issue as well. Too many short, addictive videos being recommended instead of the ones included in the channels I subscribed to. I'm going to include yt in my subscriptions.
Tardis: Affordable time-travel debugging in managed runtimes
This is some serious white-washing of the downsides and risks of crypto.

Reversible transactions for traditional currencies, for example, are often touted as a negative but they are for the most part a positive. It's what protects individuals from fraud. I hazard to think how the average person would manage a wallet without losing it to poor security or malware.

And if you use something like Coinbase, you have pretty much the exact same risk profile as using a bank.

Also, proving you own it gets real murky if the network itself is compromised. Attacks aside there have been various forks of different cryptos. My point is the immutability of the blockchain is essentially an optimistic exercise of faith.

As for hidden stockpiles and knowing how much is out there, that isn't quite true either. For something like Bitcoin, you know the upper bound of how much is out there but you don't actually know how much is out there.

There are numerous cases of lost wallet keys, for example, where you can consider the coins irrecoverable (short of a fork). But how many of these just haven't been transacted? Some of these stockpiles are huge too. Take the rumoured ~1.1M BTC associated with Satoshi. Are these lost or have they just not been used? It's impossible to say.
It's always possible there's a better way. If you know of one, maybe you can write a proposal? There is always Rust v2. Rust lacks a BDFL and so it's almost like the language grows itself. Chances are, the async model that was used was picked because it was arrived upon via consensus.
Their staff on Reddit are denying this applies to them.
Pumped thermal storage has no geographic limits. The idea is: compress argon, transfer the heat to thermal store, expand the argon back to the starting pressure to recover some work, then transfer the "cold" to another thermal store. For long term storage, use very cheap materials, like rocks, for the thermal stores. To discharge, reverse the flow, so argon is cooled, then compressed, then heated, then expanded. All this can be done with existing technologies and with a round trip efficiency of perhaps 60%.
I’m surprised nobody burned me for this comment, HN usually frowns on snark ;)

But I would like to add a constructive note: I’ve been dabbling around the RSS space for a long time, including a ten-year-old feed service and web client. In my opinion, RSS has failed where centralized social media succeeded largely because of discoverability.

I’ve put RSS clients in front of plenty of users, and the response is invariably, “okay, now what?” Using a bookmarklet to subscribe to feeds is confusing and unnatural to them. They want getting The Atlantic RSS feed to be as easy as following The Atlantic on Twitter. And they do want to see the “liked” articles of their friends who are fellow readers.

To anyone who is trying to make RSS fetch again, I beg them to take the take the social and discoverability issues seriously.

Incidentally, I think the Overcast podcast app (remember, podcasts are also RSS) is an ideal model of an in-app directory.
Why not adjust your ratings to fit the prevailing perception? Presumably the reason you're leaving reviews is not for yourself, but to help others, be it the business or future customers. To that end, it seems an adjustment is in order.
Yeah but the price starts at $0 and scales linearly with traffic.

> Also using GCR name for this is a bit weird when there’s already another GCP container product with the same exact name.

Very true! Naming is hard
Around ‘08 or ‘09 they declared defeat in the Great Webspam War and decided webspam could rank highly as long as it didn’t get too nasty. The whole web (as far as searches results will tell you) promptly turned into webspam. I imagine this, along with their plainly-evil inlining of ads with search results within a couple years of that, made their profit arrow go up-and-to-the-right so hard that no-one who opposed those moves was paid any mind.
The past year has been brutal for the entire world, and holding a championship for professional athletes doesn't really justify the billions of dollars Japan has lost in its decision to postpone the Olympics rather than cancel them.

Japan isn't even currently granting long-term work visas for professionals who will contribute to the economy for multiple years, ostensibly to curb spread of the virus. Consequently, it's a bit silly that they will soon be allowing tens of thousands of Olympic employees and athletes to enter the country, who will all be exempt from the standard quarantine procedure.
Fire declared in OVH SBG2 datacentre building
By competitive I mean that America does a better job at that thing than other countries, e.g. the examples I listed
Solar does not use rare earth metals. Please stop propagating this canard.
> caught a multi-threading bug

The compiler complained:
“error[E0308]: mismatched types”
I would say it’s clickbaity.
I've been primarily coding in rust since 2018. I never cared for async/await, and I've never used it. (at some point, coding event loops became very natural/comfortable for me, and I have no trouble writing "manual" epoll code with mio/mio_httpc).

one nice thing about rust's async/await is, you don't have to use it, and if you don't, you don't pay for it in any way. sure, I run into crates that expect me to bring in a giant runtime to make a http request or two (e.g. rusoto), but for the most part I have not had any issues productively using sans-async rust during the last few years.

so, if you don't like async/await, just don't use it! it doesn't change anything about the rest of rust.
Canon in European Languages and Arabic
Devices such as cameras are usually isolated on their on VLAN. In addition just because you are on the network doesn't really mean anything if there is a zero trust security model.
Wanted to write something similar, just not as elaborate as you did (native German speaker here).

Another good example is Java, and languages running on top of the JVM.
This is, frankly, rubbish. Asynchronous Rust works very well - and the implementation of async/await is more ergonomic than any of the progenitor languages.
Visible is owned by Verizon but they try to hide that fact.
I use it too. You have to have that curl script (not a default user experience), manually mount the ISO (and have it downloaded), and then you risk losing all of your application state if the machine crashes since there is no storage. Seems like a pretty terrible experience. Why don't we have something like Vagrant where you can quickly provision a VM from the command line following a template?
You didn't get super cheap power from nuclear because that was never in the cards. And they knew that from the start: the cost of a nuclear plant was never going to be less than the cost of a coal plant, and ended up being considerably more when all the engineering got done.
Not specifically for that API. I'd have to spend some time cleaning it up to open source it. But we have a really simple API connector example you can fork [0]. :)

[0] https://autocode.com/app/keith/connector-pokefusion/
And it can run sudo as your user after you warm it up. Or use any number of frequently disclosed OS vulnerabilities for local privilege escalation.
Every IOT device is an attack vector against the network.
It doesn't even have to be there... The main reasons to clone a repo are because you're about to compile and run the code there, or you already have and need to fix something.

I don't personally audit all the code I run, but I hope someone is doing it. That being said, source code being public is much better than the alternative of just downloading binaries from who knows where.

I don't trust anything absolutely, and I don't see a way past it.
> The virus would have survived somewhere in the world, and quickly began spreading once the 2 month lockdown ended.

No, because we can still do testing and tracing. A virus infecting a few hundred people that we can detect fast is a lot easier to contain than a virus infecting millions or one that we aren't aware of.

Asian nations (China, Japan, SK) are doing similar to New Zealand and they aren't nearly as isolated. Afaik Auckland's lockdown is going to be a couple weeks at most.

Understand that, had we done this 2-month full lockdown, we would not even be locked down now. Young people wouldn't be nearly as affected as they are now.
As a college dropout myself, this really makes me think about continuing my degree. What did you answer to Google and others who grilled you?
Right. The key point being that in Go, you can block or use some compute time without stalling out the async system.
Agreed. Max Headroom[0] should have been a sign of things to come rather than the pinnacle of this kind of thing.

[0] https://en.m.wikipedia.org/wiki/Max_Headroom_signal_hijackin...
Its almost certainly an anti spam system. The system marked the review as spam, for whatever reason. And it doesn't publish the results. The system doesn't tell you this because otherwise the first thing you will do is keep trying again in different ways until it doesn't tell you it was marked as spam.

Google drops reviews for a few known reasons. When a location gets negative coverage in the news, thousands of negative reviews from people who have never visited the location. Google then drops the reviews since review bombing is not useful.

Who knows why OPs comment was flagged, but its easy to see how this happens without a big conspiracy going on.
I'm sure different trailer park owners are a mixed bag, some good some bad.

The real issue is government limitations on the supply of housing (height, min parking, setbacks, etc).

Housing could be high quality and relatively cheap. From first principles, a 3 bed 2 bath apartment could easily be <$500/mo in any expanded metro area of the US, if you were allowed to build.

Allowing more competition for low cost housing would solve almost all of the systemic issues in this article.

But as other posters have mentioned, the US promotes the opposite - home ownership as a wealth building tool.

Housing is a cost, we should work to reduce it.
A more logical option is to wait for Hertz to inevitably go bankrupt, and THEN invest $5 billion into them.

Under no circumstances is it better for the new investors to pay billions before the bankruptcy.
From the outside they measured a high gravity even though they estimated 500 meters diameter and there's reason to believe there have been past explorers, so it only makes sense to me if it's actually bigger on the inside. The actual mass and inner depths could be expanding as you posit, though.
They have access to Tesla warehouse webcam [1] (or at least they claimed so). Pretty crazy.

[1] https://twitter.com/nyancrimew/status/1369388911693340674
> are just not viable as baseline power until batteries improve cost and density by several orders of magnitudes.

This is an outrageous falsehood. Play with the numbers at this model site to see:

http://model.energy/

Also, why is energy density relevant for stationary storage? The cost of land to site batteries is trivial.
So what do I use if I don't want to use google? Or any other free service that's co opted
The main product I work on has a specification that dictates the use of SOAP/XML. So I'm probably more familiar with SOAP than REST (by which I mean JSON/HTTP). Although I don't really delve deep into the RPC code when it can be avoided.

The answer to pretty much all your questions is "depends on the schema". There are XSD (XML Schema Definition) files that you can use to define types. You can define sequences, etc.

Then you can define a WSDL (Web Services Description Language) file which describes the RPC operations, arguments, return types, etc.

After that, you can use something like gSOAP to generate C/C++ out of the WSDL and XSDs. I think Java has a lot more variety in turning a WSDL into code, but last time I looked on the Java side of things it was super confusing. None of the tools seemed to work well together. They would never shut up about beans, and there always seemed to be a bunch of tool specific annotations. Pretty disappointing, and definitely makes me lean towards REST for personal projects, if only from a KISS perspective.

My impression is that SOAP and XML could probably make a much more complex web service than REST (again, abusing the term to mean JSON/HTTP). But after having worked on a pretty confusing contract-first web service, I am kinda jaded about it.
So what you're saying isn't entirely true. I believe you're referring to spent fuel processing, which is just one part of it.

I specifically mentioned UF6 (uranium hexaflouride) as a hazardous byproduct of centrifuge enrichment. Now France (and some other countries, including the US up until 2018 at least) do process UF6, but only to put it into a more stable form (eg UF4). That more stable form still requires long term storage.
where can you find servers like that for that price?
I went part-time and that was a great option. I almost immediately jump-started my career with a better job because my skills increased (I learned R and advanced SQL as part of a concentration).
They'll make... Macs...?

Then in 2 years the M2 chip comes out, another 2-3 years it's time for M3, etc. etc.
That actually makes a lot of sense. I wonder if that was the play the whole time.
The Evolution of Unreal Engine (1996-2021)
Why is preventing people from starting a legitimate business a good thing?
Never trust a man named Flip.

Edit: Argh... it's Filip. HN's tiny font strikes back.
Nope.

With snake oil, we would way that it is immoral for ANYONE to sell it. As a result, we (mostly) make it illegal too.

With Hertz stock, nobody seems willing to say that all sales of such stock are immoral. And certainly they're not illegal; people have been buying and selling an enormous volume of Hertz stock.
“So Canadians pay (some) income tax to the US instead of Canada and the US gives us nothing in return?”

Seems like Canadians got the ability to make money on YouTube in return. Seems like a pretty good deal.
Vote with your wallet and leave. If you can afford a school like that, you can afford to leave.

I don’t know why anyone cares to be labeled a racist anymore considering the term has lost almost all meaning.