In Project Management, procurement management involves advertising and bidding contracts, selecting sellers, writing up the statement of work, quality guidelines, etc., then continuing with performance reviews and metrics to track the quality of work and determine if it meets the contract and the project needs.
Obviously, that didn't happen.
"Better" is not a purely subjective term. Something with higher quality and lower cost is objectively better.
Well, the statement was made 2 days ago, so "last year" doesn't count. Until last year, your girlfriend was single, so having sex with her last night was okay, right?
That argument is stronger. Your argument was, "If it wasn't there at the start...." which is irrelevant when speaking about proportion.
You substituted "100%" for "majority", which need only mean "50% plus some". Linux was released 23 years ago; ICC version 6 was released in 2002, 12 years ago. That's 11 years before ICC version 6.0 for Linux and 12 years with it; I don't have numbers for pre-6.0, but assume earlier releases came at chronologically earlier points in time. Given its rapid development in that period, the earliest likely release was 2000 or so; but 2002 is the earliest release I have data for.
There have been no other credible compilers for Linux throughout the majority of its existence
Except the Intel C compiler, which is inappropriate for other reasons stated (i.e. it's shitty for non-Intel architectures). Still, given the argument--a GCC bug on x86/x86-64--and the twelve years of potential tuning for icc to support high-performance situations (i.e. embedded architecture, where 16% speed-up matters), broad compiler support is reasonable. It's not like LLVM just becoming useful last year and triggering a scramble to rebase onto CLANG.
2002 was the year of Gnome 2.0, of Linux entering the 2.5 development cycle (2.4 was state-of-the-art), of SuSE 8.0, of single-core CPUs and no AMD64. It was a long time ago, a different age, when journaling file systems were hip and new and Hans Reiser hadn't murdered Nina yet.
The same thing often happens in flocks. All the creatures sense and react in the exact same way (herd animals are not noted for their individuality), at the exact same time. Even if the herd is large, they see, or hear/
Now, if they smell the creature, or if the herd is so large that some creatures can not see or hear the stimulus, then the herd starts to react to itself. But quite a lot of the time, an entire herd will become aware of the stimulus at the exact same time and react at the exact same time.
As for what we would invent, the thing about research is if we knew what we would invent, we would already have it. Research is a surprise. It always has been and always will be.
Einstein did not know he was inventing GPS, nuclear power, nuclear weapons, etc. etc. when he figured out relativity. Tesla had no idea he would invent, well, basically our entire electrical world.
If you fund it, we will INVENT. If we don't fund it, we don't invent.
You see my point, though. Knowing your administrator log-ins isn't a never-happens situation. People get user lists all the time.
By the time I was five, we had been there, done that and decided to never go back again.
If aliens do exist, they are sitting back saying "What the f?ck man, you want to meet us but don't have the energy to get off the couch and answer the door?"
Mankind does not deserve space travel. We had our chance and refused to take it.
We spend less than 5% of our national budget on space travel. Whoops, sorry make that less than 0.5%. It is a joke.
Science and technology have funded our industry for hundreds of years - yet we refuse to spend more on space industry than we do on our aircraft carrier program (old Nimitz class cost about 4.5 billion - and we have 11 of them).
25 billion? Double that and make it a real scientific program. 50 Billion is a reasonable price to pay. Not the paltry less than 20 we currently pay
It depends upon how the VPN is set up but if it's using L2TP/IPSec then every non header part of every packet will be encrypted. There will be no pattern to analyze because the encrypted packets will appear to be random data. The only things the ISP could do then would be to block the network hosting the VPN server, which is difficult because most VPN providers have lots of servers with some of them probably hosted in popular networks, or throttle all connections that cannot be decoded by the traffic shaper which would cripple SSL too. Throttling all encrypted connections is an obvious non-starter since it would ruin online e-commerce and just imagine trying to shut off all traffic to Amazon Web Services just because some VPN providers host servers with a cloud provider. That wouldn't work well either. No, the ISPs much prefer to ignore VPNs for now, since relatively few of their subscribers use them, rather than engaging in a high profile arms race with sophisticated users which would only serve to popularize the concept of VPNs and make them easier for the unwashed masses to use.
He was just asking for a few pointers.
And yet only NULL references were returned.
Yes, that's exactly what I mean.
"Aww, if you make me cry anymore, you'll fog up my helmet." -- "Visionaries" cartoon