This doesn’t have to be forever. Maybe in the future, developers will start using React Native to build desktop applications. Or perhaps Flutter! Electron apps have a bad reputation for using too much RAM, have potential security issues, can’t (yet) match the speed of C++, and they often lack the polish and familiarity of a great native app.

But it seems clear to me that OS-specific SDKs are becoming a liability for desktop OS vendors. Developers want to use the technologies they know, and they want maximum reach for the products they build. And they’re smart enough to get what they want. A lack of cooperation on the part of Apple, Google, and Microsoft will only hurt users.

Say hello to your new Electron overlord.

Twitter has long had a strange disdain for third-party Twitter apps, but it's allowed many of them to pass under the radar for the last several years. That's starting to change this summer, when Twitter will revoke a key piece of access that developers currently have to the service, replacing it with a new access system that limits what they can do. The changes aren't going to make third-party Twitter clients useless, but they are going to make the apps somewhat worse.

This is a little exploration into applying '90s-era design & principles into a modern platform with some primitive components. The assets and design metrics were (for the most part) taken from an actual installation of Windows 95. These are pixel-accurate renditions of the original design.

Four of the largest cell giants in the US are selling your real-time location data to a company that you've probably never heard about before.

In case you missed it, a senator last week sent a letter demanding the Federal Communications Commission (FCC) investigate why Securus, a prison technology company, can track any phone "within seconds" by using data obtained from the country's largest cell giants, including AT&T, Verizon, T-Mobile, and Sprint, through an intermediary, LocationSmart.

Surface Hub 2 was designed from the ground up to be used by teams - to get people out of their seats, to connect and ideate, regardless of location. The new Surface Hub 2 is sleeker, more agile and more affordable to fit any workspace or work style. The gorgeous 4K+ 50.5" multi-touch display creates an inviting canvas to co-create, harnessing the power of Microsoft Teams, Microsoft Whiteboard, Office 365, Windows 10 and the intelligent cloud. The 4K cameras that rotate with the device, integrated speakers and far field mic arrays allow everyone in the meeting to feel as if they are right in the room with the rest of the group, while our standard Surface 3×2 aspect ratio means everyone has more usable space to create and collaborate.

This is just a slightly modified version of the standard DOSBOX emulator. I have just hacked in my own shader which emulates some aspects of old CRT monitors, as I prefer to play emulated games with such a filter, and the built-in dosbox filters are not to my taste. I made this because I wanted it myself, but since I have it I thought I'd share it. There's probably lots of things which could be done better, but it's good enough for my needs right now, so leaving it like this for now.

The kernel is the only UNIX code that cannot be substituted by a user to his own liking. For this reason, the kernel should make as few real decisions as possible. This does not mean to allow the user a million options to do the same thing. Rather, it means to allow only one way to do one thing, but have that way be the least-common divisor of all the options that might have been provided.

"Sunrise day" for the GDPR is 25 May. That's when the EU can start smacking fines on violators.

Simply put, your site or service is a violator if it extracts or processes personal data without personal permission. Real permission, that is. You know, where you specifically say "Hell yeah, I wanna be tracked everywhere."

Of course what I just said greatly simplifies what the GDPR actually utters, in bureaucratic legalese. The GDPR is also full of loopholes only snakes can thread; but the spirit of the law is clear, and the snakes will be easy to shame, even if they don't get fined. (And legitimate interest - an actual loophole in the GDPR, may prove hard to claim.)

Toward the aftermath, the main question is What will be left of advertising - and what it supports - after the adtech bubble pops?

After the release of the Iyonix PC in 2002, RISC OS started moving from 26-bit architecture towards 32-bit. Nowadays all modern RISC OS machines are 32-bit, but an awful lot of older applications are still not compatible with modern 32-bit RISC OS.

Aemulor, originally a commercial application but now free to download, is a software emulator that allows RISC OS applications which were written for a 26-bit ARM systems to be used on more recent CPUs that provide only 32-bit addressing modes. RISC OS itself is unaware that there is anything unusual about the 26-bit applications that are running under Aemulor, to RISC OS they appear as normal applications - they appear on the icon bar and can communicate fully with other 26 or 32-bit applications.

Among all the new additions to Android P including new navigation gestures, Slices API, and new biometrics API, there are some other changes which may also be impactful in a more subtle way. One of these is the removal of App Not Responding (ANR) dialogue boxes for foreground apps. The ANR dialogue appears when something is preventing the main UI thread from responding. When this happens in Android Oreo or below, the ANR dialogue is shown to the user to let them know. Now, in Android P, the application will just crash without any kind of notification for the user.

I bring this up because when Google introduced its new pill-shaped gesture area on Android P's first public beta, it was immediately apparent that Google was not aiming to recreate the simplicity, or even the convenience, of its decade-old three-button navigation scheme. Swiping up does not, in fact, go to the home screen but to the multitasking menu. Swiping up again, and only from that in-between state, reaches the app drawer. Indeed, reaching the home screen requires tapping the pill, something that's not at all obvious from its shape, or from precedent set by Apple and the rest of the industry.

We know that our smartphones are making us unhappy. At its annual developer's conference this week, Google revealed that 70% of its users actually want help balancing their digital lives. What's not so clear is what the smartphone manufacturers of the world should do about it. After all, it's in their business interests to make their phones as engaging - or addictive - as possible.

Yet at I/O, Google introduced a clever and aggressive response to its own habit-forming products. It's a broad initiative called Digital Wellbeing that CEO Sundar Pichai says will ultimately affect every Google product. "It's clear that technology can be a powerful force, but it's equally clear that we can't just be wide-eyed about ," said Pichai on stage at Google's I/O conference. "We feel a deep sense of responsibility to get this right."

Let's start with the most exciting developments this month: Korli started work on a 32/64 bit hybrid. The idea is to run a 64bit system, but allow 32bit applications to run on it. While we are just at the very first steps, it is a good thing that this is being worked on, as it will allow us to move more smoothly towards 64bit support.

Continuing our past work, Firefox 60 brings further important improvements to security sandboxing on Linux, making it harder for attackers that find security bugs in the browser to escalate those into attacks against the rest of the system.

The most important change is that content processes - which render Web pages and execute JavaScript - are no longer allowed to directly connect to the Internet, or connect to most local services accessed with Unix-domain sockets (for example, PulseAudio).

This means that content processes have to follow any network access restrictions Firefox imposes - for example, if the browser has been set up to use a proxy server, connecting directly to the internet is no longer possible. But more important are the restrictions on connections to local services: they often assume that anything connecting to them has the full authority of the user running it, and either allow it to ask for arbitrary code to run, or aren't careful about preventing that. Normally that's not a security problem because the client could just run that code itself, but if it's a sandboxed Firefox process, that could have meant a sandbox escape.