re the map - one can definitely say the current map system based on EU3 is not "Dumbed down" - if anything it has been made much more flexible and user-friendly compared to the old map system, which requires very specialized tools and hours of work to effect even the smallest graphical changes - check out the various map mods that have been developed since the release of EU3, in particular the MEIOU mod, to see what can be done with the new map system, and remember that with the HoI3 map there will be a much bigger canvas to work on compared to EU3.
Compared to the absolute pain in the rear trying to mod the EU2-engine based maps where everything is hardcoded and integrally part of the drawn map, the maps in the EU3 engine are much, much, much easier to edit to your own personal preferences. Province names are no longer drawn on the map as in the EU2-series maps, but are a graphic element over the map, much the way sprites are. The map itself is much easier to mod, just redraw the base province map (and adjust the topography and river maps if felt needed, though those are separate and thus can be left as is when changing province borders) and voila, you can change the map.
Now, all this flexibility does come at a price - because the smallest graphical unit is a pixel, and most provinces are going to be only a few dozen pixels square at most, there is going to be a degree of "blockiness" to the map that simply can not be avoided. Even with the HoI3 map being 3x the size of the EU3 map, the simple reality is that the overall size of the map means that a pixel in size will be more than a few dozen square miles, making it rather more difficult to represent a potential perfectly "smooth" border. It would only be possible to have "smooth" borders if the base map were to be something say 9x the size of the EU3 map (something say the size of the Clio map project I'm working on for Victoria, which has dimensions of approx 30Kx12K pixels), so that individual pixels represent a much smaller area of land and even the smallest provinces would be several hundred square pixels square in size. And a map that size, with all of the functionalities of the EU3 map, would likely require everyone to have super-power graphics cards that few today have. Most computers, facing a map as large as Clio based on EU3's map structure, would probably seize up.
In the end, if the exchange has to be made between artisitic look and functionality, I'd say the better choice is to go with functionality, not just because it means that many more systems will be able to use the maps in game, but because it means the map itself will be customizable to a degree almost unimaginable before the release of EU3 a couple years back. And this is not just a perk for the modders, even casual players can benefit by being able to make quick changes to maps like changing province names, the location of sprites and the like, with only a couple minutes of file tweaking. Hopefully in a few years, the technology will increase further so that you can have even larger base maps than the proposed HoI3 one, and once that happens, and the pixel ends up representing a much smaller area of real estate, will you be able to have those "smooth" borders that the EU2, Victoria and HoI2 maps have.
Compared to the absolute pain in the rear trying to mod the EU2-engine based maps where everything is hardcoded and integrally part of the drawn map, the maps in the EU3 engine are much, much, much easier to edit to your own personal preferences. Province names are no longer drawn on the map as in the EU2-series maps, but are a graphic element over the map, much the way sprites are. The map itself is much easier to mod, just redraw the base province map (and adjust the topography and river maps if felt needed, though those are separate and thus can be left as is when changing province borders) and voila, you can change the map.
Now, all this flexibility does come at a price - because the smallest graphical unit is a pixel, and most provinces are going to be only a few dozen pixels square at most, there is going to be a degree of "blockiness" to the map that simply can not be avoided. Even with the HoI3 map being 3x the size of the EU3 map, the simple reality is that the overall size of the map means that a pixel in size will be more than a few dozen square miles, making it rather more difficult to represent a potential perfectly "smooth" border. It would only be possible to have "smooth" borders if the base map were to be something say 9x the size of the EU3 map (something say the size of the Clio map project I'm working on for Victoria, which has dimensions of approx 30Kx12K pixels), so that individual pixels represent a much smaller area of land and even the smallest provinces would be several hundred square pixels square in size. And a map that size, with all of the functionalities of the EU3 map, would likely require everyone to have super-power graphics cards that few today have. Most computers, facing a map as large as Clio based on EU3's map structure, would probably seize up.
In the end, if the exchange has to be made between artisitic look and functionality, I'd say the better choice is to go with functionality, not just because it means that many more systems will be able to use the maps in game, but because it means the map itself will be customizable to a degree almost unimaginable before the release of EU3 a couple years back. And this is not just a perk for the modders, even casual players can benefit by being able to make quick changes to maps like changing province names, the location of sprites and the like, with only a couple minutes of file tweaking. Hopefully in a few years, the technology will increase further so that you can have even larger base maps than the proposed HoI3 one, and once that happens, and the pixel ends up representing a much smaller area of real estate, will you be able to have those "smooth" borders that the EU2, Victoria and HoI2 maps have.