LinuxWebLog.com

by Guido Socher

by Carlos Andrés Pérez

by Jean-Etienne Poirrier

by Guido Socher

by Guido Socher

by Tom Uijldert

by Guido Socher

A former Microsoft intern has revealed details of a YouTube incident that has convinced some Edge browser engineers that Google added code to purposely break compatibility. In a post on Hacker News, Joshua Bakita, a former software engineering intern at Microsoft, lays out details and claims about an incident earlier this year. Microsoft has since announced the company is moving from the EdgeHTML rendering engine to the open source Chromium project for its Edge browser. [...] Google disputes Bakita's claims, and says the YouTube blank div was merely a bug that was fixed after it was reported. "YouTube does not add code designed to defeat optimizations in other browsers, and works quickly to fix bugs when they're discovered," says a YouTube spokesperson in a statement to The Verge. "We regularly engage with other browser vendors through standards bodies, the Web Platform Tests project, the open-source Chromium project and more to improve browser interoperability." While we're unlikely to ever know the real story behind this particular incident, I don't doubt for a second that Google would do something like this.

It took about 30 minutes for Williamson County commissioners to unanimously approve a roughly $16 million incentive package for Apple Tuesday morning, bringing the total amount the tech giant is likely to receive in exchange for choosing Austin as the site for its newest campus to a cool $41 million. The new addition is set to be Apple's second campus in the Austin, Texas, area - located less than a mile from the company's existing facility, established five years ago. It comes with the promise of a $1 billion dollar investment from Apple in the area and the addition of up to 15,000 new jobs. But the details of the incentive package Williamson County whipped up to woo Apple tell a slightly different story. In the contract approved by county officials, Apple committed to spending at least $400 million on the new campus and creating 4,000 jobs over 12 years. The contract says the jobs don’t necessarily have to be on the new campus in order for Apple to receive the promised incentives, but rather can be anywhere within Williamson County. Shady and shoddy deals like these are only the tip of the iceberg - and don't think this is merely an American thing. This entire past year in The Netherlands has been dominated by our newly elected government wanting to shove through an incredibly unpopular tax cut specifically designed to appease major (partly) Dutch multinationals like Shell and Unilever - a 2 billion euro tax cut while various important social services like police, education, and healthcare desperately need better pay and working conditions. In the end, under immense public and political pressure, the tax cut was cancelled, but it goes to show that these things happen everywhere - in large, powerful nations like the US, but also in small, insignificant welfare states like The Netherlands.

With the significant news this week that the Fuchsia SDK and a Fuchsia "device" are being added to the Android Open Source Project, now seems like a good time to learn more about the Fuchsia SDK. Today on Fuchsia Friday, we dive into the Fuchsia SDK and see what it has to offer developers who might want to get a head start on Fuchsia. Fuchsia is the only publicly known truly new operating system designed and built by one of the major technology companies. It's strange to think this may one day power Chromebooks and "Android" devices alike.

Without question, 2018 was the year RISC-V genuinely began to build momentum among chip architects hungry for open-source instruction sets. That was then. By 2019, RISC-V won't be the only game in town. Wave Computing announced Monday that it is putting MIPS on open source, with MIPS Instruction Set Architecture (ISA) and MIPS' latest core R6 available in the first quarter of 2019. Good news, and it makes me wonder - will we ever see a time where x86 and x86-64 are open source? I am definitely not well-versed enough in these matters to judge just how important the closed-source nature of the x86 ISA really is to Intel and AMD, but it seems like something that will never happen.