I wonder, if this is the way a majority of big businesses do things, how come we don't see more leaks of entire codebases? It'd be trivial to put something up on TPB and just share all the code, but I don't see things like that happening. I also doubt that every single employee with access to the code has the moral standards not to do this. There must be something else keeping them from doing it.
Perhaps so. I tried Ubuntu with Unity a little while ago and didn't like it much--I'm used to minimizing to the taskbar and seeing the names of the programs. I settled on Linux Mint as it offers a clean and "classical" way of doing things.
I'll consider trying out Ubuntu again when 14.04 LTS comes out this month. Maybe I'll get used to it, who knows.
Same here, using the official one with Mono. It's a bit buggy, but still works properly most of the time. Do you use keepassx on Linux, and if so, does it work well?
KeePass is the program for linux I've found that fills in your details in the browser for you (short of LastPass, which I don't trust).
Any idea if it will be possible to keep the menu in the title bar from being hidden? It looks like you have to mouse-over to show it, which could be a pain if I'm trying to access it often. I'd like to see where to take my mouse without guessing.
I'm still learning this myself, but from the research I've done I've figured this out:
1. Most people don't go with two writes to a relational database (like MySQL). Syncing is hard, and when it is done, it loses its relational features.
2. Common set up is one mysql write server, scaling it up to fit your traffic, and automatically syncing it with additional servers where SELECT statements only will be made. A random read server is selected if there are multiple to choose from.
3. This also means that in the application, doing a write and immediate read on what you just wrote won't work, so you have to code your application around that.
4. In you app you separate your connections for the reads and writes.
Now, in terms of making changes to the write server is what I'm trying to figure out. Perhaps there's a way to make upgrades on one of the slaves (the reads), then automatically make that slave the master and the master a slave? Not sure, I'm reading a MySQL book (The MySQL Bible) right now that I hope will point me in the right direction.
Cool. Bitcoin is still young, so there's a lot of room for growth. I personally think Coinbase is doing a good job (though having growing pains), and others are quickly coming to join in.
You're absolutely right. How about your MySQL write server? You typically have one master that you update to and one or more slaves where you read from. If you get a sudden burst of traffic and your master can't handle all the writes, what do you do?
What if you start out small with one server, but then need to expand to multiple droplets? You won't be able to without powering off and making an image.