lower

I'm not sure about this, because it's easy to mix up two arguments of the same type.

For example, you could mean

    createFile(name, contents, /* temporary= */ true, /* overwrite= */ true)

but write

    createFile(name, contents, /* overwrite= */ true, /* temporary= */ true)

by accident.

They started building this route in 1991 right after German reunification (it connects the old East with the West). Parts of the route were built in the following years.

A part of the route goes through difficult terrain. It's a completely new route that now contains 27 new tunnels and 37 new bridges, some kilometers long. All this through an environmentally sensitive area. So it was quite expensive and difficult to agree on. Work was even stopped on this part at some point around 2000, mainly because of the costs IIRC.

fastrange is discussed in the article.

It's like this in the EU. You cannot sell 'soya milk'.

Source (PDF): https://curia.europa.eu/jcms/jcms/p1_370368/fr/

I think 'Viola!' is just perfect for this.

> I'm wondering why Thinkpad only offers their WQHD (highest available resolution, 2560x1440) glossy?

I'm writing this on a T480s with a matte WQHD screen.

> Is this single nucleotide change in SLC24A5 really the only way to decrease melanin production without having other harmful side effects? Naively I would expect lots of ways to have a loss-of-function mutation

In Asia, light skin evolved separately and is using different genes.

https://en.wikipedia.org/wiki/Human_skin_color#East_Asia

I can still open the full text of the offending books as html and as plain text. The EPUB and Kindle files are blocked, however. Maybe that's why there are conflicting reports.

But even in Germany there has been a fair amount of vandalism against new bike sharing companies.

In Munich, Deutsche Bahn has successfully operated a dockless bike sharing scheme for more than a decade. Last year, oBike dumped thousands of bikes in the streets, and these have been subject of quite a bit of vandalism. The reason is probably that the introduction was poorly managed. They literally dumped a huge number of bikes in the streets overnight, which was a bit of a nuisance and probably kind of invited vandalism.

On almost all days the sun does not reach its highest point (solar noon) exactly at 12 noon. Have a look at the graph on this site (The red line is the time of solar noon):

https://www.timeanddate.com/sun/uk/greenwich-city

Even in Greenwich, 12 noon winter time can be off of solar noon by about 15 minutes in either direction throughout the year.

Even in Greenwich, it is true only twice a year.

Yes, so maybe they could have offered a slave speaker instead of letting you buy the whole thing again?

> Create stereo sound with a second HomePod.

That seems really lazy [edit: making you buy a whole second thing instead of just a speaker]. What will they do next? Sell iMacs instead of external monitors?

Back in 1994 when the Pentium had the FDIV bug, they offered to replace the chip. Wikipedia says "Although it turned out that only a small fraction of Pentium owners bothered to get their chips replaced, the financial impact on the company was significant."

Could it be that Intel is communicating the way it does because they're afraid of lawsuits? I mean, if they admit that their processors are faulty, then they may have to recall basically all their processors.

Well, they're comparing kernel 3.10.0-693.11.6.el7.x86_64, which has the meltdown fixes, against 3.10.0-693.el7.x86_64, which does not.

My understanding was that the Spectre microcode patches give software a way to block speculative execution (via an MSR register) and to make the lfence instruction also block speculative execution. So, software support will also be needed to make use of these features in defending against Spectre.

What's being measured here must be mainly the impact of the Meltdown fixes.

I looked at the wrong rows in the table of capacities. So it's not a reduction by half. I corrected my message.

But it's still a reduction in capacity (from 99.5 watt-hours to 76).

Ok, so they couldn't increase the battery capacity. But why did they reduce it from 99.5 watt-hours to 76.0 watt-hours rather than just keeping it?

Lenovo has put out an advisory about what to do with the BIOS updates that contain the microcode:

https://pcsupport.lenovo.com/de/en/product_security/PS500151

Withdrawn CPU Microcode Updates: Intel provides to Lenovo the CPU microcode updates required to address Variant 2, which Lenovo then incorporates into BIOS/UEFI firmware. Intel recently notified Lenovo of quality issues in two of these microcode updates, and concerns about one more. These are marked in the product tables with “Earlier update X withdrawn by Intel” and a footnote reference to one of the following:

1 – (Kaby Lake U/Y, U23e, H/S/X) Symptom: Intermittent system hang during system sleep (S3) cycling. If you have already applied the firmware update and experience hangs during sleep/wake, please flash back to the previous BIOS/UEFI level, or disable sleep (S3) mode on your system; and then apply the improved update when it becomes available. If you have not already applied the update, please wait until the improved firmware level is available.

2 – (Broadwell E) Symptom: Intermittent blue screen during system restart. If you have already applied the update, Intel suggests continuing to use the firmware level until an improved one is available. If you have not applied the update, please wait until the improved firmware level is available.

3 – (Broadwell E, H, U/Y; Haswell standard, Core Extreme, ULT) Symptom: Intel has received reports of unexpected page faults, which they are currently investigating. Out of an abundance of caution, Intel requested Lenovo to stop distributing this firmware.

I think LLVM has a new approach to garbage collection, namely statepoints:

https://llvm.org/docs/Statepoints.html

The old gcroot mechanism "is mostly of historical interest at this point".

Note that the article talks about type checks for the JavaScript code that is being executed by WebKit, not type checks in the implementation of WebKit itself. So there are two different kinds of type checks involved here.

Something like this exists with function multi-versioning: https://lwn.net/Articles/691932/

For example, glibc chooses optimised machine code for memcpy depending on the CPU it runs on.

Lenovo has BIOS updates that specifically mention CVE-2017-5715 (Spectre). I wonder if this is an Intel microcode update.

https://pcsupport.lenovo.com/de/en/products/laptops-and-netb...

I think you need a certain amount of karma before this option appears.

> Pike's rules 1 and 2 restate Tony Hoare's famous maxim "Premature optimization is the root of all evil."

That quote is from Knuth, not Hoare.

https://shreevatsa.wordpress.com/2008/05/16/premature-optimi...

Suppose you have two functions

    fn f() -> Result<A, E>
    fn g() -> Result<B, E>

Then you can write

     fn h() -> Result<(A,B), E> {
        let x = f()?;
        let y = g()?;
        Ok((x, y))
     }

rather than having to do something like

    fn h() -> Result<(A,B), E> {
       match f() {
           Ok(x)  => {
             match g() {
               Ok(y)  => Ok((x,y)),
               Err(e) => Err(e)
             } 
           },
           Err(e) => Err(e),
       } 
     }

(written from memory, please excuse syntax errors)

What's new is that this also works with Option<A> now.

> I'm having a senior moment here, but wasn't it common to include space in instruction-space and initialized data space, designed to permit binary patching by jump table to (currently) un-used pre-assigned regions

Maybe you're thinking about hot patch points in Windows DLLs?

https://blogs.msdn.microsoft.com/oldnewthing/20110921-00/?p=...

For reference: http://sircmpwn.github.io/2017/10/26/Fuck-you-nvidia.html

I believe that the Ubuntu Gnome Shell will have an extension to give it a Unity-like look, see the series of blog posts here: https://didrocks.fr/