OSX Has used file extensions exclusively as the file type for a while now. You might edit a filename to remove the file extension and see that it still has an app icon, and think that file names are optional. But all that's really happened is that the "hide file extensions" flag has been added to that file. Use CMD I to see what's really going on when you rename a file in finder.

No, it's brain dead. The filename is a name. The filetype should be another piece of metadata. (and not just an executable flag either - a complete file type.)

If the file type needs to be seen by the user, then that's a UI design issue, not a reason to have brain dead mixed purpose metadata fields.

Good operating systems don't use part of the filename to store the file type. It's 2015. File types ought to be indicated by mimetypes or some other such metadata unconnected to the name.

Sadly we're limited by everyone copying the lowest common denominator.

If you never trust you never lose - but you never win either.

If someone was planning on learning a language as a stepping stone to Swift, c or c++ would be a bad choice, leading to developing bad habits that will cause frustration when moving to Swift. As I understand it they'd be best learning a functional language, after which they'll approach problems in a way which fits very well with Swift's world view.

I can't recommend the particular functional language, as I DID come up the procedural/oo path.

As an indie, perhaps. But salaries are good in OSX/iOS programming.

Not quite. Although you can compile C++ as part of an OSX or iOS project, there's no point - other than using someone else's library. The parts of projects that aren't Obj-C tend to be C.

Why?

You're dropping out of Obj-C for cross platform compatibility, because you're dealing with a low level Apple API, or because you want maximum speed for some part of the code. All these things are usually best served by C. If you're wanting objects at the expense of speed, then you wouldn't stray from Obj-C in the first place.

As we established in previous stories, you don't code in Objective-C at all. You claim experience you don't have.

In Obj-C:
NSArray *items = [string componentsSeperatedByString:@","];

Division is a single concept, whether it's ints or it's reals and complex numbers.
Bit shifting and stream i/o are completely different concepts.

We're skeptics because we see right through marketing drivel. Some technology makes sense. Some, like mobile payments, serves no practical purpose for the average consumer.

I can see why you posted AC, you were wouldn't want anyone to think you were really that stupid, right? Just trolling with an over the top utterly absurd statement, right?

I mean, replacing credit card numbers that have literally affected millions of average consumers through POS breeches, with a system just as easy to use as a CC only now the merchant never gets your card number to leak... or your name if you don't want to share it, or your drivers license number to stalk you with later (since many places rightfully ask for ID with a credit card).

I mean, there's no way anyone who can even log into Slashdot could possibly see all those things as having no benefit to everyone, much less the average consumer... right? Right?

Morale: gloomy

But!

That doesn't mean you should never contribute to hardware kick starters. It's a good idea to carefully examine what they have done before to see if they can handle making the new thing...

But!

Sometimes, it's just plain good to kickstart something even if it looks unlikely they will reach the goal. I would argue that is what happened in this case, because they found out a LOT about making this thing a lot of people want, and are sharing what they found. Eventually the thing people really wanted may well get made. If I had contributed to this Kickstarter (I did not) I wouldn't be mad, just a bit sad it didn't go through.

9% of people don't care. I set up my mother's computer with the OS on C and everything else

She sure will care if there's every a problem (and there will be a problem) with one of those drives.

As a rule of thumb it's way better not to double someones possible failure rates if they don't know themselves how to recover from it...

I've spent my life helping people get set up technically so they never need to talk to me again - at least not about their systems. It creates a lot less work for yourself, unscheduled works that generally comes at very bad times.

SSD for boot/OS/swap, and slow spinner for data gives 99% of the performance for 99% of people.

That would be great except 99% of people don't want more than one disk.

Hell, *I* don't want more than one disk, and I can ably manage them. But there's no way I can afford the SSD it would require to store everything I have (never mind the backups).

Then you're extremely lucky, I've had iOS hard lock when dogfooding apps fairly frequently

So have I, that's when I use the device reset (some combination of buttons, forget what) and it reboots in seconds.

I've never needed to drain the power to 0, no matter how bad the failure was (and they can be really bad on beta versions of iOS combined with writing apps).

No, we want a quick way to do a 100% reboot

I'm an IOS developer and I've never had to do anything more than a device reset (which is instant). Usually powering off and on is enough (though not as quick, it's still pretty quick at around a minute total).

If that's really your reason it's even more absurd.