Nowhere does this say what the hosting environment is. The only clue is the "gem" command in the example on the GitHub page, which wasn't familiar to me so I looked it up. Apparently this thing is for Ruby.
Yep. Undiscoverable crap that's less efficient and effective than the "regular" way.
One of the very few exceptions is two-fingered scrolling on trackpads. This is the first genuinely valuable use of multitouch I've seen.
The use of the term "jetpack design" is hypocritical when talking about this topic, however, since it's as meaningless and obscure as the designs we're complaining about.
Suggestion: Capitalize your company name in all communications. Making it lower-case shows disrespect for your own enterprise, and causes your brand to disappear amongst all the other non-proper nouns in text.
Not to mention that the assertions in this proposal are ridiculous:
"In reality, the number of items you can store in a folder is limited while computer folders have unlimited capacity"
So what? Who on earth is troubled by this? Weak attempt to create a problem where none exists.
"Another glitch is the possibility to store folders in folders which is not possible in real live."
Also wrong. It's quite possible to store folders in folders in real life. And you can put folders in boxes, which are nothing but a different-shaped folder. Again, this is a lame attempt to shore up a weak argument with sham "problems."
There are way bigger problems to fix on this site than table usage. How about the mysteriously broken log-ins? The lack of a way to recover the password that it claims is erroneous? The abysmal performance? The "you're posting too fast" even if you haven't posted anything in two hours?
How is it "more efficient"? Square is for garage sales. Why would a brick-and-mortar chain with electricity and Internet access use a flimsy mobile payment system, when they can use a regular card reader?
More condescending bullshit. It has nothing to do with "letting go." It has to do with GETTING THINGS DONE. There wasn't a problem here. NOW there is. GJ, Apple.
Standard smug, bullshit answer whenever glaring design defects are brought up in Apple products. Nice condescension with "you simply." No, you don't "simply" do this, because there is no way for the user to guess the defective turn of events that's about to happen.
Not to mention that the "Save As" option might as well not exist. The fact that Apple allows hidden, secret menus that are only revealed by pressing unindicated modifier keys disproves the myth of Apple's "elegance" and "attention to detail." Apple continually chooses the most cumbersome, error-prone, and idiotically roundabout solutions to simple problems.
In this case, there WAS no problem. How many layers of shit are they going to heap onto this OS? Time Machine was supposed to solve data-loss problems. Now we have a bloated, system-wide, redundant overseer for files. And sure enough, it causes data loss. Not only in this example here (which most people will never encounter because there is still, essentially, no "Save As" option) but also in regular usage. Xcode developers have had chunks of their source files simply disappear, followed by a prompt claiming that an external application modified the file.
There are so many things for Apple to fix (such as the disgraceful Finder), and they're not only wasting time loading the OS up with garbage like this, but wasting users' time by destroying their data.
Kind of a critical piece of info.