Success in pretty much every field depends on brilliance, enthusiasm and perseverance in roughly equal measure. If you have 2 out of 3, you will probably earn a good living. It's unlikely that all 3 are significantly correlated with gender in any field, be it software development or early childhood education. If you live in United States and rule out a career path based on your gender, you likely have to do some work on yourself rather than blaming any external factors.
Of course! A physical 5 processor machine running at 3Ghz would cost peanuts in hardware and power compared to an intentionally crippled 141 processor mainframe. What really happens is you pay (cost - subsidy) for the crippled machine and you or someone else eventually pays (cost + subsidy) for the less crippled machine.
With software, the equation is better. If someone sells you an edition limited to certain number of concurrent transactions, there are no manufacturing costs for your copy that have to be passed to someone else. Furthermore, you have a choice of free software and more basic software from company with smaller development costs. If done right, basic editions can also have lower memory and CPU requirements.
Unless you are saying that IBM is selling $1M systems that cost $50K to manufacture and their marginal costs are also negligible. In this case, you are better off going with a company with lower development costs that addresses just your use case specifically.
To a finances guy, it means you pay for all your hardware and its power use, but have access only to a subset of it most of the time. Inactive hardware costs exactly same as active hardware to develop and manufacture. You are paying for a "discount" on spare capacity with jacked up prices for active capacity.
You are going to serve your Chinese customers from US datacenters? Hehe. Connectivity between world regions is glitchy and high latency. Amazon, for example, provides 9 regions for its compute instances and they don't spend money for these datacenters just for the heck of it.
Even within a region, you are proposing paying for network and other equipment to handle 100% of peak traffic in each datacenter, while one sits idle most of the time. It would be much cheaper, and provide lower latency, to have 3 datacenters capable of handling 50% of peak traffic and all taking traffic at the same time. If one fails or suffers a network partition, the other two maintain a quorum and continue processing requests. In your scheme, a failover will lose at least some recent changes.
As for your "CBU engines", they are regular hardware crippled by DRM. You are paying for your "cheap" backup mainframe by jacked up prices on your primary mainframe. If both were the same, you would have access to more capacity for the same price.
Hence the point that you should not buy those unless you can afford a dozen. If I only need the power of one of those, I would be better off purchasing less powerful/cheaper systems to distribute worldwide.
No matter how reliable and maintainable the box itself is, I wouldn't want my business to lose days or weeks of revenue because the datacenter was swallowed by a sinkhole. Having hundreds of cloud compute instances around the world also helps compensate for network latencies and quickly cut expenses during a business downturn.
I am sure there is a scale at which it makes sense to have dozens of these boxes rather than many thousands of separate instances. Just not sure if volume is enough for IBM to recoup their 1B investment. Good luck!
systemd team has interesting ideas about new features and performance improvements that can be achieved with legacy-free and tightly integrated code base for standard UNIX daemons. Once the benefits are proven, it would be easy to pick and choose between simplicity/modularity and performance and some features can be ported to shell-based init. I don't see systemd developers forcing anyone to use the project.
Yes, but it takes a week to find papers and reset passwords for direct import from bank/brokerage accounts. If you have a hardcopy of everything in one place, filing by yourself is dead simple too.
You do realize you can download an image and upgrade now rather than waiting right? The first time you ever do it, you will need to backup and restore a device, but pretty simple otherwise.
Uh.. no! There are no sane reasons for using 1.44MB storage medium. I would fully understand CD-RW, zip drives or sd cards for reasons you described. And if you don't want to depend on single vendor, Blackberry is not the best choice.
From what I understand, all it takes is one knock with a hammer to ensure platters are bent and can never be used again. And there is no known practical method to restore data after a single overwrite with 0s. Everything else is pure paranoia.
- person uses drive for copyright infringement, a civil offense - a lawsuit is filed - it's now a criminal offense to destroy evidence
For civil cases, police is not involved, but it's legal requirement for both parties to preserve evidence and testify truthfully. For criminal cases, you can lie/conceal all you want without additional penalty. But jury will consider how trustworthy you appear to be very heavily.
He did exactly that and.gitignore was accidentally lost.
Service providers are responsible for 90% of work by designing solutions secure by default and in depth. It should take multiple explicit steps and dismissed warnings for an inexperienced developer to incur a catastrophic financial liability.
telnet and ftp practically died a while back, http is on the way out. In most corporate environments, other protocols such as X are local only and remote use is over ssh tunnels. IMAP/SMTP takes place over TLS when using decent providers. I guess there is a question of whether SSH and HTTPs should be merged. But a lot of work has been put in both and would be difficult to replicate and make as secure from the start. No hurry.
The only exceptions are organizations with lax security (like Sony apparently) and cases where security or integrity is completely not an issue. I guess if you broadcast a video as unencrypted UDP over a local network, that's fine.
Nope, there are things YOU can say in Japanese but not in English. Someone who has to communicate in English will use idioms and allegories to express nuances of their feelings. May not be as compact, but will do the job.
Single world language is a great thing, and I don't care if it's Spanish, Chinese or (most likely) broken English. We will get much better science when everyone can instantly read everyone else's research. With that come huge tangible improvements to our lifestyle, like clean energy, high yield/nutrition crops and cure for cancer. Next, wide access to world news and entertainment will reduce armed conflict and increase people's demands on their own governments. Even non-political soap operas invite the question of "why the frak can't we live like this".
Once we are done with language, I think we will end racial conflict by ending race. This is well underway in SF Bay Area. Nobody under the age of 30 really cares. After a few generations of gene mixing, there will be no large homogenous groups that can gang up against others.
Oh sure, there will be holdouts. I envision pure Caucasian villages in Wyoming where conservatives can, with full public support and protection, practice their indigenous hunting, armed self protection, petrol-based lifestyle, "traditional family" culture and religion. They will probably refuse government-provided healthcare in favor of homeopathy mixed in whisky and enjoy booming trade with Amish.
When you sign up for a developer account, you should be asked how much you plan to spend per month. $2375/day would not be a common option for an individual. Given proliferation of free 15GB storage accounts, a very low end developer account with no credit card is not a crazy option. People will learn the API and use it in future, but neither them nor hackers will have enough quota to run a production site. This is just like limited data cell plans where a single buggy app can run up crazy charges. Good that they refunded money, but fundamental structural problem must be fixed.
Seriously, spending the whole day in isolation and, except for a lucky few, away from natural light is depressing. Being able to holler a joke across the hallway or look at sunshine through a shared window makes all the difference. There are always noise cancelling headphones for when you need total concentration.
If good science would be still available after a decade (Opportunity) or many decades (Voyager), at least light components like flash and electronics in general should be designed with good degree of redundancy. Or else if the probe has a limited mission and has accomplished it, there is nothing wrong with abandoning it and focusing money and talent on new missions. Would engineers working on attempts to fix Opportunity be more useful working on newer Curiosity mission? My gut feeling is that making existing missions last longer is much more cost effective than launching new ones. But I am not a space scientist. The point is that mission planning should have clear focus one way or the other.
If you take a chance at making a cutting age product, technology or culture may not be ready for it. Or another company, even a startup, may take your idea and manage to make a much more successful product. But if you stick to your guns, you are 100% guaranteed to slowly fade to irrelevance. Would you rather your company end up like Yahoo or IBM in 30 years? The later at least had courage to go big on Linux even though it was in direct competition in its mainframe business. They achieved a measure of success there, even as other, more radical, research projects went nowhere. But if they were not at least exploring where the future is going, they would surely be goners by now.
Say, I further "encrypt" my https sessions using ROT13. If NSA is on to me specifically, they will have no problem figuring it out. But if they opportunistically monitor main internet pipes for vulnerable traffic, I should be safe. What if web browsers encrypted data with one of hundreds of algorithms independently developed by smart people worldwide *before* standard https? At least some of them will prove resistent to cryptanalysis and even vulnerable ones will consume some of NSA's computing power and employee time to crack.
Slashdot Mirror
Success in pretty much every field depends on brilliance, enthusiasm and perseverance in roughly equal measure. If you have 2 out of 3, you will probably earn a good living. It's unlikely that all 3 are significantly correlated with gender in any field, be it software development or early childhood education. If you live in United States and rule out a career path based on your gender, you likely have to do some work on yourself rather than blaming any external factors.
Of course! A physical 5 processor machine running at 3Ghz would cost peanuts in hardware and power compared to an intentionally crippled 141 processor mainframe. What really happens is you pay (cost - subsidy) for the crippled machine and you or someone else eventually pays (cost + subsidy) for the less crippled machine.
With software, the equation is better. If someone sells you an edition limited to certain number of concurrent transactions, there are no manufacturing costs for your copy that have to be passed to someone else. Furthermore, you have a choice of free software and more basic software from company with smaller development costs. If done right, basic editions can also have lower memory and CPU requirements.
Unless you are saying that IBM is selling $1M systems that cost $50K to manufacture and their marginal costs are also negligible. In this case, you are better off going with a company with lower development costs that addresses just your use case specifically.
To a finances guy, it means you pay for all your hardware and its power use, but have access only to a subset of it most of the time. Inactive hardware costs exactly same as active hardware to develop and manufacture. You are paying for a "discount" on spare capacity with jacked up prices for active capacity.
You are going to serve your Chinese customers from US datacenters? Hehe. Connectivity between world regions is glitchy and high latency. Amazon, for example, provides 9 regions for its compute instances and they don't spend money for these datacenters just for the heck of it.
Even within a region, you are proposing paying for network and other equipment to handle 100% of peak traffic in each datacenter, while one sits idle most of the time. It would be much cheaper, and provide lower latency, to have 3 datacenters capable of handling 50% of peak traffic and all taking traffic at the same time. If one fails or suffers a network partition, the other two maintain a quorum and continue processing requests. In your scheme, a failover will lose at least some recent changes.
As for your "CBU engines", they are regular hardware crippled by DRM. You are paying for your "cheap" backup mainframe by jacked up prices on your primary mainframe. If both were the same, you would have access to more capacity for the same price.
Hence the point that you should not buy those unless you can afford a dozen. If I only need the power of one of those, I would be better off purchasing less powerful/cheaper systems to distribute worldwide.
No matter how reliable and maintainable the box itself is, I wouldn't want my business to lose days or weeks of revenue because the datacenter was swallowed by a sinkhole. Having hundreds of cloud compute instances around the world also helps compensate for network latencies and quickly cut expenses during a business downturn.
I am sure there is a scale at which it makes sense to have dozens of these boxes rather than many thousands of separate instances. Just not sure if volume is enough for IBM to recoup their 1B investment. Good luck!
systemd team has interesting ideas about new features and performance improvements that can be achieved with legacy-free and tightly integrated code base for standard UNIX daemons. Once the benefits are proven, it would be easy to pick and choose between simplicity/modularity and performance and some features can be ported to shell-based init. I don't see systemd developers forcing anyone to use the project.
Yes, but it takes a week to find papers and reset passwords for direct import from bank/brokerage accounts. If you have a hardcopy of everything in one place, filing by yourself is dead simple too.
You do realize you can download an image and upgrade now rather than waiting right? The first time you ever do it, you will need to backup and restore a device, but pretty simple otherwise.
I can not even begin to describe goodness of the syntax. It's forever etched in my mind, right along goatse and tubgirl.
Uh.. no! There are no sane reasons for using 1.44MB storage medium. I would fully understand CD-RW, zip drives or sd cards for reasons you described. And if you don't want to depend on single vendor, Blackberry is not the best choice.
From what I understand, all it takes is one knock with a hammer to ensure platters are bent and can never be used again. And there is no known practical method to restore data after a single overwrite with 0s. Everything else is pure paranoia.
- person uses drive for copyright infringement, a civil offense
- a lawsuit is filed
- it's now a criminal offense to destroy evidence
For civil cases, police is not involved, but it's legal requirement for both parties to preserve evidence and testify truthfully. For criminal cases, you can lie/conceal all you want without additional penalty. But jury will consider how trustworthy you appear to be very heavily.
He did exactly that and .gitignore was accidentally lost.
Service providers are responsible for 90% of work by designing solutions secure by default and in depth. It should take multiple explicit steps and dismissed warnings for an inexperienced developer to incur a catastrophic financial liability.
telnet and ftp practically died a while back, http is on the way out. In most corporate environments, other protocols such as X are local only and remote use is over ssh tunnels. IMAP/SMTP takes place over TLS when using decent providers. I guess there is a question of whether SSH and HTTPs should be merged. But a lot of work has been put in both and would be difficult to replicate and make as secure from the start. No hurry.
The only exceptions are organizations with lax security (like Sony apparently) and cases where security or integrity is completely not an issue. I guess if you broadcast a video as unencrypted UDP over a local network, that's fine.
Nope, there are things YOU can say in Japanese but not in English. Someone who has to communicate in English will use idioms and allegories to express nuances of their feelings. May not be as compact, but will do the job.
I think the need for instructions to operate a toilet point more to falling average human intelligence than anything about languages?
Single world language is a great thing, and I don't care if it's Spanish, Chinese or (most likely) broken English. We will get much better science when everyone can instantly read everyone else's research. With that come huge tangible improvements to our lifestyle, like clean energy, high yield/nutrition crops and cure for cancer. Next, wide access to world news and entertainment will reduce armed conflict and increase people's demands on their own governments. Even non-political soap operas invite the question of "why the frak can't we live like this".
Once we are done with language, I think we will end racial conflict by ending race. This is well underway in SF Bay Area. Nobody under the age of 30 really cares. After a few generations of gene mixing, there will be no large homogenous groups that can gang up against others.
Oh sure, there will be holdouts. I envision pure Caucasian villages in Wyoming where conservatives can, with full public support and protection, practice their indigenous hunting, armed self protection, petrol-based lifestyle, "traditional family" culture and religion. They will probably refuse government-provided healthcare in favor of homeopathy mixed in whisky and enjoy booming trade with Amish.
ASCII porn in bash is evil man! At least he was not using rc.
When you sign up for a developer account, you should be asked how much you plan to spend per month. $2375/day would not be a common option for an individual. Given proliferation of free 15GB storage accounts, a very low end developer account with no credit card is not a crazy option. People will learn the API and use it in future, but neither them nor hackers will have enough quota to run a production site. This is just like limited data cell plans where a single buggy app can run up crazy charges. Good that they refunded money, but fundamental structural problem must be fixed.
Seriously, spending the whole day in isolation and, except for a lucky few, away from natural light is depressing. Being able to holler a joke across the hallway or look at sunshine through a shared window makes all the difference. There are always noise cancelling headphones for when you need total concentration.
If good science would be still available after a decade (Opportunity) or many decades (Voyager), at least light components like flash and electronics in general should be designed with good degree of redundancy. Or else if the probe has a limited mission and has accomplished it, there is nothing wrong with abandoning it and focusing money and talent on new missions. Would engineers working on attempts to fix Opportunity be more useful working on newer Curiosity mission? My gut feeling is that making existing missions last longer is much more cost effective than launching new ones. But I am not a space scientist. The point is that mission planning should have clear focus one way or the other.
I wouldn't put this laptop on my lap after lithium batteries have been abused to such degree.
If you take a chance at making a cutting age product, technology or culture may not be ready for it. Or another company, even a startup, may take your idea and manage to make a much more successful product. But if you stick to your guns, you are 100% guaranteed to slowly fade to irrelevance. Would you rather your company end up like Yahoo or IBM in 30 years? The later at least had courage to go big on Linux even though it was in direct competition in its mainframe business. They achieved a measure of success there, even as other, more radical, research projects went nowhere. But if they were not at least exploring where the future is going, they would surely be goners by now.
Say, I further "encrypt" my https sessions using ROT13. If NSA is on to me specifically, they will have no problem figuring it out. But if they opportunistically monitor main internet pipes for vulnerable traffic, I should be safe. What if web browsers encrypted data with one of hundreds of algorithms independently developed by smart people worldwide *before* standard https? At least some of them will prove resistent to cryptanalysis and even vulnerable ones will consume some of NSA's computing power and employee time to crack.