There was a hash-collision proof-of-concept thing some years back that purported to have generated two HTML files that hashed to the same value, but displayed different content. In reality, the files were identical, they just contained javascript that displayed different things depending on the URL that the file was served from. A simple trick, but one that could easily defeat hashing strategies applied to things that contain actual executable code, rather than just - say - an image.
As I'm sure you must know perfectly well, it's a conflict caused by a change to a file conflicting at the tree level, so that one person modified the file, and another either deleted or moved it. Git gives a conflict in the first case - naturally - and may give a conflict in the second if its magic content-tracking algorithm fails (which it does, especially in non-trivial cases). You resolve it in the usual way, you inspect both sides, and figure out what to do.
I know I'm on a losing wicket hating git like I do, but it's just so much less usable. I'd give alot to go back to revision numbers, and really knowing what goes into branches. Git does checkout (sorry... clone) alot faster though, so there's that. Can't help but think that could be fixed.
Git breaks. And when it does, good luck. Sometimes it breaks in the middle of a pull, and leaves the opposite of the repo's changes staged for you to accidentally commit. It can crap out when you're stashing, with the same effect. The bloody thing is a usability nightmare. And those hashes? Seriously... why couldn't we have just had a revision number? We're all committing to the same server.
SVN has several huge advantages over git. It's far simpler. It doesn't have a thing called 'rebase', which rewrites your commits and occasionally messes them up. Its revision numbers are actually in order, which means you always know which revision came first, given two of them, something that's impossible with git's hashes (YES - I know why the hashes are used... but the reality of 99% of software development is that the repository is centralised, so git's solving an almost non-existent problem here). SVN supports real cherry-picking, and actually records in the repo that you took code from somewhere, as opposed to git's cut-n-paste approach.
SVN has branches, git has pointers into a tree. Thus in git, it is impossible after the fact to determine to which branch a change was committed, just in which branches it now currently resides. Branches don't really exist in git at all, they aren't versioned (who created a branch, and when?), and if you accidentally delete them you tend to lose the commits against them. Tags in git are even worse. Added to which is the fact that both are implemented in the filesystem as regular files, which means you're at the mercy of your filesystem's ideas regarding case and permitted characters, and good luck if someone tries to check it out into a filesystem with different ideas. Nice design decision there Linus, guess you were having an off day? And the line-endings stuff?... Oh. My. God.
He's right about hobbyist electronics - while BGA is more or less impossible, larger SMD parts are perfectly doable, and you can have custom 2-layer (or even up to 12-layer, if you're incredibly rich...) built for you cheaply. You can populate these by hand, according to your own designs, and build things that are pretty damn useful, and definitely cool. Added to which, plenty of DIP parts are still available, and you can build devices that'll run up to 20MHz (probably more if you try) on stripboard. I've build audio hardware, and toys for the kids, and remote sensors, and so-on. Recently it's all been SMD, because it's smaller, and cheaper. All you need is a steady hand, good lighting, and a loupe. The end results look incredibly awesome too.
I do agree about Arduinos though. Electronics, they are not. And of course, you're quite right about the repairability of modern consumer electronics, it's completely impossible.
The mall is full of independent repair shops. They don't seem to be significantly impeded by the restrictions that the manufacturers impose. Often it just amounts to a funny-looking screwdriver, which isn't exactly high security.
Very true, and there's a potentially very serious downside here too. Encryption that's physically impossible to break is equivalent to a safe that physically impregnable against all attacks. Given the regularity with which I lose my keys, I'm not sure that we should put anything important in there, because losing the keys is game over.
The trouble with Twitter is that inane nonsense actually gets into real media the whole damn time, and if you want to know what's going on in the world, then you can't avoid it.
Or how I lost my health insurance and access to my doctor because of Obamacare.
I'm very interested in the exact way in which this happened, would you elaborate for us? You could also explain the first statement too, but I just plain don't understand that one.
White proper, platform-independent code, in C++, and you won't have a problem with different architectures. The same is far from true in any other language (yes, including C).
Allowing green card holders to come back to the U.S. is basically unavoidable.
Laws are just people doing things that they believe are, well, the laws. Nothing is unavoidable in that sense. All you have to do is change what the people are doing, and those greed card holders can be kept out. This executive order is basically unlawful for a large number of different reasons, but that doesn't matter, because already your laws are becoming fluid.
It is truly astonishing the extent to which this type of uncertainty about your country's own laws has become normalised - and so quickly too. In a stable Democracy, the stability of law is incredibly important. Knowing what you are, and are not, permitted to do - and being able to have enormous confidence that tomorrow the situation will be unchanged - is fundamental. And yet, here is the United States, in which the population is actually in the position of not knowing whether or not a particular person is permitted into their country - despite their being in possession of their "papers".
The whole pantomime has several different aims. Firstly we have Trump separating his supporters from his foes, and dealing with these discovered enemies swiftly. Secondly, the presidential decree itself, which is deliberately over-reached, so that it may be dialled back to the position they really want, and be made to appear reasonable. And of course, thirdly, to create the situation described above. To create uncertainty in the law itself, and thus keep a population fearful of what they might not be allowed to do tomorrow. Controlling a population is much easier if they're never quite sure of what their rights are.
Though the US has a deeply unhealthy relationship with firearms, it might yet pull itself out of this apparent nose-dive into a form of corporate totalitarianism by forming a decent citizens army, and dealing with these people in the only way that they deserve.
Personally, I don't remember either. But I was assuming that you're referring to infant teething, as opposed to that whole thing where your teeth grow wiggly, and fall out, and are replaced by bigger ones, and you've suddenly got a cast-iron excuse to moan about your dinner. Funny that the moaning tends to stop if candy, or biscuits, or cake are on offer, which is why I'm disinclined to believe that actual pain is involved.
Wisdom teeth are another matter, it seems, and while I personally suffered no pain, in many cases there seems to be insufficient room to contain them. I guess I must have a big mouth. If they grow in without pushing all your other teeth around, then there is no pain.
Also, fever is a scientifically measurable symptom of teething.
Well, it would be, if teething caused a fever, which I don't believe that it does.
probably the belladonna rather than the homeopathic ingredients
But I thought that the belladonna was the homeopathic ingredient - which is to say the ingredient that's present in homeopathic quantities - which is to say not present at all. Except that it was present, because they did the dilution wrong, and hence you end up with a product with belladonna in it that you proceed to place in your child's mouth.
Also, I'm very far from convinced that teething is even really a thing. Kids get grouchy and irritable for many, many reasons, and I don't know if there's any actual evidence for any teething pain. There's certainly no evidence for any teething products being effective. I mean, some people hang amber necklaces around their kid's necks and claim that it reduces teething symptoms. If anything ever suggested 'no real problem here', then that's it.
If infant tylenol cold and flu hadn't been yanked off the market....
Your FDA is weird. They can't ban 'medicines' that actually contain poisons, but they can ban paracetamol (which is what the rest of the planet calls tylenol). I notice that it's also not possible to get Kinder Surprise chocolate eggs either. Added to which, you currently have a certifiable lunatic in charge. You should just put up a big "do not visit" sign, maybe hang it off The Statue of Liberty or something.
That sure sounds like alot of work, especially the script-writing part to file by date, when the date's already in the file, and you can't search by range easily, etc. I can see your point regarding 1TB of free space, I have to pay something like $12 a month for that, but if that $12 means I don't have (another) script to write, then I'm very happy.
I mean, I'm not going to tell you that your approach is wrong, but it's just that you get all of that for nothing (ahem, other than paying for the online storage, but you've got to admit that your free 1TB of space is a bit of a fluke!) if you just give up and use Photos. Still, I'm happy you've got them backed up somewhere, if I had a dollar for every time someone has asked me if all their photos were gone when their HD crashed (yes, sorry. Yes, all of them. No I can't get them back. Yeah that does suck... etc), well, I'd have about two bucks, but it sure was a bit of a shit-show for those two guys.
May I ask what application you do use for managing a collection of photos, and what backup solution you employ for them? I am assuming that you use the machine for photos, since suggesting that you keep on plugging cameras into the machine sort of implies that.
Slashdot Mirror
81747
Thanks complete_loony, I'll get that integrated into our workflow.
as it can destroy history
Which should, really, be impossible for a client to a source control server.
There was a hash-collision proof-of-concept thing some years back that purported to have generated two HTML files that hashed to the same value, but displayed different content. In reality, the files were identical, they just contained javascript that displayed different things depending on the URL that the file was served from. A simple trick, but one that could easily defeat hashing strategies applied to things that contain actual executable code, rather than just - say - an image.
As I'm sure you must know perfectly well, it's a conflict caused by a change to a file conflicting at the tree level, so that one person modified the file, and another either deleted or moved it. Git gives a conflict in the first case - naturally - and may give a conflict in the second if its magic content-tracking algorithm fails (which it does, especially in non-trivial cases). You resolve it in the usual way, you inspect both sides, and figure out what to do.
I know I'm on a losing wicket hating git like I do, but it's just so much less usable. I'd give alot to go back to revision numbers, and really knowing what goes into branches. Git does checkout (sorry... clone) alot faster though, so there's that. Can't help but think that could be fixed.
Git breaks. And when it does, good luck. Sometimes it breaks in the middle of a pull, and leaves the opposite of the repo's changes staged for you to accidentally commit. It can crap out when you're stashing, with the same effect. The bloody thing is a usability nightmare. And those hashes? Seriously... why couldn't we have just had a revision number? We're all committing to the same server.
I love arguing about git.
SVN has several huge advantages over git. It's far simpler. It doesn't have a thing called 'rebase', which rewrites your commits and occasionally messes them up. Its revision numbers are actually in order, which means you always know which revision came first, given two of them, something that's impossible with git's hashes (YES - I know why the hashes are used... but the reality of 99% of software development is that the repository is centralised, so git's solving an almost non-existent problem here). SVN supports real cherry-picking, and actually records in the repo that you took code from somewhere, as opposed to git's cut-n-paste approach.
SVN has branches, git has pointers into a tree. Thus in git, it is impossible after the fact to determine to which branch a change was committed, just in which branches it now currently resides. Branches don't really exist in git at all, they aren't versioned (who created a branch, and when?), and if you accidentally delete them you tend to lose the commits against them. Tags in git are even worse. Added to which is the fact that both are implemented in the filesystem as regular files, which means you're at the mercy of your filesystem's ideas regarding case and permitted characters, and good luck if someone tries to check it out into a filesystem with different ideas. Nice design decision there Linus, guess you were having an off day? And the line-endings stuff?... Oh. My. God.
He's right about hobbyist electronics - while BGA is more or less impossible, larger SMD parts are perfectly doable, and you can have custom 2-layer (or even up to 12-layer, if you're incredibly rich...) built for you cheaply. You can populate these by hand, according to your own designs, and build things that are pretty damn useful, and definitely cool. Added to which, plenty of DIP parts are still available, and you can build devices that'll run up to 20MHz (probably more if you try) on stripboard. I've build audio hardware, and toys for the kids, and remote sensors, and so-on. Recently it's all been SMD, because it's smaller, and cheaper. All you need is a steady hand, good lighting, and a loupe. The end results look incredibly awesome too.
I do agree about Arduinos though. Electronics, they are not. And of course, you're quite right about the repairability of modern consumer electronics, it's completely impossible.
The mall is full of independent repair shops. They don't seem to be significantly impeded by the restrictions that the manufacturers impose. Often it just amounts to a funny-looking screwdriver, which isn't exactly high security.
Ok, I give up. Why is it bad to hash values inside an RDBMS?
Very true, and there's a potentially very serious downside here too. Encryption that's physically impossible to break is equivalent to a safe that physically impregnable against all attacks. Given the regularity with which I lose my keys, I'm not sure that we should put anything important in there, because losing the keys is game over.
The trouble with Twitter is that inane nonsense actually gets into real media the whole damn time, and if you want to know what's going on in the world, then you can't avoid it.
Probably not. It probably doesn't actually work in anything other than a 'simple' case of faking a fingerprint unlock.
It's good for providing a wifi hotspot, while still being an actual phone to boot.
Have you ever used one of those? I have. Never again.
The Noka 3310 (although the 1100 is superior) is the most usable cellphone ever made.
Or how I lost my health insurance and access to my doctor because of Obamacare.
I'm very interested in the exact way in which this happened, would you elaborate for us? You could also explain the first statement too, but I just plain don't understand that one.
White proper, platform-independent code, in C++, and you won't have a problem with different architectures. The same is far from true in any other language (yes, including C).
Allowing green card holders to come back to the U.S. is basically unavoidable.
Laws are just people doing things that they believe are, well, the laws. Nothing is unavoidable in that sense. All you have to do is change what the people are doing, and those greed card holders can be kept out. This executive order is basically unlawful for a large number of different reasons, but that doesn't matter, because already your laws are becoming fluid.
It is truly astonishing the extent to which this type of uncertainty about your country's own laws has become normalised - and so quickly too. In a stable Democracy, the stability of law is incredibly important. Knowing what you are, and are not, permitted to do - and being able to have enormous confidence that tomorrow the situation will be unchanged - is fundamental. And yet, here is the United States, in which the population is actually in the position of not knowing whether or not a particular person is permitted into their country - despite their being in possession of their "papers".
The whole pantomime has several different aims. Firstly we have Trump separating his supporters from his foes, and dealing with these discovered enemies swiftly. Secondly, the presidential decree itself, which is deliberately over-reached, so that it may be dialled back to the position they really want, and be made to appear reasonable. And of course, thirdly, to create the situation described above. To create uncertainty in the law itself, and thus keep a population fearful of what they might not be allowed to do tomorrow. Controlling a population is much easier if they're never quite sure of what their rights are.
Though the US has a deeply unhealthy relationship with firearms, it might yet pull itself out of this apparent nose-dive into a form of corporate totalitarianism by forming a decent citizens army, and dealing with these people in the only way that they deserve.
Good luck.
I'm pretty sure that scientific evidence doesn't exist.
Personally, I don't remember either. But I was assuming that you're referring to infant teething, as opposed to that whole thing where your teeth grow wiggly, and fall out, and are replaced by bigger ones, and you've suddenly got a cast-iron excuse to moan about your dinner. Funny that the moaning tends to stop if candy, or biscuits, or cake are on offer, which is why I'm disinclined to believe that actual pain is involved.
Wisdom teeth are another matter, it seems, and while I personally suffered no pain, in many cases there seems to be insufficient room to contain them. I guess I must have a big mouth. If they grow in without pushing all your other teeth around, then there is no pain.
Also, fever is a scientifically measurable symptom of teething.
Well, it would be, if teething caused a fever, which I don't believe that it does.
probably the belladonna rather than the homeopathic ingredients
But I thought that the belladonna was the homeopathic ingredient - which is to say the ingredient that's present in homeopathic quantities - which is to say not present at all. Except that it was present, because they did the dilution wrong, and hence you end up with a product with belladonna in it that you proceed to place in your child's mouth.
Also, I'm very far from convinced that teething is even really a thing. Kids get grouchy and irritable for many, many reasons, and I don't know if there's any actual evidence for any teething pain. There's certainly no evidence for any teething products being effective. I mean, some people hang amber necklaces around their kid's necks and claim that it reduces teething symptoms. If anything ever suggested 'no real problem here', then that's it.
If infant tylenol cold and flu hadn't been yanked off the market....
Your FDA is weird. They can't ban 'medicines' that actually contain poisons, but they can ban paracetamol (which is what the rest of the planet calls tylenol). I notice that it's also not possible to get Kinder Surprise chocolate eggs either. Added to which, you currently have a certifiable lunatic in charge. You should just put up a big "do not visit" sign, maybe hang it off The Statue of Liberty or something.
That sure sounds like alot of work, especially the script-writing part to file by date, when the date's already in the file, and you can't search by range easily, etc. I can see your point regarding 1TB of free space, I have to pay something like $12 a month for that, but if that $12 means I don't have (another) script to write, then I'm very happy.
I mean, I'm not going to tell you that your approach is wrong, but it's just that you get all of that for nothing (ahem, other than paying for the online storage, but you've got to admit that your free 1TB of space is a bit of a fluke!) if you just give up and use Photos. Still, I'm happy you've got them backed up somewhere, if I had a dollar for every time someone has asked me if all their photos were gone when their HD crashed (yes, sorry. Yes, all of them. No I can't get them back. Yeah that does suck... etc), well, I'd have about two bucks, but it sure was a bit of a shit-show for those two guys.
May I ask what application you do use for managing a collection of photos, and what backup solution you employ for them? I am assuming that you use the machine for photos, since suggesting that you keep on plugging cameras into the machine sort of implies that.
Perhaps he's just failed to type
defaults -currentHost write com.apple.ImageCapture disableHotPlug -bool YES
At a command prompt?
More software that you need, yes.