pauljohncleary

This is a really important point, having seen both public and private systems I think it's quite valid.

In this case I probably would not want a head of orthopaedics to treat a relatively straightforward leg break- I would want a practitioner who has a significant amount of recent experience in this area. The ER doctor likely sees hundreds of these a year, so may actually be the best person. Of course if my case is particularly challenging, I want a consultant with a significant amount of experience- but it doesn't seem right for that person to pushing their skills to the highest bidder, regardless of patient need.

I also don't want a steak with my meal, nor do I care for a fancy waiting room, as they aren't going to fix my leg.

...and be put on the list of state enemies?

it's a tax on organizational size

and well spent taxes aren't a bad thing, in fact, they're a great thing

something being on your property is not the same as possessing it

Switch to Firefox and only use fully reviewed/approved addons if you're serious about this. I just put a ported chrome extension through the full Firefox add on review process (thanks to web extensions they're easy to port now), and those guys rejected my extension twice because they couldn't replicate my minified code from my dependencies to the exact byte.

Chrome web store doesn't care what I upload and push down to my users. I've had numerous requests from spammers looking to buy my extension based on the number of users and their geography. I guess once they buy an extension they push malware down to the users, so even if you can trust the extension developer or source now, you can't keep that trust up indefinitely.

With cricket the player's intent is not considered unlike many other sports and in courtroom trials. So looking at the most minute detail (e.g. the snickometer, the checks if the ball made a "snick" sound passing the bat, indicating contact) makes sense to the sport.

it's almost unreadable on a widescreen monitor

Extensions are a form of vendor lock in, Google were killing Mozilla in that space because:

- network effects (chrome is more popular than ff)

- chrome extensions are so much easier to write than XUL ff extensions

Now webextensions are implemented in FF, it's incredibly easy to port extensions across (I ported one earlier this week, took about 20 minutes!)

Tree style tabs and all that jazz aren't going away yet.

It's a killer move from Mozilla and makes FF a first class citizen of the web again.

You can do something similar with voting "credits" instead of cash, everyone gets 100 and they can use them to vote on the things they want

I've done this to help elicit requirements from stakeholders and it works really well

Fair point, recent updates to Meteor (1.3) have made it much easier to use with the rest of the JS ecosystem (e.g. using react with meteor is as easy as using the default view library).

The reason you have all of this boilerplate setup with react is because it's only one small part of the equation, so you need to use and (ideally) understand a bunch of other libraries and tools to build something, hence these epic tutorials.

> the same frustrations when I was looking at things like meteor

The main strength of Meteor is the speed you can get up and running

  $ meteor create my-app-name
  $ meteor npm install
  $ meteor

will set you up with a full stack application, running locally, with zero config

I'm from the rest of the world and I do ;-)

> Wunderlich's converted value should really be stated as "ninety eight point something" if one is being honest.

or we could, you know, agree on a standard and just use that...