Linked by Thom Holwerda on Fri 12th Jun 2009 18:25 UTC
Well, this is interesting. We already have a Mono item ruffling some feathers on OSNews today, but here we have the apparent news that Tomboy has become a default part of GNOME on Squeeze, the next release of Debian. Wait, what now? Update: I've updated the article with Fedora's position in all this. Read on! Update II: Josselin Mouette replies.
Thread beginning with comment 368591
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-07
Perhaps it's just easier to "call bullshit" on the other claims of Microsoft, when they refer to technology not developed by them.
Perhaps it is in a discussion forum but not in a court of law. This is why I am re-iterating that this is a software patent issue in general not a Mono specific issue.
MonoDevelop is of course a redundant app for non-mono world.
I wouldn't agree. MonoDevelop is a very good IDE and supports many languages other than Mono.
So, I figure the porting will only get easier in the future. We might not hear of "line-by-line" port success stories of gnote, but the porting effort in itself doesn't seem insurmountable.
A big benefit to Mono over C++ is platform independence. Applications should be relatively simple to port to alternative architectures and operating systems as long as Mono itself is available for the platform. C++ is a built more complicated in that regard.
The original point I was trying to make is that just because a simple app like Tomboy was ported doesn't mean that it's going to be as easy to port more complicated programs.
Member since:2008-12-26
This is why I am re-iterating that this is a software patent issue in general not a Mono specific issue.
It's a waste of breath to talk about software patents, generally.
I wouldn't agree. MonoDevelop is a very good IDE and supports many languages other than Mono.
We have those already, so this is not a "critical" app in any sense.
A big benefit to Mono over C++ is platform independence. Applications should be relatively simple to port to alternative architectures and operating systems as long as Mono itself is available for the platform. C++ is a built more complicated in that regard.
This is why I'd advocate people use C++ & Qt instead, if they insist on a "static" language. C++ with Qt is really not harder than Java / C#, and probably as/more portable.
The original point I was trying to make is that just because a simple app like Tomboy was ported doesn't mean that it's going to be as easy to port more complicated programs.
Probably true. But it's doable in reasonable time. What's important is who is willing to put in the resources, and where. Currently, some developers want to develop in Mono, and that's all fine and dandy. If some app becomes "problematic", it can be ported to C++ or Python (probably C++ - you'll want some significant runtime performance/footprint benefits if you are doing the porting in the first place); if nobody is willing to put in the time, then the app isn't/wasn't that important in the first place.
Member since:2009-06-16
So, I figure the porting will only get easier in the future. We might not hear of "line-by-line" port success stories of gnote, but the porting effort in itself doesn't seem insurmountable.
Redesign will be necessary for anything that makes use of reflection.
Also, wouldn't it be easier to write a compiler backend for Mono that outputs simple, portable C code? This fixes the portability issue, but not the size issue (CIL is smaller than the equivalent machine code in many cases); but if you have a framework that you expect people to use, you may as well bite the bullet.
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:
2008-12-26
Perhaps it's just easier to "call bullshit" on the other claims of Microsoft, when they refer to technology not developed by them.
MonoDevelop is of course a redundant app for non-mono world.
Here's an interesting relevant link:
http://www.figuiere.net/hub/blog/?2009/04/01/656-porting-to-cpluspl...
It mentions:
So, I figure the porting will only get easier in the future. We might not hear of "line-by-line" port success stories of gnote, but the porting effort in itself doesn't seem insurmountable.
In any case, even if we were dealing with a reimplementation instead of port, it's still easier because you can copy architecture (class structure) and algorithms directly.
What I'm saying is - it's not necessary to be terribly worried about Mono, as long as we have a good backup strategy.