437 karma · joined December 12, 2009
For example the configuration changes - instead of gconf, you now have mateconf, which uses a whole other set of files that are not compatible with gnome. So switching from an old Gnome desktop (say) to Mint+Mate means your settings are all lost, even though the forked code between gnome2 and mate is really close.
On a default LMDE install it adds gnome-terminal and mate-terminal, so on the menus you have 2 "Terminal" entries. Ditto for a load of other core applications that are in Gnome and Mate - stuff like Archive Manager, screenshot, and document viewer. Was there really a need to fork file-roller?
Debian have already pretty much said "no" to including Mate - the reason being that the duplication and resuscitation of crufty old code is not a good idea. It would be better, the say, to work with Gnome upstream to get a more Gnome2-ish feel in Gnome3. I think Cinnamon is in Debian or will be shortly, which probably has a brighter future.
Anyway, for now I'm happy with Mate - it works fine and didn't need any tweaking to get to a usable state, compare that to Gnome3 classic-session on Ubuntu 12.04 which I spent weeks tweaking and patching (!) to get back to a state that worked like 10.04 - but I think its days are numbered. The Mint devs alone can't keep a full-on Gnome2-fork alive forever, it has too many duplicated applications that are already fine in base Gnome, and eventually I think Cinnamon will be the only viable option for Mint.
https://blogs.oracle.com/olaf/entry/jdev_including_a_classpa...
Shame a CSS hack can't get the sharing features back!
EDIT: ah, I see that this is likely to be a Wordpress generic thing.
2188
55 Objective-C
40 Delphi
36 Java
24 VB.NET
19 VB
16 Haskell
14 vb.net
13 Objective C
12 Scala
11 ColdFusion
10 VB.Net
10 ActionScript
9 HTML
8 R
6 Lua
6 F#
5 vb
5 PowerShell
5 objective-c
5 Groovy
There were a lot of "objective-c and some comment", so objective-c is even more popular. Other languages in there included: ocaml, assembly, klingon, tcl, fortran, COBOL, and quite a few matlabs.Here's the text file of that column for you to see for yourself http://pastebin.com/wMZUBMub
The problem is that Google can't penalize a site for using these technologies. And not because Google makes money from sites using these adverts, which they do, but because it'd be an arms race. The guys taking advantage of SEO would catch on and change advertisers. Google could penalize other advert networks too (Bing say), but then they'd be open to accusations of anti-competitive behavior.
1. You have to provide Amazon with all software that is yours on the Market 2. You have to add Amazon specific DRM to the apps you add to Amazon and cannot use any other DRM 3. There are privacy requirements on embedded advertising 4. The parentheses in the agreement are not well balanced! There are a lot of missing closing )s.
So you cannot pick and choose which of your software goes on Amazon and which on the Market. The DRM means you would at the very least need 2 versions of your software if you use Google's licence server "DRM" - one with Google's technology and another version with Amazon's.
I'd say that if you go the DRM route, you'd want to use Amazon or the Market, but not both. If Amazon turns out to be more popular with paying customer this could really have an impact. Especially the "all your Apps belong to us" requirement - I think having a free-with-adverts version of an App on the Market and a paid version on Amazon is forbidden under this agreement.
Policing rogue advertising is good, though I doubt Amazon will really kick anyone off for using AdMob or any of the big players.
Also, #4 shows that the agreement was not written by a Lisp programmer. It makes reading parts of the agreement tricky.
There's also http://code.google.com/p/android-market-api/ (OT: just me, or is the new Google Code look much more confusing/cluttered?), but that is not official in any way.
(FWIW I don't really like the "an" either, sorry!)
It doesn't fix outgoing mails, so when you plain text reply to the original author they'll get their "J" right back at them :-)
IMO the reason this has not been cracked wide open is that there are not enough DSi-only commercial games to make it worthwhile for the folks that create cartridges used mainly for unauthorized copying. Being able to copy and run DS-only games is enough.