Monday, February 25, 2013

Problems with Server Side Baking

Here are some links regarding the in-development server-side-baking feature being prepared for gridwide use by Linden Lab:

http://modemworld.wordpress.com/2013/02/23/sl-projects-week-8-3-viewer-materials-and-ssb-load-test/

http://modemworld.wordpress.com/2013/02/23/playing-with-ssb-and-viewers-quick-test/

http://modemworld.wordpress.com/2013/02/25/viewer-round-up-summary-week-8/

As expected, there are some issues with the feature, but many Third Party Viewer (TPV) developers seem to be getting their viewers up to speed, most notably Singularity and Cool VL Viewer.

Not surprisingly, the Firestorm elitists and liars are having a tougher time getting their resource-hogging, crashtastic, low-frame-rate to work, and are claiming that it will likely be some time before a stable version that can handle Serve Side Baking will be released -- so naturally, the Firestorm clowns will release a version of the viewer that has SSB before they can even get it working properly with Linden Lab's code.  "Genius" at its finest.

Also not surprising is that some commenters aren't buying the lies Jessica Lyin' and her merry gang of suckups are telling.  "Joseph" writes:
It really does not surprise me at all that Firestorm is in such a terrible state right now. And at the meeting it sure had a tone and implied like so many problems are caused by LL’s code even though Jessica did make sure to state that many problems come from Firestorm itself. The LL 3.4.5 is a GREAT viewer and certainly isn’t some mess of buggy code like it sounds like the Firestorm devs make it out to be. If any Firestorm user or any of the Firestorm devs truely used the LL 3.4.5 viewer for a decent amount of time they would see that not only does it perform a hell of a lot better than Firestorm it has a hell of a lot less bugs. Firestorm is a crappy clunky mess in comparison. All things considered the LL 3.4.5 viewer is an awesome viewer. The problems Firestorm is having right now is because instead of just adding features and UI improvements over the past couple of years to the LL viewer, they have delved and messed with so much of the internals of the program itself thinking they can do everything better than the lab. If one looks at the commits to the code since the beginning of Firestorm over two years ago, the developers have mucked and messed with so much more of the code than just adding features and UI changes. Instead of just letting LL deal with the internals of the program they have gone in and tinkered and messed with so much of the guts of the program itself and this is why now after merging it is such a terrible mess. If the Firestorm devs had a minimalistic approach to what they changed in the code other than UI improvements and adding features, the current internal version wouldnt be the unstable horrendous god awful mess it is now. Anyone can go to their mercurial repository and see exactly what they do to their source code, and see hundreds if not thousands of commits since the beginning of the project of them making changes to the core engine of the program so to speak and that is why they are in the mess they are in today. Often times Phoenix was described as a monstrous unmaintainable collection of hacks held together by bail wire, spit, duct tape etc…and the irony is that now a days that is exactly what Firestorm has become.
As evidenced from this and other comments, not everyone believes what Ms. Lyin' has to say, and for good reason -- people know from actually trying to use Firestorm that it's an unworkable mess of code, the very same critiques used against Phoenix, which actually works on more people's computers and which has now been abandoned by the developers.

As for the Server Side Baking issues, it's clear that the official roll-out may not come quite as soon as previously stated by Linden Lab or others.  It'll be implemented across the grid sooner or later, but it seems clear that the TPVs most likely to have stable viewers that have SSB won't include Firestorm.

No comments:

Post a Comment