Language Selection

English French German Italian Portuguese Spanish

Enlightenment E17 - A Detailed Look

Filed under
Reviews

My first Linux experiences came through Knoppix and Mandrake, which send you to the KDE desktop by default. I used KDE at first, but I wanted to experiment with other less Windowsesque environments. The first one I installed was Enlightenment 16, which I must confess I had first heard of in Neal Stephenson's essay "In The Beginning There Was the Command Line.” In that essay he said Enlightenment "may be the hippest single technology product I have ever seen" and that "it looks amazingly cool." Since these sentiments were written in 1999, plenty of rivals have emerged for the title of “hippest tech.”

Once I had Enlightenment installed on my laptop there was no going back. I tried out a few other window managers, but the efficiency of E16 was hard to beat. My only complaints were that Enlightenment seemed a bit short on conveniences such as launchers, so I ended up running GNOME stripped down to one panel and the main menu with E16 as the window manager. Meanwhile, I read the descriptions of the new "desktop shell" that the Enlightenment crew was working on, dubbed Enlightenment DR17 (or E17, as I'll refer to it from here on) and thought it sounded like exactly what I wanted.

The Full Monty

More in Tux Machines

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more

The OS LinuX Desktop

Reader Oliver wanted to make his Linux Mint desktop look as much like a Mac as possible so others would find it easy to use. Given some of our previous Linux featured desktops, we know it wasn't tough, but the end-result still looks great. Here's how it's all set up. Read more

A Linux Desktop Designed for You

Desktop environments for Linux are not released ready-made. Behind each is a set of assumptions about what a desktop should be, and how users should interact with them. Increasingly, too, each environment has a history -- some of which are many years old. As you shop around for a desktop, these assumptions are worth taking note of. Often, they can reveal tendencies that you might not discover without several days of probing and working with the desktop. Read more