pitdicker
Quote:
The Rust project was initiated to solve two thorny problems:
- How do you do safe systems programming?
- How do you make concurrency painless?
Initially these problems seemed orthogonal, but to our amazement, the solution turned out to be identical: the same tools that make Rust safe also help you tackle concurrency head-on.
That was an eye-opener at the time, at least for me. Maybe Fearless SIMD borrows it's name from that sentiment.
Edit: the original announcement says this is the inspiration (https://raphlinus.github.io/rust/simd/2018/10/19/fearless-si...)
This seems like a good start: https://www.reddit.com/r/CureAphantasia/comments/xgtyd3/trad...
However the software has a terrible label placement algorithm that happily switches around the labels of adjacent elements. And it does so without notice after random changes to the model. That is behavior that can lead to pretty dangerous mistakes.
The reply of the software company: you have to check it anyway. That is why you get paid, right?
Of course you can't expect someone who just put something online as a hobby project to take much responsibility. But to ask some basic security/reliability from companies, foundations etc... Shouldn't that just be normal?
If that is true it is no surprise to me all sorts of folk medicine work on warts.
Of course cardio and strength training are useful for building/preserving muscle mass and general fitness. But for weight loss looking at food seems more effective.
Luckily when it comes to regular cake cutting there may be a host involved that just wants to give his guests something nice. And the guests hopefully just enjoy the cake instead of being overly sensitive about the fairness of the divisions.
This field is called paleovirology, and the paper also discusses in some more detail how fragments of viral DNA can end up in human DNA.
> When evolutionary biologists like Chuong mapped the genomes of these cells, they found that the protein that allowed these cells to fuse into a wall, called syncytin, didn’t look like it came from human DNA. It looked more like HIV.
So the entire premise of the placenta evolving from a virus rests on the fact that the organ has a unique function requiring a unique protein in the body. Saying the source probably is a virus seems quite a leap of thought. And aren't there many highly specialized proteins in the body?
Has anybody has some more information on what protein in a retrovirus looks similar to syncytin?
But I'll be giving this a try!
The Eurocode defines 3 consequence classes: CC1, CC2 and CC3. CC1 has the lowest consequence and is used for regular homes, light industry and agriculture. The chance of dying as a result of structural failure is low, 0.001. The chance for a CC2 building (apartment buildings, offices, hotels etc.) is defined as moderate with 0.03. And CC3 is for special buildings, such as large stadiums, with a high risk of death on structural failure, 0.3. There are other factors that go in defining a consequence class however, including economic and social concerns.
The consequence class maps to the chance that we find it acceptable for a building to collapse in a given year. Causes can be anything, like extreme weather. For CC1 this is 1 in 100, for CC2 1 in 10.000, for CC3 a chance of 1 in 100.000.
So the chance one or more people die in a stadium during a heavy storm due to structural failure could be 1 in 300.000 in a year if you purely look at the statistics behind the structural safety standard.
The statistics map to simple reference values for the loads of wind, snow, rain, usage etc. and easy safety factors. For example CC2 has a safety factor of 1,5 over all variable loads.
There are over 2000 of these turbo roundabouts in the Netherlands.
> Early pen plotters, e.g., the Calcomp 565 of 1959, worked by placing the paper over a roller that moved the paper back and forth for X motion, while the pen moved back and forth on a track for Y motion. The paper was supplied in roll form and had perforations along both edges that were engaged by sprockets on the rollers.
> In the 1980s, the small and lightweight HP 7470 introduced the "grit wheel" mechanism, eliminating the need for perforations along the edges, unlike the Calcomp plotters two decades earlier. The grit wheels at opposite edges of the sheet press against resilient polyurethane-coated rollers and form tiny indentations in the sheet. As the sheet is moved back and forth, the grit wheels keep the sheet in proper registration due to the grit particles falling into the earlier indentations, much like the teeth of two gears meshing. The pen is mounted on a carriage that moves back and forth in a line between the grit wheels, representing the orthogonal axis. These smaller "home-use" plotters became popular for desktop business graphics and in engineering laboratories
I think plotting on sheets was more common though.
So if the drawing doesn't fit on a standard paper paper we just take the width of an A0 (841mm) and pick some arbitrary length. My personal limit is 200cm because then it becomes a bit impractical to handle. And if it really, really doesn't fit in the 841mm width, I'll take the edges of the 900mm that are usually cut off too instead of splitting the drawing awkwardly over two papers.
Being able to compress well is closely related to intelligence as explained below. While intelligence is a slippery concept, file sizes are hard numbers. Wikipedia is an extensive snapshot of Human Knowledge. If you can compress the first 1GB of Wikipedia better than your predecessors, your (de)compressor likely has to be smart(er). The intention of this prize is to encourage development of intelligent compressors/programs as a path to AGI.
The Task: Losslessly compress the 1GB file enwik9 to less than 114MB. More precisely:
- Create a Linux or Windows compressor comp.exe of size S1 that compresses enwik9 to archive.exe of size S2 such that S:=S1+S2 < L := 114'156'155 (previous record).
- If run, archive.exe produces (without input from other sources) a 10^9 byte file that is identical to enwik9.
- If we can verify your claim, you are eligible for a prize of 500'000€×(1-S/L). Minimum claim is 5'000€ (1% improvement).
- Restrictions: Must run in ≲50 hours using a single CPU core and <10GB RAM and <100GB HDD on our test machine.
I finally picked up a new HL-L2375DW (and passed on the trusty old printer) and have to admit Brother made excellent innovations. As far as there were any annoyances, they are fixed. I no longer turn it off, it remains in standby sipping <<1W of power. And driverless printing is just great.
If you experienced poor performance the common explanation at the time was that you either had a profile folder that had accumulated all sorts of stuff that somehow caused a slowdown, or had some unfortunate extensions installed.
But libraries and users are caught in the middle.
And you are right about time-rs (or I think you are). Version 0.1 was never fixed, and version 0.3 does the OS and thread count checks.
It does have some advantage for chrono to do everything in Rust: it can now return two results for ambiguous local time during DST transition fold, and properly return None during a transition gap.
CVE-2020-26235, RUSTSEC-2020-0071 and RUSTSEC-2020-0159 where opened against the crates. That left the Rust ecosystem with a pretty much unsolvable issue for many months. Chrono went with the solution to parse the timezone database of the OS natively and read the environment using the Rust locks. Time tries to detect if the libc version has thread-safety guarantees to access the environment, and otherwise panics if there are multiple threads.
More reading: https://docs.rs/chrono/latest/chrono/#security-advisories
Does anyone have an idea of the amount of effort it would take? Would the effort be comparable with the original proof by Andrew Wiles?
There were not countless adblockers, just Adblock and Adblock Plus. Adblock was abandoned, and Adblock Plus was were the innovation and performance improvements were happening.
Adblock Plus was there in the first controversies around adblocking ethics. It 'took care' of the first lawsuit. It did a lot of good work that the later adblockers benefit from.
Personally I have never been a fan of the acceptable ads feature. But it comes from that time, and offers a middle ground in the adblocking ethics debate, and a way to finance legal troubles.
Now I have not been involved in a very long time (Using uBlock Origin and whatever filters are default), but just condemning Adblock Plus outright is a bit too quick.