865 karma · joined March 14, 2008
I wouldn't have trusted either Bush or Obama with these powers. Government officials have proven time and time again that they don't always have the general populace's interests at heart. The saying "Absolute power corrupts absolutely" is the first thing to come to mind.
For instance, at $work we have a bunch of tables which are archives of raw click data. They are taking up quite a bit of space on disk, which we'd like to reclaim. Keeping the raw data around is good, since I want to create a summary table and you can't recreate raw data from summaries. The idea was to export the table data as CSV, and then when I had the time to for messing around with summaries I'd reload the data. With FDW I can leave the data as CSV and read it just like it was in a proper DB table. Win!
Or even better, again at $work we use Mysql. But I hate it because SQL strict mode isn't enabled and mysql does really stupid things with my data in "normal" mode. I can't safely turn on strict at this point because I don't have the time for testing everything. I also really like Pg and would love to switch. But again, I don't have the time to do it. What I've been thinking about is using the FDW capabilities (in particular the upcoming writable FDW in 9.3) as a way to safely and slowly migrate DB platforms. It's only an idea in my head right now, but it's an intriguing one.
Opinionated frameworks are great, until you need to do something they didn't anticipate. If you're lucky it's easy to work around, and if you're not then welcome to your latest nightmare.
The whole polyfill concept is exactly what the world needs to allow browsers to grow and mature at different rates.
The best I can relate it, is that I can take all the widgets that are used throughout the website and wrap them up into their own CSS and JS. No need for rigorous CSS namespacing, JS modules, etc. It's all packaged up, ready to drop into an HTML page. The most interesting part are the polyfills for the various Web Components, erm components, that are currently being drafted. At the moment, the polyfills have to implement most everything but eventually won't be needed when the specs are finalised and the browsers caught up.
I watched seasons 1 & 2 before I started reading the books, and now I'm more interested in finishing book 5 than I am in staying current on the TV episodes.
I expected the Dropbox notification. :) What I would like is a way to see where my photos are currently being stored, and a way to switch storage back from Dropbox to Trovebox (I only have 8GB of storage in DB).
1) How different is the OpenPhoto webapp from the Trovebox app? Does they support all the same features?
2) How does the Dropbox integration work? Can I move photos into the Apps/Trovebox folder and have them be automatically synced with the web site? I'm using the Dropbox Photo Sync feature, so it would be super handy to not have to re-upload them to Trovebox.
3) After signing up and uploading photos, I clicked on a link someone posted below to associate my dropbox account with the trovebox account. My photo upload was still going at the same time, and I started to get dropbox notifications about new files being added so I stopped the uploading. However, I can't see anything in the settings that tells me what storage back my account is using. How can I see/change it?
This is a very exciting app & service, which might be The Solution to sharing photos within my extended family!
All this reminds me of the famous quote from Jerry Maguire: "Show me the money!" Is there anything wrong with pandering to people's base desires, namely "If the government spends less money, we can lower my taxes without implications"?
My argument against them is simple: it's very hard to align the two goals of 1) making as much money as possible and 2) providing the best care possible, which in my mind means making their stay as short and inexpensive as possible. Even as a youngish person (late 30's), I don't want to go in the hospital at all and if I do have to go I want to be in and out as soon as it is safe to do so.
The ultimate goal is to keep people as healthy as possible, and to spend the least amount of money to do so. This requires finding the right balancing point, but I'm positive it can be done if the political will exists.
As for avoiding complications, I agree with you. The best action is to avoid the disease, and then to avoid the effects of the disease.
As mentioned in the article, sending a person in a car to visit someone is obviously more expensive than a phone call. But the nurse's visit can help to avoid a problem which requires a far more expensive visit to the hospital. That is where the cost savings come into play.
Wouldn't it be better if people never had to go into the hospital in the first place? Aside from the supplemental costs - "surgical complications increase the margin the hospital makes on the patient by 330 percent for the privately insured and 190 percent for Medicare patients." - consider the quality of life issues.
If Medicare is concerned with scaling this program up from a couple thousand people, instead of completely cutting a program which has proven its ability to cut costs AND improve quality of life, why not try it with five or ten thousand people first? If that works, then try it with 20 thousand people, then 50 thousand. If it doesn't scale at that point, then cut it.
Another possible solution is to find a way to eliminate the for-profit hospitals. But Medicare's solution - "It’s pushing providers to band together into accountable care organizations, or ACO, that get a flat fee for all care related to a patient." - sounds destined to fail from the outset to this layman.
For the moment, we're a Gigya customer but even the base license isn't cheap and don't use (or anticipate using) most of the functionality these 3rd party providers offer. We do use some of the other addons, but even those won't stay around forever either.
My knowledge of Persona's functionality is only passing, but could it take the place of 3rd party social sign in providers like Gigya & Janrain? That is, if Google, Facebook, etc provided Persona endpoints could I use them to login people to $work's website? We're currently using one of the social sign in providers (after trying another) and haven't been entirely happy about the experience. All we really need is a way to authenticate a user and associate them with a user ID in our local database. In a perfect world, I wouldn't have to care whether they were a local , Google+, FB, Twitter, etc user.