I left that out as sour grapes. I submit apps to the app store (and also develop for other platforms); Apple's rules are actually both well-documented and fairly static. I'd be interested to see what it was that they thought was a major change, especially since with an office suite its not like they'd get into content issues (the most classic gray area).
As for code signing being a "tedious technical problem to fix"... really? Really?
From that article: "There are a rather large number of quite tedious technical problems to fix.” These included adding the required sandboxing, changing the behavior of LibreOffice to obey rules about read-write access to files within packages,"
You know, that's possibly not the best attitude the team could have taken. Sandboxing and obeying rules about not writing to your declared program files are actually both good things, and I hope the they make it back into the core package. Yes, they're "quite tedious technical problems," but if the app had been well-behaved to start with they wouldn't have taken any significant time. The fact that they did shows that the time was needed, and that's exactly the kind of boring investment in quality that rarely comes as a requirement from the community.
Why not take your MS Office budget for a year ($1M?) and hire someone (or a few someones) to build that feature for you,
You know, even at full retail, that'd get you 10,000 copies and include a very long-lived support agreement. And - protip - if you're spending 7 figures you can get a pretty hefty discount, too.
Ubuntu hacked a Motorola Atrix so it ran Android when you used it like a phone, but plug it into a dock and suddenly it became a full blown Linux desktop. That's a concept ripe with potential. Doesn't have to be Android of course, but just the idea that it's a phone when you carry it around but you can use it as a computer too with a dock with some ports on it.
Why? We're rapidly reaching the point where for the cost of the dock/monitor/keyboard/etc the additional uncharge for the processor and network card is basically zero. Combine that with cloud-storage (or even phone-storage if you have to) and you have a much simpler, more flexible solution that's usable independently.
The OS itself is a confusion of UI elements and interactions that require one to spend more time navigating the OS than using it.
That's the classic problem. I don't want an OS to be noticeable - if I see your transition as anything other than "expected", you're doing it wrong. The job of the OS should be to get the fuck out of the way and let me use my device. So far - for me at least - that leaves me at OSX/iOS by default (although they still manage to intrude, they're getting even better with age).
I feel the same way about *NIX window managers - if you have to "use" them on a regular basis, they're doing it wrong.
If you hire contractors to staff a phone bank, the contractors don't get to bring in their own phones to use, you can make them use your own phone system.
And if you hire a 3rd party corporation to do that, you're in the clear. Of course those people are often W2 employees of that corporation.
If you bring in a bunch of individuals and tell them what to do, how to do it, and even when to do it (Uber, for example, doesn't compensate you the same way if you won't work during their required hours) then that starts to look a whole lot like you have employees and are trying to dodge the tax consequences thereof.
As a tech contractor myself, I won't sub out to anyone who doesn't have an LLC and always represented myself behind one for the good of my clients.
See also everything from Cisco to Pets.Com. Just because a very few companies were not overvalued - or at least have not yet crashed - doesn't mean that the vast majority weren't.
Re:And so the cycle of "reform" continues
on
FDA Bans Trans Fat
·
· Score: 2
This stuff goes in cycles.... Butter is bad, use trans fats.... To Trans fats are bad, use butter....
Not necessarily. If Trans-Fats come back into style at some point, that's a cycle. If not then it was a mistake due to an inadequate understanding of the foodstuff, possibly caused by an inadequate sample size and time, which has now been recognized and adjusted for. So far it doesn't seem as if there'll be a big pro-trans-fat movement in the foreseeable future.
Re:Excellent. Now how about High Fructose Corn Syr
on
FDA Bans Trans Fat
·
· Score: 1
However, given the rate of obesity and type 2 diabetes in this country with strong evidence they are caused by our increased consumption of various kinds of sugar ("real" sugar and HFCS), I would be very much in favor of a relatively high tax on them.
If you won't acknowledge that the language can guide users to make the correct choices then I think you're missing the point. By your definition ASM is safe and clear. Personally I prefer to have projects coded in a language that encourages expressiveness and convention, but that's mainly because most of my time is spent on systems that are designed to live for 15-20 years. Reducing or eliminating maintenance time is more valuable to me than pure wire-level performance. Others may have different trade-offs. You should know your project's goals and choose accordingly.
If you've got a safety feature you can include at trivial incremental cost, ethically, you have to include it.
If, on the other hand, you have a safety feature that costs the manufacturer 10% of the cost of building the car and is far from standard in the marketplace, you are under no such obligation.
Except, of course, that it wasn't a self-driving car, simply a self-steering parking mode, and the driver had full control over the speed at all times. Le sigh...
Oh, please. Compared to even a moderately laden truck, a reasonable increase in fuel tax has almost no affect. Running a semi from coast to coast will burn 400-500 gallons of diesel while moving a whole lot of merchandise (and tearing up the roads in the process - a train would be far more efficient in both cases but that's not up for discussion at this point).
That thinking is why the Escalade exists - it basically counts as a commercial vehicle at the Federal level based on GVWR, and indeed can easily be registered as one locally if there's a good tax reason for doing so. Or go back further - the fact that trucks were exempt from CAFE is why the station wagon died and the SUV became a big deal. Well intentioned exemptions often do more harm than good. Whereas an extra cent per mile passed through to the person buying the service wouldn't even really show up on most transactions.
That already happens; people live in Vancouver WA (no income tax) and shop in Portland, OR (no sales tax), effectively asking the remaining residents of both states to subsidize their lifestyle.
No, the tax burden shifts from low MPG vehicles to vehicles in general. Big difference.
A better approach would be to have the fee slide based on the weight of the vehicle, since damage to roadways occurs by the square of the vehicle's weight, which would actually continue to reward more frugal drivers and shift the burden to those who actually incur the most cost.
Because that paralleled the concepts in the article, as a way of pointing out that the UI decisions people make do in fact have a tendency to influence the behavior of the users of the products (physical or digital) that they create. People build things to suggest that a certain behavior or set of decisions is "normal", "obvious", "easy", and "correct" all the time, and some times doing that sloppily or incorrectly has serious consequences.
It's so realistic you could almost swear it was motion captured. In a way it was. Some animator spent hundreds of hours watching film of how people's hair and clothes move while they danced that scene in real life, then used that knowledge to draw the cels in that movie in what your brain interprets as realistic motion. Nowadays, you just motion capture it and transfer it straight onto a 3D model via computer, without ever having to learn why it looks realistic.
Sorry, but that's not quite correct. Disney was famous for their use of rotoscoping, which basically involves filming live actors and then tracing their movements to create animations. Basically it was motion captured, just in 2D with far more primitive technology.
A company designs and builds a car to safely drive at 70 mph.
You drive at 140mph in the rain, hydroplane and lose control hitting a bridge column, and die. I'd say the fault lies with the driver. What about you?
Said company puts in an ignition switch that's faulty and disconnects the entire control system while driving at 70mph and ignores reports of this problem for a decade. That would not only be the fault of said company, but adds layers of premeditation still to be decided.
Alternately:
A company designs and builds a car to safely drive at 70mph.
They spend lots of time and money showing pictures of the car on a race track and design the interior to make it feel like a race car.
The default position of the gearshift when pulled down disables all of the speed limiters and briefly flashes a "Race mode" light that, if you read your owners' manual, indicates that you agree to not hold them responsible for anything.
A complex procedure drops you into "street mode" which baffles the exhaust to legal levels and enables traction control.
When someone drives at 80mph and wrecks, the car developers act surprised and alarmed that anyone would be so irresponsible.
Accurate points, and congratulations on your successful business - and showing that doing things the right way doesn't have to prevent you from succeeding.
Slashdot Mirror
I left that out as sour grapes. I submit apps to the app store (and also develop for other platforms); Apple's rules are actually both well-documented and fairly static. I'd be interested to see what it was that they thought was a major change, especially since with an office suite its not like they'd get into content issues (the most classic gray area).
As for code signing being a "tedious technical problem to fix" ... really? Really?
http://www.infoworld.com/article/2937816/open-source-software/libreoffice-debuts-in-the-mac-app-store.html
From that article: "There are a rather large number of quite tedious technical problems to fix.” These included adding the required sandboxing, changing the behavior of LibreOffice to obey rules about read-write access to files within packages,"
You know, that's possibly not the best attitude the team could have taken. Sandboxing and obeying rules about not writing to your declared program files are actually both good things, and I hope the they make it back into the core package. Yes, they're "quite tedious technical problems," but if the app had been well-behaved to start with they wouldn't have taken any significant time. The fact that they did shows that the time was needed, and that's exactly the kind of boring investment in quality that rarely comes as a requirement from the community.
Why not take your MS Office budget for a year ($1M?) and hire someone (or a few someones) to build that feature for you,
You know, even at full retail, that'd get you 10,000 copies and include a very long-lived support agreement. And - protip - if you're spending 7 figures you can get a pretty hefty discount, too.
Ubuntu hacked a Motorola Atrix so it ran Android when you used it like a phone, but plug it into a dock and suddenly it became a full blown Linux desktop. That's a concept ripe with potential. Doesn't have to be Android of course, but just the idea that it's a phone when you carry it around but you can use it as a computer too with a dock with some ports on it.
Why? We're rapidly reaching the point where for the cost of the dock/monitor/keyboard/etc the additional uncharge for the processor and network card is basically zero. Combine that with cloud-storage (or even phone-storage if you have to) and you have a much simpler, more flexible solution that's usable independently.
The OS itself is a confusion of UI elements and interactions that require one to spend more time navigating the OS than using it.
That's the classic problem. I don't want an OS to be noticeable - if I see your transition as anything other than "expected", you're doing it wrong. The job of the OS should be to get the fuck out of the way and let me use my device. So far - for me at least - that leaves me at OSX/iOS by default (although they still manage to intrude, they're getting even better with age).
I feel the same way about *NIX window managers - if you have to "use" them on a regular basis, they're doing it wrong.
Yes... that was my point. Many things that look "ridiculously overvalued" are, in fact, ridiculously overvalued.
The US equivalent is "drug store". Tends to be somewhat regional though, as do most things US.
If you hire contractors to staff a phone bank, the contractors don't get to bring in their own phones to use, you can make them use your own phone system.
And if you hire a 3rd party corporation to do that, you're in the clear. Of course those people are often W2 employees of that corporation.
If you bring in a bunch of individuals and tell them what to do, how to do it, and even when to do it (Uber, for example, doesn't compensate you the same way if you won't work during their required hours) then that starts to look a whole lot like you have employees and are trying to dodge the tax consequences thereof.
As a tech contractor myself, I won't sub out to anyone who doesn't have an LLC and always represented myself behind one for the good of my clients.
See also everything from Cisco to Pets.Com. Just because a very few companies were not overvalued - or at least have not yet crashed - doesn't mean that the vast majority weren't.
Just look at page 3.
This stuff goes in cycles.... Butter is bad, use trans fats.... To Trans fats are bad, use butter....
Not necessarily. If Trans-Fats come back into style at some point, that's a cycle. If not then it was a mistake due to an inadequate understanding of the foodstuff, possibly caused by an inadequate sample size and time, which has now been recognized and adjusted for. So far it doesn't seem as if there'll be a big pro-trans-fat movement in the foreseeable future.
Well summarized, AC, well summarized.
However, given the rate of obesity and type 2 diabetes in this country with strong evidence they are caused by our increased consumption of various kinds of sugar ("real" sugar and HFCS), I would be very much in favor of a relatively high tax on them.
So... not a subsidy then? 'Cos that'd be a start.
If you won't acknowledge that the language can guide users to make the correct choices then I think you're missing the point. By your definition ASM is safe and clear. Personally I prefer to have projects coded in a language that encourages expressiveness and convention, but that's mainly because most of my time is spent on systems that are designed to live for 15-20 years. Reducing or eliminating maintenance time is more valuable to me than pure wire-level performance. Others may have different trade-offs. You should know your project's goals and choose accordingly.
If you've got a safety feature you can include at trivial incremental cost, ethically, you have to include it.
If, on the other hand, you have a safety feature that costs the manufacturer 10% of the cost of building the car and is far from standard in the marketplace, you are under no such obligation.
An auto-driving car, should also auto-break.
A car like this one though, that was not auto-driving despite the misleading summary, has no such requirement.
Except, of course, that it wasn't a self-driving car, simply a self-steering parking mode, and the driver had full control over the speed at all times. Le sigh...
Oh, please. Compared to even a moderately laden truck, a reasonable increase in fuel tax has almost no affect. Running a semi from coast to coast will burn 400-500 gallons of diesel while moving a whole lot of merchandise (and tearing up the roads in the process - a train would be far more efficient in both cases but that's not up for discussion at this point).
That thinking is why the Escalade exists - it basically counts as a commercial vehicle at the Federal level based on GVWR, and indeed can easily be registered as one locally if there's a good tax reason for doing so. Or go back further - the fact that trucks were exempt from CAFE is why the station wagon died and the SUV became a big deal. Well intentioned exemptions often do more harm than good. Whereas an extra cent per mile passed through to the person buying the service wouldn't even really show up on most transactions.
That already happens; people live in Vancouver WA (no income tax) and shop in Portland, OR (no sales tax), effectively asking the remaining residents of both states to subsidize their lifestyle.
No, the tax burden shifts from low MPG vehicles to vehicles in general. Big difference.
A better approach would be to have the fee slide based on the weight of the vehicle, since damage to roadways occurs by the square of the vehicle's weight, which would actually continue to reward more frugal drivers and shift the burden to those who actually incur the most cost.
Because that paralleled the concepts in the article, as a way of pointing out that the UI decisions people make do in fact have a tendency to influence the behavior of the users of the products (physical or digital) that they create. People build things to suggest that a certain behavior or set of decisions is "normal", "obvious", "easy", and "correct" all the time, and some times doing that sloppily or incorrectly has serious consequences.
It's so realistic you could almost swear it was motion captured. In a way it was. Some animator spent hundreds of hours watching film of how people's hair and clothes move while they danced that scene in real life, then used that knowledge to draw the cels in that movie in what your brain interprets as realistic motion. Nowadays, you just motion capture it and transfer it straight onto a 3D model via computer, without ever having to learn why it looks realistic.
Sorry, but that's not quite correct. Disney was famous for their use of rotoscoping, which basically involves filming live actors and then tracing their movements to create animations. Basically it was motion captured, just in 2D with far more primitive technology.
http://www.lomography.com/maga... etc.
A company designs and builds a car to safely drive at 70 mph.
You drive at 140mph in the rain, hydroplane and lose control hitting a bridge column, and die. I'd say the fault lies with the driver. What about you?
Said company puts in an ignition switch that's faulty and disconnects the entire control system while driving at 70mph and ignores reports of this problem for a decade. That would not only be the fault of said company, but adds layers of premeditation still to be decided.
Alternately:
A company designs and builds a car to safely drive at 70mph.
They spend lots of time and money showing pictures of the car on a race track and design the interior to make it feel like a race car.
The default position of the gearshift when pulled down disables all of the speed limiters and briefly flashes a "Race mode" light that, if you read your owners' manual, indicates that you agree to not hold them responsible for anything.
A complex procedure drops you into "street mode" which baffles the exhaust to legal levels and enables traction control.
When someone drives at 80mph and wrecks, the car developers act surprised and alarmed that anyone would be so irresponsible.
Accurate points, and congratulations on your successful business - and showing that doing things the right way doesn't have to prevent you from succeeding.