In 2006 I got an Inspiron 6400, and almost seven years later I think the only way to stop the damn thing is to throw it into a garbage compactor: In all this time I had to change the display bezel (20 US$) , and the original battery is down to one hour of capacity, but the machine is absolutely rock-solid, to the point that my other (brand-new) notebook is used a lot less than I expected.
Why do have so many people problems accepting there are non-native English speakers? It's not difficult.
Actually, as a native English speaker living in Germany, I find Germans make these kinds of errors significantly less than native English speakers.
This can be easily explained: English as a foreign language is usually taught in primary schools and (also) in written form. Native speakers learn the basics of the language when they're little kids from their parents before they are able to write. Even when you start going to school, verbal communication is still used more (think of how many words you say during your day, even for insignificants tasks, and how many you write). If this kind of spelling mistakes are not corrected by teachers or parents, they can be easily carried on to adult age, especially for people whose daily occupation doesn't involve a lot of writing.
I just ordered (seriously) a vacuum cleaner. Please stay tuned for the test of the thermonuclear device I'm going to get.
The problem here is that, according to TFA, the developer pocketed about 1 million dollars in sales. If he even gets to keep 30% of that, after paying fees and commissions to Microsoft and taxes, it's about 300,000 US$. I understand that paying (again) a hefty certification fee sucks, but certainly we're not talking about a teenager working out of his basement.
Yes, COBOL, when compared with any modern language, sucks, because it just sports a dozen features instead of 1200. The thing is: those features are rock-solid. and this is why COBOL is still in use and programs written in the 70s still run flawlessly
... what happened to the cat?
I also think it's safe to assume that Apple is the seller of the item.
Actually not, here in Italy Apple sells a lot through non-Apple-branded channels (independent retailers, consumer electronic chains, etc.), also giiven the fact that we have just a handful of Apple Stores, and in all these cases the "seller" (as defined by the European Directive) is the retailer itself, not Apple. The fine was levied due to abuses perpetrated by Apple in its stores and on its site, so in these cases the manufacturer and the seller are the same entity.
An Apple customer who used a generic retailer could "sue" the retailer (the "seller") but of course the outcome would/could be different.
Quite the contrary: Jobs wanted to cancel or downsize almost everything else in order to support the Macintosh. What everybody seems to have forgotten is that, despite the good reception both by reviewers and the general public, the first Mac wasn't selling well: sales basically slowed down to a crawl in the second half of 1984 (when sales of the Apple II still contributed to 70% of Apple's revenue), and in March 1985 they amounted to 1/10th of the forecast. Jobs was forced to leave because hiis decisions, and his stubborness when confronted with the need to change them, were turning an innovative and promising product into a possible half-baked venture, and ultimately damaging to the whole company.
Not really an issue for Italy since the last reactor was shut dowin in 1990
Cheaper is most definitely of interest to a business, $130 may not be a lot but $130 * 500 is a significant amount
You don't buy retail in quantity 500. Volume deals drop the price to something like $50-70. Besides, you can't simply add costs up, come up with a large number and wave it in the air. If you have 500 employees you have far greater expenses, and you have even greater profit that those employees make.
There is one more thing in business, it is called COGS. It reduces the effective cost of a tool, and MS Office is a tool. So you have now a competition between a cheap top-notch tool and a free but somewhat weirder tool. What will you, as a business leader, buy? I think the decision is preordained here.
To be fair it should be said that the US$ 130 price (about the same in EUR) is for the Product Key Card versiion, a sort of not-activated OEM where the supplier of the PC bundles the software and you can optionally activate it buying a so-called "license card". Prices for a full license of Office Home and Business 2010 start from 220$ on Amazon. Not that this matters, given that most businesses are going to buy Open/volume licenses anyway.
The problem I have with Vlingo, or Google voice actions, is that they only work in English. While I have no problem in saying "Call" instead of "Chiama" (in Italian) I would have to "translate" the pronounciation of my contacts'names into English, for Google to be able to find them. This is immensely awkward and, by the way, doesn't work well (I tried). It's a pity, also because Google's voice recognition engine works very well in Italian (Voice Search works, Voice Actions do not) and a major usability hurdle: my old Nokia N70 allows to make a completely hands-free call while my new Desire HD does not. VoicePod is the only software that seems to work, but it doesn't support Bluettoth headphones.
The people behind Diaspora decided to shoot themselves in the foot when they published a software implementation with no documentation of design, protocols, etc. I just checked and no technical documentation seems to be readily available (actually I had to resort to Wikipedia to find a link to their forum), something can be probably found in bits and pieces on the support forums, but obviously it is not enough for a project whose aims are so far-reaching. To add insulto to injury, the implementation they're running with is in Ruby: now, seriously, I don't have anything against Ruby and I think diversity in programming environments is a great thing because it's what ultimately innovation comes from. But if you want to get help, support and, ultimately, code from the community, you're supposed to use a language that is more widely used so that people can get up to speed more quickly with your codebase, especially when the documentation isn't there.
No, it's typical for software written by people who don't understand the meaning of the word interoperability, or who were not given specifications in that direction. Yes, if you want to use Mono to run a large
The real problem with VB.Net is that it tries too hard to stay compatible with its awful and numbingly failure-prone predecessor (VB6). If you just activate a couple of language features ("option strict", etc.) VB.Net is actually a modern and well behaved language: there's no automatic type conversion, late binding is disabled, etc. Of course, when you do that, you also find out that writing directly in C# is much faster...