China is a much more capitalist society than the USA
I don't disagree with this, but I wonder why you think that this means it has more liberty. Unless you happen to be one of the ones that controls most of the capital, of course.
The problem is, social networks invariable involve sharing data with your friends. With most of the current models, that means that you need to trust the server that your friends are using. Even for email and XMPP that's a problem: if half of your friends are using GMail for both then there's a good chance that Google can get a big chunk of our email and your social graph. Privacy preserving protocols are an ongoing research area, but I've not yet seen anyone trying to integrate them into a well-defined standard with a good reference implementation.
If they had a federated model and I could easily migrate away from storing stuff on their servers, then I might be tempted to pay them so that I didn't have to go to the trouble of running the server and keeping it patched. The last time I paid to be in a walled garden, it was CompuServe, and I learned my lesson.
You can use Facebook to log in to a lot of services as well, but that's not really "using" Facebook because you're not doing anything with what Facebook offers. You're just telling a website that you are who you say you are.
Sounds like you're using Facebook for exactly it's intended purpose: to allow someone to build a big database of things that you do to target advertising. You're not just telling a website something, you're telling Facebook what other sites you visit and care enough about to log in to and what your identity on those sites is.
When I was a student, sharing a house with three other people, we paid extra to get the 1Mb/s connection that was the fastest that the cable company offered. The top gradually grew to 3Mb/s, 5Mb/s and then 10Mb/s. When it hit 10Mb/s (I'd moved house and was living with a different group of people, but) we still paid for it. But then I stopped caring. The 10Mb/s went from being the fastest that they offered to the slowest. Then 20Mb/s and 30Mb/s became the slowest. I'm now still on their slowest connection (although living in a different city). At work, I have a GigE connection that means that most of the time the bottleneck isn't my local connection, and I can usually get 10-20MB/s to any moderately large Internet site. I very occasionally notice the difference between the speed at home and at work, but most of the time there's no user-perceptible difference. Oh, and my ISP sent me a letter a few weeks ago saying that they don't offer 30Mb/s anymore and they'll be moving me to 50Mb/s soon. I think somewhere around 10-20Mb/s was when I stopped noticing Internet speed as a bottleneck.
Unless I'm misreading something, Seafile seems to just do file sharing (for which a simple WebDAV server is mostly enough). The value of owncloud (for me, at least) is that it also does contact and calendar sync, so my phone and computer always have the same data for these.
I found it pretty easy to set up on FreeBSD - install the owncloud, php5, and nginx packages and then a tiny bit of configuration (mostly copying and pasting from the owncloud site). The only gotcha was that the default nginx configuration doesn't know the correct MIME type for svg files, so I needed to fix that or none of the images in owncloud worked correctly.
OwnCloud is open source and does the same things as Dropbox (although in really crappy PHP on the server, so you'd better have a lot of spare cycles to burn - it's the first time for several years I've seen file transfers across the Internet be CPU limited).
The problem is that they're comparing apples to oranges. Of course a direct local connection will be faster than two devices sharing the same Internet connection and going via a server, but most of the time that I want to use a server as part of a sync workflow it's because the devices aren't together and I want to do it asynchronously. The equivalent for BitTorrent Sync would involve having a central server somewhere (possibly in your own home) that's always on and is a party in the sync.
Bullshit. Nokia mismanaged itself to death by promoting infighting and sabotaging other product groups (rather than competing with other companies) until adopting Windows Phone and killing internal OS development was the least bad option.
Burning the money actually works reasonably well as an alternative. It reduces the money supply and therefore lowers inflation, resulting in a relative increase in the value of everyone's money. The counter argument is that rich people profit more, but generally if you have enough money lying around that the effect would be noticeable, you've invested most of it in things that have a much better return on investment than cash, so as a proportion of net worth if favours the people whose money is mostly money (predominantly poor people).
That's fine, if late fees are for their original purpose (preventing people using a shared resource from impacting the quality of service for others). It's only a problem when they require them for revenue. Ideally, you want to completely decouple the revenue from punitive fines from the organisation that can set them.
And then those same elected officials are subject to calls to cut taxes, but keep public services the same. Want to be reelected? It's difficult if you voted against lowering taxes and your opponent promises that he won't. But no one notices when you make a decision that raises revenue at the expense of safety.
I've been in quite a few places in the US where the lights one way turn red at exactly the same time that the lights going the other way turn green. In the UK, there's always a few second pause between the two to ensure that the junction is clear. We like to mock drivers in the US for its high level of road accidents per driven mile, but a lot of the blame goes to the road and signal design, which is just dangerous in a lot of places.
Beer should be served at room temperature (not warm). If it needs to be chilled, which reduces the sensitivity of the tastebuds, then the correct solution is to buy better beer.
My ability to put 'latex manuscript.tex' and 'dvi2pdf manuscript.dvi' into a makefile is not magic, it is basic automation
It's also redundant and likely not to do the right thing (ironic, given previous comments about libraries). Look for latexmk, which is part of the standard LeXLive distribution. Oh, and since this is not 1970 anymore, let's skip the DVI step and go straight to PDF with pdflatex (latexmk -pdf manuscript.tex is probably what you actually want).
If you're a photographer dealing with 30MB images, then you're almost certainly using non-destructive editing on them. It sounds like the tool that you want is not a version control system at all, it's a filesystem.
You can checkout a subdirectory if (and that's a big proviso) you structure your code in such a way that each directory is a separate git repository, referenced as a submodule. The submodule points to a specific version of the other repository. Unfortunately, there are still a lot of issues with this approach:
The biggest is that you have to think about what parts of the project you might want to check out individually before you start. For new (small) projects, it's sometimes easy, but typically projects grow organically and parts get factored out. There's no good way of turning a subtree in a git repo into a new repo preserving history (and no way at all that allows you to merge into both).
The second big one is that you lose atomic commits (the thing we all switched to svn from cvs for in the first place). If you only have one layer of submodules, it's quite nice because committing something to the submodule and updating the version of the submodule are independent. That means that you can make changes to a component, unit test them, commit, and then later update their consumers. Unfortunately, there's no way of atomically updating two independent subtrees simultaneously.
The third annoyance is the most embarrassing for a DVCS: the remote repository for upstream is identified by an absolute URL. You can do relative URLs, but they don't work very well, which means that if you want people to use a local version then it's quite convoluted. There's no simple 'clone this repo and all of the submodules in such a way that someone else can clone my copy and it all work sensibly'.
In general, the dire UI of git has been an unexpected advantage. No one can stand working with it, so people have been motivated to write nice GUIs that make it tolerable.
Freescale mostly sells PowerPC chips for automotive and similar applications. They already had the low power parts, but they didn't have them at the speeds that Apple wanted. Most of their customers use their chips for engine control or entertainment systems. They also made the chips for consoles. Their biggest weakness was that Apple was the cheapest supplier of a PowerPC system that you could develop on, and they were undercut by a long way by Intel machines. This is the same problem that Alpha had: it didn't matter that their Windows NT systems were faster than Intel's, they didn't get them into the hands of developers so everyone wrote software for Intel.
Slashdot Mirror
China is a much more capitalist society than the USA
I don't disagree with this, but I wonder why you think that this means it has more liberty. Unless you happen to be one of the ones that controls most of the capital, of course.
The problem is, social networks invariable involve sharing data with your friends. With most of the current models, that means that you need to trust the server that your friends are using. Even for email and XMPP that's a problem: if half of your friends are using GMail for both then there's a good chance that Google can get a big chunk of our email and your social graph. Privacy preserving protocols are an ongoing research area, but I've not yet seen anyone trying to integrate them into a well-defined standard with a good reference implementation.
The news here is that you're willing to spend an entire day touching PHP for only $100.
If they had a federated model and I could easily migrate away from storing stuff on their servers, then I might be tempted to pay them so that I didn't have to go to the trouble of running the server and keeping it patched. The last time I paid to be in a walled garden, it was CompuServe, and I learned my lesson.
You can use Facebook to log in to a lot of services as well, but that's not really "using" Facebook because you're not doing anything with what Facebook offers. You're just telling a website that you are who you say you are.
Sounds like you're using Facebook for exactly it's intended purpose: to allow someone to build a big database of things that you do to target advertising. You're not just telling a website something, you're telling Facebook what other sites you visit and care enough about to log in to and what your identity on those sites is.
In case you were wondering, no that whooshing noise above your head wasn't someone trying to stone you to death.
I'm using Mb and MB when I mean Mb and MB. If you read all of the words in my post, you'll see that the 10MB/s is over the 1Gb/s connection.
When I was a student, sharing a house with three other people, we paid extra to get the 1Mb/s connection that was the fastest that the cable company offered. The top gradually grew to 3Mb/s, 5Mb/s and then 10Mb/s. When it hit 10Mb/s (I'd moved house and was living with a different group of people, but) we still paid for it. But then I stopped caring. The 10Mb/s went from being the fastest that they offered to the slowest. Then 20Mb/s and 30Mb/s became the slowest. I'm now still on their slowest connection (although living in a different city). At work, I have a GigE connection that means that most of the time the bottleneck isn't my local connection, and I can usually get 10-20MB/s to any moderately large Internet site. I very occasionally notice the difference between the speed at home and at work, but most of the time there's no user-perceptible difference. Oh, and my ISP sent me a letter a few weeks ago saying that they don't offer 30Mb/s anymore and they'll be moving me to 50Mb/s soon. I think somewhere around 10-20Mb/s was when I stopped noticing Internet speed as a bottleneck.
Unless I'm misreading something, Seafile seems to just do file sharing (for which a simple WebDAV server is mostly enough). The value of owncloud (for me, at least) is that it also does contact and calendar sync, so my phone and computer always have the same data for these.
I found it pretty easy to set up on FreeBSD - install the owncloud, php5, and nginx packages and then a tiny bit of configuration (mostly copying and pasting from the owncloud site). The only gotcha was that the default nginx configuration doesn't know the correct MIME type for svg files, so I needed to fix that or none of the images in owncloud worked correctly.
OwnCloud is open source and does the same things as Dropbox (although in really crappy PHP on the server, so you'd better have a lot of spare cycles to burn - it's the first time for several years I've seen file transfers across the Internet be CPU limited).
The problem is that they're comparing apples to oranges. Of course a direct local connection will be faster than two devices sharing the same Internet connection and going via a server, but most of the time that I want to use a server as part of a sync workflow it's because the devices aren't together and I want to do it asynchronously. The equivalent for BitTorrent Sync would involve having a central server somewhere (possibly in your own home) that's always on and is a party in the sync.
Microsoft poisoned them killing the company
Bullshit. Nokia mismanaged itself to death by promoting infighting and sabotaging other product groups (rather than competing with other companies) until adopting Windows Phone and killing internal OS development was the least bad option.
Well, there is that, but if you'd make it a little bit harder then we'd move back to nearer targets, like the French and the Irish...
Burning the money actually works reasonably well as an alternative. It reduces the money supply and therefore lowers inflation, resulting in a relative increase in the value of everyone's money. The counter argument is that rich people profit more, but generally if you have enough money lying around that the effect would be noticeable, you've invested most of it in things that have a much better return on investment than cash, so as a proportion of net worth if favours the people whose money is mostly money (predominantly poor people).
That's fine, if late fees are for their original purpose (preventing people using a shared resource from impacting the quality of service for others). It's only a problem when they require them for revenue. Ideally, you want to completely decouple the revenue from punitive fines from the organisation that can set them.
And then those same elected officials are subject to calls to cut taxes, but keep public services the same. Want to be reelected? It's difficult if you voted against lowering taxes and your opponent promises that he won't. But no one notices when you make a decision that raises revenue at the expense of safety.
I've been in quite a few places in the US where the lights one way turn red at exactly the same time that the lights going the other way turn green. In the UK, there's always a few second pause between the two to ensure that the junction is clear. We like to mock drivers in the US for its high level of road accidents per driven mile, but a lot of the blame goes to the road and signal design, which is just dangerous in a lot of places.
Debian makes renames latexmk to pdflatex? I sincerely hope not...
Beer should be served at room temperature (not warm). If it needs to be chilled, which reduces the sensitivity of the tastebuds, then the correct solution is to buy better beer.
My ability to put 'latex manuscript.tex' and 'dvi2pdf manuscript.dvi' into a makefile is not magic, it is basic automation
It's also redundant and likely not to do the right thing (ironic, given previous comments about libraries). Look for latexmk, which is part of the standard LeXLive distribution. Oh, and since this is not 1970 anymore, let's skip the DVI step and go straight to PDF with pdflatex (latexmk -pdf manuscript.tex is probably what you actually want).
The Dalek suits were originally inspired by female dancers gliding along the ground in long skirts, so there may be even more to it than you think...
If you're a photographer dealing with 30MB images, then you're almost certainly using non-destructive editing on them. It sounds like the tool that you want is not a version control system at all, it's a filesystem.
The biggest is that you have to think about what parts of the project you might want to check out individually before you start. For new (small) projects, it's sometimes easy, but typically projects grow organically and parts get factored out. There's no good way of turning a subtree in a git repo into a new repo preserving history (and no way at all that allows you to merge into both).
The second big one is that you lose atomic commits (the thing we all switched to svn from cvs for in the first place). If you only have one layer of submodules, it's quite nice because committing something to the submodule and updating the version of the submodule are independent. That means that you can make changes to a component, unit test them, commit, and then later update their consumers. Unfortunately, there's no way of atomically updating two independent subtrees simultaneously.
The third annoyance is the most embarrassing for a DVCS: the remote repository for upstream is identified by an absolute URL. You can do relative URLs, but they don't work very well, which means that if you want people to use a local version then it's quite convoluted. There's no simple 'clone this repo and all of the submodules in such a way that someone else can clone my copy and it all work sensibly'.
In general, the dire UI of git has been an unexpected advantage. No one can stand working with it, so people have been motivated to write nice GUIs that make it tolerable.
Freescale mostly sells PowerPC chips for automotive and similar applications. They already had the low power parts, but they didn't have them at the speeds that Apple wanted. Most of their customers use their chips for engine control or entertainment systems. They also made the chips for consoles. Their biggest weakness was that Apple was the cheapest supplier of a PowerPC system that you could develop on, and they were undercut by a long way by Intel machines. This is the same problem that Alpha had: it didn't matter that their Windows NT systems were faster than Intel's, they didn't get them into the hands of developers so everyone wrote software for Intel.
If it is open source (and a cursory look around the web site didn't show me any links to the source), it's a shame that it isn't in F-Droid.