If you want to write Assembly programs for the Amiga you can either work directly on a real system or use a cross-compiler. I prefer to work on my Linux system because, as much as I like retro architectures, I also like the power of a good Unix system and a modern editor.

Cross-compiling is a very simple concept: instead of compiling source code and creating binaries for the architecture you are running the compiler on, you create binaries for a different architecture. In this case the host architecture is Linux/amd64 and the target architecture is Amiga.

As this is not the only project I am following at the moment, I created a directory to host everything I need for the Amiga development: compiler, documentation, scripts.

It’s official. The Federal Communications Commission's repeal of net neutrality rules, which had required internet service providers to offer equal access to all web content, took effect on Monday.

The rules, enacted by the administration of President Barack Obama in 2015, prohibited internet providers from charging more for certain content or from giving preferential treatment to certain websites.

At the beginning of the '90s, the PC platform was often mocked by its rivals. Of course, PCs were much more powerful than, say, an Amiga 500. But the Amiga offered a flat memory address, while a DOS program could only access memory using cumbersome 64 KiB segments. And to add insult to injury, there was this strange 640 KiB memory limitation. No matter how much physical memory you had in your box, the utter most important Conventional Memory was limited to 640 KiB!

The Legend teaches us that Bill Gates once declared that "640 KB ought to be enough for anybody", then designed MS-DOS to enforce this limitation.

The truth is of course a little more complicated than that.

With the launch of Android 8.0 last year, Google released Project Treble into the world. Treble was one of Android's biggest engineering projects ever, modularizing the Android operating system away from the hardware and greatly reducing the amount of work needed to update a device. The goal here is nothing short of fixing Android's continual fragmentation problem, and now, six months later, it seems like the plan is actually working.

Korli continued his work on 32-bit applications support for x86_64. He now has most of the binary-loading, commpage, signals, and syscall system changes merged, though there are still a lot of pending changes to fix individual syscalls and then start applications in 32-bit mode.

But I think the reason that this year's WWDC felt a little Googley is that both companies are trying to articulate a vision of computing that mixes AI, mobile apps, and the desktop. They're clearly heading in the same general direction.

The computer industry is full of noble failures. Big ones. Little ones. Ideas that were 10 years too early. Ideas that were 15 years too early. Ideas that were 30 years too early. And concepts that, while fundamental to the way that our computing culture works today, hadn’t yet reached their full potential. Though certainly successful in its early years, the ARM processor very much fits in the latter category. Today, variants of these processors are in just about everything, from tiny computers, to smartphones, to video game consoles, to television sets, and even some servers. But the company that initially forged the processor is almost forgotten at this point, seemingly lost to history (especially outside of Europe) despite being an early icon of British computing. Tonight's Tedium ponders the story of Acorn Computers, the long-departed company whose best idea is probably in the device you're using to read this.

Better start saving up for that PlayStation 5, Xbox Two, or Nintendo Swatch (that last follow-up name idea is a freebie, by the way). That generation of consoles might be the last one ever, according to Ubisoft CEO Yves Guillemot. After that, he predicts cheap local boxes could provide easier access to ever-evolving high-end gaming streamed to the masses from cloud-based servers.

Windows Insider Preview build 17686 includes a hint that Microsoft may soon allow users to "switch to S mode". If true, the software giant may finally reverse on of the worst design decisions in Windows history.

You can see this hint by opening the Settings app and typing S mode. As you can see in the shot above, Settings provides a search hint for a Settings interface called Switch to S Mode.

It's a Monday night in Bristol in July 1983. Your parents are downstairs watching Coronation Street while you skulk in your bedroom under the pretence of doing homework. In reality, you're hunched over your cassette recorder, fingers hovering over the buttons in feverish anticipation. A quiver of excitement runs through you as a voice from the radio announces: "and now the moment you've all been waiting for..." There's a satisfying clunk as you press down on play and record simultaneously, and moments later the room is filled with strange metallic squawks and crackles. "SCREEEEEEEEEEE..."

You're listening to the Datarama show on Radio West and partaking in the UK's first attempt to send a computer program over local radio. Joe Tozer, who co-hosted the show, recalls how it all began: "I think it was just one of those 'ping!' moments when you realise that the home computer program is just audio on a cassette, so why not transmit it over air? It just seemed a cool idea."

My project is both simple and complicated. I want to add to ReactOS an option to install on and boot from BTRFS partitions. There are a few little things left to implement this:

• BTRFS support in bootloader.
• Fixes in cache controller and memory manager in order to boot with WinBtrfs driver. It is getting better every week, but right now used only with fastfat driver for FAT32.

My primary goal for this internship is implement BTRFS support in FreeLdr - our bootloader.

Because the Developer Tools teams (especially .NET and Roslyn) do so much work in GitHub, you'll start to see check-ins that indicate that we're laying the foundation for Visual Studio 2019, and we're now in the early planning phase of Visual Studio 2019 and Visual Studio for Mac. We remain committed to making Visual Studio faster, more reliable, more productive for individuals and teams, easier to use, and easier to get started with. Expect more and better refactorings, better navigation, more capabilities in the debugger, faster solution load, and faster builds. But also expect us to continue to explore how connected capabilities like Live Share can enable developers to collaborate in real time from across the world and how we can make cloud scenarios like working with online source repositories more seamless. Expect us to push the boundaries of individual and team productivity with capabilities like IntelliCode, where Visual Studio can use Azure to train and deliver AI-powered assistance into the IDE.

Our goal with this next release is to make it a simple, easy upgrade for everyone - for example, Visual Studio 2019 previews will install side by side with Visual Studio 2017 and won't require a major operating system upgrade.

Developer conference season is coming to an end with Apple's WWDC this week, and the main takeaway is that between Google's "Digital Wellbeing" and Apple's "Screen Time", the two biggest smartphone developers are taking some time to discourage smartphone overuse.

On the surface, the two companies are taking very similar approaches with the tools they're offering to present information to users. Apple and Google are both adding new dashboards, with options for more zoomed-out perspectives on how you're spending your time, along with more granular views of how often you're using individual apps - down to the minute. There's data on how many notifications you've received, where they're coming from, and breakdowns of when you're actually on your phone.

Apple has one hardware-specific feature planned that wasn't announced at Monday's WWDC keynote. In iOS 12, users will be able to use Live Listen, a special feature previously reserved for hearing aids certified through Apple's Made for iPhone hearing aid program, with their AirPods.

After enabling the feature in the iPhone's settings, users will be able to use their phones effectively as a directional mic. This means you can have AirPods in at a noisy restaurant with your iPhone on the table, for example, and the voice of whomever is speaking will be routed to your AirPods.