Stop trying to oversimply things you don't understand.
Well gee I dunno brain, I've only been a professional sysadmin for a decade and been using XFS as my weapon of choice for a good three or four years, but you and your laptop should feel free to carry on.
For all its shortcomings, one wonders if the mass-market, affordable Spectrum wouldn't have been a more suitable candidate for the BBC's aim of computer literacy
The Beeb was well suited to education due to the extreme flexibility it offered through all of it's expansion and I/O capabilities. Hooking up printers, floppy drives, robotic arms or turtles was easy with the Beeb. If you wanted to get a Spectrum to do the sorts of things the Beeb could do out of the box, you'd have to spend hundreds of pounds on expansion cartridges, so the price would probably end up comparable to the Beeb at the end of it anyway.
Then there was the +2 which had a built in cassette player and the +3 with a built in microdrive.
There was also the +2A (& +2B), which was a +2 but with +3 ROMs, so it could run CP/M and the BASIC commands to access the RAM disk were different (The 128 & +2 used E.g. "SAVE!" to access the RAM disk, while on the +2A/B & +3 it was just drive M: and you could access it through the normal DOS I.e "SAVE M:foo")
unless a bunch of rock musicians who wanted smaller synthesizers and funkier sounds were geeks, or a bunch of psychedelic poster designing hippies were geeks, or a bunch of political minority publishers were geeks
Les Solomon, Steve Wozniak, Stewart Brand and most of the rest of the Homebrew Computer Club weren't geeks?
To be fair, the BBC are far more pragmatic about copying than most other broadcasters. For example, Top Gear is the most downloaded show on the internet, and they've referenced this fact a couple of times in the show. The only action I've ever known them to take over that is to shut down a few websites who hosted every single episode ever, which was frankly taking the piss just a little bit anyway.
Claims are meaningless. Lets see them actually sue. Not a single company making such a claim has ever sued On2, Xiph or Google. They can't have much faith in their own claims.
Google will not offer indemnification for a reason
Yes, because the MPEG-LA also do not offer indemnification. Double standards much?
Every...study has shown that the best available VP8 encoders require almost 2x the bitrate of the best H.264 high profile encoders.
What do you think happens when you point the camera on your phone at something and hit the record button? Those terrible videos people upload to YouTube don't encode themselves.
Sure, your scenario is bang on and I don't think anyone would seriously suggest that H.264 isn't a great solution for that work. However, this bit:
Eventually the media goes onto the web for a few thousand people to watch
That bit right there is where VP8 can just as easily replace H.264, and where Google are not surprisingly positioning it with WebM. As you're transcoding the original high quality source anyway, you lose nothing transcoding it to VP8 instead of back to H.264.
Google has made it VERY clear that they HAVE NOT and WILL NOT offer indemnity for their users.
That's fine. The MPEG-LA do not indemnify their licensees either.
That is one thing MSFT should be given credit for as they make it clear they WILL indemnify their customers.
I'm not sure what Microsoft licenses for Android have to do with the MPEG-LA.
the free codecs currently suck balls
Which, as I said in a previous post, is subjective and isn't supported by the reality of the situation. Under normal viewing conditions, WebM and H.264 are comparable.
So your strategy for not getting sued by a patent troll is to hide behind the big guys? Then use WebM and hide behind Google. Either way, lying about the patent situation with VP8 is dishonest, and you should probably stop doing that.
As far as "subjective" quality issues go, this article sums it up good:
Yes, we've all seen the highly unbiased article by the x264 developer. It's just as subjective as anyone else's article. It's mostly moaning about the specification, a claim on one hand that VP8 is "too close to H.264 for comfort" while at the same time a claim that VP8 "probably can't be improved that much", and yet more subjective and biased opinion on which the author prefers the most. Surprise, an x264 developer prefers H.264!
Until you define "better" or "best", it's subjective. Until you define what use cases you're applying your measurements too, it's subjective. H.264 is better is some things. VP8 is better in others. Mostly though, VP8 and H.264 are of comparable quality under normal viewing conditions.
And use inferior technology that is a patent minefield?
"Inferior" is subjective, and I'd love to see any proof you have that VP8/WebM is a "patent minefield".
At least with H.264 I can be certain that my business isn't going to be taken to court one day and I lose it all. With H.264 I don't need to worry about such
Where did you get such a silly idea from? An H.264 license simply provides you a license to the patented technologies in H.264 that are owned by the MPEG-LA members. There are no guarantees or indemnities against any non-MPEG-LA member from suing you and everyone else for using H.264.
The risk from submarine patents for H.264 is exactly the same as VP8.
1. If you don't already have it, implement some sort of centralised authentication mechanism. This can be NIS+, LDAP, Kerberos, whatever, but have it.
2. Disable root logins and start to make everyone use sudo. Sudo is auditable. Sudo permissions can be made fine-grained.
3. Implement configuration management. Even if that's only managing critical system components (I.e. the sudoers files, sshd_config, passwd & group files). Even if you "only" use Cfengine (but seriously take a look at Puppet and Chef before you make a decision).
Slashdot Mirror
Emphasis mine.
The God of the gaps is alive and well.
Hey, I wasn't the one being wrong and calling people dumb.
Where did you get the impression I wanted to help? You were just wrong. Get over it.
Well gee I dunno brain, I've only been a professional sysadmin for a decade and been using XFS as my weapon of choice for a good three or four years, but you and your laptop should feel free to carry on.
No you don't. Either force unmount the filesystem, or if you deem that too dangerous, boot into single user mode.
Damn, the UK supermarkets are a dream of choice compared to even high-end supermarkets in the US.
Must...resist...Python joke...
The Beeb was well suited to education due to the extreme flexibility it offered through all of it's expansion and I/O capabilities. Hooking up printers, floppy drives, robotic arms or turtles was easy with the Beeb. If you wanted to get a Spectrum to do the sorts of things the Beeb could do out of the box, you'd have to spend hundreds of pounds on expansion cartridges, so the price would probably end up comparable to the Beeb at the end of it anyway.
There was also the +2A (& +2B), which was a +2 but with +3 ROMs, so it could run CP/M and the BASIC commands to access the RAM disk were different (The 128 & +2 used E.g. "SAVE!" to access the RAM disk, while on the +2A/B & +3 it was just drive M: and you could access it through the normal DOS I.e "SAVE M:foo")
You're right, you should always use descriptive function names which describe exactly what the function does.
See, the world is always ready with a bigger idiot...
I think you've missed the point of "General purpose".
Google will force the hands of TV and movie companies in a similar manner. I'd bet on it.
Les Solomon, Steve Wozniak, Stewart Brand and most of the rest of the Homebrew Computer Club weren't geeks?
Developers can't write standards compliant code without knowing what the standards are.
Oh what am I saying? Developers won't write standards compliant code even if they do know what the standards are!
To be fair, the BBC are far more pragmatic about copying than most other broadcasters. For example, Top Gear is the most downloaded show on the internet, and they've referenced this fact a couple of times in the show. The only action I've ever known them to take over that is to shut down a few websites who hosted every single episode ever, which was frankly taking the piss just a little bit anyway.
Claims are meaningless. Lets see them actually sue. Not a single company making such a claim has ever sued On2, Xiph or Google. They can't have much faith in their own claims.
Yes, because the MPEG-LA also do not offer indemnification. Double standards much?
Got links?
What do you think happens when you point the camera on your phone at something and hit the record button? Those terrible videos people upload to YouTube don't encode themselves.
That bit right there is where VP8 can just as easily replace H.264, and where Google are not surprisingly positioning it with WebM. As you're transcoding the original high quality source anyway, you lose nothing transcoding it to VP8 instead of back to H.264.
That's fine. The MPEG-LA do not indemnify their licensees either.
I'm not sure what Microsoft licenses for Android have to do with the MPEG-LA.
Which, as I said in a previous post, is subjective and isn't supported by the reality of the situation. Under normal viewing conditions, WebM and H.264 are comparable.
The Wikipedia article you quote says
So there is a cost to "play" or "show" H.264 encoded content.
"Inferior" is subjective, and I'd love to see any proof you have that VP8/WebM is a "patent minefield".
Where did you get such a silly idea from? An H.264 license simply provides you a license to the patented technologies in H.264 that are owned by the MPEG-LA members. There are no guarantees or indemnities against any non-MPEG-LA member from suing you and everyone else for using H.264.
The risk from submarine patents for H.264 is exactly the same as VP8.
Here's a generalised three step plan:
1. If you don't already have it, implement some sort of centralised authentication mechanism. This can be NIS+, LDAP, Kerberos, whatever, but have it.
2. Disable root logins and start to make everyone use sudo. Sudo is auditable. Sudo permissions can be made fine-grained.
3. Implement configuration management. Even if that's only managing critical system components (I.e. the sudoers files, sshd_config, passwd & group files). Even if you "only" use Cfengine (but seriously take a look at Puppet and Chef before you make a decision).
Funnily enough I do use my own DNS. It just happens that the DNS servers in question are hosted by an ISP who happens to be my previous employer.
Kill it with fire:
sudo apt-get remove overlay-scrollbar liboverlay-scrollbar-0.1-0
I'm not talking about replacing an AD server with Samba. I'm talking about integrating non-Windows clients into an AD domain.