feelix

Your resentment may or may not be valid. Can you explain any reasoning behind it?

This is an extremely well written piece of (false) propaganda. Going into why would take a long time, and each person who cares and isn't sure will need to do his or her own research.

I will note however that people are paid by Roger Ver himself to make comments like this. eg: https://np.reddit.com/r/BitcoinMarkets/comments/6rxw7k/infor...

>works for Google because they're such an attractive employer that they're dealing with essentially zero risk that they accidentally filter out all their qualified applicants with stuff like this

You know the founder of homebrew was filtered out by exactly this, right?

This advice sounds good on the surface, but the staggering incompetence I continuously see in "medical professionals" has left me with the belief that someone who is smart and has enough time is probably better off researching things on their own in many cases.

What you think you know about the experience of having a disease like HIV from passive conjecturing is nowhere what it is like actually having it, including "biomedical" symptoms.

I'm not here to try to educate you on all of the nuances of it in a comment, but suffice to say that you would not be so cavalier if you found yourself infected with HIV.

You can't fairly compare a deadly chronic disease to "not wanting to eat his vegetables'.

By calling it "his emotional state" you are, again, disregarding the disease and the effects of it on many aspects of his life. It's not his "emotional state" as you call it, it's a chronic deadly and debilitating disease which is afflicting him.

You are being dismissive and disregarding something which you appear to know nothing about. See my comment above. You have no right to pass judgement.

Unless you have a horrible incurable disease, you have absolutely no right to comment like this. You have no idea what it is like to live like that. People with such diseases are often on the verge of suicide anyway - you are unlikely to be able to put yourself in their position sufficiently to be able to judge their choices.

>The knockout punch for unencrypted sites will come when browsers make the decision to not load plain HTTP sites by default

Or encryption will just get backported to http eventually. I never understood why they didn't just do that in the first place.

My Install Disk Creator is nicer than that by any measure, in my completely biased opinion.

https://macdaddy.io/install-disk-creator/

That was due to a separate bug related to code signing. The poster above you who got downvoted was correct.

Does anyone have any theories as to how this may work, assuming that it's not a case of correlation does not equal causation?

It'd be particularly useful to have a chess bot that can play badly in the same way a human does.

The problem with the current chess bots is that they play badly, badly. They choose a terrible random mistake to make every few moves, while some of their other moves are brilliant. They cannot accurately mimic beginner or intermediate level players.

Bitcoin seems to be following Metcalfe's law[1] down to a tee. So, based on that, it seems it's not too late.

https://steemit.com/bitcoin/@eric-blair/does-metcalfe-s-law-...

When installing a major OS update it's often worthwhile to do a clean install. As a shameless plug of some free software I made, Install Disk Creator will make you a bootable USB installer out of any USB disk you have laying around made from the macOS installer that you download from Apple.

I honestly have no idea what you are talking about. Shirt Pocket would not "access/modify/create low level block devices". They would also be working at the file layer. If you mean that you think that they are implementing their own way of reading the filesystem through the POSIX node, I really dont think that they are, and also it would be crazy to try to do that.

I was initially planning on a complete rewrite in order to start supporting snapshots in a different way (by using the ones saved by APFS). Going into that was outside the scope of the article.

All of those, bar one, are from previous versions (not the latest GM) of High Sierra, and then it's not certain that that was what they were using. So granted, you have managed to find up to one case of what you were saying.

I just answered this in another response (and in addition the answer, you could answer a lot of the questions yourself by actually trying the app. It has animations built into it for example, it's clear at a glance that it's far beyond what you described):

It's also not just a GUI. There is loads of code in there that does stuff. For example:

• Scheduling for scheduled backups

• A background daemon that looks for events to launch the UI for scheduled backups

• Manipulation of disks ownership stuff in order to allow backups with permissions to happen correctly

• Volume blessing, etc, in order to make bootable volumes

• Trash handling & maintenance for deleted files

• Deleting files (for removing old backups) And that was just off the top of my head. The app is many thousands of lines of code and it performs literally hundreds of functions. They're nearly all transparent to the user, and that is the idea.

It's also not just a GUI. There is loads of code in there that does stuff. For example:

• Scheduling for scheduled backups

• A background daemon that looks for events to launch the UI for scheduled backups

• Manipulation of disks ownership stuff in order to allow backups with permissions to happen correctly

• Volume blessing, etc, in order to make bootable volumes

• Trash handling & maintenance for deleted files

• Deleting files (for removing old backups)

And that was just off the top of my head. The app is many thousands of lines of code and it performs literally hundreds of functions. They're nearly all transparent to the user, and that is the idea.

That's the way it looks until you actually try to make a commercial piece of software by doing that.

As it mentions in the blog post I come from a background of low level system programming (data recovery, even some kernel extensions, etc). It would have not added significant time to have rolled my own file copy tool. Irrespectively, it took about 1000 hours of work to make that app, as it says in the blog post. Things are nowhere as easy as they look. Doing the actual file copy is the easy part.

I finished up the APFS compatible version of the software way quicker than I thought I would, and was so happy and energized that as part of my release I whipped up a quick blog post about the experience.

Indeed it's pretty light on content, it's more just a nod to Apple for making this a painless process rather than an excruciating one, as well as an early relay of the experience to others who are going to upgrade who may be harboring some concerns like I was.

The marketing for this site sucks, the software has been around since 2011 and it has nowhere near the marketshare of its competitors because it sucks. If I were really some SEO genius (and you'll see the google rankings are terrible), then this would not be the case. In short, I wish I was the evil genius that you claim, but I'm not. I'm just a dev sharing his experience with the filesystem.

In regards to it not implementing the file copying tool directly - that is covered in the article. The fact that the file copying tool was compiled in 2015 and still works flawlessly is the whole premise of the article stating that it's impressive. And it being a _file_ copying tool is the part that _makes_ it impressive. You seem to have no idea how complex the metadata, built up over 30 years without a rewrite, on HFS+ is. Take a look at BackupBouncer and the associated blog posts to get an idea of the situation. It's pretty crazy.

It cares about those metadata a lot. Backups wont be bootable without it. And there is also disastrous data loss without it, a lot of files have their actual file data embedded in the metadata (resource forks et al). It's nuts because it's based on a 30 year old filesystem. That's one of the reasons why the smooth transition is impressive.

rsync has a ton of HFS+ specific code. Making a faithful duplicate of a file (specifically its metadata) is a feat on its own: http://blog.plasticsfuture.org/2006/03/05/the-state-of-backu...

It's the metadata that's really important. Just copying a file, while faithfully preserving metadata, is actually a feat on HFS+. That is why popular tools such as BackupBouncer (to test the integrity of backups) came to be.

What about TenX? They have a debit card you can order now

I'm just reading your blog now. The first article has this statement in it:

>The fundamentals are broken and whatever happens to the price in the short term, the long term trend should probably be downwards. I will no longer be taking part in Bitcoin development and have sold all my coins.

That was written back in January 2016. I think you were wrong about that.

I'm curious as to why you consider brilliant, production ready code.

I also read through the original codebase and I came to a different conclusion. To me it looks like something that was hacked at for a year or so, and was all just glued together. It looked like the first iteration of a codebase, the thing that you usually don't release, but then re-work so it is presentable to the outside world and then release.

To me that says a couple of things. One is that Satoshi is one, normal, human. Another is that he is very human. For example, a lot of the OP codes have had to be disabled because they were totally insecure. In early versions of bitcoin there were bugs that allowed anyone to spend anyone's bitcoins, and so forth.

Not that I mean to attack Satoshi, he was a good coder who started what could become a revolution. But he was a human like the rest of us, and it shows.

What is it about his code that makes you consider it brilliant and production ready?

Are you qualified to make these criticisms?

I'd really appreciate something that takes my hacked-together code and cleans it up and makes it presentable. That's usually the second phase of the job anyway, which could be automated.

can you elaborate on that?