Re:"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
by andruby on Thursday August 13, 2020 @12:26PM
(#24145115)
The tool was firebug. It was a big difference when browsers didn’t offer built in tools.
Re:"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
by vosper on Thursday August 13, 2020 @02:46PM
(#24146767)
When Firebug came out it was such a big deal that it was the sole reason our IE-only product (which was not a simple application, it was fully-fledged fleet management, tracking, mapping, and reporting platform, entirely web-based) got cross-browser compatibility (we made it work with Firefox).
Being able to use Firebug was such a huge boon to development back in the day, though it probably looks primitive today.
Re:"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
by irrational on Thursday August 13, 2020 @01:12PM
(#24145654)
Firebug is what got me to use Firefox in the beginning. I continued to use Firefox out of habit after firebug went away, though the replacement was inferior (it still is). Now... I might have to switch to Chrome, but I really don’t want to due to privacy issues. I suppose I could use it just for development.
Re:"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
by hinkley on Thursday August 13, 2020 @02:48PM
(#24146794)
I think Firebug got most of us to use Firefox, and then we got other people to use Firefox, directly or indirectly.
I worked on two teams back to back. Everyone was using Firebug. Management was telling us NOT to support Firefox, but tough shit, you want this work done yesterday and the only way that's going to happen is by engineering on Firefox/Firebug and then going back to black magic for the 10% that didn't work on IE (and soon, Safari).
Re:"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
by dustingetz on Thursday August 13, 2020 @01:59PM
(#24146168)
I think SV's theory is that if you make something that potentially a billion people will use, that's worth doing even if you don't know the business model yet because when the fog of war clears you might be FAAMG
He leaves a publicly funded team building a web browser, starts a commercial entity, and for whatever reason they don't feel they can charge for their browser funded by private equity. You could in fact buy it in a box at the local electronics store, but with the pricing I suspect most of that money went to distribution, not NCC. So they try to find other ways to make money, like their web server and overpriced consulting (for their notoriously awful web server).
The entire dotcom era then emulated this pattern. There were certainly other logistical reasons for it (like the state of credit card billing at the time), but I can't help but feel like this was the rock that started the avalanche of adware and commercial cyberstalking.
And so here we are 25 years later, and the last remnant of Netscape is trying to build the free browser and not much to fund it. I'm kinda surprised it lasted this long.
To be fair to them though, and particularly on the topic of this story, if they were going to build a free browser, it always should have been on the community to contribute to the dev tools. It's the part of the browser that we have a vested interest in.
And in fact, it used to be that way. Firefox had no dev tools at the beginning. They copied a very popular add-on, which I now recall made absolutely no sense to me at the time. I felt like their attempt was less effective in several ways, and why are they shouldering out this tool that made them in the first place (as GP asserts, nobody develops first-class support on a browser they can't debug in, or at least not when there is an alternative.)