It is fixing the following issue:
- NIM039250 - Replica system versions are not removed when synchronizing a 1 way or 2 way replica using connected synchronization
For the same cost, you can build your own supercomputer and it works just as well if not better. Plus, you can use it over and over again, indefinitely.
Microsoft and Google, and Yahoo to a large extent, are very much consumer-focused. They look at mapping and geospatial visualisation as one more aspect of search. It’s all about spatial search as an augmentation to traditional web search. This is a very exiting field; it concentrates on a global base map for visualisation and association.
They both become active in being able to support embeddable mapping for locator services and they are both spending between $100m - $150m, a year on developing content for that base map. The technology itself is highly optimised for fast visualisation access; it’s not a GIS system.
OpenCL (Open Computing Language) is the first open, royalty-free standard for general-purpose parallel programming of heterogeneous systems. OpenCL provides a uniform programming environment for software developers to write efficient, portable code for high-performance compute servers, desktop computer systems and handheld devices using a diverse mix of multi-core CPUs, GPUs, Cell-type architectures and other parallel processors such as DSPs.
New release v 3.0 of Python was released on two days ago on 3rd of December. There are some significant changes in this release as stated on the top of the page:
Python 3.0 (a.k.a. "Python 3000" or "Py3k") is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Also, the standard library has been reorganized in a few prominent places.
Some of the big changes are
Of course there is a more on What’s new page. This may make things more interesting for ESRI. ArcGIS is using Python as one of languages supported for geoprocessing. This will not be a problem from installation point of view because ESRI provides installer for it but from support and migration of existing models. I don’t expect ESRI to make a utility (but that would be nice) that would convert Python 2.X to 3.0 scripts. Most likely they will include some documentation like on what’s new page on Python.org or they will write up a smaller more focused document.
Anyway it is good to see these changes and hopefully that won’t cause too much trouble for GIS script developers.