« Caja's SL Flickr Pick: The Monstrous Beauty of Adra Braeden | Main | Caja's Daily Flickr Pick: Pepsi Sheen Creates Gorgeous, Whimsical Composites from Second Life Screenshots »

Tuesday, October 08, 2019


Feed You can follow this conversation by subscribing to the comment feed for this post.


Sadly they would have been better off just coding a new Metaverse

Adeon Writer

They could just rename Firestorm Viewer to "Second Life Viewer" and hire them as employees. Y'know, that works too. 🤔

Orca the Terrible

I was thining the same as Adeon: If the FS team is so much more capable than LL's own viewer team, why not offer Jessica and gang some well-paids jobs?
And the Singularity folks as well. For they are keeping the V1.2.3 look and feel alive much better than even FS's Phoenix mode can do.

return man 3

Firestorm will be set on the largest map of Battle Battlefield - Hal Halvoy. DICE and co-developer Criterion will offer solo and team play mode (16 teams with four players), whereby the player must complete a mission to unlock the use of vehicles, including tanks and aircraft. helicopters, or support aircraft calling feature, ... DICE said the two-player game mode will arrive with Firestorm sometime in April.

CronoCloud Creeggan

Adeon's got a great point there. I used to use LL's own viewers exclusively, usually running one of the Snowstorm test builds (though I kept a Firestorm install for testing), but then LL's own Linux viewer would refuse to run on a 64-bit Linux. Apparently, LL never switched their Linux build system to 64-bit. The only LL viewer I could run was the Obsolete system viewer, which had....issues. So even though I preferred the LL viewer UI, I switched to Firestorm because Firestorm DOES have a proper 64-bit Linux build that WORKS and has fixes to bugs in LL's Linux builds LL never got around to fixing.

Summer Haas

Think about all the ramifications of hiring that team. We have no idea what the financial situation is for the FS team. I'm guessing most of them would rather not work under the thumb of a major corporation. Some may not even be able to based on their location. Then of course there is liability on LL's part. They can't just allow the team total autonomy due to legal issues. Attempting to hire the team and make that viewer official would likely completely kill it off in less than a few months time.

One thing I would be curious to know though is exactly how many hours go into converting LLs code over to Firestorm every year on average. Is this something they devote a couple weekends to every time an update to the code comes out or is this a major operation that takes thousands of hours?

Luther Weymann

Two things I hope I never have to contend with in SL. 1. Linden Research having a proprietary SL viewer and no other viewers but theirs will work. 2. The Firestorm team becoming employees of Linden Research and the Firestorm code being taken over by Linden Research. Neither one of those has a good outcome for residents.

Mary Goonlife

Why no love for the Darkstorm Viewer?


While I'm sure you no doubt think you're being funny Mary Goonlife, your Darkstorm copybot viewer, as well as being not allowed to connect to the secondlife grid, which of course makes no difference to you is completely outdated and doesn't support things like animesh, bento, the new inventory system, bakes on mesh and probably more.
Probably why most of you copybottors use a different viewer based on Singularity now which still doesn't support bakes on mesh.
That's why there's no love for Darkstorm or you.

Tonya Souther

Disclaimer: I'm speaking only for myself, not the Firestorm team.

Personally, I'd love to be hired by LL. I've even applied a couple of times. But I'm not the tiniest bit interested in living in either California or Massachusetts, and while they are now open once more to hiring remote employees (they weren't for several years), they do not as yet hire in Minnesota where I live. I think it would be a great place to work, even if I would have to give up my connection with the Firestorm team.

And that points to the main problem with hiring the Firestorm team: we're spread out not just across the US, but internationally. Most of the developers live in various countries in Europe; I may be the only current developer in the US, as a matter of fact. That goes for the remainder of the team, as well. Don't forget that a large part of what makes Firestorm as amazing as it is is the participation of folks not just in developing, but in supporting and QAing and the gateway team that helps people learn about SL and gives them a place to start getting involved. I can't see LL hiring the entire team even if it could.

I don't think LL would ever pick up the entire Firestorm codebase. In the end, Firestorm addresses a different need from the LL viewer, which is aimed at the casual or new user, learning to navigate in SL. Firestorm is explicitly aimed at the power user. There are features that LL will never adopt, the one springing most quickly to mind being RLV. (Their Experience platform can do some but not all of what RLV does.)

I've long thought that LL's position, where their platform depends heavily on the efforts of a group of third-party volunteers, is one that I would not want my own platform to be in. That said, we do try hard to keep up with new features as LL adds them, Bakes on Mesh being the most recent, and when EEP lands, we're going to try hard to follow that quickly as well.

We'll see how it works out. It does seem to work well enough, though.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Your Information

(Name is required. Email address will not be displayed with the comment.)

Wagner James Au
Wagner James "Hamlet" Au
Dutchie 0223 Masssage table Slideshow
my site ... ... ...

PC/Mac readers recommend for SL:

Classic New World Notes stories:

Linden Limit Libertarianism: Metaverse community management illustrates the problems with laissez faire governance (2008)

The Husband That Eshi Made: Metaverse artist, grieving for her dead husband, recreates him as an avatar (2008)

Labor Union Protesters Converge On IBM's Metaverse Campus: Leaders Claim Success, 1850 Total Attendees (Including Giant Banana & Talking Triangle) (2007)

All About My Avatar: The story behind amazing strange avatars (2007)

Fighting the Front: When fascists open an HQ in Second Life, chaos and exploding pigs ensue (2007)

Copying a Controversy: Copyright concerns come to the Metaverse via... the CopyBot! (2006)

The Penguin & the Zookeeper: Just another unlikely friendship formed in The Metaverse (2006)

"—And He Rezzed a Crooked House—": Mathematician makes a tesseract in the Metaverse — watch the videos! (2006)

Guarding Darfur: Virtual super heroes rally to protect a real world activist site (2006)

The Skin You're In: How virtual world avatar options expose real world racism (2006)

Making Love: When virtual sex gets real (2005)

Watching the Detectives: How to honeytrap a cheater in the Metaverse (2005)

The Freeform Identity of Eboni Khan: First-hand account of the Black user experience in virtual worlds (2005)

Man on Man and Woman on Woman: Just another gender-bending avatar love story, with a twist (2005)

The Nine Souls of Wilde Cunningham: A collective of severely disabled people share the same avatar (2004)

Falling for Eddie: Two shy artists divided by an ocean literally create a new life for each other (2004)

War of the Jessie Wall: Battle over virtual borders -- and real war in Iraq (2003)

Home for the Homeless: Creating a virtual mansion despite the most challenging circumstances (2003)

Newstex_Author_Badge-Color 240px