On Thu, Jan 29, 2015 at 8:24 PM, Rugxulo <rugx...@gmail.com> wrote:
> On Tue, Dec 16, 2014 at 4:32 PM, dmccunney <dennis.mccun...@gmail.com> wrote:

>> But I'm not holding my breath while Flash goes away. A technology that
>> pervasive and deeply embedded doesn't simply go away overnight.  It
>> needs to be replaced, and the content that used it recrafted in
>> something else.
>
> 1). http://www.osnews.com/story/28253/YouTube_now_defaults_to_HTML5_video
> 2). 
> http://youtube-eng.blogspot.nl/2015/01/youtube-now-defaults-to-html5_27.html
>
> Keep in mind that YouTube is currently owned by Google. Also keep in
> mind that it currently only claims to be fully supported on "Chrome,
> IE 11, Safari 8 and in beta versions of Firefox". Infer whatever you
> want from that.

I infer that you need a relatively current browser.  (And note that
current release versions of Firefox support YouTube.  A beta is not
required.)

The biggest use case for Flash has been video, which historically has
been presented on the web as SWF objects.  Google has been migrating
YouTube away from Flash and to HTML5.  The biggest reason for most
folks to go to HTML5 has been the <video> keyword, which allows video
to be embedded *without* requiring Flash.  You still need a codec to
decode and render video, but the codec can be delivered as part of the
browser, and not require a plugin.

(And there were amusing moments there, too.  YouTube had a beta site
where you could test the HTML5 versions.  IE and Chrome worked.
Firefox did not.  The problem was that the HTML5 videos were encoded
using H.264, a proprietary technology requiring a license fee.  MS and
Google paid the fee and included the plugin binary.  Firefox did not
because it was open source and required all components supplied with
Firefox to have source available, and could not do so with the H.264
codec.  Google subsequently decided to open source Chrome as well, and
was looking at alternate codecs that could be offered as open source
but had performance equivalent to H.264.)

Current browser development makes the underlying assumption that
plugins are bad, and that the user should need only a browser to view
web content.  Plugins get called as external processes, and a failing
plugin can take the browser with it.  That fact is responsible for
Mozilla's plugin_helper executable, which runs plugins in a sandbox so
a failing plugin doesn't  also take down the browser, and for in part
Chrome running each browser tab in a separate process.

Meanwhile, if you are attempting to browse from DOS, you are
increasingly far behind.  I don't even *try* to browse from FreeDOS.
Since I have Windows and Linux available, and currently supported
browsers run in both, I have no need to.  I do not see current web
standards being supported in DOS browser.  Aside from the fact that
I'm not sure it's *possible*, who would invest the development effort
to do it, and why?

FreeDOS here is a toy.  I run it to keep my hand in, and to play with
old technology.  I *don't* try to do critical work in it.  I have
Windows and Linux for that, and a lot of what I do simply can't be
done in DOS.

There are folks who *are* using DOS as a production OS, and have done
so since DOS *was* the main OS on a PC.  If your needs can be met by
what DOS and DOS applications can do, more power to you.  Mine can't.

Too many discussions on topics like this resolve to "I don't want to
change.  I want to keep doing what I've always done.  Development
should stop in its tracks so I can continue to do that."  I see this
in Windows and Linux forums as well.  There's a chap in a Linux forum
elsewhere still trying to use Thunderbird 2.0 and finding it
increasingly difficult.  All I can say is "TBird 2.0?  God.  *Why?*"
(The answer is he has it the way he likes it and doesn't want to
change.  He's near the point where he won't have a choice.)

Unfortunately, the world does not sit still.  Change is a constant,
and adapting to change is a requirement.  Tough.  Deal with it.  The
world will not sit still for you.
______
Dennis
https://plus.google.com/u/0/105128793974319004519

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to