Yet the hardware decoding adoption for consumers for VP9 stands precisely at 0%
Intel has been shipping VP9 hardware decoding for years. By default Microsoft Edge enables VP9 when hardware decoding is present (though you can override that to enable VP9 in software). VP9 is a standard video format on Android and many Android phones have VP9 hardware decoding.
H.265 is futureless for web video. Major streaming services are members of the Alliance for Open Media (Google, Netflix, Hulu, Amazon) because they want to use AV1 on their service. They recognize correctly that H.265's licensing mess makes it a poor option.
There's broad hardware support for VP9 as well. The major CPU and GPU manufacturers are all members of the Alliance for Open Media, so eventually they'll all have AV1 support when it's finished.
The licensing mess around H.265 makes it a non-starter. There are three separate patent pools you need to buy a license from (MPEG LA, HEVC Advance, and Velos Media).
No one can tell you what your final licensing cost will end up being. Velos Media hasn't even announced their licensing terms yet. Some companies, like Technicolor, are not in any patent pool so you need to negotiate a separate license will them.
The farcical licensing situation makes H.265 impractical. VP9 and AV1, in contrast, are both royalty-free for all use cases. There's no point wasting time with licensing uncertainty when you can just go ahead and use royalty-free codecs.
I think that sums up the basic problem with Flash. You're put in a position where you have to petition and hope. The Shumway git repository hasn't seen much activity for a couple of years.
How do you know? Are you sure Java isn't bigger? And if I use a language like Pascal which can use C libraries in addition to Pascal libraries, doesn't that mean the set of libraries available to Pascal is bigger?
To do that Ada, Pascal and FORTRAN would have needed more low level features
Pascal has the same low level features as C with a better type system and optional bounds checking. Pascal gives you the same power as C with better safety.
Strings and dynamic arrays are a good example. Strings and dynamic arrays are far easier to work with in Pascal than in C. They're both reference counted in Pascal as part of the core language. It makes things much simpler.
But equally if you really want to manage memory manually in Pascal then you can choose to do that too.
That is correct. Free Pascal, for example, doesn't link against libc unless you use libc directly or use some library which depends on libc. Free Pascal is not dependent on libc.
These have nothing to do with the technical features of the language.
Review what you have previously said. You said C is more difficult to use and takes longer to get right. The technical features of the C language create the necessity of an organizational perfection that will never exist.
Rust eliminates some classes of mistakes
So you agree Rust helps you make fewer mistakes and saves time and money over C. We're not actually arguing here.
There's no silver bullet, and the problems are institutional, not technical.
The technical problems create the institutional problems. You said you need more support and hand-holding to develop in C. You said you needed management to cosset you and QA to find your mistakes for you.
Rust helps you make fewer mistakes and to be more independent.
Unless you believe, as I do, that the majority of those security problems stem from dev cycle time pressure, mismanagement, and inadequate QA.
So your argument is that it is more difficult and it takes longer to get C programs right and, as a consequence, C creates organizational complexity and overhead.
You've made a strong case for everyone to save time and money by using Rust.
Decades worth of security problems have clearly demonstrated that no one has learnt to program and no one has learnt their tools. It's naive to claim otherwise.
C has been around for decades, is welll understood and does exactly what we want?
Because it doesn't do exactly what you want. Decades of C usage has lead to decades worth of security problems. The history of security flaws in programs written in C has been a costly one. Rust doesn't solve the whole security problem but it offers memory safety features that C doesn't.
With reflection, you can do things like replace the implementation of a method at run time.
You can do that with Pascal. You just assign your method implementation to one of the method properties of some object. It's the standard way of doing events in the VCL.
Slashdot Mirror
Yet the hardware decoding adoption for consumers for VP9 stands precisely at 0%
Intel has been shipping VP9 hardware decoding for years. By default Microsoft Edge enables VP9 when hardware decoding is present (though you can override that to enable VP9 in software). VP9 is a standard video format on Android and many Android phones have VP9 hardware decoding.
I suspect Google will support h.265 in addition to their own codecs
No. They use VP9 on YouTube and have been for two years. They dropped support for 4K video in H.264 on YouTube a while back. YouTube will start encoding video with AV1 around six months after the bitstream is finalized.
H.265 is futureless for web video. Major streaming services are members of the Alliance for Open Media (Google, Netflix, Hulu, Amazon) because they want to use AV1 on their service. They recognize correctly that H.265's licensing mess makes it a poor option.
baked into all hardware
There's broad hardware support for VP9 as well. The major CPU and GPU manufacturers are all members of the Alliance for Open Media, so eventually they'll all have AV1 support when it's finished.
The licensing mess around H.265 makes it a non-starter. There are three separate patent pools you need to buy a license from (MPEG LA, HEVC Advance, and Velos Media).
No one can tell you what your final licensing cost will end up being. Velos Media hasn't even announced their licensing terms yet. Some companies, like Technicolor, are not in any patent pool so you need to negotiate a separate license will them.
The farcical licensing situation makes H.265 impractical. VP9 and AV1, in contrast, are both royalty-free for all use cases. There's no point wasting time with licensing uncertainty when you can just go ahead and use royalty-free codecs.
indications are Netflix is going with h.265.
No. Netflix is going with VP9 and in future will go with AV1. Netflix is a member of the Alliance for Open Media.
Now you're just getting petty. It's true that C has let you down but it's time to let it go.
You've completely missed the point
You didn't make one other than to tell me to use Rust instead of C.
Hopefully
I think that sums up the basic problem with Flash. You're put in a position where you have to petition and hope. The Shumway git repository hasn't seen much activity for a couple of years.
What I'm arguing
No. You've tried to mount a defense for C's shortcomings but you've failed. All you've done is make the case that Rust is a better choice than C.
The users still want it
Users don't know what they want. Users fundamentally don't care if their dancing pigs animation is implemented in Flash or something else.
You're right. It's naive of me
So again you admit Rust is the better choice over C. I don't know what you're trying to argue. You've done nothing but agree with me.
chasing that silver bullet
Whoever said anything about a silver bullet?
has the largest set of libraries in the world
How do you know? Are you sure Java isn't bigger? And if I use a language like Pascal which can use C libraries in addition to Pascal libraries, doesn't that mean the set of libraries available to Pascal is bigger?
Presumably, the first Rust compiler was written completely in C
No, the Rust compiler was written in OCaml before it became self-hosting.
To do that Ada, Pascal and FORTRAN would have needed more low level features
Pascal has the same low level features as C with a better type system and optional bounds checking. Pascal gives you the same power as C with better safety.
Strings and dynamic arrays are a good example. Strings and dynamic arrays are far easier to work with in Pascal than in C. They're both reference counted in Pascal as part of the core language. It makes things much simpler.
But equally if you really want to manage memory manually in Pascal then you can choose to do that too.
They don't link against libc?
That is correct. Free Pascal, for example, doesn't link against libc unless you use libc directly or use some library which depends on libc. Free Pascal is not dependent on libc.
making mistakes you shouldn't be making anyway, if you know what you're doing
You're arguing for a fantasy world that doesn't exist. This is naive. Decades worth of C usage has demonstrated that it will never exist.
All you have done is effectively make the case for the necessity of languages like Rust. You have convinced me that Rust is the better choice over C.
These have nothing to do with the technical features of the language.
Review what you have previously said. You said C is more difficult to use and takes longer to get right. The technical features of the C language create the necessity of an organizational perfection that will never exist.
Rust eliminates some classes of mistakes
So you agree Rust helps you make fewer mistakes and saves time and money over C. We're not actually arguing here.
There's no silver bullet, and the problems are institutional, not technical.
The technical problems create the institutional problems. You said you need more support and hand-holding to develop in C. You said you needed management to cosset you and QA to find your mistakes for you.
Rust helps you make fewer mistakes and to be more independent.
Unless you believe, as I do, that the majority of those security problems stem from dev cycle time pressure, mismanagement, and inadequate QA.
So your argument is that it is more difficult and it takes longer to get C programs right and, as a consequence, C creates organizational complexity and overhead.
You've made a strong case for everyone to save time and money by using Rust.
Learn to program. Learn your tools.
Decades worth of security problems have clearly demonstrated that no one has learnt to program and no one has learnt their tools. It's naive to claim otherwise.
It was the same test for all the browsers. Four times better than the next best is not an anomaly, it's a fundamentally better architecture.
C has been around for decades, is welll understood and does exactly what we want?
Because it doesn't do exactly what you want. Decades of C usage has lead to decades worth of security problems. The history of security flaws in programs written in C has been a costly one. Rust doesn't solve the whole security problem but it offers memory safety features that C doesn't.
Is Firefox developed in Rust?
It's just now starting to be. Mozilla's research browser, Servo, is written in Rust and they have started to integrate Servo components into Firefox. Components like Servo's WebRender significantly outperform other browsers.
uses a codec that is a minefield of patents
Which codec would that be? The same H.264 that Flash used?
HTML5 video also offers the option of VP9 video. VP9 is royalty-free for all use cases and outperforms H.264.
So just use VP9 and be happy.
For one, there's a lot of on-line games that are not practical or reliable in JavaScript/Html5 yet.
Like what? Offer an example.
With reflection, you can do things like replace the implementation of a method at run time.
You can do that with Pascal. You just assign your method implementation to one of the method properties of some object. It's the standard way of doing events in the VCL.