You can check a few files in a directory and then easily deduce the whole directory is a dupe. You don't have to do it file by file.
Plus, when the system finds a dupe, you need to tell it which copy it should delete, or else you risk having stuff all around and not knowing where it is. Some file you knew was in directory A/B/C/D is suddenly not there anymore and you have no clue where its "dupe" is located. Unless the dupe finder creates symlinks in place of the deleted file...
1. Install MySQL, 2. create a table (CRC, directory, filename, filesize) 3. fill it in 4. play with inner joins.
I'd even go down the path of forgetting about the CRC. Before deleting something, do a manual check anyways. CRC has the advantage of making things very straightforward but is a bit more complex to generate.
I don't know why you're jumping at me on that one. I am in 100% agreement on this one, even though my primary computer has Ubuntu running for about 8 years now.
I was merely trying to point out to the GP that voting with one's wallet doesn't say much when the software you use costs $0.
Are you implying you can't understand someone who doesn't share your exact set of values? That would be a failure n your part.
Because me too I own an iPhone, and I'm perfectly happy with it. I know Android, and yet, I've had three different models of iPhones so far (original, 3GS, 4S). So tell me, what exactly is it that you don't understand with me?
From what I remember, you can call the GUI lib in an event handler. You can call anything, but while handling the event, the UI is frozen. What you cannot do is modify the state of a GUI object while in any other thread than the "Swing Thread". The "Swing Thread" is the only thread allowed to touch anything UI related.
The result is that you end up with countless anonymous "runnable" classes that you feed the Swing Thread for later execution.
The concept holds water, but it is a pain to program with and it also is very fragile because calling anything UI related through another thread will have consequences that are no always immediately visible nor obvious.
I would be really surprised if Apple lost a dime on every iPhone 4 sold this year. Even on the 3GS models.
They don't have to produce a limited number. They still sell more iPhone 4 than any other phone around save Samsung and the 4S. What makes you think they need to produce a limited number of anything? They sell plenty of everything.
And finally, if you have to change (as opposed to simply extend) the API each time you release a new version of the client, IMHO you've done something wrong.
However, with AJAX you don't have to do that anymore. You can very well release a new API without touching your UI and you can release a new UI without releasing new DATA API. Look at gmail for example. They now have at least 5 different UIs (mobile, new, old, pure html, tablet,...), and trust me, they have only one DATA API.
As surprising as it may seem, the web has evolved since 1995.
Swing is anything but simple. I'd dare call it fragile. It's not a library you can just jump in and program with. You need to understand the intricacies of the threading model before you can start soing anything good with it.
Hence, I still can blame the language from coming with an overly delicate UI library.
And yes, it is perfectly possible to make a good app with swing.
To be fair to AC, Java is dead slow to start up. Once it's up and running there are no issues anymore, but on the desktop, the startup time is pretty bad.
Also, IIRC, I think there are still a few libraries that are not open source (and that don't work well in OpenJDK)
You have a far bigger problem with local apps. The problems are your APIs. You have (presumably) a web server somewhere serving data to your local apps. And every time you will release a new version of your app, you will also release a new version of your API. But you also should remember to keep the old one working, because guess what: Some people will upgrade, and then some will not.
All of a sudden, you have your server and a gazillion apps out there, some more or less buggy than the others.
THIS is the biggest benefit of a web based app, not the reach of the 1205 users of FreeBSD. You have a bug? Fix it. Instantly, no one has a bug anymore. THAT is convenient.
Can you elaborate on what is awful about the Java platform? And no, lack of an open source option is NOT one of the drawbacks since Java has those as well (which is not true of C# btw where the open source alternative is not really operational).
Now, before you jump in realize that I'm not asking about JAVA APPLETS, but about the Java platform.
This is completely different. The government can go to the phone company and ask them who was using the IP 1.2.3.4 at 8:40PM on friday. Hence, the phone company can default its responsability on the person responsible.
I doubt the cyber cafe owner can say who was using which PC at any given time. And even if (s)he did, they all share the same IP and likely the same user agent so there really isn't a way for the government to get to the poster.
Remember that free doesn't necessarily mean anonymous.
Slashdot Mirror
You can check a few files in a directory and then easily deduce the whole directory is a dupe. You don't have to do it file by file.
Plus, when the system finds a dupe, you need to tell it which copy it should delete, or else you risk having stuff all around and not knowing where it is. Some file you knew was in directory A/B/C/D is suddenly not there anymore and you have no clue where its "dupe" is located. Unless the dupe finder creates symlinks in place of the deleted file...
Exactly.
1. Install MySQL,
2. create a table (CRC, directory, filename, filesize)
3. fill it in
4. play with inner joins.
I'd even go down the path of forgetting about the CRC. Before deleting something, do a manual check anyways. CRC has the advantage of making things very straightforward but is a bit more complex to generate.
I don't know why you're jumping at me on that one. I am in 100% agreement on this one, even though my primary computer has Ubuntu running for about 8 years now.
I was merely trying to point out to the GP that voting with one's wallet doesn't say much when the software you use costs $0.
I think you got the TTL wrong.
Or ping is buggy as hell.
Vote with your wallet
Who did you buy your Linux distro from? And how much?
Are you implying you can't understand someone who doesn't share your exact set of values? That would be a failure n your part.
Because me too I own an iPhone, and I'm perfectly happy with it. I know Android, and yet, I've had three different models of iPhones so far (original, 3GS, 4S). So tell me, what exactly is it that you don't understand with me?
Some head hunter referred to the guys he was proposing as "top guns".
I never talked to the salesman again.
From what I remember, you can call the GUI lib in an event handler. You can call anything, but while handling the event, the UI is frozen. What you cannot do is modify the state of a GUI object while in any other thread than the "Swing Thread". The "Swing Thread" is the only thread allowed to touch anything UI related.
The result is that you end up with countless anonymous "runnable" classes that you feed the Swing Thread for later execution.
The concept holds water, but it is a pain to program with and it also is very fragile because calling anything UI related through another thread will have consequences that are no always immediately visible nor obvious.
Someone let Apple know, that Itunes on windows is garbage.
Is barely worse than iTunes on Mac OS.
I would be really surprised if Apple lost a dime on every iPhone 4 sold this year. Even on the 3GS models.
They don't have to produce a limited number. They still sell more iPhone 4 than any other phone around save Samsung and the 4S. What makes you think they need to produce a limited number of anything? They sell plenty of everything.
The only problem is that stock is costing money !
Huh?
If you made more than you can sell then you lose money. If you have to sell them off at a reduced price you lost even more.
Do you really think Apple is losing money on all iPhone 4 sales? Really?
I have also disabled password based logins but for one user. You never know when you're going to need to get in without a key at hand.
This user has a 18chars password that is nowhere near containing anything in any dictionary I know of. Punctuation, digits, letters, etc.
Java Applet are a horrendous piece of crap. Everyone agree on this. Even on this thread. Thanks for playing though.
Of course, you have the pros of your cons.
And finally, if you have to change (as opposed to simply extend) the API each time you release a new version of the client, IMHO you've done something wrong.
However, with AJAX you don't have to do that anymore. You can very well release a new API without touching your UI and you can release a new UI without releasing new DATA API. Look at gmail for example. They now have at least 5 different UIs (mobile, new, old, pure html, tablet, ...), and trust me, they have only one DATA API.
As surprising as it may seem, the web has evolved since 1995.
That's not addressing the problem, that's doing it wrong. I mean, imagine facebook with a policy like that. How do you scale?
Swing is anything but simple. I'd dare call it fragile. It's not a library you can just jump in and program with. You need to understand the intricacies of the threading model before you can start soing anything good with it.
Hence, I still can blame the language from coming with an overly delicate UI library.
And yes, it is perfectly possible to make a good app with swing.
To be fair to AC, Java is dead slow to start up. Once it's up and running there are no issues anymore, but on the desktop, the startup time is pretty bad.
Also, IIRC, I think there are still a few libraries that are not open source (and that don't work well in OpenJDK)
You have a far bigger problem with local apps. The problems are your APIs. You have (presumably) a web server somewhere serving data to your local apps. And every time you will release a new version of your app, you will also release a new version of your API. But you also should remember to keep the old one working, because guess what: Some people will upgrade, and then some will not.
All of a sudden, you have your server and a gazillion apps out there, some more or less buggy than the others.
THIS is the biggest benefit of a web based app, not the reach of the 1205 users of FreeBSD. You have a bug? Fix it. Instantly, no one has a bug anymore. THAT is convenient.
Good desktop applications are rare in Java, and the only ones I'd recommend are developer tools anyways: Eclipse, SmartSVN.
The only drawbacks are startup times for me.
Can you elaborate on what is awful about the Java platform? And no, lack of an open source option is NOT one of the drawbacks since Java has those as well (which is not true of C# btw where the open source alternative is not really operational).
Now, before you jump in realize that I'm not asking about JAVA APPLETS, but about the Java platform.
Go.
They are Apple, so any decision they make is inherently evil. Period.
And even that one was probably made so that they could file a patent on removing Java in the Web browser to impeach other vendors for doing so.
There.
This is completely different. The government can go to the phone company and ask them who was using the IP 1.2.3.4 at 8:40PM on friday. Hence, the phone company can default its responsability on the person responsible.
I doubt the cyber cafe owner can say who was using which PC at any given time. And even if (s)he did, they all share the same IP and likely the same user agent so there really isn't a way for the government to get to the poster.
Remember that free doesn't necessarily mean anonymous.
And yes, I've already returned it and gotten another one, just to be sure it wasn't a lemon.
It doesn't prove anything.
Your second quote is not from Jobs. He said it while Citing Picasso, but that is all.