0 A.D. Promises Real Gaming for Ubuntu


As a history Ph.D. student by day and free-software geek by night, I find that my poles of interest rarely converge. That’s why I was so excited when the real-time historical strategy game 0 A.D. was switched to an open-source license in July. I’ve been meaning since then to give it a try, and finally found the time and hardware necessary to do that. Here are the results.
Set in antiquity and designed with historical accuracy as a priority, 0 A.D. is a real-time strategy game that supports Linux, Windows and OS X. The developers, Wildfire Games, originally intended to distribute it as freeware, but decided to open-source the code last summer in hopes that it would speed the development process.
Why it’s great
0 A.D. is probably the only open-source RTS game besides Glest that attempts to bring to Linux users a gaming experience otherwise available only on Windows (or through wine, sometimes). Other strategy games for Linux exist, some of them decent enough to provide a few hours’ entertainment, but they’re mostly half-baked and lack the professional quality of their commercially developed betters, especially when it comes to art and gameplay.
-
- Login or register to post comments
Printer-friendly version
- 1245 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
GitLab Web IDE
| Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
|
Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
| Security: Updates, Trustjacking, Breach Detection
|
Recent comments
1 hour 6 min ago
1 hour 18 min ago
8 hours 10 min ago
1 day 10 hours ago
1 day 11 hours ago
1 day 16 hours ago
2 days 17 hours ago
3 days 23 hours ago
3 days 23 hours ago
4 days 11 hours ago