I see that a couple of popular restaurants that have been around for at least a decade are still not shown, but maybe that is anomalous? I'll have to re-consider OSM.
76 karma · joined July 1, 2016
I see that a couple of popular restaurants that have been around for at least a decade are still not shown, but maybe that is anomalous? I'll have to re-consider OSM.
We only need the places API for having a comprehensive list of nearby places. Other services had too few places in general, but didn't necessarily lack information about the places that were available.
We could switch to using OSM + Places, to at least partially alleviate our problem, except that Google requires any Google Places API results that are displayed on a map to be displayed on a Google Map, which really locks us in.
Is anyone aware of a good Google Places API alternative, including any paid self-hosted databases?
1. Hardware manufacturers be separated from software manufactures
2. All hardware sold must have available appropriate documentation to write software for it.
3. Hardware and software be purchasable piecemeal, even when also available as a pre-configured bundle.
For example, for Google to sell a Google Home device they would:
1. Have to have a company, Google Home:Hardware, that produces the physical device and it's documentation
2. Have a company, Google Home:Software, that implements the software for that device, and perhaps bundles it.
3. These companies can collaborate, e.g., through support contracts, but any documentation made available to Google Home:Software must also be made available to purchasers of the physical device, separate from Google Home:Software.
Advantages of this approach:
1. This supports the "Right To Repair" movement.
2. Production of hardware has a very high cost-of-entry relative to software, making it prohibitively expensive for new entrants to compete. This allows smaller entrepreneurs to build software on existing hardware designs, bringing new features to consumers.
3. New competition will help to naturally break the anti-consumer monopolies and oligopolies currently existing, because they will have to compete with features that they currently refuse to implement, fix issues they currently refuse to acknowledge.
4. As a re-iteration of 3, would provide more consumer choice. Where as right now an individual may like the hardware features of one television set, they may dislike the software features if it (privacy invasion and phoning home?). Consumers could mix and match.
Although I've focused on tech with Google, this is applicable to many industries: smart phones, TVs, smart home devices, farming equipment, vehicles, robotic vacuums...
The parent is suggesting that there are other topics that people feel are important and want to discuss, and your dismissive response seems to be, "We have all of these other things to discuss that I think are important, without justification, we don't have much more room for what you want to discuss, so you need to justify it for me."
Why is anything worth discussing? Because people think it is! It should be self-evident! Enough people mis-understand enough things that we got this new incompetent president; maybe we aught to discuss what they want more so that we can all be on the same page?
I agree with you; the things you mention are worth talking about, but so are many things that are shouted down and we have room to talk about them all.
In fact, I am pretty left-leaning, as are most of my friends, co-workers, social-circle, and neighborhood.. Trump is not popular in the context of my life.
However, I don't agree with all of the left dogma. While I can talk frankly about my criticisms of those topics with close friends, even polite and genuine questioning of some left-dogma has been met with immediate vitriol by otherwise friendly acquaintances, despite having not made any statement of judgement, and otherwise agreeing on most topics!
If you grovel down and frame your discussion as "I am dumb, educate me!" they are willing to have a happy discussion where they tell you their opinion.
On the other hand, if you are mildly informed and frame it as "I question a few things and want to discuss for introspection's sake", you are in for a dismissive discussion.
Scorning introspection is very unhealthy.
Meatball Wiki[0] might be close to what you are looking for? From the about:
> Meatball is a LearningCommunity of the leaders of online communities--their proprietors, developers, mentors, and samaritans. We explore what it means to build an online community or, perhaps better, a community online. As it is a community, it is defined solely by the personal relationships that form it. Our breadth of interest is fairly wide as we take a holistic stance to community development. What differentiates us from many online meta-communities is that while we do talk about technology, we spend more time talking about sociology; and when we do talk about technology, we do so in a social context.
The reason Lodash is able to do this is because the collection is wrapped in an a special object that keeps track of all of the functions you call on it. Those functions don't run until you call .value() on the whole pipeline that you have setup, and then the optimization happens.
Note that this requires a separate API. One API returns your results immediately, the other (lazy) API instead returns a wrapper object after each call without yet doing the mapping/filtering/etc, ready to add more instructions to the pipeline that you must ultimately call .value() on in order to actually run.
Native functions don't have this separate lazy API that does the wrapping with this special object, and don't have/return an object with a similar .value() method.