3) Apple loses a major leader in their OS development team, stating he wants to pursue "other interests"
***whistles***
If you are thinking what I think you are thinking...stop thinking it. Undoubtedly, he'll have a non-compete for some period of time 6-12 months I'd guess.
Don't forget either, "pursue other interests" could just be good PR for he's being asked to leave. I doubt that's the case unless he and Steve had a serious falling out over the direction of OS X. Is it the end of an era at Apple? No doubt ... but will it cause serious problems for the OS X development team ... I doubt it. Apple will find some other bright mind capable of handling the design and implementation of OS X to replace him and life will go on for both the company and we, the loyal users.
Edison devloped the light bulb, but it was those who came after him that improved on his design and theories that gave us longer lasting, more powerful bulbs, halogen bulbs, neon lights, etc.
Somebody who leads a team of 350 people is not somebody who has much input on the code - the people at the bottom matter more than the people at the top.
Avie Tevanian has joined MS in the Windows group to develope a windows shell. In order to keep the look and feel that windows users have come to love a few bugs and hardware conflicts have been added.
Don't forget either, "pursue other interests" could just be good PR for he's being asked to leave. I doubt that's the case unless he and Steve had a serious falling out over the direction of OS X. Is it the end of an era at Apple? No doubt ... but will it cause serious problems for the OS X development team ... I doubt it. Apple will find some other bright mind capable of handling the design and implementation of OS X to replace him and life will go on for both the company and we, the loyal users.
Edison devloped the light bulb, but it was those who came after him that improved on his design and theories that gave us longer lasting, more powerful bulbs, halogen bulbs, neon lights, etc.
Avie is Steve's right hand. He and him are very solid. The man's put in his time--nearly 20 years.
Bertrand will most certainly take his spot and yet the spot might be have a revised approach because Bertrand's areas of expertise are quite varied and he loves to keep his hands in the cookie jar to improve matters.
Avie was a phenomenal taskmaster. Read: he kept people on task and his will always prevailed thus garnering respect from Steve for always delivering products. This didn't always sit well with the less disciplined members in engineering but then again the taskmaster's job is to shape a direction and meet it.
Avie was a very conservative and matter-of-fact.
That daring fireball article is a joke. The biggest delay in OS X has been accommodating the Carbon/Classic cruft of the past. His "flamed" support note was a reflection of the dichotomy between the past and the future.
OS X will continue to gain in performance the less and less legacy crap is retained in the OS. And that legacy is the transition layer, Carbon.
Somebody who leads a team of 350 people is not somebody who has much input on the code
Maybe not, but you can bet he checks up on it aloing the way. And just because he doesn't spend his day coding, doesn't mean he can't or that he doesn't know what's going on under him. I bet Steve hasn't done any coding on Mac OS in a long time, but I'm pretty sure he takes a look at its development every now and then.
Steve: "Avie, we're going to add feature X to the next OS X upgrade. Get it done."
Avie: "Sure Boss"
Avie to Coding Group assigned to new feature X: "Guys, this is what we're going to do, this is how it needs to look, this it what it needs to be able to do"
Programmers: "All right ... <type, type, type>"
Avie upon examining compiled code: "Wow, this is great, it works fine" OR "Wow, this is shitty and slow, guys. Let me see the source..."
That's why he's there. He offers his input when its needed. He should expect it to be working when it finishes compiling and the programmers give it to him, but it's not what Steve wants or he comes up with some better idea then he might ask them to try something different.
Quote:
Originally posted by e1618978
the people at the bottom matter more than the people at the top.
Eh, as someone who's been on both ends of that rope as a peon and a supervisor (in construction, not programming, but they kinda work the same way...) they both matter equally. It's too much work for one person to do, so he has a team that (hopefully) is very good at its job and he trusts. He's been there before, knows how it should be done and expects is done a certain way. He comes back and checks up on the job, make ssure it's going according to schedule and plans then he comes back at the end, inspects the final product and *poof* you're done. He needs those under him to finish the job.
Other side of the coin - something happens in the build, unexpected compatibility problems, unexpected errors, differing of opinions - that's when supervisors are important. The interject their experiences, they make the call and they're ultimately responsible for the success or failure of the project.
Take football as an example: The quaterback can't throw the ball unless he has a line to block for him, but the line is pretty useless if they don't know what play the quaterback has called, and at the end of the game, people will usually blame the team's success or failure on the quaterback - not the line.
One of Apples great assets. He even gets along great with the man!!
That all being said, the past seven years have been a burner on folks. Steve himself was talking about the need to throttle development times back to something that could be considered half sane.
A March 31 resignation announced on March 28 just doesn't smell right.
Apple is aware of how Avie and Steve J. are viewed, particularly by the market. One would think they would announce such a departure months in advance and name a successor at the same time.
Such a speedy departure certainly looks like there was a "difference of opinion".
Either way, thanks Avie - your tireless work in keeping the Mac platform ahead of the curve will definitely go down in history.
That daring fireball article is a joke. The biggest delay in OS X has been accommodating the Carbon/Classic cruft of the past. His "flamed" support note was a reflection of the dichotomy between the past and the future.
OS X will continue to gain in performance the less and less legacy crap is retained in the OS. And that legacy is the transition layer, Carbon.
This is pure fantasy. Carbon is faster than Cocoa, and neither have anything to do with how slow the core of MacOS X is as a UNIX (which is pretty darn slow). The only legacy code in MacOS X is the Classic environment and that is optional anyway.
At this point MacOS X can only gain in performance through honest-to-goodness new research and development on locking mechanisms, thread/process spawning, I/O buffer sharing, and other low-level OS mechanics. These are features that already exist in most of the other major OSes. In other areas, they're ahead, such as VM paging, but those areas aren't common. They are going to need a new Avie.
A March 31 resignation announced on March 28 just doesn't smell right.
Apple is aware of how Avie and Steve J. are viewed, particularly by the market. One would think they would announce such a departure months in advance and name a successor at the same time.
Such a speedy departure certainly looks like there was a "difference of opinion".
Could be just that it was publicly "discovered" this week and someone asked Apple and they confirmed.
Don't know.
I would have expected a more public announcement further back. But perhaps they chose not to for some other reason.
Avie is Steve's right hand. He and him are very solid. The man's put in his time--nearly 20 years.
Bertrand will most certainly take his spot and yet the spot might be have a revised approach because Bertrand's areas of expertise are quite varied and he loves to keep his hands in the cookie jar to improve matters.
Avie was a phenomenal taskmaster. Read: he kept people on task and his will always prevailed thus garnering respect from Steve for always delivering products. This didn't always sit well with the less disciplined members in engineering but then again the taskmaster's job is to shape a direction and meet it.
Avie was a very conservative and matter-of-fact.
That daring fireball article is a joke. The biggest delay in OS X has been accommodating the Carbon/Classic cruft of the past. His "flamed" support note was a reflection of the dichotomy between the past and the future.
OS X will continue to gain in performance the less and less legacy crap is retained in the OS. And that legacy is the transition layer, Carbon.
as someone who's been on both ends of that rope as a peon and a supervisor (in construction, not programming, but they kinda work the same way...)
They don't work the same way at all - if you want to use a construction analogy, it would be like being a construction manager where you can't leave the trailer to go look at the building. All you get are reports from your workers, inspectors and customers - and all of them know more about what your building is and should be than you do.
Even a first level manager (with 10 engineers, say, working for them) will probably never have time to look at a single line of code - and even if they spent all their time looking at it, they would only be able to see and understand 5% of it.
A team of good engineers with a bad manager will still get the job done - but a good manager will never be able to get the job done with a team of lousy engineers, which is why people at the bottom matter more to your success or failure.
I wouldn't worry about the loss of a VP - the time you have to worry is when you start losing lots of programmers (like microsoft is doing right now).
Comments
Originally posted by Anders
1) MS delaying their next OS.
2) MS emplyees complains over their bosses
3) Apple loses a major leader in their OS development team, stating he wants to pursue "other interests"
***whistles***
If you are thinking what I think you are thinking...stop thinking it. Undoubtedly, he'll have a non-compete for some period of time 6-12 months I'd guess.
Originally posted by AgNuke1707
Don't forget either, "pursue other interests" could just be good PR for he's being asked to leave. I doubt that's the case unless he and Steve had a serious falling out over the direction of OS X. Is it the end of an era at Apple? No doubt ... but will it cause serious problems for the OS X development team ... I doubt it. Apple will find some other bright mind capable of handling the design and implementation of OS X to replace him and life will go on for both the company and we, the loyal users.
Edison devloped the light bulb, but it was those who came after him that improved on his design and theories that gave us longer lasting, more powerful bulbs, halogen bulbs, neon lights, etc.
Somebody who leads a team of 350 people is not somebody who has much input on the code - the people at the bottom matter more than the people at the top.
what can apple possibly improve on besides finder for the next OS?
the only complaints i have with OSX is finder, thats it i think.
MS has purchased the right to license OSX.
Avie Tevanian has joined MS in the Windows group to develope a windows shell. In order to keep the look and feel that windows users have come to love a few bugs and hardware conflicts have been added.
Originally posted by AgNuke1707
Don't forget either, "pursue other interests" could just be good PR for he's being asked to leave. I doubt that's the case unless he and Steve had a serious falling out over the direction of OS X. Is it the end of an era at Apple? No doubt ... but will it cause serious problems for the OS X development team ... I doubt it. Apple will find some other bright mind capable of handling the design and implementation of OS X to replace him and life will go on for both the company and we, the loyal users.
Edison devloped the light bulb, but it was those who came after him that improved on his design and theories that gave us longer lasting, more powerful bulbs, halogen bulbs, neon lights, etc.
Avie is Steve's right hand. He and him are very solid. The man's put in his time--nearly 20 years.
Bertrand will most certainly take his spot and yet the spot might be have a revised approach because Bertrand's areas of expertise are quite varied and he loves to keep his hands in the cookie jar to improve matters.
Avie was a phenomenal taskmaster. Read: he kept people on task and his will always prevailed thus garnering respect from Steve for always delivering products. This didn't always sit well with the less disciplined members in engineering but then again the taskmaster's job is to shape a direction and meet it.
Avie was a very conservative and matter-of-fact.
That daring fireball article is a joke. The biggest delay in OS X has been accommodating the Carbon/Classic cruft of the past. His "flamed" support note was a reflection of the dichotomy between the past and the future.
OS X will continue to gain in performance the less and less legacy crap is retained in the OS. And that legacy is the transition layer, Carbon.
Originally posted by e1618978
Somebody who leads a team of 350 people is not somebody who has much input on the code
Maybe not, but you can bet he checks up on it aloing the way. And just because he doesn't spend his day coding, doesn't mean he can't or that he doesn't know what's going on under him. I bet Steve hasn't done any coding on Mac OS in a long time, but I'm pretty sure he takes a look at its development every now and then.
Steve: "Avie, we're going to add feature X to the next OS X upgrade. Get it done."
Avie: "Sure Boss"
Avie to Coding Group assigned to new feature X: "Guys, this is what we're going to do, this is how it needs to look, this it what it needs to be able to do"
Programmers: "All right ... <type, type, type>"
Avie upon examining compiled code: "Wow, this is great, it works fine" OR "Wow, this is shitty and slow, guys. Let me see the source..."
That's why he's there. He offers his input when its needed. He should expect it to be working when it finishes compiling and the programmers give it to him, but it's not what Steve wants or he comes up with some better idea then he might ask them to try something different.
Originally posted by e1618978
the people at the bottom matter more than the people at the top.
Eh, as someone who's been on both ends of that rope as a peon and a supervisor (in construction, not programming, but they kinda work the same way...) they both matter equally. It's too much work for one person to do, so he has a team that (hopefully) is very good at its job and he trusts. He's been there before, knows how it should be done and expects is done a certain way. He comes back and checks up on the job, make ssure it's going according to schedule and plans then he comes back at the end, inspects the final product and *poof* you're done. He needs those under him to finish the job.
Other side of the coin - something happens in the build, unexpected compatibility problems, unexpected errors, differing of opinions - that's when supervisors are important. The interject their experiences, they make the call and they're ultimately responsible for the success or failure of the project.
Take football as an example: The quaterback can't throw the ball unless he has a line to block for him, but the line is pretty useless if they don't know what play the quaterback has called, and at the end of the game, people will usually blame the team's success or failure on the quaterback - not the line.
Originally posted by Robin Hood
Maybe his Steveness wasn't happy with the Finder.
*Post of the Month*
One of Apples great assets. He even gets along great with the man!!
That all being said, the past seven years have been a burner on folks. Steve himself was talking about the need to throttle development times back to something that could be considered half sane.
A well earned brake-and our loss!!!!
THANK YOU AVIE---Good Luck and Enjoy!!!
Apple is aware of how Avie and Steve J. are viewed, particularly by the market. One would think they would announce such a departure months in advance and name a successor at the same time.
Such a speedy departure certainly looks like there was a "difference of opinion".
Either way, thanks Avie - your tireless work in keeping the Mac platform ahead of the curve will definitely go down in history.
Originally posted by mdriftmeyer
That daring fireball article is a joke. The biggest delay in OS X has been accommodating the Carbon/Classic cruft of the past. His "flamed" support note was a reflection of the dichotomy between the past and the future.
OS X will continue to gain in performance the less and less legacy crap is retained in the OS. And that legacy is the transition layer, Carbon.
This is pure fantasy. Carbon is faster than Cocoa, and neither have anything to do with how slow the core of MacOS X is as a UNIX (which is pretty darn slow). The only legacy code in MacOS X is the Classic environment and that is optional anyway.
At this point MacOS X can only gain in performance through honest-to-goodness new research and development on locking mechanisms, thread/process spawning, I/O buffer sharing, and other low-level OS mechanics. These are features that already exist in most of the other major OSes. In other areas, they're ahead, such as VM paging, but those areas aren't common. They are going to need a new Avie.
Originally posted by Frank777
A March 31 resignation announced on March 28 just doesn't smell right.
Apple is aware of how Avie and Steve J. are viewed, particularly by the market. One would think they would announce such a departure months in advance and name a successor at the same time.
Such a speedy departure certainly looks like there was a "difference of opinion".
Could be just that it was publicly "discovered" this week and someone asked Apple and they confirmed.
Don't know.
I would have expected a more public announcement further back. But perhaps they chose not to for some other reason.
Could be the more sinister possibility too.
Originally posted by mdriftmeyer
Avie is Steve's right hand. He and him are very solid. The man's put in his time--nearly 20 years.
Bertrand will most certainly take his spot and yet the spot might be have a revised approach because Bertrand's areas of expertise are quite varied and he loves to keep his hands in the cookie jar to improve matters.
Avie was a phenomenal taskmaster. Read: he kept people on task and his will always prevailed thus garnering respect from Steve for always delivering products. This didn't always sit well with the less disciplined members in engineering but then again the taskmaster's job is to shape a direction and meet it.
Avie was a very conservative and matter-of-fact.
That daring fireball article is a joke. The biggest delay in OS X has been accommodating the Carbon/Classic cruft of the past. His "flamed" support note was a reflection of the dichotomy between the past and the future.
OS X will continue to gain in performance the less and less legacy crap is retained in the OS. And that legacy is the transition layer, Carbon.
100% agree
Put carbon in the trash and empty the trash!
(finder is carbon...)
tf
Originally posted by frogggy
Put carbon in the trash and empty the trash!
(finder is carbon...)
There's no reason to keep it carbon anymore.
Originally posted by tink
Maybe .........
Its not fun when its true
Originally posted by AgNuke1707
as someone who's been on both ends of that rope as a peon and a supervisor (in construction, not programming, but they kinda work the same way...)
They don't work the same way at all - if you want to use a construction analogy, it would be like being a construction manager where you can't leave the trailer to go look at the building. All you get are reports from your workers, inspectors and customers - and all of them know more about what your building is and should be than you do.
Even a first level manager (with 10 engineers, say, working for them) will probably never have time to look at a single line of code - and even if they spent all their time looking at it, they would only be able to see and understand 5% of it.
A team of good engineers with a bad manager will still get the job done - but a good manager will never be able to get the job done with a team of lousy engineers, which is why people at the bottom matter more to your success or failure.
I wouldn't worry about the loss of a VP - the time you have to worry is when you start losing lots of programmers (like microsoft is doing right now).
Originally posted by CosmoNut
There's no reason to keep it carbon anymore.
Please name a reason to make it Cocoa.
"It'll be faster" doesn't count because that's wrong.
"It'll be less buggy" doesn't count because that's wrong.
"It'll be more featureful" only counts if being able to use emacs text shortcuts and spell checking while renaming files is a major feature for you.
"It'll fix synchronization issues with FTP and other network media" is wrong.
Originally posted by Chucker
Please name a reason to make it Cocoa.
Because I said so.