254 karma · joined June 5, 2014
If you have multiple workspaces that you switch between, you have to install your plugins into each of them.
It's legalized genetic discrimination, and no protections on how the data can be used (or who it can be sold to).
Maybe MS has tried to clean that up recently, but it has a track record of inaccuracy, at best.
I wouldn't be surprised if the Wine developers were the ones submitting the corrections to the MSDN, anyway.
But I am convinced this good will was a ruse, a charade, to excuse their questionable business practices at the the expense of the consumer. Advertising directly inside the O.S. is a good example.
And we, who reaped the benefits of this goodwill, are more likely to turn the other cheek when they are out of line - especially if (god forbid) our product relies on Windows.
"Oh, that's just Micro$oft being Micro$oft again."
"But what about all the good things they've done lately?"
"Once Scott returned to the ground, the length of his telomeres returned to his pre-flight levels relatively quickly. "
One thing not mentioned in the article is you can interact with htop using the mouse, for example clicking on column headers to sort by that column, or selecting a process.
You can get get this mouse support for example by installing the gpm package, which enables the mouse support for the terminal.
The universe is fake? Is this along the same lines as "everything is a simulation"?
Or worse even, they use a Facebook discussion plugin, so whatever you say is attached to your Facebook account.
1. The plane has to be at a safe weight to fly. I'm ok with this.
2. The airline wants to charge more money for heavier passengers. This is getting into discrimination territory.
But because of the Github thread and HN thread, this proposal is finally getting a fair shake by the public dev community. So, that's good at least :)
The main issue regarding the proposal and its sudden withdrawal seems to be an all-around lack of transparency.
* Each directory authority generating a random hash at midnight, a "global random value", no info on how this will be used yet.
* "Single" Onion services, dropping the anonymity requirement on specifically configured Onion Services to improve bandwidth (Possibly motivated by Facebook?)
* Dropping the TAPS handshake in favor of NTOR handshake.
The two big reasons I see every day are:
1. Cryptography is difficult to use effectively, and it's not getting easier fast enough.
2. Cryptography and security are seen by users as the developer's problem, and seen by developers as the user's problem.
Also, why is every response with a hint of negativity towards google getting down voted?
If Google was doing the right thing, they wouldn't have to be shielded from online criticism.
Remember Microsoft in the 1990's, remember the massive Antitrust case about IE?
Perhaps the people providing the Environment shouldn't be the people designing the language?
Google is very quickly turning into 1990's Microsoft.
I'm starting to wonder why these TC's have so many Google employees, and you can claim it's because "they hire a lot of smart programmers", but the ratio of Googlers to not is way too high to represent the web development community as a whole - the majority of whom do NOT work for Google.
Google trying to strong-arm control of JS for themselves.
Will the Qubes Team be sharing a portion of their commercial profit with members of the Open Source Community who have previously contributed to Qubes OS?
Don't be afraid to say "no" to the client, especially if you have given them an honest estimate and they are pushing you to revise the estimate downward.