I love firefox.. My big problem as a late though seems to be that sites stop loading intermittently, need to be refreshed or I need to wait (and I don't have this problem on Chrome).
Also, I got kind of annoyed when one of their leaders came begging for donations by email, but are getting paid FAR beyond normal wage.
Actually, back in early days, Linux was probably worse than Windows 98. A few things changed the landscape. Compositing on Xorg (to make the desktop modern finally), Pulseaudio (before then, Audio always had issues), DBUS and the rest of project Utopia. Steam also made a huge difference.
I think Linux will be the better option after: SNAP/Wayland goes mainstream and JACK becomes easier (Low latency Audio on Linux is still a nightmare compared to Windows and OSX).
But there are still a few rough edges. That being said, I use it for everything at home now, except for my Suunto GPS tracker, and Serato.
Never mind that Alsa offered dmix even back then, but you had to know to enable it yourself.
Frankly the major reason for PA to exist at all is to handle transitory audio devices. I think Poettering started working on it because he bought himself a pair of USB headphones (basically a USB soundcard with some headphones hardwired to the analog pins).
Dmix could just as well have been extended to do audio routing. Or just ram sound down all channels unless the user decides to mute some of them.
I heard this stuff ("...it was terrible until PulseAudio delivered us from evil") so many times that I actually began to question my memory and dug down in old mailing list threads and my old screenshot folder. It especially pisses me off that so much of it is PR -- which I appreciate, but which I think has little place in the world of free software, at least the way I see it.
For all of you poor onlookers who have no idea why people don't like PulseAudio, sit down and let grumpy ol' notalaser tell you the story of how PulseAudio gets all this hate -- much of which is, in fact, entirely undeserved today.
Back in 1999-2000 or so, things were really bad when it came to audio on Linux. The biggest problem most users faced right after being able to finally make something come out of their speakers was mixing audio streams from more than one source. This was especially relevant because, at the time, audio effects were really in vogue on the desktop.
The problem was that OSS was flaky and had basically no support for software mixing -- which meant that, save for the few sound cards that supported this feature in hardware, you couldn't play more than one stream at once. ALSA, on the other hand, was in a very early state, had all sorts of trouble, not too many drivers and updates were going slow considering that this was back when virtually everyone installed Linux from CDs and the biggest hurdle to a rolling release model was dial-up.
The way most desktops solved this problem was with a sound server (yep, basically PulseAudio). KDE used something called aRts; Gnome, I think, used Enlightenment's ESD. Both of these would do the mixing in software and pour everything into /dev/dsp. The bad news? They were really slow, high-latency (and I mean high latency, sometimes I'd get the sound alert a dialog about ten seconds after closing the dialog) and were a little funky. If aRts' queue stalled, for instance, the effect was a little comic -- after unstalling it would end up playing all the sounds that had accumulated in the queue. It was very comic.
By 2004-2005 or so, however, the whole concept ended up being mostly irrelevant, as ALSA began to really support hardware (and software mixing). Gnome eventually dropped ESD altogether. KDE kept up with aRts (but IIRC a lot of distributions started shipping KDE with aRts disabled) up to 2004, then embedded some of its ideas into Phonon. Those of us using something else finally rejoiced and never ran a sound server again.
2004 is also the year when PulseAudio was first released. By the time it got included by default in Fedora, in 2006, playing multiple streams using nothing but ALSA was very much a solved problem. I think it was so solved that it worked on Gentoo out of the box, without having to configure anything, on the more common sound card models. Not that Linux sound was perfect -- drivers were still flaky-ish sometimes, but obviously that was not something that a sound server, be it PA or something else, could solve.
So fast forward to 2007, when PulseAudio is actually unleashed upon the computers of everyone else except Lennart and his friends as it's adopted and enabled by default in Fedora 8. To put it mildly, nothing worked anymore. Very literally -- when we installed it at the crufty place where I held a part-time job there, it broke sound on every single one of the 10-15 different configurations we had, from laptops to desktops. On really old desktops, the breakage was subtle (high latency, occasional crashes). On newer laptops it was entirely terrible, they wouldn't even hiss. PA had no useful documentation, basically no means to do any useful debugging, and its upstream team quickly made a lot of friends due to its leaders' difficult (if superficially gentle) personality.
This was extremely unfortunate because alsa -- while not sucking as much as Pulse's PR machine claimed -- was still pretty bad, and many of its design decisions were firmly rooted in the landscape of the late 1990s Linux. dmix wasn't too power efficient and it had a bunch of other problems re. dynamically-added devices. Linux' sound system needed the improvements that PulseAudio brought; unfortunately, PulseAudio was both very slow in delivering them (in a manner that would not crash once a day, that is) and very eager in being adopted, which resulted in it being widely deployed while it was pretty much in early beta.
This is how everyone came to hate PulseAudio (and Lennart Poettering). It created quite a rift in the community, too, one that went on to be made even deeper. It also hurt PA's development pace in the long run.
tl;dr PulseAudio was too bold, too soon, even though it was, in many ways, too late.
I think the real PA shit storm hit when it was adopted by Ubuntu because Canonical wanted to match the pr program volume control that was introduced in Windows 7 (only use i have found for it so far was to mute a pesky game launcher/updater).
This complete with a "you are holding it wrong" like statement from Poettering as new servings of bile rolled in...
I don't think being able to play multiple sounds simultanously from the desktop in the Win9x era was that common anyway although some sound cards probably supported it. I do find it useful for playing my own music while playing a game or watching some talk-only video and so on. Never had any issues with OSS or ALSA so I can't say audio "always having issues" before PulseAudio matches my experience at all... Maybe that's referring to ESD.
It is just not allowed for an employer to offer a job that will seriously damage employees' health. It doesn't matter if employees have the choice to switch jobs or even if they let them sign some waiver to acknowledge they accept the health damage. Laws have been put into place to prevent this, basically to protect naive employees against themselves.
They can always claim that they were told it's not that bad and that they did get company counseling but it was not sufficient and the actual dangers were undersold. This paragraph makes me think there's actually a decent case:
"""Program authorities advised the workers to take walks and smoke breaks and suggested Blauert play video games to manage his symptoms, the complaint said. Later, however, his supervisors allegedly gave him a poor evaluation for “lack of production and too much time playing video games”."""
Very good use case for machine learning. I don't know what tech is used but prescreening with ML should already be quite helpful if you don't want to rely on it fully.
Great idea, but I'd say practical applications are limited..
Industrial sensors shouldn't rely on Wifi. Hospitals shouldn't rely on WiFi. In a car just run ethernet alongside power.
Since you can't guarentee wireless maximum latency on WiFi, I still wouldn't use it for multi-channel audio (only multi-room, which NTP is good enough for anyway probably). Especially a problem if you want to sync against Video.
So its a nice idea, but it will probably affect very few people..
That still introduces other issues though. You will probably need larger than 200ms to be safe, which will make the setup annoying for applications such as gaming.
Or it would need great error correction. Either way, wifi equipment needs to accept interference (nothing you can do)
Well, considering Sonos has multi channel and multi room capabilities wirelessly, it can work. That said I have no idea how this spec works vs whatever proprietary magic they've got going on.
The funny thing about 4K is that I do home AV installs, and its almost impossible not to have compatibility issues still.
To this day, I don't think we've had a single installation with 4K projector / Receiver / player working together of different brands without some kind of serious issue.
ARC is another disaster that we STILL are having trouble with, and thats been out for years. I really hope that more has been done in the way of standardisation to help iron out these issues
I had to use an optical cable between my TV and AVR to get audio. The only thin ARC did was allow me to control the AVR volume control using thr TV's remote. Not very useful when no audio is coming back.
Yep, lets all make assumptions on beta-quality code.
Firstly, Microsoft aren't the only ones who don't play well with others. Openoffice, Abiword, iWork and every other office suite on the planet uses its own formats.
Secondly, is OpenOffice OOXML 100% Strict compliant yet?
Finally, it's easy for people to stand by on the sidelines and whinge that a year old bug isn't fixed, or a new feature isn't added. Developers often calculate an estimated time required for development in advance, and for all we know, perfect compliance with the standard now may have been pushed back because implementation would have forced other features to be dropped. From a business/development perspective, this often makes sense.
Next release if they aren't compliant with strict, then yes, its time to freakout. But from a business decision, it doesn't make sense to rewrite code many times before it becomes a standard. And when applications sometimes do so, the end result is a mess, because the browsers then often need to support their broken standard, and the correct standard, or risk breaking compatibility with some websites.
Microsoft had no way of knowing exactly when the standard would be approved, or how many changes would be made. I don't think this is overwhelming proof that they are going out of their way to destroy standardisation.
UPDATE: Looks like Openoffice doesn't support saving to OOXML anyway.
So seems the only reason OO implemented it, is to encourage people to save to their own standard. So, from one perspective, OpenOffice are trying to destroy standardisation too (they are trying to force people to use their own standard).
Really, the whole thing is a power struggle to become the dominant format anyway. Since their main competitors are doing dodgy stuff to help force people to move to their own standards, I'd say its hardly surprising Microsoft aren't willing to sacrifice functionality to help competitors.
If OpenOffice were serious about standardisation, they would add support for OOXML saving, but they haven't yet!
No.. They didn't.. For starters, Steve Jobs didn't have anything to do with the HTML5 tags, it was introduced by consumer demand. However, it seems he is trying to take credit for its introduction. Every non-Apple geek wanted the change anyway (but sure, despite the fact I don't use Apple equipment anymore, my feedback to Google "was inspired by Apple" obviously).
Everyone knows that there are still no good tools to replace Flash's development tools, and sites which used flash before, are unlikely to switch only because of the iPhone or iPad (the iPad isn't out yet and the iPhone only has a tiny marketshare). Furthermore, FLASH DOES MORE THAN VIDEO! I am sick of every Pro-Apple article pretending as though video is its only purpose.
"iPhone only has a tiny marketshare" - iPhone dominates mobile web content at north of 40%. If you have mobile content, you have no choice but to support the iPhone. When the iPad is released, content providers have no choice but to support the iPad.
I'm sure Flash does more than video, but I've been running (on Windows XP/Firefox) FlashBlock for the last four months, and I've never seen anything but Video and SlideShows when I've clicked on the "F". I'm guessing there is an entire game ecology that I've never tripped across, but, well, the iPhone OS isn't particularly lacking in that area... :-)
No idea why Oracle hasn't been split apart