This is a complex feature to implement and they "don't have all the answers...yet, but hope to start uncovering some of them with user research and feedback." If customization is important to you, you can let them know: "We hope to gather feedback on this basic experience to see how we can iterate on the design to make it more convenient, elegant, and usable for our users. Try it out and share your feedback by filling out this quick form or writing to containers@mozilla.com."
My post was more of a mini-rant about how UX of otherwise useful/good features always seems to be an afterthought. The UX ends up being poor resulting in an underused and often later abandoned feature.
Although it is likely my social niche - I know more people with multiple personal or social accounts who will find this feature useful but have a terrible UX due to the container names.
"Hand me the long, blue screwdriver - by which I mean the short, red hammer." - terrible UX
I'll be providing concern this as feedback via email when I get home and have access to my personal email.
Yes you can use any of them as platform-independent glue code. But there are several disadvantages:
None of them is preinstalled on all platforms (including Windows).
Functionalities like process piping are not convenient to use.
Hard to integrate with existing code written in Bash or Batch.
The basic rule of thumb in investing is "buy low, sell high". The twist here is that you don't need to do it in that order (i.e. he was hoping to "sell high" first, then later "buy low" - referred to as "shorting"). So, since he thought the stock was overvalued (and that the price would eventually drop) he decided to sell some shares, even though he didn't yet own any. The way he did this is by borrowing the shares from ETrade, then selling them. So he then owes ETrade the amount of shares that he just borrowed. Later (hopefully for him, when the price dropped) he could purchase shares of the stock, and repay ETrade. So, what he's hoping for: Borrow X shares from ETrade, and immediately sell them at $2. Sometime in the future, buy P shares at ($2-y$) and return them to E*Trade. He makes a profit of P($2-$y) (excluding fees). Note here that the absolute maximum he can profit is P($2), if the stock goes to $0. What actually happened was that the stock had a dramatic price increase (something like +$14). At that point, ETrade wants its shares back that he borrowed at $2 a piece, so he buys them at $16 and loses P($14), which is much more than he had in his account.
This brings back some fond memories. One of the first interesting projects I worked on professionally was a post-mortem debugger that ran under OS/2. We used Microsoft's compilers and it was a bit of a challenge to reverse engineer enough of the debugging symbols to make something useful. Definitely could have used this back then :)
What if I don't want to connect through the Cloud?
That's okay! The Cloud is there to make the Core easier to work with, but if you'd rather do it yourself, that's no problem. The Core lets you do your own socket programming over TCP and UDP.
If you want the simplicity of the Cloud but you want it on your own server, we'll be releasing an open source version of the Cloud designed for quick and easy deployment.
Thanks, so the answer is no, as long as that open source version is vaporware.
The reason I asked is that once they get purchased by, say, Google or Facebook, their cloud services will probably get either shut down, or severely constrained. I'm not interested in sinking resources into a platform based on question marks.
We'll probably do a small beta as we get the local cloud ready for release to make sure things are easy to use and work as expected. Since it'll be open source, I'm hoping the beta group can help find bugs and even send in pull requests if there are pieces they want added. The beta signup thread is here at the moment: https://community.spark.io/t/where-is-the-source-code-for-th...
Supposedly they are going to open source the cloud side of the software so you could setup your own. I would wait for this instead of writing my own tcp connection.
