5 ms·

Describe a "new problem". I only rarely encounter truly unique problems. One thing it does do is allow scalability in a pretty straight-forward, integrated way

Describe a "new problem". I only rarely encounter truly unique problems. One thing it does do is allow scalability in a pretty straight-forward, integrated way.

ChuckMcM 11y ago
I like the scaling aspect of it very much. There are lots of "new" problems with respect to changing conditions in our day to day lives. Here are a few - Identity management across Internet and non-Internet properties - Configuration, control, auditing, and monitoring of billions of Beacon level devices - Zero knowledge proofs as a technique for anonymous and no repudiated purchases online - "home" level cloud services for local and on the road implementation of always available services (mail, journaling, calendaring, Etc.) - Reliable third party payment systems (somewhat of an old system but one that benefits from revisiting with current technology from time to time) - Navigation and cartography tools for people in disconnected regions of the planet. - Civil process augmentation with automation and authentication. - Connectivity as a tax payer civic utility, without an editorial bias. -Dynamic skills assessment for students in the presence of confounding factors (mostly remote access) - Low friction capital markets for charitable giving (think Watsi but for everything, and with better controls than 'GoFundMe') - Providing civic services for indigenous homeless populations. I could go on, there are lots and lots of problems. But to be clear it isn't a criticism of Phoenix that they are not solving a new problem, the feedback was that there are lots of solutions to the general form of problem they are solving and, as feedback on this announcement, I was trying to learn from their materials how they were different (and presumptively better) than those other solutions. I'm still looking for that summary somewhere.
- prapam2 11y ago
  These seems like architecture level problems rather then framework level.

Describe a "new problem". I only rarely encounter truly unique problems. One thing it does do is allow scalability in a pretty straight-forward, integrated way.

ChuckMcM 11y ago

I like the scaling aspect of it very much. There are lots of "new" problems with respect to changing conditions in our day to day lives. Here are a few - Identity management across Internet and non-Internet properties - Configuration, control, auditing, and monitoring of billions of Beacon level devices - Zero knowledge proofs as a technique for anonymous and no repudiated purchases online - "home" level cloud services for local and on the road implementation of always available services (mail, journaling, calendaring, Etc.) - Reliable third party payment systems (somewhat of an old system but one that benefits from revisiting with current technology from time to time) - Navigation and cartography tools for people in disconnected regions of the planet. - Civil process augmentation with automation and authentication. - Connectivity as a tax payer civic utility, without an editorial bias. -Dynamic skills assessment for students in the presence of confounding factors (mostly remote access) - Low friction capital markets for charitable giving (think Watsi but for everything, and with better controls than 'GoFundMe') - Providing civic services for indigenous homeless populations. I could go on, there are lots and lots of problems. But to be clear it isn't a criticism of Phoenix that they are not solving a new problem, the feedback was that there are lots of solutions to the general form of problem they are solving and, as feedback on this announcement, I was trying to learn from their materials how they were different (and presumptively better) than those other solutions. I'm still looking for that summary somewhere.

prapam2 11y ago
These seems like architecture level problems rather then framework level.