Nacraile
This is just incorrect.
If you talk to HPE, they should be quite happy to sell you the my employer's software (Qumulo) alongside their hardware. 10+ PB is definitely supported. (The HPE part is not required)
If you talk to Dell EMC, they will quite happily sell you their competing product, which is also quite capable of scaling beyond 1-2PB.
> “It’s a way to compensate people who really believe in us in the beginning,” Schiermeyer said. “That’s how we’re structuring the blockchain. The people who were first to play it are going to get more than people who are last to play it. So, I mean, there’s definitely a reason to come in.”
So, uh, it's a pyramid scheme, thinly disguised as a game?
"the third-child deterrent appears stronger among wealthier families"
So this has both the most and least effect on families that have little reason to care about needing a bigger car (because they can easily afford it, or they can't afford any car at all, respectively). When you go fishing for a correlation, form a post-hoc hypothesis for its mechanism, and then other data fits that hypothesis poorly, it's a strong sign you've found yourself a red herring. Which is the usual result of failing to properly understand the distinction between correlation and causation.
For those times when I really just want to play a specific game that's Windows-only, dual-boot works great. I couldn't care less if telemetry tells Microsoft I start my PC every few months to play a few games ;)
I'm pretty skeptical that there are many real cases where eliminating Windows as a primary OS is a matter of "can't" and not "don't care enough to tolerate an occasional minor inconvenience". The latter case gets little sympathy when they complain about Microsoft's bad behavior.
Skiing does make for some examples of a couple weaknesses in the heuristic, though:
First the "best equipment you can afford" part is pretty poorly defined. Suitability of ski equipment is contingent on the skill of the skier and the type of skiing, so you can't just pick the most expensive thing and expect it to be the best for you. Skis are especially nasty in this regard in that the most expensive equipment often makes performance trade-offs that are actively hostile to beginners or use in the wrong conditions.
Additionally, ski equipment is consumable (at least in the hands of an aggressive skiier), which largely invalidates the cost-optimization rationale of the heuristic.
Skiing probably wants a somewhat modified heuristic, along the lines of "Start with the cheapest tool, use it until it wears our or you find an intolerable problem, and then choose a replacement that solves the problems with the previous iteration."
Still a compelling result, but not quite as incredible as it sounds in the article. I'm not sure what the p-value would be.
That's nowhere near the worst-case "bad tenant". The worst-case scenario takes months to evict and leaves behind tens of thousands of dollars of property damage. There might even be some personal harassment thrown in just for good measure. Avoiding such a tenant is absolutely worth missing some opportunities to fill the property with a paying tenant.
Not that missing rent this April 1 is likely to tell you much about that particular risk.
2. In outer tmux, ssh to some other machine you need to administrate.
3. screen because you need multiple terminal sessions on that machine, or need detachability/reconnectability for some long-running process.
I really don't know how this response surprised any of their employees (as a previous employee, it certainly does not surprise me). Those who can't abide it oughtn't work there; this isn't something that is going to be changed from the inside.
Although I'm not sure why I bothered typing that, given the current readings I'm getting on my troll detector.
This argument can be applied to your definition just as well as it can to my definition. Which underlines the pointlessness of arguing over the definition of "open source", and therefore the pointlessness of telling somebody that their thing is "not open source".
No. Everybody who disagrees with these has been driven from your ideological bubble. "Open source" has become a general term that is part of the natural language; nobody has the right to demand everybody use their preferred definition. Many people who use the term will never have visited gnu.org or opensource.org. Many others will have, but will have concluded that the strictness of those definitions is silly. It seems quite reasonable to disagree with a definition of "open source" that makes it practically impossible to make a living off of your work. If you want to have a debate on the merits, fine, but running around telling people they're using English wrong because they disagree with you is just foolish.
Is this actually a problem, or even particularly surprising? Remote positions provide massive non-monetary benefits to employees (flexibility in general, but particularly: you can live wherever you want, including on the road, with no commute, in low cost-of-living areas, closer to other things you value, etc). These benefits attract more applicants, which alters the supply/demand balance, with predictable effect on market salary. Remote work should be understood as a win-win, where the employee gets significant quality-of-life and maybe reduced cost of living in exchange for somewhat reduced salary, and the employer gets significantly reduced costs (directly in terms of salary and office space, indirectly in terms of easier recruitment) in exchange for (maybe) somewhat harder management. If you don't like the employee-side trade-off, tough to be you, because you're competing against a lot of people who do.
> when it's remote you compete with people in India, China
It's not clear that this is really true. It's relatively easy to run a distributed organization that has a common native language, legal system, and continent. Language barriers, massive timezone discrepancies, and ..challenging international legal systems make successful management much harder. In practice, it seems that many companies are unwilling to take on those costs and risks.
This is certainly a pain, but it's hardly the first time a broken kernel has shipped. Reasonable recovery mechanisms are in place.
The issue, I think, is that the specific name doesn't really add anything to the discussion: you don't actually contact Hamano and get his perspective, and you don't use the name to link any additional relevant information. You could omit the name entirely without detracting from what you're trying to say.
Including the name makes the (public!) criticism needlessly personal. Not really cool.
See: https://arstechnica.com/security/2017/05/an-nsa-derived-rans...