smallduck
Joined 12 years ago
Joined 12 years ago
Governments are bad: long before now there should have been rules about applying 100%-automation to previously people-driven industries, public debate about the ramifications and proposed means to keep the resulting economy working for masses of people.
That's the purpose of economies and societies, after all, to enable the livelihood of the masses. Not to fulfill the fever dream of entitled asshats at the expense of billions of livelihoods.
So if governments are as bad, and woefully delayed, at acting to support the social transformations of these utopian dreams, its the responsibility to the industrial forces pursuing them to proactively drag governments into doing so. Any firm doing one without equally the other, I just cannot support or take seriously.
People have come to expect that phones nearly always work, and rely on them for critical communication with loved ones, services like emergency services. When these aren't dependable you don't have a phone but instead a toy.
The case made two decades ago is that running arbitrary software on a phone incurs a risk that malware can compromise the device and alter its dependability. _General purpose computers don't have this historical burden._ Phone and mobile OS makers sell their products with their purposeful limitations made fairly clear. You want a mobile device with different capabilities then seek out am alternate device, it's kinda obvious.
There's always communities of people who attempt to repurpose the products they own for purposes the weren't originally intended, and I would like to see that laws that make that hobby more legitimate and legal. I would love to see 3rd parties able to support these hobbyists, that would be great. But Apple, Google with their hardware partners have no obligation to do so, and justifiable positions for making repurposing non-trivial to do.
Providers should not be making market-standard profits, or revenue that subsidize ventures other than the services rendered to those users, like media creation or M&A.
How knows how many avoided infection at all, severe symptoms, or even death because they were similarly convinced by restrictions and mandates. In this light, I really don't have much sympathy for some people who felt a little discriminated against. A public heath emergency doesn't care about your petty feelings.
To save this undo stack on this and similar platforms would also require changing the undo mechanism entirely, from using pointers into using static references having meaning across instances of the document model. The inverse model function would have to be identified by an enumeration, the object to change would have to be identified by a kind of search path. The details about saving the data, and where to save it, would be the tiniest part of this problem.
But even on these platforms, if an individual app wishes to implement a custom undo stack which supported this feature, that would be very possible. If cross-platform frameworks implemented support for this that could be a definite advantage over native APIs.
However the intent of the Swift call described in the article is indeed that of a string literal with 2 data "parameters".
So is the correct use of NSLog in this case is this:
NSLog("%@", "Failed to get modification date at URL: \(url) - \(error)")
This should really be the behavior of NSLog in Swift, that it expands not to the variadic NSLog(format-string-parameter, objc-object-parameters..)
but to NSLog(@"%@", string-parameter)