The bigger impact being made by the browser wars is we finally see more than one damn browser on the list, forcing many websites to adopt to user choice rather than the IE "my way or the highway" web hole we dealt with for many years.
Unfortunately, this has turned into the IE & Firefox "my way or the highway".
The Lightning Talks at FOSDEM should be a good start. It's only within a month, too! You get 15 minutes to talk about your project in front of a crowd.
That only Win7 has H.264 support of all Windows versions is irrelevant, because by the time VIDEO element is actually in widespread non-beta use, Win7 will take the majority.
Given that web browsers are already implementing the video element, and sites are starting to use it, I don't think this would take that long. Furthermore, you don't know if Windows 7 will have the majority by then. Windows Vista, anyone?
Yeah, Vista had a lot of bad publicity. But you can't really make predictions in this field, especially now. There's a huge installed base of Windows XP computers currently, and for most people Windows XP is good enough. Combine that with the recession possibly affecting the purchase of new computers, the rising availability of GNU/Linux in stores, and I don't think it's too far-fetched to say that Windows 7 will not necessarily take the absolute majority.
In fact, all these points equally apply to e.g. GStreamer on Linux, so I take it to mean that Firefox won't use GStreamer there either.
Actually, they're working on that. Search Bugzilla.
"Damn, some shit escaped the toilet and is now floating around."
"I just drank some floating champagne."
How interesting. Have you forgotten that tweets are composed of very short text? Hard to fit anything remotely interesting in there. If there's something interesting to talk about, you do it on a weblog.
Actually, I don't use Firefox. I use SeaMonkey. No biscuit!:P
I think we should stop giving them such a hard time over it sometimes - if they didn't try anything we wouldn't get the good stuff they come up with, even though we have to pay the price of having to accept the not-so-good.
This constant drive to (often needlessly) reinvent the wheel, and forcing it on the users without the option to get the old back is one of the big reasons why I'll never use Firefox, and stay with SeaMonkey.
The only reason I'm following this at all is because Firefox controls Gecko, which the other Mozilla applications are also built on. Removing themes from the back-end will adversely impact all the others.
Personas are not light-weight themes. In fact, they're not themes at all. They're more like little gadgets that you hook up to your web browser to customise one part of its UI. It doesn't even compare to a theme.
But what's worse is that Mozilla is looking to depreciate themes in favour of Personas. From the Add-ons Manager, click "Get Themes". You won't see a page listing themes, but a page listing Personas. There isn't even a link there to the actual themes listing.
No need to find or create a fork. SeaMonkey is the project anyone leaving Firefox behind needs to look at, with most of the same bells and whistles, but without the dumbing down.
Extensions were broken from day one. You only need to look at the fact that they are bound to specific versions for proof of that.
On day one, extensions were not bound to any version, and installed through an install script provided by the extension package itself.
Extension compatibility checking along with the entire extension infrastructure has existed only since Firefox version 0.8. The Mozilla suite, now named SeaMonkey, kept using the old method until SeaMonkey 2.0 finally introduced the extension infrastructure that's part of the newer, Firefox-dominated backend.
Extensions see too much of the internals of the browser without any insulating abstraction.
Much of these internals are all provided through interfaces, with a significant number of them being frozen since Mozilla suite 1.0.
I thought the same thing, until I looked it up. It's as the grandparent says, actually. But then you have dictionaries define words differently, so it it's on a case-by-case basis in practice.
I think the secret to any object oriented language is to avoid complex memory references as much as possible, and just stick with dumb arrays and procedural programming as much as possible.
In other words, the secret to using an OO language is not to use its OO features? Are you for real?
C# would arguably be the logical replacement for C++ in a new programmer, these days.
It definitely is not, especially after C. C# is like C++, but with the neat parts ripped out and the control of resources and program flow taken away from you. It's a managed language, after all.
Slashdot Mirror
Unfortunately, this has turned into the IE & Firefox "my way or the highway".
--a SeaMonkey user
The Lightning Talks at FOSDEM should be a good start. It's only within a month, too! You get 15 minutes to talk about your project in front of a crowd.
Given that web browsers are already implementing the video element, and sites are starting to use it, I don't think this would take that long. Furthermore, you don't know if Windows 7 will have the majority by then. Windows Vista, anyone?
Yeah, Vista had a lot of bad publicity. But you can't really make predictions in this field, especially now. There's a huge installed base of Windows XP computers currently, and for most people Windows XP is good enough. Combine that with the recession possibly affecting the purchase of new computers, the rising availability of GNU/Linux in stores, and I don't think it's too far-fetched to say that Windows 7 will not necessarily take the absolute majority.
Actually, they're working on that. Search Bugzilla.
Congratulations, you're /. user #1001 to suggest this. Read why Gecko won't use DirectShow in the foreseeable future.
Mod parent up. People need to get this.
roc has explained why using DirectShow in Mozilla's Gecko won't happen in the foreseeable future.
Yeah, like:
How interesting. Have you forgotten that tweets are composed of very short text? Hard to fit anything remotely interesting in there. If there's something interesting to talk about, you do it on a weblog.
...What the hell are you going on about?
So they finally get Internet access, and one of the first things they use it for is a tweet on Twitter? Talk about useless.
Actually, I don't use Firefox. I use SeaMonkey. No biscuit! :P
This constant drive to (often needlessly) reinvent the wheel, and forcing it on the users without the option to get the old back is one of the big reasons why I'll never use Firefox, and stay with SeaMonkey.
The only reason I'm following this at all is because Firefox controls Gecko, which the other Mozilla applications are also built on. Removing themes from the back-end will adversely impact all the others.
Personas are not light-weight themes. In fact, they're not themes at all. They're more like little gadgets that you hook up to your web browser to customise one part of its UI. It doesn't even compare to a theme.
But what's worse is that Mozilla is looking to depreciate themes in favour of Personas. From the Add-ons Manager, click "Get Themes". You won't see a page listing themes, but a page listing Personas. There isn't even a link there to the actual themes listing.
Could you be referring to Best Color Scheme For Coding, Easiest On the Eyes? ?
What a joke. There's plenty of evidence that women prefer scumbags, not great men.
No need to find or create a fork. SeaMonkey is the project anyone leaving Firefox behind needs to look at, with most of the same bells and whistles, but without the dumbing down.
On day one, extensions were not bound to any version, and installed through an install script provided by the extension package itself.
Extension compatibility checking along with the entire extension infrastructure has existed only since Firefox version 0.8. The Mozilla suite, now named SeaMonkey, kept using the old method until SeaMonkey 2.0 finally introduced the extension infrastructure that's part of the newer, Firefox-dominated backend.
Much of these internals are all provided through interfaces, with a significant number of them being frozen since Mozilla suite 1.0.
Your claims do not hold up.
This has more to do with sucky IDEs that bog down the computer than developing on 'slow' hardware.
I thought the same thing, until I looked it up. It's as the grandparent says, actually. But then you have dictionaries define words differently, so it it's on a case-by-case basis in practice.
What's VESA doing in that list? That's a display standard, not a motherboard slot.
Not all "Win9x'ers" feel forced to migrate. :)
Comparing this issue to IPv6 is not fair, because we've known about its existence for longer, and there is more support for it out there.
Not to mention that there is no real need to switch to 4096-byte sectors. Sure, it's nice, but not necessary to keep going.
Then again, there are people who doubt the need for IPv6 as well, saying it's a solution in search of a problem.
What a sick joke. If there's one thing that will always stop America from reaching 'perfection', it's blind nationalism.
In other words, the secret to using an OO language is not to use its OO features? Are you for real?
It definitely is not, especially after C. C# is like C++, but with the neat parts ripped out and the control of resources and program flow taken away from you. It's a managed language, after all.
C++ is the logical step after C.
Just because girls waste more time on MMOs on average than boys doesn't mean they're more 'hardcore' gamers.
Err, the CSS 2.1 spec is not a proper recommendation yet. It's a candidate, though.
CSS 3 is tested by the Acid3 test [reference 1], [reference 2].
The point is that it's a deprecated practice. You should make your HTML documents semantically rich instead.