Linked by on Sun 26th Feb 2006 16:17 UTC
ActiveWin reviews Office 2007 beta 1, and concludes: "It's an innovative interface yes, but will the benefits outweigh the changes? That's for users to decide. Yes this early code does have glitches and performance issues left to be ironed out; right now the focus is on reliability and stability. The BETA 2 release should provide us with an early glimpse of what's in store in the final product. My personal say is getting used to interface should not be a problem for many since the familiar tools are organized in ways that makes it convenient for the user, and new tools make the interface more intelligent and more aware of what the user is doing, presenting the right tools for the task at hand."
Permalink for comment 99595
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
The Verge pointed me to a blog post by Leap Motion - which reveals how their Kinect-like motion control works with Windows 8. "From the second you plug in your Leap Motion Controller, you'll be able to browse the web and interact with your computer just by moving your hands and fingers in the air. With Leap Motion technology and Windows, you can do everything that's possible with multi-touch inputs - without actually touching anything. This also means that existing applications in Windows 7 and 8 will respond to your natural hand and finger movements. Soon, we'll show you how Leap Motion will work with Mac OS X." Quite cool.
Linked by Thom Holwerda on 05/20/13 21:50 UTC
PocketNow interviews Marc Dillon, and there's an interesting note about why Jolla is keeping the display properties under wraps: "We're leaving some of those details out because we do understand that there are a lot of really big players in the market and they tend to take certain components in the market and dominate them. We created the ability to actually be able to run Sailfish on multiple hardware displays and be able to swap components, so this is part of the demand and supply planning phase. We are committed to this industrial design which is a 4.5-inch display, an 8 megapixel camera on the back and a front-facing camera at the front, and the exact specs of the display we'll provide when we're close to delivery." Something you rarely hear anything about.
Linked by Thom Holwerda on 05/19/13 23:15 UTC
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.More News »
Sponsored Links
Member since:
2005-07-06
Your entire argument is nonsensical. DOS is a rather poorly designed batch operating system while vi[1] is a text editor.
You also seem confused about the difference between text mode interfaces and GUI's. Vi is not a command line program simply because it can run in a text mode terminal. It is an interactive full screen program with many of the same features of any other text editor (graphical or not). The fact that vim[2] has a graphics mode interface makes this a rather moot issue.
The ability to multitask is not an intrinsic property of a GUI. Most any UNIX like system has virtual terminals, and let us not forget GNU screen which allows terminal multiplexing. Further, terminal emulators can be run inside of a graphics mode interface. In fact, a common usage of X11 servers is simply to run multiple xterms for the multitasking function. This brings us to the myth of the GUI.
Both technical and non-technical folks put forth the false dicotomy that one either must have a GUI or a command line. The two are not mutually exclusive. This myth seems to have stemmed from the popularity of the WIMP interface whereby the mouse has become the dominate input method and command lines are entirely absent or neglected. Of course, this is the reason why new comers to UNIX systems believe that it is some how backwards. UNIX users do not subscribe to the WIMP ideal[3] but rather keep the command interpreter and utilize the graphics mode server (X11) to leverage the greater output capabilities that it affords.
The important thing to realize is that one could write an application in a graphics mode environment and have it behave in every way that a full screen program would in a text mode environment and still leverage the output flexibility of the former. One does not need menus, icons and buttons to have a GUI. These symbolic devices simply emulate commands. The GUI as a concept is ill defined and nebulous.
It is also important to realize that usability does not imply a low learning curve. Vim (or vi) are not great because they are hard to learn. They are great because they are flexable and efficient. The fact that is difficult to use (debatable) at first is a side effect.
To end, I would like to point out that vi and vim are not the only text editors available on UNIX like systems. Emacs is another editor that is commonly used. In fact, there is still unrest between vi and emacs users. Which of the two are superior is still up in the air and I, quite frankly, don't care. The list doesn't stop there, either, for there are many more editors to choose from including the WIMP variety you cherrish so intensely.
[1] Linux systems usually symlink vi to vim.
[2] Vim is an improved (more features) rewrite of vi.
[3] KDE and GNOME provide a WIMP style interface which ultimately shows that attacks on UNIX are usually attacks on a particular UI. UNIX does not enforce UI policy nor does X11.
Edited 2006-02-27 09:15