HN user
It boggles my mind that Apple’s market position allows it to pocket $18 billion a year in pure rent for this real estate on its platform and the company paying is the one that gets an antitrust suit.
I just started using godo [1] and I like it so far. Implement tasks in Go, bash, or the provided wrappers around os/exec.
Biggest advantage over a generic tool like Make is that you can import your project dependencies (such as your database configuration) into your task.
By downloading a shared key over TLS rather than the provider's public key?
No difference from the perspective of the token consumer. From the perspective of they token generator, it means rotating per-tenant keys rather than a single keypair.
Also, issuing servers and verifying servers don't even need to be part of the same organization, allowing you to outsource credential management (see Auth0, Firebase Authentication).
Printed last Tuesday: http://mobile.nytimes.com/2016/07/12/world/europe/recep-tayy...
Beats has a track record of producing consumer electronics that are accepted as fashionable. The iPhone already blurs the line between tool and accessory and it spends most of its time in a pocket or purse. A smart watch or head mounted display is more visible and needs to overcome a nerdy bias to appeal to the mass market.
So the code to load the videos came in under 100KB. How large were the videos themselves?
What if you covered existing skyscrapers with hydroponic trellises?
As someone who typically has a Clojure repl handy, I found it convenient to be able to copy-and-paste and play around with the model.
Honest question, does AT&T inform customers living in areas without 3G coverage of that fact when selling them an iPhone 3G?
Even with msttcorefonts installed?
Appealing when presented in the abstract, but I have nightmarish visions of such a system.
On the one hand, you'd further motivate those consumers who were already likely to avoid preventive care and ignore symptoms until they require costly (to me as contributor to the catastrophic plan) emergency and intensive care. And the author's position that folks would be able to withdraw funds that exceed a certain ceiling adds the perverse incentive to risk not spending this money, with the downside being absorbed by the catastrophic plan.
On the other hand, you'd do nothing to discourage consumers with irrational fears about their health from distorting prices upwards, or to discourage unscrupulous providers from fomenting those fears. The plan he describes takes fee-for-service and all its problems to a whole new level. I think of things like the celebrity anti-vaccine mess and the healthcare debate with its distorted media coverage and disingenuous advertising, and I have hard time accepting a consumer-driven market succeeding, even with all the government-collected and -analyzed data in the world.
Even worse, I fear that such a system would result in a tiered system, where the best and brightest providers provide excessive care to those with means while the rest of us continue to struggle with barely adequate, barely affordable care.
I don't think that any system that relies on healthcare consumers making the choice between limiting their usage of healthcare services and spending money is destined for success. Providers need to be rewarded for providing the best outcomes for the lowest cost with the fewest mistakes, not the most and most expensive services. Significant efforts must be made to improve the public health of Americans. The conversation should be about how to make those things happen. All this debate about who pays when is just a side show that is obstructing real reform.
At least it's Clojure and not SciPy :)
It doesn't. Objects imply state and a set of methods to mutate that state, which is incompatible with Clojure's immutable-by-default design. Instead it provides tools that facilitate the same things as OO features: polymorphism via multimethods and inheritance via ad hoc hierarchies on names.