x.264 is open source, nothing stops you to maintain it for the next 100 years. BTW did google commit to maintain VP8 for some given amount of time? No? They could drop it tomorrow if they want? Oh well, then how does that make it "superior" from a maintenance and viability point of view to any other open source alternatives?
What is the percent of devices relative to the total nr of sold devices coming with firefox preinstalled? How do you install firefox on ipads and iphones? What are the chances that any of these codecs would get hardware acceleration on a significant nr of devices in the future?
They seem to use "MP4" and "H.264" in a pretty much interchangeable way in the original article. This does nothing but make things difficult to understand. Here's what they really need to standardize upon:
- a container format (such as mkv or mp4/m4v)
- a video codec (such as VP8 or H.264)
- an audio codec (such as Vorbis or AAC)
In order to make it "open/free", they need to chose all three components in this respect, such as an mkv container with VP8 video and Vorbis audio inside. Which will guarantee that the result won't play on any device right out of the box. OTOH if they chose something like m4v with H.264 video and AAC audio inside, it will play right out of the box on about anything from Windows PCs to tablets to PS3s to WD TV live boxes. The patent stuff doesn't affect the end user as these devices are already licensed to use the mentioned containers/codecs (and in a pretty efficient way such as having hardware accelerators). Now even if they figure out the video part, I'm curios what they're gonna use for audio codec/compression. There isn't much to chose from that isn't patented either.
Yes it does say so, quote: "A few minutes later, fire alarms in the garage went off, and firemen arrived to put out the blaze, which was described as "intense"."
I find it interesting that the owner of the car had a smoke alarm installed in his garage, especially since he also had a gasoline car parked there. That would lead to a pretty high number of nuisance alarms. In fact, even the fire depts themselves suggest that you should not install one:
The book's summary mentions a dataset from "163 US electric utilities". While South Carolina may be different, the book gets to the result that, on average, burying the lines would shorten both downtime and repair time.
May I also understand that the price/kW you're currently paying is also entirely of your choice? Or that, at a minimum, you have negotiated it with the power company?
Those figures were mentioned recently in the press, without quoting a source for them. Most likely they pulled them out of a hat. These gentlemen got to a different conclusion:
You can't really move a jeep through a gridlock no matter what model of jeep and tires you have. Check what happened in Atlanta the last round. It wasn't that cars couldn't get any traction. It was about several crash scenes that gridlocked the whole traffic.
It continuously amazes me that people would easily pay in excess of 50k in order to get the largest SUVs ever, yet they would fight teeth and nails against an one time 3k fee to get their power lines buried. The SUVs have been proven useless during the ice storms, while having electrical power was proven to be priceless.
It was Noah who put the dictionary together. His brother Daniel, the senator, pushed the "copyrightz" law so his bro could "make money". It was all about business. And that's how, ladies and gentlemen, you first got a copyright law in US.
First, you may notice that I was talking about guys "building robots in their basement". Bringing some to the interview does not clash with their (former/current) employer (intellectual/physical) property. If anyone has those robots to show, it means that the guy is really passionate about his work, which in turn means that he has explored his field to the last detail, will take pride in his work and will go the extra mile to turn out quality/outstanding products.
Second, if the prototype comes from his workplace, he might have it with the agreement of his (former) employer. By the time your guy is looking for a new job, that device is either a complete fail, or the final product (copyrighted, trademarked and patented) is already on the market. If anyone wants to duplicate it in some shady way, it would be more productive to study the final product instead of some proto/proof of concept of it.
Third, unless you're the kind that comes up with "but companies are persons my friend" statements, you would notice that a company cannot have an intellect, and thus no "intellectual" property. What companies have are contracts about it.
If you think about Software Engineering as being about writing smartphone apps or Weblogic "enterprise" application, I will agree with you. However what good EEs have is a good understanding of systems theory and methodology. They will generally look at an embedded system as a (finite) state machine and work their way down from there. Their first draft would be a graph not a flowchart. They will be very thorough in making sure they cover all angles, instead of "throwing exceptions" every so often. If you want a working ECU get the EE.
Unobtainium. Like "moon diamonds". The perfect gift for your future honey moon partner. At x100 price premiums compared to regular versions that are found in earth dirt. Rare! Only 3 available! With laser engraved serial number!
Well I didn't say *all* of them are good at it. Some cannot write software at all. You're looking for one with experience in embedded software. Do a pertinent job description ("Electrical Engineer experienced in designing and writing software for embedded systems"), list C and assembly as requisites, ask candidates to bring previous work examples (prototypes or whatever) if they have any. You might fall onto the guy building robots in his basement, if anyone brings you a bag full of strange flashing moving things hire him on the spot. Make sure you don't mention *java* anywhere, they're allergic to it. C++ is ok.
For embedded development try Electrical Engineers, they're better at it than the CS types. You may be surprised that many of them are very productive in assembly language too.
Slashdot Mirror
x.264 is open source, nothing stops you to maintain it for the next 100 years. BTW did google commit to maintain VP8 for some given amount of time? No? They could drop it tomorrow if they want? Oh well, then how does that make it "superior" from a maintenance and viability point of view to any other open source alternatives?
What is the percent of devices relative to the total nr of sold devices coming with firefox preinstalled? How do you install firefox on ipads and iphones? What are the chances that any of these codecs would get hardware acceleration on a significant nr of devices in the future?
They seem to use "MP4" and "H.264" in a pretty much interchangeable way in the original article. This does nothing but make things difficult to understand. Here's what they really need to standardize upon:
- a container format (such as mkv or mp4/m4v)
- a video codec (such as VP8 or H.264)
- an audio codec (such as Vorbis or AAC)
In order to make it "open/free", they need to chose all three components in this respect, such as an mkv container with VP8 video and Vorbis audio inside. Which will guarantee that the result won't play on any device right out of the box. OTOH if they chose something like m4v with H.264 video and AAC audio inside, it will play right out of the box on about anything from Windows PCs to tablets to PS3s to WD TV live boxes. The patent stuff doesn't affect the end user as these devices are already licensed to use the mentioned containers/codecs (and in a pretty efficient way such as having hardware accelerators). Now even if they figure out the video part, I'm curios what they're gonna use for audio codec/compression. There isn't much to chose from that isn't patented either.
Yes it does say so, quote: "A few minutes later, fire alarms in the garage went off, and firemen arrived to put out the blaze, which was described as "intense"."
I find it interesting that the owner of the car had a smoke alarm installed in his garage, especially since he also had a gasoline car parked there. That would lead to a pretty high number of nuisance alarms. In fact, even the fire depts themselves suggest that you should not install one:
http://www.windsorfire.com/eco...
(search for the word "garage" in the page).
So, what else was the owner doing in that garage that required the installation of the smoke detector, nuisance alarms be damned?
.
Of course it has. Where would all the spent electrons go?
The book's summary mentions a dataset from "163 US electric utilities". While South Carolina may be different, the book gets to the result that, on average, burying the lines would shorten both downtime and repair time.
May I also understand that the price/kW you're currently paying is also entirely of your choice? Or that, at a minimum, you have negotiated it with the power company?
Those figures were mentioned recently in the press, without quoting a source for them. Most likely they pulled them out of a hat. These gentlemen got to a different conclusion:
http://www.sciencedirect.com/science/article/pii/S0957178711000622
.
The dunce cap should be reintroduced. Albeit for chancellors not students.
You can't really move a jeep through a gridlock no matter what model of jeep and tires you have. Check what happened in Atlanta the last round. It wasn't that cars couldn't get any traction. It was about several crash scenes that gridlocked the whole traffic.
Yeah, to put it in perspective it's less than 1/16th of a bankers bailout:
http://www.forbes.com/sites/tr...
.
It continuously amazes me that people would easily pay in excess of 50k in order to get the largest SUVs ever, yet they would fight teeth and nails against an one time 3k fee to get their power lines buried. The SUVs have been proven useless during the ice storms, while having electrical power was proven to be priceless.
Did anyone notice that Microsoft already has an Android phone? Not "Android compatible" but 100% Android?
http://www.businessinsider.com...
.
It was Noah who put the dictionary together. His brother Daniel, the senator, pushed the "copyrightz" law so his bro could "make money". It was all about business. And that's how, ladies and gentlemen, you first got a copyright law in US.
What were they thinking....... :
http://driving.ca/bmw/i8/auto-...
???
And you would be wrong in several ways.
First, you may notice that I was talking about guys "building robots in their basement". Bringing some to the interview does not clash with their (former/current) employer (intellectual/physical) property. If anyone has those robots to show, it means that the guy is really passionate about his work, which in turn means that he has explored his field to the last detail, will take pride in his work and will go the extra mile to turn out quality/outstanding products.
Second, if the prototype comes from his workplace, he might have it with the agreement of his (former) employer. By the time your guy is looking for a new job, that device is either a complete fail, or the final product (copyrighted, trademarked and patented) is already on the market. If anyone wants to duplicate it in some shady way, it would be more productive to study the final product instead of some proto/proof of concept of it.
Third, unless you're the kind that comes up with "but companies are persons my friend" statements, you would notice that a company cannot have an intellect, and thus no "intellectual" property. What companies have are contracts about it.
I fully agree with your opinion on feta:
http://kidshealth.org/parent/question/infants/cheese_louise.html
If you think about Software Engineering as being about writing smartphone apps or Weblogic "enterprise" application, I will agree with you. However what good EEs have is a good understanding of systems theory and methodology. They will generally look at an embedded system as a (finite) state machine and work their way down from there. Their first draft would be a graph not a flowchart. They will be very thorough in making sure they cover all angles, instead of "throwing exceptions" every so often. If you want a working ECU get the EE.
Unobtainium. Like "moon diamonds". The perfect gift for your future honey moon partner. At x100 price premiums compared to regular versions that are found in earth dirt. Rare! Only 3 available! With laser engraved serial number!
I can take the Beta, but a direct feed from Fox News is a little bit to much....
Well I didn't say *all* of them are good at it. Some cannot write software at all. You're looking for one with experience in embedded software. Do a pertinent job description ("Electrical Engineer experienced in designing and writing software for embedded systems"), list C and assembly as requisites, ask candidates to bring previous work examples (prototypes or whatever) if they have any. You might fall onto the guy building robots in his basement, if anyone brings you a bag full of strange flashing moving things hire him on the spot. Make sure you don't mention *java* anywhere, they're allergic to it. C++ is ok.
And soon some medical devices will be penetrating the hackers.
The reason I cannot program it because it is not in my possession, mr. smart hat.
For embedded development try Electrical Engineers, they're better at it than the CS types. You may be surprised that many of them are very productive in assembly language too.