As released on several sources, I'll link the one I have here for reference Linden Labs plans to release 30% of their workforce.

I'll quote the bit from the article where its explained to us by Mark Kingman, or M Linden themselves.

"We've emerged from a two-year investment period during which, among other things, we've spent a considerable amount of time improving reliability and the overall user experience. Today's announcement about our reorganization will help us make Second Life® even simpler, more enjoyable, relevant and engaging for consumers starting with their first experience. It will also enable us to invest in bringing 3D to the web and will strengthen our profitability," - Mark Kingman, CEO, Linden Research Inc.

So we already have a grid that...only sort of works, partially, in any real fashion, and we are, by this statement led to believe that a 30% reduction in their workforce will somehow make this more enjoyable and relevant and engaging for us "consumers".

To echo the sentiments of our American Indian brothers and sisters, "Man with big hat speaks with forked tongue." at least at the very end he mentioned "profitability" which means he wasn't going to let this entire bullshit statement filled with meaningless corporate mnemonics pass without at least saying one thing that was true.

Amazing to me, how do people do this kind of thing and take themselves seriously? Is it that hard to say, we're looking to ensure we can keep our profits in the black while reinvesting our efforts in some new browser based viewer technology we've got going in the background. And why can't we have Phillip back....who actually said what he meant pretty much 90% of the time.

No offense M, but we know bullshit spin language when we see it, we're not idiots out here you know. The grid is yes, more reliable, you hardly ever have a sim crash these days, sims just grind to a halt and become unusable and have to be voluntarily restarted by the estate owner...I guess thats, more reliable, from a certain point of view. And the overall user experience...hrrm....have you really improved that? I think I have 25 related groups that manage the CoLA/CCS Network and almost all the related group chats work with about a 90% reliability to not send your messages when you type them, or to send your messages long after you've typed them, or to finally send the message you typed yesterday 18 hours later when its no longer relevant. The overall user experience has been improved? Where? I still can't hard set Windlight profiles at the estate level, you've got a half implemented version of Havok 4 that stabilized the grid but retarded the capacity of sims to use their resources AND have more than 30 people in them, then you pink slipped the team that was working on that and declared it "WORKING AS INTENDED", you implemented mono with a huge loading bug issue thats still not fixed and you pink slipped the team that was managing that and will likely do the same thing "WORKING AS INTENDED! THESE ARE NOT THE DROIDS YOU'RE LOOKING FOR."

Seriously, many of us have spent years of our lives now on this grid, watching it go from 10,000 user concurrency to nearly 100,000 user concurrency, and we've contributed to that rise just like Linden Labs has, in our own ways. And you really, seriously, can try to throw out corporate double talk like this that might as well read like a Mission Statement, then right at the end throw in "profitability" to ensure someone can't flat out call you a bullshit artist.

I want to know on what planet a development situation or any corporation can provide a "better" experience to their customers by firing 30% of its work force. Especially when some of those releases include people working on some pretty major problems that still aren't fixed as of the latest server release.

Amazing. Seriously.

Just a heads up to the community the 1.0.2 Rel 3 test unit we have out in the testing group is returning very good results. All known bugs are addressed and we're pretty much "ready" to go live.

But there are a couple things Melanie and I have been preparing for at the back end, in regards to pushing http-in data to the meter, which Melanie and I are debating taking the time to get finished NOW rather than push out 1.0.2 then push a 1.0.3 revision in a month or so.

The http-in functionality we're looking at here will manage multiple things but the most visible things to the user and admin user will be the fact that the meter will no longer need to be detached/reattached on level up, and the admin user will start noticing that instead of having to pull out a calculator and manually add XP awards to players, that the player data sheet on the back end will now have some preset buttons you can simply push to auto award a certain amount of XP 100/350/500/1000 and 100xLevel which will automatically adjust the XP table by the set amount, push the new XP data to the meter in real time with no need for detaching and reattaching and auto-notate the award on the player record.

These are a couple of the top end visible functions that people will notice about it. Main deal is, the back end work for this is mostly done, its simply finishing it off and we're highly considering doing so prior to releasing 1.0.2 so we're not raining updates and we can then consider CCS "stable" and back off and work on the respec on demand/XP transfer system and API 3.0

So I know a lot of people are hoping for the 1.0.2 release and I could release it now and we'd be alright, but we'd simply be issuing a new meter very soon after it without addressing the http-in functions we're looking to add to the system.

So, patience, if you would, we're wanting to ensure we finalize the 1.0.2 release as solidly as possible before releasing it. And I think going with what we got, while totally viable, would simply require us to push another update fairly soon after we release 1.0.2 and I'd rather be able to focus on the web features we've promised and API 3.0, than get stuck in yet another meter update hamster wheel.

Just a heads up, doesn't mean its going to take another month we can probably have this stuff done in a week or so and get the testing in on it and get the meter out before mid-June barring any unforeseen issues. Just need everyone to be patient a little bit longer. The 1.0.2 meter build is solid and is more than viable as a release candidate, but, I feel like we'd be releasing it with a couple of things we've been working on since 1.0, left out of it, that really shouldn't be left out.

This http-in functionality is also needed to be in place for the web features we've promised so its just better to have the 1.0.2 platform ready and capable, rather than releasing it without the needed functionality to simply drop in the web features and have the 1.0.2 platform be able to run it by default.