Blaming a specific user can be entirely reasonable. Unless you know that everyone else has the same experience as you, you may just be an outlier that uses cables in ways they just can't handle. I don't know what you do with your cables, but I've never had the connector of any cable break on me. The cables themselves, especially near the connectors, and the connectors on devices: those break.
If you had actually tried to explain what a "template" was in words it would have helped a great deal. My assumption was that they were fixed text structures and you could fill in the blanks, but comments seem to indicate they are actually more like database schemas.
Thanks for the suggestion. We are actually working now on explaining the concept "visually" more than relying on words. They are indeed database schemas but obviously we are avoiding to use technical terms given the audience is non-technical from the business and corporate worlds.
Employees should be paid at least what they are worth. Unfortunately, the workers responsible for the top 40% of the nation's productivity make only 10% of the money.
I don't see why this user shouldn't be frustrated, though. It is still an OS-specific limitation, since it appears that Windows will run them in a manner acceptable to the user.
It seems to be intentional though. I seem to recall Microsoft and IBM got into big trouble for anti-competitive conduct. This is the sort of thing that brings about anti-trust suits.
The frustration is targeted at Apple, because someone there likely made this decision... The support was likely already written, and expressly removed, because Apple makes Thunderbolt monitors. Not to mention that Apple is known for it's wide profit margin, so any cost/benefit analysis is less meaningful in that regard.
I'm not sure where you think said frustration should be directed.
Rather than speculating on what Apple did internally, I think the real question is whether Apple advertises DisplayPort 1.2 support, since this feature is part of the DP 1.2 spec. So far I can't find anything about this on their product pages. If that's the case it's basically users demanding features that were never put into the specs of a product.
The Mini DisplayPort Connector is a small form factor connector designed to fully support the VESA DisplayPort protocol. It is particularly useful on systems where space is at a premium, such as portable computers or to support multiple connectors on reduced height add-in cards.
I agree with some frustration, but getting upset that apples aren't oranges isn't valid.
Someone would need to write the driver for this functionality. I expect Intel is happy letting apple do the work, but so long as that is the case, Apple has no need to support every hardware and protocol under the sun. They merely have to support their stuff fully, and beyond that it is someone else's problem.
Intel wrote the driver for windows, and it works on Windows. That's also apples and oranges IMO.
I am fairly certain the "trial expired" experience is exactly the reason. They're also trying to make a commodity out of software and having an app store half full of trial versions doesn't help them with that goal.
This seems more fair. But it is weird, because thinking about it, isn't buying N units of work the most fair pricing scheme? I didn't have the same gut reaction to Amazon's Lambda service.
Perhaps it is that we know the article limit isn't related to any real-world costs that make the difference.
It's fair but the worry comes in with what happens if I run out of units of work and send a new article. Does it reject the article and I miss out? Does it charge as and when I send an article[1]? Do I get charged extra for unexpected usage?
If I have to ponder any one of these questions I'd just switch to a different app, there's a fair few that provide this functionality
[1] In this case the main worry is what if I accidentally somehow send every tab I have open to this service through a bug or something? Do I pay or does the app maker take one for the team?
