I don't think anyone from Waze ever said not to map POI's. It was the Waze community's recommendation not to map POI's in the Waze map if your country has good POI data via the other search options in the client (Google, Bing, FourSquare, Yelp, etc.)
Here is why POI's should generally not be mapped in the Waze Map Editor:
* There is no ability to add POI details that show in the client with a search - phone number, address, etc.
* Since there is no ability to add these details it makes it difficult to determine which location you want to go to for common searches. Eg. if you search for McDonalds is it helpful to see the street address in the search results to help you determine which location you want to go to. Also very helpful to click on the phone number if you want to call to see if the POI is open, etc. The external providers POI data contains these details.
* If some editors are mapping some POI's, these POI's will show up in the default Waze search results even if they are hundreds or thousands of miles away. Eg, if someone adds a POI for McDonalds in Oregon and I am searching in San Diego my Waze client shows me the location in Oregon in the Waze results instead of showing one of the better options that shows relevant data.
* POI's that are added need to be maintained. Restaurants, stores, etc are always changing. If the POI is added and it changes, the data is wrong until someone finds and edits it. There are already great sources of this data that are being updated, why do we need yet another source of POI data?
Really in countries such as the USA only Parks and large POI landmarks that should show in the client map view should be mapped. Leave the rest out.
Again, this may not be relevant for other counties that don't have good POI data via the other providers.
Wazer in San Diego, California USA and Tijuana, Mexico
iPhone 6 Plus, iOS 8.1.3, Waze 3.9