presidentscroob

I don't understand the point of this article, it comes across to me as sheltered people with too much spare time maundering over petty, victimhood-ology nothingburgers. First responders and third-world climate refugees have real trauma to deal with compared to the petty whining and whinging of sub/urban white-collar employees who don't know how good they have it.

Community (solidarity, cooperation, concern for others and knowing one's neighbors) is in steep decline in most of the US for many reasons, and especially in Silicon Valley because the vast majority of its denizens aren't settling permanently but are just in town temporarily to earn an income, so they care less about their surroundings or anyone else but themselves. Furthermore, higher income leads people to care less about others. (UC Berkeley Monopoly experiments)

Possible solutions:

- There ought to be a modern replacement for churches (the Atheist unchurches, multi-denominational churches), which were the focal points of communities for centuries.

- Civic involvement in local law-making and local concerns.

- Putting screens away to prioritize human interaction.

- Revive the art of small-talk.

- Less polarized/political interactions, seeking understanding of others' points of view (you can't persuade true believers of anything new if they're already in violent agreement).

- Take the lead to create new leagues for group activities: bowling, skiing/snowboarding, ultimate frisbee, etc.

Hackintosh or not isn't relevant because it's a macOS + Google update service issue.

PS: Written on a Hackintosh

Yeap. It's a completely worthless article. The more important numbers are:

0) cost-of-living adjusted income (for daily living expenses)

1) housing to yearly income ratio (housing affordability)

Absolute yearly salary is primarily useful data for non-local inelastic demand and luxury items that tend to not track local costs-of-living, i.e., a Tesla (sans tax credits) or a Nest thermostat.

Better articles:

https://qz.com/1195354/tech-salaries-in-austin-texas-are-eff...

https://www.techrepublic.com/article/the-10-cities-with-the-...

¯\_(ツ)_/¯ Maybe because you can't spell "there?" ;)

Maybe Python 2 can go away soon. Also, modern Python 3 support isn't even close to 100% either.

https://pyreadiness.org/3.7/

I'm disappointed by the deprecation and decay of features of DDG and Goog in recent years, it seems like the trend is toward dumbing-down.

It used to be that double-quoted strings meant "search for exactly this, not fuzzy searches". Now, DDG requires a plus sign in front of a double-quoted string. +"KS-19319ZJFT"

Also, way, way back, you could conduct elaborate boolean searches like (space equals implicit "and", so it's omitted):

    site:foo.com -site:docs.foo.com ((lemons "crab apples") or ((oranges beans) (cherries plums)))

Ideally, I'd like a syntax that looks like this:

    search = "( search ")"
           | "-" search
           | search ("and")? search
           | search "or" search
           | constraint
           | term

    term = quoted_term
         | simple_term

    quoted_term = '"'([^"\\]|'\\"')+'"'
                | "'"([^'\\]|"\\'")+"'"

    simple_term = [^'" ]+

    constraint = file_type_constraint
               | url_constraint
               | site_constraint
               | temporal_constraint

    file_type_constraint = "filetype:" (common_type|"*"?"."?[a-z0-9]+)
                         | "mimetype:" regex

    common_type = "video"|"photo"|"audio"|"email"|"web"|"document"|"text"

    url_constraint = "inurl:" regex
 
    site_constraint = "site:" regex

    time_constraint = "before:" date 
                    | "after:" date
                    | "within:" time

    /* "and," "or," and : prefixes should be case-insensitive and localizable */
    /* date, time and regex are "exercises for the reader" ;) */

It's a good pattern to DRY-up resource-releasing unwind code. In an ideal world, there would be closures, RAII and fluent interfaces (macros) that would wrap allocation, deallocation, error and success handling without needing C++ and avoiding resource leaks.

    int
    some_func(void) {
      int result = ERR;

      HANDLE foo = alloc_foo();
      if (!foo) goto err0;

      HANDLE bar = alloc_bar();
      if (!bar) goto err1;

      if (do_something_else() < 0) goto err2;

      result = OK;
    err2:
      release_bar(bar);
    err1
      release_foo(foo);
    err0:
      return result;
    }

Exactly. I was just at a community dinner for survivors of the Paradise Camp Fire, and reflected on the greater numbers of single, older men sitting by themselves. It's as if a segment of society is deemed like Detroit: unnecessary and left to rust in solitude in the fields. Americans are being atomized, divided and distracted from one-another into quiet, lonely, purposeless, idleness# and desperation#. # These two states that are explosive on their own, brought together are incendiary. Add conspiracy theories, no hope for the future and prevalence of firearms, and it's a recipe for stochastic terrorism, omnicide, suicide and revolution.

There's likely plenty:

https://www.quora.com/Is-there-enough-lithium-in-the-world-t...