facebook has something like this internally (bunnylol), everyone's browser uses an internal search engine by default that parses the query into commands that can take args and often route to internal tools, etc
it's pretty neat, the open source version is called bunny1
Your comment is a little misleading...Rio Grande and Pioneer park are literally right next to each other. And other than those couple streets in that corner of downtown, you'd be hardpressed to find any other gathering of homeless people.
The Road Home (mentioned in the article) and a Catholic food bank and other homeless services are located in that area, hence the reason for the homeless density in that area.
In the early 2000s my dad left his cushy job as an electrical engineer at a nuclear power plant in eastern europe to come to the US with an H1B to fix AC systems for a company owned by an eastern european that only hired immigrants.
They would count the price of plane ticket, technical training classes, english classes, etc to a "debt" that you had to pay off. You would get paid a salary, but depending on how much money you made the company each month, this debt would either go up or down, and the company claimed you wouldn't be able to leave the company until you paid off this debt (eventually my dad figure out that this was not true or at least not legal, but this policy still goes on as we speak).
You can imagine most people who worked there struggled for years to pay off said debt.
How many spaces do you like to indent your code? Some people like 3 space indentations, some like 8 spaces, and some like 5. It's very personal (but anyone who doesn't use 3 is a reeky brazen-faced mammet).
A simple solution is to use tabs, because then every developer can set the tab distance however they like, and they are happy. It breaks down when you have code that is aligned beyond the indent, like this:
if(a && b &&
c && d &&
e && f ) {
In that case, increasing (or decreasing) the tab distance will ruin the intention.
The best solution is to use tabs to the point of indentation, and then spaces thereafter, but a lot of code editors don't support that, so in practice it's hard to implement, so people use spaces to preserve their formatting when it gets uploaded to github.
I say this from experience, not narrow mindedness.
Open a file where it is all spaces, and it looks the same on every machine. Open a file with a mix of spaces and tabs, and it often turns out an absolute mess.
Longer version: First understand that there is no tabs vs. space. There is only tabs + spaces vs. only spaces. (Because not all indentation line up with tab spaces, and someone may wish to line up assignments, lists, etc.) Only one developer in the history of your project that uses another tab stop standard is then enough to mess up your indentation. And that's just one way to mess it up, in a sufficiently large project some creative developer will find another.
Spaces just work and ensures your guidelines are followed. The only downside is a few wasted bytes. It might have been a religious debate in a long distant past when someone actually counted bytes, but today it's mostly young developers who don't know better who engage in it (with a few exceptions). Linus uses spaces. OpenSSL changed to spaces as part of cleaning up their codebase. It's the default behaviour of GNU indent. It is a good idea.
I personally like the idea of tabs better, but prefer spaces because it makes navigating the text less awkward when traversing tabs. It may sound stupid, but for my own stuff it's just more comfortable.
I imagine their content review platform, trust & safety tools, etc all have some designers working on them