I've been playing around on Apple's site in the last half hour and, frankly, it turns out to be dirt cheap.
Take any of the previous MBA or MBP, 13" or 15" as applicable, and then play around with the options. Boost its specs so it comes as close as you can get to a Retina MBP....
What is the value of a random persons stolen linkedin account... I'm trying to figure out how its not zero. I have a pretty devious mind but I can't think of any way to make money off this with a reasonable chance of success.
Many people, especially younger people, have a unique weak password. So if you've their login and their password, chances are you can also access their Facebook account, their paypal account, their bank account, etc.
You merely do a fine job of imitating native speakers. As a native speaker of English, along with those of every other native speaker my utterances define English. Of course, the reverse is true for me of Norwegian and all the many many other languages of which I'm not a native speaker.
Language is actually a lot more malleable and dynamic than you suggest.
As a native, your utterance of words define English only to the extent that you're influential enough that your peers pick up and parrot these words. I can utter the word "toaurznuok", but if only a handful of relatives understand what it means and we stick to using it between ourselves, it doesn't enter the English language -- it's merely part of our local dialect.
As a non-native, your utterance of words can also define English, whether you're speaking English with an approximative accent, your native language, or an odd mix of the two. Thus, words like tomato or avocado, which originate from Nahuatl (tomatl and huacatl respectively). Or words such as beef (from boeuf, as uttered at the dinner table by the initially French-speaking British royalty) vs cow (as in Kuh, its not-so-distant German cousin). About 30% of English words are of French origin.
Adding to this, and you'll excuse my tease, most Americans do not speak a foreign language at all, and those that do (bar first- or second-generation immigrants) generally have the mother-of-all accents.
Ireland is widely considered to be in the same boat as Greece, Portugal, Spain and Italy. They'll need to balance their budget at some point, and I wouldn't bet on the corporate tax rate to stay this low when they do.
Rovio is probably trying to pull a bluff to get a local tax break.
As humbling and troubling a thought as it is, you need to face it: If you had the above-average social skills that are relevant for this new job, you'd have held firm while negotiating, and obtained your raise.
I pay for my connection. Facebook, et al pay for their connection. Shouldn't be anything besides this.
The problem is who pays the middle man who connects you and Facebook? In particular, international cables aren't exactly cheap, and someone has to foot the bill.
Someone already does. When the traffics are materially different -- which happens frequently -- peering agreements put a price tag on the difference. This holds for voice and data. Someone gets charged for it, directly if or indirectly.
There is no such thing as a money drain in this arena: the costs are passed down to hosts and end-users, and the pipes as a whole, including international pipes, are widely profitable...
I'd be very hard pressed to shed a tear for US and EU oligopoles who are fighting their commoditization. Telecoms, in case it needs reminding, is one of if not the most profitable industries in history. This already held in the 19th century. Their lavish profits are shrinking of late? They can cry me a river.
If they're really serious about taxing this for health reasons, they should make it one dollar per ounce so that the can of coke's price skyrockets. A penny per ounce of sugar is just an excuse to raise some tax money on low earners. They might as well run a lottery for the same effect.
You just disclosed password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM" to an untrusted third party (us). You have no way to find out what we intend to do with it. Maybe we logged it and intend to publish it or to use it against you? For this reason, password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM" is now compromised. It is therefore insecure and should not be used in any situation.
Suggestions
Do not disclose your passwords to any untrusted third party for any reason.
If you are actually using password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM", stop using it and change it immediately.
Change any other password you may have compromised in this way before you used the Estatis Password Security Checker.
I'm irked to no end by articles that suggest the use of impossibly long to remember passwords. Can we please be told to use pass phrases instead?
Much about everyone knows witty quotes, religious quotes, song lyrics, movie lines, etc. Surely they can successfully use these as pass phrases? Good luck brute forcing something like this:
Proverbs 21:19 -- It is better to live alone in the desert than with a crabby, complaining wife.
Insurance deals in risks, not unknowns or certainties. There is a fine line between the two that is frequently misunderstood. A risk is an event whose probability you can calculate; an unknown is an event whose probability you cannot calculate; a certainty is, well, certain to occur.
We know for instance, with a statistically meaningful sample, that a certain percentage of the population dies or has a car accident each year. They follow near perfect gaussian distributions, and therefor are risks. You can price them appropriately and a private insurance take care of them.
From a mathematical standpoint, an insurance company's usefulness begins and ends here: guaussian distribution, large enough sample. This can be priced; nothing else can. Collecting an insurance coupon for anything else is gambling, leeching, or both -- and on the tax payer's back, more often than not.
Earthquakes or stock market moves, for instance, follow power laws, and therefor are unknowns. You cannot price them appropriately and a private insurance cannot credibly take them. When it does, you end up with lavish profits and dividends in good years (heads, I win), and State emergencies / AIGs in bad years (tails, you lose).
Health follows a power law too (diseases are contagious, health degrades with health issues) with the added twist of certainties (e.g., the majority of one's health care costs are concentrated in the last few years of one's life). These are unknowns and certainties, not risks. As such, they cannot be priced appropriately from an insurance's standpoint. For healthy people, the best an insurance can do is gamble (heads, I win); for the elderly or chronic diseases, it needs to price (or refuse to "insure") the inevitable (tails, you lose).
Yet other things, such as space flight accidents, might arguably follow gaussian distributions. They could be insured in theory -- if gaussian indeed. In practice however, the sample is too small to know the precise risk. Until it's larger, this risk cannot be adequately priced. And the best a private insurance can do is gamble. The insurance might over-price the risk and over-provision for catastrophes (heads, I win, tails, you win; yay!). It might also under-price the risk and distribute lavish dividends (heads, I win) and go bust when a space ship crashes into a nuclear power plant (tails, you lose). It simply lacks the data to take the appropriate decision; it's an unknow.
So the real question is: is the tax payer comfortable with someone winning on heads, without knowing if he'll win or lose on tails?
A sale involves many aspects, including cold-calling, setting up meetings, dealing with the paperwork, worrying about invoices, etc. all of which is best taken care of by existing sales reps.
Another aspect is to convince another programmer to buy. This should be done by someone who can explain why and how he uses the tool, complete with demo. Surely there are a couple of coders in the existing staff who can do this. Ideally, it should be someone with a knack for picking up realistic feature requests -- and be commissioned for reporting them..
Even if your sales staff have rudimentary understanding of what programming is, they'll still have no idea of what your customers do all day long, aka shovel through mountains of git branches and core dumps all day long. They'd need to have written their fair share of code to fully appreciate and communicate the usefulness of the tools you're selling.
Have the existing sales bring one of your own coders along when they meet customers. The coder should be in charge of presenting and demo'ing the product: he, more than anyone else, will be able to communicate how and why he uses your product. (Hold: your coders *do* use the tools they make because they find them very useful, right? Because if not, fix that first.)
Slashdot Mirror
Mod parent up!
So, the SSDs in these things are a proprietary Apple part? I fail to see how that is more 'elegant' and 'efficient'.
You must have been living under a rock in recent months. Apple bought Anobit last December.
I've been playing around on Apple's site in the last half hour and, frankly, it turns out to be dirt cheap.
Take any of the previous MBA or MBP, 13" or 15" as applicable, and then play around with the options. Boost its specs so it comes as close as you can get to a Retina MBP. ...
Back? Shockingly low, isn't it?
The screen real-estate on a mobile device is too tight ..
As is bandwidth. Which also tends to be ridiculously overpriced.
And is battery life, which gets drained when you serve ads over a wireless network.
Perhaps, but in this case I'd rather have an actual keyboard, mouse, and a huge screen. This product is supposedly meant to be transportable.
What is the value of a random persons stolen linkedin account... I'm trying to figure out how its not zero. I have a pretty devious mind but I can't think of any way to make money off this with a reasonable chance of success.
Many people, especially younger people, have a unique weak password. So if you've their login and their password, chances are you can also access their Facebook account, their paypal account, their bank account, etc.
If the salt used is not part of your password's hash, you're doing it wrong. Salts should be unique per user, not site-wide.
You merely do a fine job of imitating native speakers. As a native speaker of English, along with those of every other native speaker my utterances define English. Of course, the reverse is true for me of Norwegian and all the many many other languages of which I'm not a native speaker.
Language is actually a lot more malleable and dynamic than you suggest.
As a native, your utterance of words define English only to the extent that you're influential enough that your peers pick up and parrot these words. I can utter the word "toaurznuok", but if only a handful of relatives understand what it means and we stick to using it between ourselves, it doesn't enter the English language -- it's merely part of our local dialect.
As a non-native, your utterance of words can also define English, whether you're speaking English with an approximative accent, your native language, or an odd mix of the two. Thus, words like tomato or avocado, which originate from Nahuatl (tomatl and huacatl respectively). Or words such as beef (from boeuf, as uttered at the dinner table by the initially French-speaking British royalty) vs cow (as in Kuh, its not-so-distant German cousin). About 30% of English words are of French origin.
Adding to this, and you'll excuse my tease, most Americans do not speak a foreign language at all, and those that do (bar first- or second-generation immigrants) generally have the mother-of-all accents.
You forgot Hero of Alexandria's Aeolipile:
http://en.wikipedia.org/wiki/Aeolipile
Ireland is widely considered to be in the same boat as Greece, Portugal, Spain and Italy. They'll need to balance their budget at some point, and I wouldn't bet on the corporate tax rate to stay this low when they do.
Rovio is probably trying to pull a bluff to get a local tax break.
As humbling and troubling a thought as it is, you need to face it: If you had the above-average social skills that are relevant for this new job, you'd have held firm while negotiating, and obtained your raise.
It would be nice if this got merged with Street View and Google Maps.
I wonder what the figures (Blu-Ray and piracy) would look like if they sold Season-1 and Season-2 on iTunes...
Best I can recollect, the theoretical limit in question would be with single atom widths, aka 0.1nm
I pay for my connection. Facebook, et al pay for their connection. Shouldn't be anything besides this.
The problem is who pays the middle man who connects you and Facebook?
In particular, international cables aren't exactly cheap, and someone has to foot the bill.
Someone already does. When the traffics are materially different -- which happens frequently -- peering agreements put a price tag on the difference. This holds for voice and data. Someone gets charged for it, directly if or indirectly.
There is no such thing as a money drain in this arena: the costs are passed down to hosts and end-users, and the pipes as a whole, including international pipes, are widely profitable...
I'd be very hard pressed to shed a tear for US and EU oligopoles who are fighting their commoditization. Telecoms, in case it needs reminding, is one of if not the most profitable industries in history. This already held in the 19th century. Their lavish profits are shrinking of late? They can cry me a river.
If they're really serious about taxing this for health reasons, they should make it one dollar per ounce so that the can of coke's price skyrockets. A penny per ounce of sugar is just an excuse to raise some tax money on low earners. They might as well run a lottery for the same effect.
It's actually a great prank by a French Grande Ecole.
Here's what you get when you enter one:
Security assessment for password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM"
Thanks for disclosing password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM" to us!
Password Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM
Score
0 % - Insecure
Assessment
You just disclosed password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM" to an untrusted third party (us). You have no way to find out what we intend to do with it. Maybe we logged it and intend to publish it or to use it against you? For this reason, password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM" is now compromised. It is therefore insecure and should not be used in any situation.
Suggestions
Do not disclose your passwords to any untrusted third party for any reason.
If you are actually using password "Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM", stop using it and change it immediately.
Change any other password you may have compromised in this way before you used the Estatis Password Security Checker.
I'm irked to no end by articles that suggest the use of impossibly long to remember passwords. Can we please be told to use pass phrases instead?
Much about everyone knows witty quotes, religious quotes, song lyrics, movie lines, etc. Surely they can successfully use these as pass phrases? Good luck brute forcing something like this:
Proverbs 21:19 -- It is better to live alone in the desert than with a crabby, complaining wife.
Massive Cracking Array Scenario:
(Assuming one hundred trillion guesses per second) 23.36 billion trillion trillion trillion trillion trillion trillion trillion trillion trillion trillion trillion trillion trillion centuries
Insurance deals in risks, not unknowns or certainties. There is a fine line between the two that is frequently misunderstood. A risk is an event whose probability you can calculate; an unknown is an event whose probability you cannot calculate; a certainty is, well, certain to occur.
We know for instance, with a statistically meaningful sample, that a certain percentage of the population dies or has a car accident each year. They follow near perfect gaussian distributions, and therefor are risks. You can price them appropriately and a private insurance take care of them.
From a mathematical standpoint, an insurance company's usefulness begins and ends here: guaussian distribution, large enough sample. This can be priced; nothing else can. Collecting an insurance coupon for anything else is gambling, leeching, or both -- and on the tax payer's back, more often than not.
Earthquakes or stock market moves, for instance, follow power laws, and therefor are unknowns. You cannot price them appropriately and a private insurance cannot credibly take them. When it does, you end up with lavish profits and dividends in good years (heads, I win), and State emergencies / AIGs in bad years (tails, you lose).
Health follows a power law too (diseases are contagious, health degrades with health issues) with the added twist of certainties (e.g., the majority of one's health care costs are concentrated in the last few years of one's life). These are unknowns and certainties, not risks. As such, they cannot be priced appropriately from an insurance's standpoint. For healthy people, the best an insurance can do is gamble (heads, I win); for the elderly or chronic diseases, it needs to price (or refuse to "insure") the inevitable (tails, you lose).
Yet other things, such as space flight accidents, might arguably follow gaussian distributions. They could be insured in theory -- if gaussian indeed. In practice however, the sample is too small to know the precise risk. Until it's larger, this risk cannot be adequately priced. And the best a private insurance can do is gamble. The insurance might over-price the risk and over-provision for catastrophes (heads, I win, tails, you win; yay!). It might also under-price the risk and distribute lavish dividends (heads, I win) and go bust when a space ship crashes into a nuclear power plant (tails, you lose). It simply lacks the data to take the appropriate decision; it's an unknow.
So the real question is: is the tax payer comfortable with someone winning on heads, without knowing if he'll win or lose on tails?
A sale involves many aspects, including cold-calling, setting up meetings, dealing with the paperwork, worrying about invoices, etc. all of which is best taken care of by existing sales reps.
Another aspect is to convince another programmer to buy. This should be done by someone who can explain why and how he uses the tool, complete with demo. Surely there are a couple of coders in the existing staff who can do this. Ideally, it should be someone with a knack for picking up realistic feature requests -- and be commissioned for reporting them..
Both should get commissioned for the sale.
Even if your sales staff have rudimentary understanding of what programming is, they'll still have no idea of what your customers do all day long, aka shovel through mountains of git branches and core dumps all day long. They'd need to have written their fair share of code to fully appreciate and communicate the usefulness of the tools you're selling.
Have the existing sales bring one of your own coders along when they meet customers. The coder should be in charge of presenting and demo'ing the product: he, more than anyone else, will be able to communicate how and why he uses your product. (Hold: your coders *do* use the tools they make because they find them very useful, right? Because if not, fix that first.)
Don't the NSA and the DHS do this already when tracking terrorists?
How about the tear cloud?
Per deeper sub-thread, a+b = b+a is necessary for numbers because a cyclical group is necessarily abelian, therefor your point is moot.
Re (!P) I'm not rue what you were arguing about since that was what my initial reply was all about... :-P
At any rate, I believe QED and the OP's point further up is moot.