My first draft of a program will compile. Doesn't mean that I want to even think about trying to execute it.
It seems to me that I remember that Mozilla had a system that not only would make sure that a program would run, but would also exercise it to make sure that they got the results they were expecting out of the various program actions.
But what happened certainly isn't unexpected. Usually when it fails like this, at least it gets a little further down the road before it craps out. When I see that the next nightly is available (and that's not today), I'll download and install and be back to normal.
Running a pre-alpha build of a browser in a "production" environment
The nightly is alpha, not pre-slpha. The fact that you cannot parse that tells me plenty.
My "production" environment in this case is my home. And as I stated, I am
well prepared with alternate browsers. Now, why would I run something like an alpha? Mainly because I figure that I
will run into issues such as crashing and situations like this, because I
like the product and have no issue with dealing with such issues because I expect a better program at the end.
As far as me whining about the situation, it was more the synchronicity of seeing a good article about FF 18.0A1 on the same day that the Windows version was nerfed, not the fact that Firefox was screwed for that day.
I've been running the alpha version for over a year if not years. What have
you done for Firefox lately? And have you done it as long as I have?
Facebook
Twitter
Instagram