Freenode Debacle Prompts Staff Exodus, New Network

It’s no secret that Internet Relay Chat (IRC) has lost some of its appeal in recent years. These days there’s plenty of free chat platforms boasting slick web interfaces and smartphone push notifications, to say nothing of social networks like Facebook and Twitter. The ability to communicate with like minded individuals from all over the planet in real-time is now something we take for granted, so it’s little surprise that newer and flashier protocols and services have steadily eroded the IRC user base.

But there’s often a hidden cost to using these more modern communication protocols. A lack of operational transparency naturally leads to concerns over monitoring and censorship, which makes such services a poor match for the free and open source community. As such, many open projects have eschewed these newer and more popular services for IRC networks that were developed and maintained by the community itself. Among these, the best-known and most respected is Freenode. Originally started as a Linux support channel in 1995, Freenode grew to become the defacto communication and support tool for free and open source projects of all shapes and sizes, and by 2013 had officially become the largest and most active IRC network in the world.

Unfortunately, the incredible legacy of Freenode is now being jeopardized by what former staff members are describing as nothing short of a hostile takeover. Through a complex series of events which actually started several years ago, control of Freenode has been taken from the community and put into the hands of an enigmatic and wealthy entrepreneur who claims his ultimate goal is to revolutionize IRC and return it to the forefront of online communication. Here’s where it gets weird.

Continue reading “Freenode Debacle Prompts Staff Exodus, New Network”

Terminal Magic With Notcurses

Writing a command line program that needs a little more pizzaz? Ncurses just not colorful or high res enough? Or maybe you want to bring the demo scene to the command line. Notcurses has your back. The demo is great, and looks like it can push out enough detail to pull off silliness like pushing an SNES game’s output straight to the console. What might be the most impressive element of the library is that while it can blit high res graphics through a terminal emulator with graphical support, it will also work on the basic Linux console, with no graphical system installed, by using some very old tricks. I know what you’re wondering: That’s all well and good, but can it run Doom? Yep. Come back after the break for a demo.
Continue reading “Terminal Magic With Notcurses”

What NES Development Looks Like On The Apple II

These days, if you want to code a game for the original Nintendo Entertainment System, it’s about as easy as downloading an assembler, firing up Notepad, and running the ROMs you cook up in any one of a variety of emulators. In the 1980s none of those things existed, and the process was a little more complicated – as demonstrated by [Tyler Barnes] in the video embedded below.

[Tyler] has put together a 40-minute guide on what it takes to get to “Hello World” – or more accurately, a simple pink screen – on the NES, using period-correct hardware. He starts the process by formatting some floppy disks and whipping up some basic assembly code on an Apple IIe, which gets run through the Merlin assembler for the 6502. It’s particularly convenient as the Apple II line and the NES both run the same CPU. From there it’s a case of using a standalone EPROM programmer to verify some appropriately-datecoded chips are empty, before programming them in a special add-on card for the Apple II. From there, the EPROMs are loaded into a cart custom modified with chip sockets, where it can be inserted into a NES for testing.

It’s a tedious process, with just the programming side of things taking on the order of ten to twenty minutes with a few fiddly steps along the way. While there are likely some efficiency gains to be had that were used by studios back in the day, it remains clear that development in this era was a much slower process.

Of course, if you prefer your Nintendo homebrew a couple generations hence, consider getting stuck in on the Nintendo 64. Video after the break.

Continue reading “What NES Development Looks Like On The Apple II”