" would have made it way ahead of the curve predicted by Gordon Moore"
They are ahead of the curve. Intel is postponing because of their recent trigate tech. Intel could still release 22nm right now if they wanted, but it wouldn't be worth it with such a huge difference in power leakage.
Now, if you want to look at processing power, look at GPUs. They're beyond doubling every 18 months already and are expected to approach 2.5x-3x/18months in the next 2-3 years.
There is actually quite a few cases where a managed language is faster at allocation/deallocation than a unmanged language. Yes, there is overhead, but just like multi-threading, sometimes you sacrifice a bit of overhead for overall scalability.
GC does remove some determinisim to memory management, but it does give a positive trade-off for situations where it's worth it, which is actually quite often.
On the other hand, a GC does cause many programmers to become spoiled in application design and coding, but that's not a language problem.
It would be, but application are meant to run within an OS, not across several. Also, as a system admin, you don't manage applications, you manage systems.
By server, I don't mean the physical hardware, unless stated, I mean the actual OS instance. The hosted admin manages the web servers, the db admin manages the db servers, the storage admin manages the SAN, and the systems admin manages the physical server. There is very little overlap.
The hosted admin doesn't need to know which system is web server is running on. The storage admin doesn't need to worry about anything except making sure the SAN isn't getting overloaded. The Systems admin doesn't need to know what runs on the server or where the data resides, he just needs to know how loaded the server is and shuffle around the load to other servers if need be.
The logical hierarchy just makes OS virtualization a better choice.
An OS live migration does a live copy of memory and CPU state. From the view point of the OS, nothing has changed. Nothing get's stopped or interrupted. The OS never sees anything happened, the client never sees anything happened. It's 100% transparent to all users in the system except the host OS. A small burst of packetloss during the hand-off window may happen, but packetloss is to be expect at some point in any networking system.
To be fair, Thalagyrt has been more correct than you, and quite patient with your lack of common knowledge. You pick one his one stumbling of words, which were caused by your inept knowledge on the subject coupled by your refusal to do basic research, then attempt to tear him down.
What Thalagyrt meant, is the only thing the end user may see is possibly minor packet loss during the final switch over. There is a very very small window of no response during the hand off. "fault-tolerant design of TCP" just meant the TCP stack would handle re-sending any lost data. Yes, the point is moot because every program must assume packet loss, but I knew were he was going with it and I've made the same mistake only 101 times myself. Don't focus on the fly in his distilled water, when you're drinking chemical sludge.
I find my most productive time for researching new things is 9:30-11:30 and my most productive time for complex ideas that I'm familiar with is 1p-2:30p
I don't see why you need a teacher's cert to teach at home. I was a C and D student in 1st-7th grade. My mom decided to homeschool me during 8th-10th grade. All I did was sit around, watch TV, play video games, and had lots of fun thought provoking discussions with my mom. I went back to school for 11th and 12th grade, was an A student. I slept through class, had my homework done before I got home and my teachers stopped waking me up in class to ask me a question because I got them right. They just let me sleep. The only problem is a bunch of other kids eventually saw that I did well and started to congregate around me for help explaining what the teacher just said../sigh
My 3 years of not learning taught me more than going to school ever did.
Now college, that was fun. You actually learned stuff and it was easier than highschool, less busy work and the classes were fun/interesting.
Although, all of my siblings had poor grades when bored in school. My one brother was failing math before my mom bothered the teacher enough to put my 10th grade brother in a 12th grade AP math class. Now he's getting As. My other brother was also honor roll, once they put him in more advanced classes.
My entire family finds school boring and a waste of time. The idea is great, the implementation sucks.
At my dad's work, everyone one knows this one guy who is in the union and he typically punches in for work, leaves to the local bar for an hour or so, gets drunk, comes back to work.
When he was caught, he was immediately fired, then the union fought for him and won. He still has his job and no one wants to work with him because he's always drunk.
I do this all the time, mostly when working on new things. When the busy time hits and I'm doing the grind, I "need" it less, but it still keeps be from feeling burnt out so fast.
I actually come up with most of my ideas when randomly browsing the web.
"Education is more important than the kids in school realize" Kids not caring about education is a failure of the school... and parents. Guess which one you can fix.
The kids shouldn't be punished, the school and/or parents should be.
I find a "back and forth" between high and low level has helped me.
Issue 1) Harder to write good low level code unless you can see the big picture Issue 2) Harder to create a good design(aka big picture) unless you know how things work on the low level
FF5 didn't upgrade to FF6 automatically on any of my machines. It did tell me that there was an update, but it didn't force anything. Chrome's auto-upgrade can be turned off, they just don't make it easy to the end user because 99% of the time, it shouldn't be. Anyone in IT should easily be able to disable this.
"That's not actually true for learning. I find I learn by far the fastest if thrown in to a problem, and then have someone critique what I come up with." (see "work" learning)
Here's how I learn the best for school: 1) Text book learn something new 2) Use newly learned knowledge to solve a problem 3) See correct way to solve problem; Compare and Contrast benefits and pitfalls between your way and the proper way 4), Win
Here's how I typically learn at work: 1) See problem and identify all major points 2) Design own solution 3) Look for similar solutions and Similar problem points 4) Compare and Contrast mine and others 5) Research benefits and pitfalls 6) Stumble upon proper pattern 7) Win
The school learning is nice because I brings up common issues and proper patterns. Fast and efficient.
The work learning is more rewarding because it involves more research and more intimate knowledge about the issue as a whole, which allows better incorporation of newly gained knowledge. Less efficient, but better results for most common cases. I make the assumption that whatever I come up with, someone has done before, and probably better. MSDN has a pattern for almost everything.
From one of the links going around: "...having an ideal computer, working at the freezing temperature of 3.2 Kelvin... Even sucking all the energy from a supernova would be just enough to pass through all states of a 219-bit counter... So, it is clear that a 256-bit key (which, just to be represented while we brute-force it on our ideal computer, would require the energy that 400.000.000.000.000.000.000 suns like our sun radiate in a year...) seems errrr... kinda difficult to brute-force..."
Its "effective" key size is smaller because of logic flaws.
Yeah, my cousin took an advanced cryptography class for CS, and his teacher ran the math on brute forcing a 256bit key with the theoretical physical minimum amount of energy required with ultra-advanced technology, on average would consume more usable energy than there is in the MilkyWay.
Brute forcing is out of the question for sure, unless we start to consume galaxies for energy.
Unfortunately, AES isn't perfect, and it's effective strength is much lower than 256bit. The 3-5x reduction might be enough to bring it near the realm of practical with enough money.
It's not only about being easier, but also proven. I would rather use a lockless thread-safe multi-reader/writer queue than implement it myself only to have a possible race-condition. It would be fun to learn it some day when I have free time, but enterprise code? No Way. I'll let engineers with PHDs and tons of testing figure out the hard stuff.
I can get cable internet without basic cable, but basic cable costs only $15 and if I don't bundle basic with internet, the price goes up $10. So it's effectively paying $5 for basic.../sigh
I do pay for extended, almost entirely for Discovery, TLC, History, and Cartoon.
Slashdot Mirror
" would have made it way ahead of the curve predicted by Gordon Moore"
They are ahead of the curve. Intel is postponing because of their recent trigate tech. Intel could still release 22nm right now if they wanted, but it wouldn't be worth it with such a huge difference in power leakage.
Now, if you want to look at processing power, look at GPUs. They're beyond doubling every 18 months already and are expected to approach 2.5x-3x/18months in the next 2-3 years.
Horton can hear us, we must yell louder!
Last I check, anything government sponsored shouldn't be censoring.
Or large amounts of money injected strait into your blood.
http://en.wikipedia.org/wiki/Tonsil_Trouble
There is actually quite a few cases where a managed language is faster at allocation/deallocation than a unmanged language. Yes, there is overhead, but just like multi-threading, sometimes you sacrifice a bit of overhead for overall scalability.
GC does remove some determinisim to memory management, but it does give a positive trade-off for situations where it's worth it, which is actually quite often.
On the other hand, a GC does cause many programmers to become spoiled in application design and coding, but that's not a language problem.
+1 internet for Simpson's reference
It would be, but application are meant to run within an OS, not across several. Also, as a system admin, you don't manage applications, you manage systems.
By server, I don't mean the physical hardware, unless stated, I mean the actual OS instance. The hosted admin manages the web servers, the db admin manages the db servers, the storage admin manages the SAN, and the systems admin manages the physical server. There is very little overlap.
The hosted admin doesn't need to know which system is web server is running on. The storage admin doesn't need to worry about anything except making sure the SAN isn't getting overloaded. The Systems admin doesn't need to know what runs on the server or where the data resides, he just needs to know how loaded the server is and shuffle around the load to other servers if need be.
The logical hierarchy just makes OS virtualization a better choice.
obvious troll is obvious
An OS live migration does a live copy of memory and CPU state. From the view point of the OS, nothing has changed. Nothing get's stopped or interrupted. The OS never sees anything happened, the client never sees anything happened. It's 100% transparent to all users in the system except the host OS. A small burst of packetloss during the hand-off window may happen, but packetloss is to be expect at some point in any networking system.
To be fair, Thalagyrt has been more correct than you, and quite patient with your lack of common knowledge. You pick one his one stumbling of words, which were caused by your inept knowledge on the subject coupled by your refusal to do basic research, then attempt to tear him down.
What Thalagyrt meant, is the only thing the end user may see is possibly minor packet loss during the final switch over. There is a very very small window of no response during the hand off. "fault-tolerant design of TCP" just meant the TCP stack would handle re-sending any lost data. Yes, the point is moot because every program must assume packet loss, but I knew were he was going with it and I've made the same mistake only 101 times myself. Don't focus on the fly in his distilled water, when you're drinking chemical sludge.
I find my most productive time for researching new things is 9:30-11:30 and my most productive time for complex ideas that I'm familiar with is 1p-2:30p
For boring repetitive things, any time is good.
I don't see why you need a teacher's cert to teach at home. I was a C and D student in 1st-7th grade. My mom decided to homeschool me during 8th-10th grade. All I did was sit around, watch TV, play video games, and had lots of fun thought provoking discussions with my mom. I went back to school for 11th and 12th grade, was an A student. I slept through class, had my homework done before I got home and my teachers stopped waking me up in class to ask me a question because I got them right. They just let me sleep. The only problem is a bunch of other kids eventually saw that I did well and started to congregate around me for help explaining what the teacher just said.. /sigh
My 3 years of not learning taught me more than going to school ever did.
Now college, that was fun. You actually learned stuff and it was easier than highschool, less busy work and the classes were fun/interesting.
Although, all of my siblings had poor grades when bored in school. My one brother was failing math before my mom bothered the teacher enough to put my 10th grade brother in a 12th grade AP math class. Now he's getting As. My other brother was also honor roll, once they put him in more advanced classes.
My entire family finds school boring and a waste of time. The idea is great, the implementation sucks.
At my dad's work, everyone one knows this one guy who is in the union and he typically punches in for work, leaves to the local bar for an hour or so, gets drunk, comes back to work.
When he was caught, he was immediately fired, then the union fought for him and won. He still has his job and no one wants to work with him because he's always drunk.
One personal anecdote.
" I needed a mental reboot"
I do this all the time, mostly when working on new things. When the busy time hits and I'm doing the grind, I "need" it less, but it still keeps be from feeling burnt out so fast.
I actually come up with most of my ideas when randomly browsing the web.
My new saying: "You can't inspire children to learn under a harsh regime of terror"
"Education is more important than the kids in school realize"
Kids not caring about education is a failure of the school... and parents. Guess which one you can fix.
The kids shouldn't be punished, the school and/or parents should be.
It's NY Times, just disable javascript. That's what I've read anyway, haven't tried it myself.
I find a "back and forth" between high and low level has helped me.
Issue 1) Harder to write good low level code unless you can see the big picture
Issue 2) Harder to create a good design(aka big picture) unless you know how things work on the low level
Chicken and the Egg issue.
Solution, Get experience in both areas
FF5 didn't upgrade to FF6 automatically on any of my machines. It did tell me that there was an update, but it didn't force anything. Chrome's auto-upgrade can be turned off, they just don't make it easy to the end user because 99% of the time, it shouldn't be. Anyone in IT should easily be able to disable this.
The version numbers make perfect sense and do exactly what they're suppose to do... The larger the number, the "newer" it is.
I could care less what kind of numbering system the use, so long as it's incremental.
"That's not actually true for learning. I find I learn by far the fastest if thrown in to a problem, and then have someone critique what I come up with." (see "work" learning)
Here's how I learn the best for school:
1) Text book learn something new
2) Use newly learned knowledge to solve a problem
3) See correct way to solve problem; Compare and Contrast benefits and pitfalls between your way and the proper way
4), Win
Here's how I typically learn at work:
1) See problem and identify all major points
2) Design own solution
3) Look for similar solutions and Similar problem points
4) Compare and Contrast mine and others
5) Research benefits and pitfalls
6) Stumble upon proper pattern
7) Win
The school learning is nice because I brings up common issues and proper patterns. Fast and efficient.
The work learning is more rewarding because it involves more research and more intimate knowledge about the issue as a whole, which allows better incorporation of newly gained knowledge. Less efficient, but better results for most common cases. I make the assumption that whatever I come up with, someone has done before, and probably better. MSDN has a pattern for almost everything.
Which is why I said "brute force"
From one of the links going around:
"...having an ideal computer, working at the freezing temperature of 3.2 Kelvin...
Even sucking all the energy from a supernova would be just enough to pass through all states of a 219-bit counter... So, it is clear that a 256-bit key (which, just to be represented while we brute-force it on our ideal computer, would require the energy that 400.000.000.000.000.000.000 suns like our sun radiate in a year...) seems errrr... kinda difficult to brute-force..."
Its "effective" key size is smaller because of logic flaws.
Yeah, my cousin took an advanced cryptography class for CS, and his teacher ran the math on brute forcing a 256bit key with the theoretical physical minimum amount of energy required with ultra-advanced technology, on average would consume more usable energy than there is in the MilkyWay.
Brute forcing is out of the question for sure, unless we start to consume galaxies for energy.
Unfortunately, AES isn't perfect, and it's effective strength is much lower than 256bit. The 3-5x reduction might be enough to bring it near the realm of practical with enough money.
It's not only about being easier, but also proven. I would rather use a lockless thread-safe multi-reader/writer queue than implement it myself only to have a possible race-condition. It would be fun to learn it some day when I have free time, but enterprise code? No Way. I'll let engineers with PHDs and tons of testing figure out the hard stuff.
I can get cable internet without basic cable, but basic cable costs only $15 and if I don't bundle basic with internet, the price goes up $10. So it's effectively paying $5 for basic... /sigh
I do pay for extended, almost entirely for Discovery, TLC, History, and Cartoon.
I totally agree, my post wasn't as much for argument as a practical tip for decent internet. :-)