Linked by Thom Holwerda on Sat 26th Nov 2005 17:02 UTC, submitted by Megatux
"I followed the debate about a successor for the C/C++ combination as the primary language for developing the GNOME core desktop platform very closely last month. There has been discussion about a number of options. What I would like to do on this page is give an overview how a probably less well-known language might be a viable compromise as a C/C++ successor. This language is called Eiffel and exists for over a decade. Eiffel takes the principle of Object-Oriented programming to its extremes and, as a consequence, is a very easy to learn language."
Thread beginning with comment 64981
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: There are easier ways to kill GNOME
by corentin on Sat 26th Nov 2005 18:44
in reply to "There are easier ways to kill GNOME"
Member since:2005-08-08
> Using an exot like Eiffel would drain the source for fresh developers even more and therefore switching to Eiffel (or any other exotic language) would effectivly kill the GNOME project quickly.
Eiffel is NOT a language for the language lawyers; it is designed to be very simple to learn, write and read. Its syntax is very straightforward.
Unfortunately, this is a not so known language, so using it in GNOME would be a very good thing to make it much more popular.
RE[2]: There are easier ways to kill GNOME
by rayiner on Sat 26th Nov 2005 18:50
in reply to "RE: There are easier ways to kill GNOME"
Member since:2005-07-06
Syntax is largely immaterial. A little bit of a learning curve is no problem for something you're going to be using to build very large programs. The question really is semantics. It seems to me that Eiffel hails from the same side of the language debate as Pascal, and honestly, in this day of highly dynamic languages like Ruby, Python, and even Objective-C becoming popular, do we really need to retread that old road?
RE[2]: There are easier ways to kill GNOME
by Ronald Vos on Sat 26th Nov 2005 20:39
in reply to "RE: There are easier ways to kill GNOME"
Member since:2005-07-06
RE: There are easier ways to kill GNOME
by CaptainPinko on Sat 26th Nov 2005 19:26
in reply to "There are easier ways to kill GNOME"
Member since:2005-07-21
With enough exposure the community can build itself. Kinda like advertising. You already have a captive audience. Get a few key Gnome people to hype it up. Release a killer application written in Eiffel to draw a little more attention,to it. Then you have a small but decent group of curious and/or sold developers. From ther let it snowball.
Look at how one guy got sold on Haskell and suddenly you have the Pugs project.
RE: There are easier ways to kill GNOME
by on Sun 27th Nov 2005 16:10
in reply to "There are easier ways to kill GNOME"
Member since:News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
The new WebKit Opera for Android has been released. "Opera 14 for Android is built on top of Chromium 26, with a total overhaul of the UI in native code, making it fit well with the latest Android design guidelines. Go get the build from Google Play or point your browser to m.opera.com, and give it a spin!"
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."More News »
Sponsored Links
Member since:
2005-07-06
You forgot one important criterion: The programming language you choose must have broad support among developers as otherwise you run out of volunteers doing the work quickly. GNOME already as a problem to find new developers when using a popular language like C. Using an exot like Eiffel would drain the source for fresh developers even more and therefore switching to Eiffel (or any other exotic language) would effectivly kill the GNOME project quickly.
If you need a proove, just look how much the Java vs. Mono vs. Python battle splits the community already.
Edited 2005-11-26 18:35