"No minimum salary" was correct. By removing the minimum wage, more jobs will open up (including less skilled and easier jobs that are now affordable to employers). By providing basic income, nobody would feel forced to work for wages that are too low.
Employer competition will result and they will have to pay competitive wages. On top of a basic income, each person would have more choice on what lifestyle they want to live.
If your current strategy works, great. But as someone who has also been involved in administering Linux and Windows boxes, Powershell is a great tool with a multitude of very useful features. As much as I love Bash, I would be very happy if Powershell got ported to Linux.
1) China's isolationism is over. That ship has left dock and there's no turning back. 2) What's worse, SK trying to rebuild NK and accepting refugees, or SK getting nuked by NK?
The difference between government and private concerns is that governments are at least hypothetically responsive to the voter.
Another difference is that private parties are responsive to their own welfare, and not just hypothetically because they must play well with others in order to have continued success.
So this debate boils down to which has more power to push common good: the set of voters or market forces? My thought is "both", and I think it's foolish to play the game of attacking one side just to promote the other.
But when pressed by Representative Anna Eshoo, a California Democrat, for the source of that claim, Cohen only cited news reports. "That takes my breath away," a visibly frustrated Eshoo said. "That is a huge allegation."
Considering that this group's main role is to investigate before making allegations, someone should be fired over this comment.
In a distributed VCS like git, there isn't really a distinction between clone and fork.
The operation is the same but the purpose is different... a fork provides the ability to push changes to the hosting service when you don't have write access to the original repository. A local clone is usually distinguished from a fork in this way.
I would imagine (hope?) that at the very least the "lifetime" period is specified in the fine print somewhere.
I would hope for much more than that. The "fine print" isn't always easily accessible at the time of purchase.
"Lifetime" should not be considered an acceptable term to establish a warranty timeframe. It's redundant; warranties are supposed to define the lifetime of the product, not the other way around.
Because it clarifies which things are certainly breaking the law. The "otherwise" clause shows the general intent of the law, but intent is subject to interpretation; the list ensures some things are not interpreted.
Which is pretty much admitting that a huge, sudden increase would cause big issues (such as sudden increases of unemployment) and that an incremental and smoother process helps.
Microsoft has a developer conference whose announcements are more directly related to the primary purpose of this site than 90% of the other posts. It happens once a year.
Don't worry, we will get back to your typical unrelated crap posts soon enough, and you'll be happy for the next 362 days.
Yes I did. But the article took a quote from its source and summarized it a bit differently. Here is the original quote from the source:
As of this writing we assume that only the file access is blocked but the files themselves are not encrypted. Experts at the G DATA SecurityLabs are still analyzing this new type of ransomware.
Sounds more like a problem where the author of the article doesn't know the difference between DOS and "not GUI".
This changes the Master Boot Record and encrypts files while it displays the skull logo and warning message. From what I can tell, you can simply unplug your computer to stop the process of encrypting your files... the earlier you stop, the fewer files are affected.
I never rely on street numbers in maps apps. It may have improved since I cared (circa 2006), but in my experience it's at best interpolated data from a variety of sources that may not be 100% accurate.
Read again. You were talking about an encrypted SMTP protocol, my comparison was HTTPS (i.e. an encrypted HTTP protocol). Since my point flew over your head, let me state it directly:
Encrypted versions of protocols are a good thing. This is evidenced by HTTPS. It's not perfect, but without it the web may never have had a chance to become as useful as it is. It would have been a burden on users. Without a standard, different encryption schemes may all need to be supported, users may need to manage certificates, and considering that headers would not be encrypted, something would have to be done about those.
An encrypted email protocol would lift those burdens. A simplified and ubiquitous system would allow significantly faster growth than a smorgasbord of options.
Is having an encrypted version of an unencrypted protocol the best? No... even better is to never have the unencrypted protocol in the first place.
"HTTP is fine, and it does exactly what it was intended to do. People like you want web servers to be something different, but always arbitrary because there is no solution which works to encrypt out of the box which can not be tampered with. You want secure, that's fine but don't make an insecure protocol for web serving the answer. Stop demanding that generic "web browsing" does it all for you, because if you trust any of the companies listed in TFA to give you bullet proof security, you are a tool."
Computers became orders of magnitude faster, smaller, and cheaper, and the industry realized simultaneous reuse (large up-front investment in writing an OS or program, and relatively tiny or zero cost to scale)... those things made computing ubiquitous, drastically raising demand.
If all of the computing industry had the same people working on it as we did in the 50s and 60s, they would be paid millions of dollars an hour today. The demand is so much larger and far outweighs any argument of meniality.
I never made a claim that all Windows-based computer OEMs are great. My claim was that Apple isn't always great, either.
In my personal experience, I can't say I've regularly used many different brands and Toshiba has never really stood out to me as producing great designs. What I can say is how Apple compares with Dell, which I've used almost exclusively at work for about 15 years. Apple was certainly worse. In that time I've had a backlight go out on a Dell laptop, and a battery that no longer held a charge. That's for about 6 different Dell computers. Compare with my 3 MacBooks over less than a decade: a bulging MacBook battery, multiple frayed chargers cables (typical use), keyboard casing breaking apart, iSight camera no longer recognized, logic board failure, and a broken trackpad. Not to mention that OS X is not supported on my oldest MacBook, but Windows would work on it along with the Dells.
I know this isn't everyone's experience, but either I'm very unlucky or Apple failures aren't as rare as folks suggest.
I agree that Time Machine is a nice backup system and Windows would do well to copy it, at least conceptually. My only complaint is that only Time Capsule is considered reliable if you want to do it continuously over Wi-Fi, and I don't want to pay so much for a router that is inferior to the one I already spent big bucks on. Having to grab the portable drive out of the fire-proof safe and individually plug up results in far fewer backups than I'd like, just from inconvenience.
"No minimum salary" was correct. By removing the minimum wage, more jobs will open up (including less skilled and easier jobs that are now affordable to employers). By providing basic income, nobody would feel forced to work for wages that are too low.
Employer competition will result and they will have to pay competitive wages. On top of a basic income, each person would have more choice on what lifestyle they want to live.
If your current strategy works, great. But as someone who has also been involved in administering Linux and Windows boxes, Powershell is a great tool with a multitude of very useful features. As much as I love Bash, I would be very happy if Powershell got ported to Linux.
1) China's isolationism is over. That ship has left dock and there's no turning back.
2) What's worse, SK trying to rebuild NK and accepting refugees, or SK getting nuked by NK?
The difference between government and private concerns is that governments are at least hypothetically responsive to the voter.
Another difference is that private parties are responsive to their own welfare, and not just hypothetically because they must play well with others in order to have continued success.
So this debate boils down to which has more power to push common good: the set of voters or market forces? My thought is "both", and I think it's foolish to play the game of attacking one side just to promote the other.
But when pressed by Representative Anna Eshoo, a California Democrat, for the source of that claim, Cohen only cited news reports. "That takes my breath away," a visibly frustrated Eshoo said. "That is a huge allegation."
Considering that this group's main role is to investigate before making allegations, someone should be fired over this comment.
In a distributed VCS like git, there isn't really a distinction between clone and fork.
The operation is the same but the purpose is different... a fork provides the ability to push changes to the hosting service when you don't have write access to the original repository. A local clone is usually distinguished from a fork in this way.
I would imagine (hope?) that at the very least the "lifetime" period is specified in the fine print somewhere.
I would hope for much more than that. The "fine print" isn't always easily accessible at the time of purchase.
"Lifetime" should not be considered an acceptable term to establish a warranty timeframe. It's redundant; warranties are supposed to define the lifetime of the product, not the other way around.
Isn't it then deceptive to not advertise the quantity of time that is considered to be "lifetime"?
Has anyone purchased this device within said quantity of time?
Does the expiration of my dishwasher warranty allow the company to send a guy to my home to permanently disable it?
Because it clarifies which things are certainly breaking the law. The "otherwise" clause shows the general intent of the law, but intent is subject to interpretation; the list ensures some things are not interpreted.
Which is pretty much admitting that a huge, sudden increase would cause big issues (such as sudden increases of unemployment) and that an incremental and smoother process helps.
Microsoft has a developer conference whose announcements are more directly related to the primary purpose of this site than 90% of the other posts. It happens once a year.
Don't worry, we will get back to your typical unrelated crap posts soon enough, and you'll be happy for the next 362 days.
Different topics should have different posts. Doing so directs conversation, provides better organization, and eases search.
It's not "Hello Login", it's just "Hello".
Well, the other side proposes that the Rich get poorer, the Poor get richer, so now the Middle Class will have more people getting screwed.
Says the person named "Anonymous Coward".
Yes I did. But the article took a quote from its source and summarized it a bit differently. Here is the original quote from the source:
As of this writing we assume that only the file access is blocked but the files themselves are not encrypted. Experts at the G DATA SecurityLabs are still analyzing this new type of ransomware.
That is a bit less confident than TFA states.
Sounds more like a problem where the author of the article doesn't know the difference between DOS and "not GUI".
This changes the Master Boot Record and encrypts files while it displays the skull logo and warning message. From what I can tell, you can simply unplug your computer to stop the process of encrypting your files... the earlier you stop, the fewer files are affected.
I never rely on street numbers in maps apps. It may have improved since I cared (circa 2006), but in my experience it's at best interpolated data from a variety of sources that may not be 100% accurate.
An encrypted email protocol is what this entire conversation is about.
Read again. You were talking about an encrypted SMTP protocol, my comparison was HTTPS (i.e. an encrypted HTTP protocol). Since my point flew over your head, let me state it directly:
Encrypted versions of protocols are a good thing. This is evidenced by HTTPS. It's not perfect, but without it the web may never have had a chance to become as useful as it is. It would have been a burden on users. Without a standard, different encryption schemes may all need to be supported, users may need to manage certificates, and considering that headers would not be encrypted, something would have to be done about those.
An encrypted email protocol would lift those burdens. A simplified and ubiquitous system would allow significantly faster growth than a smorgasbord of options.
Is having an encrypted version of an unencrypted protocol the best? No... even better is to never have the unencrypted protocol in the first place.
Same thing would apply for HTTPS, wouldn't it?
"HTTP is fine, and it does exactly what it was intended to do. People like you want web servers to be something different, but always arbitrary because there is no solution which works to encrypt out of the box which can not be tampered with. You want secure, that's fine but don't make an insecure protocol for web serving the answer. Stop demanding that generic "web browsing" does it all for you, because if you trust any of the companies listed in TFA to give you bullet proof security, you are a tool."
Computers became orders of magnitude faster, smaller, and cheaper, and the industry realized simultaneous reuse (large up-front investment in writing an OS or program, and relatively tiny or zero cost to scale)... those things made computing ubiquitous, drastically raising demand.
If all of the computing industry had the same people working on it as we did in the 50s and 60s, they would be paid millions of dollars an hour today. The demand is so much larger and far outweighs any argument of meniality.
Most importantly, they had genocidal foreign policy. Not left-wing or right-wing, but wrong-wing.
I never made a claim that all Windows-based computer OEMs are great. My claim was that Apple isn't always great, either.
In my personal experience, I can't say I've regularly used many different brands and Toshiba has never really stood out to me as producing great designs. What I can say is how Apple compares with Dell, which I've used almost exclusively at work for about 15 years. Apple was certainly worse. In that time I've had a backlight go out on a Dell laptop, and a battery that no longer held a charge. That's for about 6 different Dell computers. Compare with my 3 MacBooks over less than a decade: a bulging MacBook battery, multiple frayed chargers cables (typical use), keyboard casing breaking apart, iSight camera no longer recognized, logic board failure, and a broken trackpad. Not to mention that OS X is not supported on my oldest MacBook, but Windows would work on it along with the Dells.
I know this isn't everyone's experience, but either I'm very unlucky or Apple failures aren't as rare as folks suggest.
I agree that Time Machine is a nice backup system and Windows would do well to copy it, at least conceptually. My only complaint is that only Time Capsule is considered reliable if you want to do it continuously over Wi-Fi, and I don't want to pay so much for a router that is inferior to the one I already spent big bucks on. Having to grab the portable drive out of the fire-proof safe and individually plug up results in far fewer backups than I'd like, just from inconvenience.