Does the article say MS is discontinuig the production versions of SQL Server and VS? No.
Does the article say you must buy the beta if you want to license today? No.
What's the big deal? It sounds to me like there's enough customer demand to charge for the beta version of the apps for those customers who so choose. If MS has all the "free" teaters they need yet stil has customers clamoring for features/improvements in the next version, I see no reason why they can't charge these folks for early acceess.
root is unsafe because it is very easy to shoot one's self in the foot when root. Consider the trivial example of typing rm *, or rm -rf * in the wrong dir.
I'm sure this was a report sponsored in part by Apple in an attempt to boos the stock price back up soon after Apple's stock got hammered by the Street because there are widespread concerns about what Apple does "next". i.e., is the Ipod a one-hit wonder?
I'm sure the Apple zealots will mod this into oblivion.
Did you even read my post? I suggested that the questioner provide back a prioritized list along with cost ($$$ and hours) to remedy each item.
To use your analogy, the expert security company found water in the frozen pipes. I did not see where they proposed remedies (see earlier comment about follow-on engagements). So you write up a response to the VP of Pipe Protection explaining the time & $$$ required to remove the water from the pipes to prevent them from freezing again. Of course, since they are water pipes, you have a one-up on the expert security company. You don't recommend the absurd thing of removing them from the tank. You recommend wrapping them in heater tape or insulting them or somesuch. It's up to the VP of Pipe Protection to decide if the benefit of having water in the pipes outweighs the risk to the business.
You may publicly comment that he's an idiot or that your strongly disagree with him, but unless you are a VP yourself (or sleeping with one), I'd suggest you get your resume up to date.
Each person in a company has a role to play. I've been in IT for over 20 years. A very common flaw with IT people is, because they are so smart, they often want to play many roles. Unfortunately, this doesn't work well in organizations of significant size/complexity as there are already other people tasked with playing those roles.
They get paid to find every little nitpicky thing. It's in their best interest to make everything sound major (ever heard of the term follow-on engagement?)
Sit down, take the list and prepare a reasonable time & budget to fix each item along with your recommendations of the order to fix them in (based on business risk). Make sure your numbers and hours are realistic, because chances are excellent that he'll ask the consultants for the same info.
Then Mr VP can either allot internal resources to fixing the problem or hire outside consultants, or both. Business risk deals with a lot of things both real and perceived. In some cases, having the perception of risk is just as bad a the real thing (from a liability perspective, thank you Millberg Weiss).
Your VPs job is to determine the acceptable level of risk for the company. Yours is to aid him in that decision, not make it for him.
This is the biggest stumbling block to most OSS software. Developers dont get it that if they want to make a living off it they have to be customer-focused. Wheeler clearly understands this.
They also have a correspondingly long history of having huge piles of cash. If you're going to go to the expense of suing somebody, you don't waste your time on somebody who has little or no ability to pay.
At Network Mirror I'm showing 79.4% Mozilla, 18.9% IE. Since all traffic is Slashdot derived, it's probably a pretty good representative sample of the Slashdot population as a whole.
Esc-Esc might have been a ksh-only command, which would explain why I can't get it work with zsh. It really changed how I protyped shell scripts and probably helped me move to perl (if I have to open the editor window anyway, etc...)
Does the article say MS is discontinuig the production versions of SQL Server and VS? No.
Does the article say you must buy the beta if you want to license today? No.
What's the big deal? It sounds to me like there's enough customer demand to charge for the beta version of the apps for those customers who so choose. If MS has all the "free" teaters they need yet stil has customers clamoring for features/improvements in the next version, I see no reason why they can't charge these folks for early acceess.
Which assumes that one doesn't backup my homedir. I'd counter that one is more likely to do that than back up the entire box.
I think everyone with an IQ above room temperature learns not to click on random things pretty early on.
I think almost every desktop support person I know would disagree with the above statement.
Many users like to explore and click on random things. Same potential for disaster.
root is unsafe because it is very easy to shoot one's self in the foot when root. Consider the trivial example of typing rm *, or rm -rf * in the wrong dir.
Mirror here
after you knew you has been "damaged"? This happened at least 2 yrs ago.
All I see are pictures of dirt and fields and water & junk. Not a dammned egg in the bunch! :)
Look here among other places
Google is becoming the one-stop shop for information. While I know their motto is, "Do no evil", I can't help but feel a little squeamish about it.
I'm sure this was a report sponsored in part by Apple in an attempt to boos the stock price back up soon after Apple's stock got hammered by the Street because there are widespread concerns about what Apple does "next". i.e., is the Ipod a one-hit wonder?
I'm sure the Apple zealots will mod this into oblivion.
My intial post said nothing of Appletalk at all.
Did you even read my post? I suggested that the questioner provide back a prioritized list along with cost ($$$ and hours) to remedy each item.
To use your analogy, the expert security company found water in the frozen pipes. I did not see where they proposed remedies (see earlier comment about follow-on engagements). So you write up a response to the VP of Pipe Protection explaining the time & $$$ required to remove the water from the pipes to prevent them from freezing again. Of course, since they are water pipes, you have a one-up on the expert security company. You don't recommend the absurd thing of removing them from the tank. You recommend wrapping them in heater tape or insulting them or somesuch. It's up to the VP of Pipe Protection to decide if the benefit of having water in the pipes outweighs the risk to the business.
You may publicly comment that he's an idiot or that your strongly disagree with him, but unless you are a VP yourself (or sleeping with one), I'd suggest you get your resume up to date.
Each person in a company has a role to play. I've been in IT for over 20 years. A very common flaw with IT people is, because they are so smart, they often want to play many roles. Unfortunately, this doesn't work well in organizations of significant size/complexity as there are already other people tasked with playing those roles.
...what we say goes. No questions asked.
until you want to be a public company.
They get paid to find every little nitpicky thing. It's in their best interest to make everything sound major (ever heard of the term follow-on engagement?)
Sit down, take the list and prepare a reasonable time & budget to fix each item along with your recommendations of the order to fix them in (based on business risk). Make sure your numbers and hours are realistic, because chances are excellent that he'll ask the consultants for the same info.
Then Mr VP can either allot internal resources to fixing the problem or hire outside consultants, or both. Business risk deals with a lot of things both real and perceived. In some cases, having the perception of risk is just as bad a the real thing (from a liability perspective, thank you Millberg Weiss).
Your VPs job is to determine the acceptable level of risk for the company. Yours is to aid him in that decision, not make it for him.
is here
:)
The rest, you can find on your own.
It's all about support. Do you want one-time revenue or recurring revenue? Which one requires less sales critters?
You mean, you're a GNOME developer?
This is the biggest stumbling block to most OSS software. Developers dont get it that if they want to make a living off it they have to be customer-focused. Wheeler clearly understands this.
They also have a correspondingly long history of having huge piles of cash. If you're going to go to the expense of suing somebody, you don't waste your time on somebody who has little or no ability to pay.
OK, then only the smart people use the mirrors. :)
At Network Mirror I'm showing 79.4% Mozilla, 18.9% IE. Since all traffic is Slashdot derived, it's probably a pretty good representative sample of the Slashdot population as a whole.
(thank you) * 1000
That works! It must have been fixed sometime since 4.0 (which I think was when I finally abandoned hope).
No, I use Esc-k and Esc-/ (search) all day long.
Esc-Esc might have been a ksh-only command, which would explain why I can't get it work with zsh. It really changed how I protyped shell scripts and probably helped me move to perl (if I have to open the editor window anyway, etc...)
According to this, Microsoft met with them, asked them for the architecture details, the ceased contact 2 months later. Interesting.
As dubious as it sounds, it can also be a matter of, after looking at it indetail, they discovered that there was nothing special about it.
Alacritch sounds like something you need Tinactin to get rid of.