Oh, I agree. A startup I've been advising is in the GIS space, and the old OSM license meant they had to use other map sources instead.
On one hand sharing modifications to base layers would not be an issue, but the business model revolves around allowing clients to upload their own layers, many of which they can't release for business reasons or in some cases legal reasons.
The old license meant a lot of effort was wasted on producing own base maps which could've gone into fixing issues with OSM instead (e.g. areas covered by customers include sparsely populated areas where both OSM and Google's maps are severely lacking, but where getting GPS traces of all the local roads that they could release would be easy).
The new license seems to be sufficient for their usage. The problem currently is just that it's vague. E.g. I think it's safe to assume that your example would be ok, but there's still a lot of grey areas. For the company mentioned above, I also think the new license is probably ok, but it'll take some time to review.
While on one hand the new license gives more opportunities for keeping data private in some instances, I think it'll actually result in more data released for the reason that it allows a lot of people that previously would never dare touch OSM data to actually use it, and so gives them a reason to contribute fixes and improvements.
On one hand sharing modifications to base layers would not be an issue, but the business model revolves around allowing clients to upload their own layers, many of which they can't release for business reasons or in some cases legal reasons.
The old license meant a lot of effort was wasted on producing own base maps which could've gone into fixing issues with OSM instead (e.g. areas covered by customers include sparsely populated areas where both OSM and Google's maps are severely lacking, but where getting GPS traces of all the local roads that they could release would be easy).
The new license seems to be sufficient for their usage. The problem currently is just that it's vague. E.g. I think it's safe to assume that your example would be ok, but there's still a lot of grey areas. For the company mentioned above, I also think the new license is probably ok, but it'll take some time to review.
While on one hand the new license gives more opportunities for keeping data private in some instances, I think it'll actually result in more data released for the reason that it allows a lot of people that previously would never dare touch OSM data to actually use it, and so gives them a reason to contribute fixes and improvements.