skysight-inc/HackerNews huggingface dataset:
Any raspberry Pi’s? :-)
Not in this context - "trolling" as described there would apply to targeted indexing of a specific site; while "trawling" would refer to a wide net that attempts to catch all the sites.
the two weeks were to build up health care capacity. We erected field hospitals to manage the sick and then closed them because they weren’t being used.

If this truly is an energy and hospitals truly are at risk, find a way to build more capacity even if it is temporary. Blaming the public for the failure to do this is wrong. And if you aren’t building this capacity… maybe this really isn’t an emergency?
It sounds like you read that off the government shill brochure.

The decline in public healthcare quality has nothing to do with the lack of government oversight but it's due to the lack of funding and personel (which is also funding related). Ask any overworked healthcare worker in the public system.
In the very beginning Germany was doing _extremely_ well, until the protesters showed up.

Which is crazy, because Germany managed to do well by good organisation and mass testing, not by lockdowns.
Hi folks, we're working on it. We'll be back up and functional shortly.
You forget one, the people that are dying have taken the risk for ther own and didn't want to get vaccinated. It's ok when they die, it's their decision that's gone wrong. Other people didn't got vaccinated and will never get covid anywhere.
This is a decision that not the government has to make for the people.
Forcing a standardized test is not the same as forcing an injection that people still have to sign a legal waiver for.

If you're talking about taking away freedoms and forcing injections, it better solve something, not "meh it probably helps".

-- edit --

To below, the 14th amendment. Why do you think they keep losing court cases with the vaccine mandates?

My body my choice. Ring a bell? If it's a good enough argument to kill life inside you, it's a good enough argument against forced injections.

Don't be a useful idiot, don't advocate for your own oppression: https://en.wikipedia.org/wiki/Useful_idiot
For those use cases you typically have specialised hardware or an FPGA.
What can Computer Vision do
>in which case the code size advantage of ARMv8 vs. RISC-V would increase significantly.

Many things could be said about ARMv8, but that it has good code size is not one of it. It does, in fact, have abysmal code density. Both RISC-V and x86-64 produce significantly smaller binaries. For RISC-V, we're talking about a 20% reduction of size.

There's a wealth of papers on this, but you can verify this trivially yourself, by either compiling binaries for different architectures from the same sources, or comparing binaries in Linux distributions that support RISC-V and ARM.

>where combined compare-and-branch instructions could be added, and with a larger branch offset range than in RISC-V

If your argument is that ARMv8 could get better over time, I hate to be the bearer of bad news. ARMv9 code density isn't any better.

>and the worst is the lack of indexed addressing, which frequently requires 2 RISC-V instructions instead of 1 ARM instruction.

These patterns are standardized, and they become one instruction after fusion.

RISC-V, unlike the previous generation of ISAs, was thoroughly designed with hindsight on fusion. The simplest microarchitectures can of course omit it altogether, but the cost of fusion in RISC-V is low; I have seen it quoted at 400 gates.
I don't see why crypto can't just be a peripheral. Here's a block of memory and a key. Tell me when you're done.
> Families have and always should lookout for themselves first. That's the way things work and should work.

You're assuming this axiomatically, at first blush this is simply nepotism which is typically a term w/ negative connotations.
I think the "track count" has to do with the number of tracks available for mixing in the sound editing stage, not how many channels are in the final mix. At the time the sound editors would have been limited by the mixing board itself - how many tapes can run simultaneously. These days, computer audio workstations can have essentially an unlimited number of tracks, allowing endless tinkering and post-production that can become a crutch. My experience is in music production but I think the same applies to film.
I think he's confused about the data. Based on the Google data (from the graph that's visible when searching "COVID Denmark"), there are more Danish cases now than at the previous 2020 peak (3500/day then vs 4300 now), BUT hospitalizations (920/day then vs 430 now) and deaths (32/day then vs. 11 now) are down significantly.
I don't think they're enforceable in the US either. Once you have it you have it. This is what a sale legally is, it terminates the rights of the former owner. They can refuse to sell to you if they think you'll do something with it, but if you get it from them by lying or from a second hand sale they can't do anything.

For software you can also have person A buy something, then give it to person B who didn't click a license agreement. But this isn't really necessary -- the case where Microsoft got slapped for motherboard locking Windows XP and had to undo it shows that if software is integral to the operation of a device rights to its use are transferred along with the sale of the item, much to the chagrin of CNC companies everywhere who have yet to be challenged on this.

It's relatively common for companies to use shell companies or employees to buy hardware off the record for investigative purposes. Place I used to work at would investigate buyers for this reason (difference being we really did give our customers free reign with the equipment, we just had to try to stop fraud and other things).
> Right, so how can I get a bank account that nobody can shut down?

What's a bank account when there's literally nothing useful you can do with it, except hoard, scam, and trade other meaningless tokens?

> Neither is bitcoin's.

The absolute vast majority use cases for bitcoin are scams and hoarding.

> I mean if Bitcoin is a scam, it is probably one of the most complicated scams ever?

It's not. It's very, very simple.

> How many millions of lines of code have already been written for the Bitcoin ecosystem?

You assume that having many lines of code is equal to something not being a scam.

There exactly two kinds ow people who peddle bitcoin and crypto: scammers who know what they are doing (and yes, writing millions of lines of code), and gullible idiots.

> So gold is also a scam?

Outside of technical uses? Yes, mostly, as in the usual scenario of "you need to hoard gold because soon everything will fall, and you'll need gold". So are diamonds. There are very many scams. But blockchains, and bitcoin among them, take the current crown.
That's like saying, people are still hospitalized after car crashes so seatbelts and airbags are useless.
I'm getting a 404 response and this message;

> The requested page "/system/files/ca%20hitech%20dtn%201020172.pdf" could not be found.

EDIT: Now I'm not, and I can load the PDF. Not sure why.
Did the file move? Am getting file not found for:

https://oag.ca.gov/system/files/CA%20HITECH%20DTN%201020172....
You should add Mortality + mortality in the following year. Studies coming out that people who survived severe covid had over twice the risk of dying within the next year.
You can get a compressor/limiter for pretty cheap, but only if you have wires somewhere between the DAC and your speakers.
_For the purposes of implementing multi-word arithmetic_, which is Torbjörn's whole deal, it kind of does. (Also the actual post subject is "greatly underperforms").
Best Linux desktops for pros 2021: Our top
"I am the Lord thy God!" - God

"Prove it!" - Me

"aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f" - God
Train left the station as soon as orders were placed for massive amounts of vaccine well before it was ever developed.
I don't think you're supposed to. The compiler handles that stuff, ideally RISC-V is just another compilation target.
'Tis a bit of a silly article, I'd go insane trying to keep my application windows in the sweet spot for viewing them at a 22 degree rotation. One thing strikes me that I've wondered about when I would rotate some of my monitors: the color shift/viewing angle issue. I can understand in older monitors that have different viewing angles for horizontal and vertical, but some of my monitors over the years have been 176 degrees H + V or 178 degrees H + V, so why is there such a marked difference in what is being displayed when it is at 0 degrees rotation vs 90 degrees rotation?
> Ah, sorry, I misunderstood you. I thought you were placing the emphasis on what the code was doing, rather than where it was being piped. But why do you think that most of the possible optimisations would only be relevant if the output were being piped to somewhere other than a terminal?

One of the primary optimizations is using vm_splice to avoid memory copies. vm_splice only works if the file descriptor is a pipe.

> Also, why would making it absolutely optimal be "equivalent to solving the halting problem"?

https://en.m.wikipedia.org/wiki/Rice%27s_theorem

Or more specificly, if a program always halts (without outputting things) then the best optimization would be to have it halt immediately but to know that you have to have solved the halting problem.

You're right of course, absolutes are a bit of a distraction we just need something good for 99% of programs. However that's still really hard, and an optimization applied in the wrong context will slow down a program. There's still lots of room for compilers to grow, but the types of optimizations in use in this example are at best probably NP-complete to determine if they apply (i dont have any evidence for that though)
> Unvaccinated people are to blame for this

This satirical article from Ireland is probably applicable in every Western country that has had its health system systematically hollowed out by cynical neoliberal fuckheads: https://waterfordwhispersnews.com/2021/11/19/unvaccinated-be...

> Increasing ICU capacity right now is not a solution. It's completely misguided

What you fail to understand is that the people who cut those bed numbers across Europe are responsible for far more death than a small percent of mRNA vaccine hesitant people. And they're fucking delighted that so many people are so misdirected.
Based on the title I thought this was going to be about simulated organisms, but no, it's real organisms designed by an AI.

This is simultaneously really cool and supremely creepy.
What makes you think Ethereum Foundation gave themselves the majority of Ether? I'm pretty sure it was 15% but I might be wrong
Who exactly are the customers for this chip?
Exploring Container Security: A Storage Vulnerability Deep Dive
There is also CDK for Terraform now actually. Hope they'll keep it up to date.
FTC sues to block Nvidia-Arm merger
When I say they don't reduce transmission, I mean (and the article backs up) that an infected vaccinated person transmits the virus just as much as an infected unvaccinated person. Probability of infection between the two groups is a different subject.
> countries have reached the point where the majority of Covid patients in their ICUs are vaccinated at well below 100% vaccination

Which countries? I find it hard to get data at vaccination prevalence in ICU population specifically, but in Switzerland, the figures I see cited is 60-70% of patients unvaccinated (With 90% of 80%+ year olds in the population being double vaccinated).
Nearly any instance of a cop interacting with a black man compared to interacting with a white man.

The law isn’t like to explicitly favor one group over another, but the the systems of law have shown they do favor one group over another.
You honestly think that it's the wrong answer to show that website when somebody searches for that term?

The title tag of the site is as follows: "Download music, movies, games, software! The Pirate Bay - The galaxy's most resilient BitTorrent site"

And it's the number one search result for that phrase on DDG. Because search engines are actually programmed well enough to figure out that's the right answer. I'm not sure why you think it's the wrong answer to show that site as the first result, but I'm pretty sure everybody else in the world disagrees with you, and would prefer that they see the website they are searching for, instead of news articles about the site they are searching for.
Not Ami Pro. That was a Windows application from the very first version.
Smallpox vaccines were not "highly sterilizing."

https://twitter.com/santiagokique/status/1465014078938628099
Could you elaborate on how this Hamilton framework is a case of Dependency Inversion (which in my understanding is about removing dependency on low level class and using dependency on high level class instead)?

What's the low and high level classes in this application?
Not the only way. What is with the north korean way? Just shot anyone that has covid?
From a US perspective, I think walkability score is overrated because walkability scores are ridiculously inflated. There are like 5 places in the entire country I would consider actually walkable (and they aren't affordable), yet many places will have a good or great "walkability score".

And walkability is a tradeoff for space. Pretty much everyone in my family are Single-family home for life kind of people, but they all enjoy visiting walkable places and talk about how nice they are. I guess what I'm trying to say is, it's not that people don't value walkability, it's that there are very, very few good walkable places to live. Would even go as far to say close to none, but I'm sure some smaller towns are out there that go under the radar.
In my experience CDK has much nicer documentation. It also has a lot of high-level constructs, e.g. I can very easily say give me an EC2 instance on the public internet, whereas with pulumi you have to set up all of the security groups, vpc, internet gateway, etc.
Well everything ALREADY IS software. :)

Loosely speaking. Software in a computer, or in our brains.

With the "software in a computer" camp ascending rapidly, at the expense of the only alternative "software in a brain".

So we already need to solve all these problems with software soon. Or with a large amount of software as a required ingredient, anyway.

(I realize some people don't think machines will ever outthink biology (for ... hands and head waving around ... "Reasons! Man. Reasons!"). But, most of us probably agree that this is a loose goose first approximation of the long term trend we are in since the transistor, with no end in sight.)
In other words, we checked ourselves found everything we did was right!

But those of use paying attention to press releases and what actually happened know better.
Trains that don’t even reach their intended destinations.

45-minute to 1-hour drive to a nonexistent but planned train stations times TWO (for end-waypoints) just to enjoy a two-hour (or less) time-saving trip across the California farmland makes about much sense as skydiving off a plane to reach your destination.
It kind of chafed when I excitedly read the ISA docs and found that overflow testing was cumbersome.

That said, I think it's less of an issue these days for JS implementors in particular. It might have mattered more back in the day when pure JS carried a lot of numeric compute load and there weren't other options. These days it's better to stow that compute code in wasm and get predictable reliable performance and move on.

The big pain points in perf optimization for JS is objects and their representation, functions and their various type-specializations.

Another factor is that JS impls use int32s as their internal integer representation, so there should be some relatively straightforward approach involving lifting to int64s and testing the high half for overflow.

Still kind of cumbersome.

There are similar issues in existing ISAs. NaN-boxing for example uses high bits to store type info for boxed values. Unboxing boxed values on amd64 involves loading an 8-byte constant into a free register and then using that to mask out the type. The register usage is mandatory because you can't use 64-bit values as immediates.

I remember trying to reduce code size and improve perf (and save a scratch register) by turning that into a left-shift right-shift sequence involving no constants, but that led to the code executing measurably slower as it introduced data dependencies.
I don't know about others, but when I think of the "good old google days" I'm _not_ expecting the results for your example queries to be any good.

In those days querying took some effort but the effort paid off. The results for "history" just couldn't matter less in this mindset. You search for "USA history" or "house commons history" or "lake whatever history" instead. If the results come up with unexpected things mixed in, you refine the query.

It was almost like a dialog. As a user, you brought in some context. The engine showed you its results, with a healthy mix of examples of everything it thought was in scope. Then you narrowed the scope by adding keywords (or forcing keywords out). Rinse and repeat. As a user, you were in command and the results reflected that.

The idea that the engine should "understand what you mean" is what took us to the current state. Now it feels like queries don't matter anymore. Google thinks it knows the semantics better than you, and steering it off its chosen path is sometimes obnoxiously hard.
I disagree, over the summer they aimed for low infection rates, explicitly coupling openings to certain infection rate thresholds, knowing full well at that time that the virus was going to be endemic and without any good reason at all believing that sufficiently many people would be vaccinated in order to contain the pandemic in the winter. Other countries such as France or the Britain simply didn't care about high infection rates over the summer and face a smaller wave this winter.
Mac automation for things like CI is a pain in the ass (at least for small businesses) and their virtualization story for e.g. older version of the OS blows, despite having had a built-in hypervisor for a really long time.

"Load this specific OS, install these other programs, download some data, get it to this overall state, then run this script and send the output somewhere else, then destroy it when you're done" is actually a pretty big pain to do with macOS, without paying someone. Not that rentable M1 Macs solve that problem, exactly, but rentable, managed Macs in general can be useful for this, when you're renting from places with the automation in place to do easy virtualization or re-imaging.
It's interesting to note that Patrick Steward might be responsible for changing the way people commonly pronounce the word Data. If so, I wonder how much impact his stage training had on how he chose to pronounce the word.
If you're vaccinated, how can anybody infect you with it?
Hence why this is a completeness "probability". In practice this is fine as alternative mechanisms to prove such things as identity involve mechanisms like signatures and hashes, which also can be guessed.
Andrew Waterman's thesis ("Design of the RISC-V Instruction Set Architecture") has a very approachable comparison of RISC-V to MIPS, SPARC, Alpha, ARMv7, ARMv8, OpenRISC, and x86:

https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-...
"One SSD in a Macbook is ~1000x faster than the default disk in an EC2 instance" - I did not know that!
I don't even see the issue. RISC-V is supposed to be a RISC-type ISA. It's in the very name. That it takes more instructions when compared to a CISC-type ISA like x86 is completely normal.

https://en.wikipedia.org/wiki/Reduced_instruction_set_comput...
During the complete pandemic I never heared a so good fiting wise word like this.
Financial 'innovations' are increasingly rhetorical. Investors are seemingly being asked to bet on whether the humans can tell a rose by another name.
Understand, we're in the second epidemic and headed for the third. Plans made on the basis of the original virus may not be valid. "The enemy get a vote", as the military says.

The original virus had a R0 rate of about 3, that is, in normal conditions, each infected person infects three others. That's about what the first generation of vaccines could control well enough that eventually the virus would die out.

The delta variant has an R0 of about 8. The current vaccines can slow down the spread, but not stop it. Which is why we've had a second epidemic. By last August, delta variant cases were 90% of the cases seen.

We don't know enough about the omicron variant yet.
and for k8s
> I don't think they even tried to read the ISA spec documents. If they did, they would have found that the rationale for most of these decisions is solid: Evidence was considered, all the factors were weighted, and decisions were made accordingly.

It's perfectly possible to have read the spec and disagree with the rationale provided. RISC-V is in fact the outlier among ISAs in many of these design decisions, so there's a heavy burden of proof to demonstrate that making the contrary decisions in many cases was the right call.

> Which is easy to verify as utter nonsense. There's not even a need to look at the research, which shows RISC-V as the clear winner in code density. It is enough to grab any Linux distribution that supports RISC-V and look at the size of the binaries across architectures.

This doesn't seem to be true when you actually do an apples-to-apples comparison.

Taking as an example the build of Bash in Debian Sid (https://packages.debian.org/sid/shells/bash). I chose this because I'm pretty confident there's no functional or build-dependency difference that will be relevant here. Other examples like the Linux kernel are harder to compare because the code in question is different across architectures. I saw the same trend in the GCC package, so it's not an isolated example.

riscv64 installed size: 6,157.0 kB
amd64 installed size: 6,450.0 kB
arm64 installed size: 6,497.0 kB
armhf installed size: 6,041.0 kB

RV64 is outperforming the other 64-bit architectures, but under-performing 32-bit ARM. This is consistent with expectations: amd64 has a size penalty due to REX bytes, arm64 got rid of compressed instructions to enable higher performance, and armhf (32-bit) has smaller constants embedded in the binary.

Compressed instructions definitely do work for making code smaller, and that's part of why arm32 has been very successful in the embedded space, and why that space hasn't been rushing to adopt arm64. For arm32, however, compressed instructions proved to be a limiting factor on high performance implementation, and arm64 moved away from them because of it. Maybe that's due to some particular limitations of arm32's compressed instructions that RISC-V compressed instructions won't suffer from, but that remains to be proven.