You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Deepak MS <me...@gmail.com> on 2017/08/14 12:19:17 UTC
Re: Adobe has announced the end-of-life of the Flash Player
Let's say Adobe releases final version of flash player version 35 for
instance, by end of 2019, without further maintenance or development of the
plugin. Will this version continue to stay forever, whether or not users
want to use it or is it that flash player will be blocked by browsers
themselves? It isn't clear in the article. Or did I miss it?
On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
nicholaskwiatkowski@gmail.com> wrote:
> Looks like we have a date :
>
> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
>
> -Nick
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Vincent Sotto <ds...@gmail.com>.
really unfortunate really, were still using flash player for our local apps
in our company, now we have to migrate this to another language and we have
around 2 years to do this. i mean if they still allow flashplayer even
without updates would be great
On Tue, Aug 15, 2017 at 7:15 AM, Gary Yang <fl...@gmail.com> wrote:
> The problem roots in Adobe's determination, the web without Flash is not
> that bad really, mobile is supporting 4k, Adobe lost its unique single
> chance without even a try, I am moving on to JavaFx+Gluon,
>
> On Mon, Aug 14, 2017 at 1:24 PM, Deepak MS <me...@gmail.com>
> wrote:
>
> > Thanks everyone. For sure, web apps that we have are lined up to be
> > migrated.
> >
> > Only reason I asked that question was that we have several other
> > applications which run as embedded shockwave flash objects within
> microsoft
> > powerpoint slides, which are completely offline (excel data is embedded
> > within the swf file). I'm not sure how that is going to work. And I
> haven't
> > seen any option of embedding HTML\JS applications, which are offline,
> > within powerpoint.
> >
> > On Mon, Aug 14, 2017 at 9:44 PM, piotrz <pi...@gmail.com>
> wrote:
> >
> > > That is definitely something which I'm all for - We shouldn't waste our
> > > time
> > > on something which is slowly ending.
> > >
> > > We have tremendous opportunity with FlexJS and all stuff related around
> > it
> > > to still writing code with pleasure and give customers what they
> > currently
> > > want - JS applications.
> > >
> > > I encourage everyone to try the stuff which we have been created so far
> > in
> > > Apache Flex project and help us improve it.
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > >
> > >
> > >
> > > -----
> > > Apache Flex PMC
> > > piotrzarzycki21@gmail.com
> > > --
> > > View this message in context: http://apache-flex-
> > > development.2333347.n4.nabble.com/Adobe-has-announced-the-
> > > end-of-life-of-the-Flash-Player-tp63544p63882.html
> > > Sent from the Apache Flex Development mailing list archive at
> Nabble.com.
> > >
> >
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Gary Yang <fl...@gmail.com>.
The problem roots in Adobe's determination, the web without Flash is not
that bad really, mobile is supporting 4k, Adobe lost its unique single
chance without even a try, I am moving on to JavaFx+Gluon,
On Mon, Aug 14, 2017 at 1:24 PM, Deepak MS <me...@gmail.com> wrote:
> Thanks everyone. For sure, web apps that we have are lined up to be
> migrated.
>
> Only reason I asked that question was that we have several other
> applications which run as embedded shockwave flash objects within microsoft
> powerpoint slides, which are completely offline (excel data is embedded
> within the swf file). I'm not sure how that is going to work. And I haven't
> seen any option of embedding HTML\JS applications, which are offline,
> within powerpoint.
>
> On Mon, Aug 14, 2017 at 9:44 PM, piotrz <pi...@gmail.com> wrote:
>
> > That is definitely something which I'm all for - We shouldn't waste our
> > time
> > on something which is slowly ending.
> >
> > We have tremendous opportunity with FlexJS and all stuff related around
> it
> > to still writing code with pleasure and give customers what they
> currently
> > want - JS applications.
> >
> > I encourage everyone to try the stuff which we have been created so far
> in
> > Apache Flex project and help us improve it.
> >
> > Thanks,
> > Piotr
> >
> >
> >
> >
> >
> > -----
> > Apache Flex PMC
> > piotrzarzycki21@gmail.com
> > --
> > View this message in context: http://apache-flex-
> > development.2333347.n4.nabble.com/Adobe-has-announced-the-
> > end-of-life-of-the-Flash-Player-tp63544p63882.html
> > Sent from the Apache Flex Development mailing list archive at Nabble.com.
> >
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Deepak MS <me...@gmail.com>.
Thanks everyone. For sure, web apps that we have are lined up to be
migrated.
Only reason I asked that question was that we have several other
applications which run as embedded shockwave flash objects within microsoft
powerpoint slides, which are completely offline (excel data is embedded
within the swf file). I'm not sure how that is going to work. And I haven't
seen any option of embedding HTML\JS applications, which are offline,
within powerpoint.
On Mon, Aug 14, 2017 at 9:44 PM, piotrz <pi...@gmail.com> wrote:
> That is definitely something which I'm all for - We shouldn't waste our
> time
> on something which is slowly ending.
>
> We have tremendous opportunity with FlexJS and all stuff related around it
> to still writing code with pleasure and give customers what they currently
> want - JS applications.
>
> I encourage everyone to try the stuff which we have been created so far in
> Apache Flex project and help us improve it.
>
> Thanks,
> Piotr
>
>
>
>
>
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-
> development.2333347.n4.nabble.com/Adobe-has-announced-the-
> end-of-life-of-the-Flash-Player-tp63544p63882.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by piotrz <pi...@gmail.com>.
That is definitely something which I'm all for - We shouldn't waste our time
on something which is slowly ending.
We have tremendous opportunity with FlexJS and all stuff related around it
to still writing code with pleasure and give customers what they currently
want - JS applications.
I encourage everyone to try the stuff which we have been created so far in
Apache Flex project and help us improve it.
Thanks,
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Adobe-has-announced-the-end-of-life-of-the-Flash-Player-tp63544p63882.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Jeffry Houser <je...@dot-com-it.com>.
I agree w/ Josh's fear of security problems coming from Flash.
I wonder if a different sandboxing model for plugins would prevent
security issues?
However, beyond that I'd encourage the effort. I think it's a neat
idea that sounds like a big challenge and wish you best of luck with that.
On 8/14/2017 11:14 AM, Josh Tynjala wrote:
> It's best to assume that Adobe is no longer going to provide security
> updates for Flash Player in 2020. Do not fork any web browsers to try to
> continue supporting Flash Player or other plugins. You will put the
> security of your users at great risk. It's not worth it.
>
> The age of browser plugins, and Flash Player on the web, is coming to an
> end. It's time to move on. You can migrate your apps to AIR. You can
> contribute to FlexJS. The folks working on the spriteflexjs library are
> trying to recreate the display list and other flash.* APIs in the browser.
> Contribute to those efforts, and you'll be able to keep writing the same
> code for the web.
>
> - Josh
>
> On Mon, Aug 14, 2017 at 7:41 AM, flex capacitor <fl...@gmail.com>
> wrote:
>
>> Microsoft, Google and Firefox have all explicitly disabled FP in the
>> browser and then faced backlash from users and then they reenabled it.
>> Remember Microsoft's exclusion list? We read tech blogs and have heard the
>> news but the average user isn't paying attention or they'll be distracted
>> around 2020 (by elections).
>>
>> My opinion is businesses won't move over unless they have to and many of
>> them don't want to spend the money to. And some companies don't have the
>> money to.
>>
>> What if we fork a version of Firefox that continues to support plugins. Get
>> announcements out to the major tech blogs. Clear up the misconceptions at
>> the same time. Unity would be down for that and they have major investors.
>> They were thrown under the bus too.
>>
>> I had written a paragraph about Googles web team here but to keep it short
>> they are bias and are trying to make decisions for everyone. Firefox is
>> following their lead so they somehow don't lose users. When the browsers
>> makers decide (for everyone) to disable plugins there will be a huge
>> audience looking for a browser that continues to support them.
>>
>> At the same time maybe we can put some part of Flex into it like client
>> side MXML rendering or compiling. I think Alex said the compiler could be
>> stripped down to 29MB. Almost everyone uses IE to download Chrome or
>> Firefox. Download size is not a big an issue as it used to be.
>>
>> HTML, CSS, JS need an upgrade. HTML can be upgraded to MXML (Flex or
>> FlexJS), CSS in Flex has always been fine for me but it could be upgraded
>> to SCSS or post CSS (I'm sure there are others). JS is being upgraded to
>> ES5, 6 slowly but even ES6 still feels less than ES4. That might generate
>> interest from developers. My 2 cents.
>>
>>
>> On Mon, Aug 14, 2017 at 9:10 AM, Jeffry Houser <je...@dot-com-it.com>
>> wrote:
>>
>>> For legacy applications or archival purposes, you'll probably want to
>>> keep an installer for the Flash Player and/or older browsers. So they
>> can
>>> be reset up on an old machine, or in a VM. Browsers, for the most part,
>>> have already shut down their plugin APIs.
>>>
>>>
>>>
>>> On 8/14/2017 8:26 AM, Clint M wrote:
>>>
>>>> I remember reading that browsers won't be supporting after that.
>>>>
>>>> On Mon, Aug 14, 2017 at 6:19 AM, Deepak MS <me...@gmail.com>
>>>> wrote:
>>>>
>>>> Let's say Adobe releases final version of flash player version 35 for
>>>>> instance, by end of 2019, without further maintenance or development of
>>>>> the
>>>>> plugin. Will this version continue to stay forever, whether or not
>> users
>>>>> want to use it or is it that flash player will be blocked by browsers
>>>>> themselves? It isn't clear in the article. Or did I miss it?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
>>>>> nicholaskwiatkowski@gmail.com> wrote:
>>>>>
>>>>> Looks like we have a date :
>>>>>> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
>>>>>>
>>>>>> -Nick
>>>>>>
>>>>>>
>>> --
>>> Jeffry Houser
>>> Technical Entrepreneur
>>> http://www.dot-com-it.com
>>> http://www.jeffryhouser.com
>>> 203-379-0773
>>>
>>>
--
Jeffry Houser
Technical Entrepreneur
http://www.dot-com-it.com
http://www.jeffryhouser.com
203-379-0773
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Josh Tynjala <jo...@gmail.com>.
It's best to assume that Adobe is no longer going to provide security
updates for Flash Player in 2020. Do not fork any web browsers to try to
continue supporting Flash Player or other plugins. You will put the
security of your users at great risk. It's not worth it.
The age of browser plugins, and Flash Player on the web, is coming to an
end. It's time to move on. You can migrate your apps to AIR. You can
contribute to FlexJS. The folks working on the spriteflexjs library are
trying to recreate the display list and other flash.* APIs in the browser.
Contribute to those efforts, and you'll be able to keep writing the same
code for the web.
- Josh
On Mon, Aug 14, 2017 at 7:41 AM, flex capacitor <fl...@gmail.com>
wrote:
> Microsoft, Google and Firefox have all explicitly disabled FP in the
> browser and then faced backlash from users and then they reenabled it.
> Remember Microsoft's exclusion list? We read tech blogs and have heard the
> news but the average user isn't paying attention or they'll be distracted
> around 2020 (by elections).
>
> My opinion is businesses won't move over unless they have to and many of
> them don't want to spend the money to. And some companies don't have the
> money to.
>
> What if we fork a version of Firefox that continues to support plugins. Get
> announcements out to the major tech blogs. Clear up the misconceptions at
> the same time. Unity would be down for that and they have major investors.
> They were thrown under the bus too.
>
> I had written a paragraph about Googles web team here but to keep it short
> they are bias and are trying to make decisions for everyone. Firefox is
> following their lead so they somehow don't lose users. When the browsers
> makers decide (for everyone) to disable plugins there will be a huge
> audience looking for a browser that continues to support them.
>
> At the same time maybe we can put some part of Flex into it like client
> side MXML rendering or compiling. I think Alex said the compiler could be
> stripped down to 29MB. Almost everyone uses IE to download Chrome or
> Firefox. Download size is not a big an issue as it used to be.
>
> HTML, CSS, JS need an upgrade. HTML can be upgraded to MXML (Flex or
> FlexJS), CSS in Flex has always been fine for me but it could be upgraded
> to SCSS or post CSS (I'm sure there are others). JS is being upgraded to
> ES5, 6 slowly but even ES6 still feels less than ES4. That might generate
> interest from developers. My 2 cents.
>
>
> On Mon, Aug 14, 2017 at 9:10 AM, Jeffry Houser <je...@dot-com-it.com>
> wrote:
>
> > For legacy applications or archival purposes, you'll probably want to
> > keep an installer for the Flash Player and/or older browsers. So they
> can
> > be reset up on an old machine, or in a VM. Browsers, for the most part,
> > have already shut down their plugin APIs.
> >
> >
> >
> > On 8/14/2017 8:26 AM, Clint M wrote:
> >
> >> I remember reading that browsers won't be supporting after that.
> >>
> >> On Mon, Aug 14, 2017 at 6:19 AM, Deepak MS <me...@gmail.com>
> >> wrote:
> >>
> >> Let's say Adobe releases final version of flash player version 35 for
> >>> instance, by end of 2019, without further maintenance or development of
> >>> the
> >>> plugin. Will this version continue to stay forever, whether or not
> users
> >>> want to use it or is it that flash player will be blocked by browsers
> >>> themselves? It isn't clear in the article. Or did I miss it?
> >>>
> >>>
> >>>
> >>> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
> >>> nicholaskwiatkowski@gmail.com> wrote:
> >>>
> >>> Looks like we have a date :
> >>>>
> >>>> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
> >>>>
> >>>> -Nick
> >>>>
> >>>>
> > --
> > Jeffry Houser
> > Technical Entrepreneur
> > http://www.dot-com-it.com
> > http://www.jeffryhouser.com
> > 203-379-0773
> >
> >
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by flex capacitor <fl...@gmail.com>.
Microsoft, Google and Firefox have all explicitly disabled FP in the
browser and then faced backlash from users and then they reenabled it.
Remember Microsoft's exclusion list? We read tech blogs and have heard the
news but the average user isn't paying attention or they'll be distracted
around 2020 (by elections).
My opinion is businesses won't move over unless they have to and many of
them don't want to spend the money to. And some companies don't have the
money to.
What if we fork a version of Firefox that continues to support plugins. Get
announcements out to the major tech blogs. Clear up the misconceptions at
the same time. Unity would be down for that and they have major investors.
They were thrown under the bus too.
I had written a paragraph about Googles web team here but to keep it short
they are bias and are trying to make decisions for everyone. Firefox is
following their lead so they somehow don't lose users. When the browsers
makers decide (for everyone) to disable plugins there will be a huge
audience looking for a browser that continues to support them.
At the same time maybe we can put some part of Flex into it like client
side MXML rendering or compiling. I think Alex said the compiler could be
stripped down to 29MB. Almost everyone uses IE to download Chrome or
Firefox. Download size is not a big an issue as it used to be.
HTML, CSS, JS need an upgrade. HTML can be upgraded to MXML (Flex or
FlexJS), CSS in Flex has always been fine for me but it could be upgraded
to SCSS or post CSS (I'm sure there are others). JS is being upgraded to
ES5, 6 slowly but even ES6 still feels less than ES4. That might generate
interest from developers. My 2 cents.
On Mon, Aug 14, 2017 at 9:10 AM, Jeffry Houser <je...@dot-com-it.com>
wrote:
> For legacy applications or archival purposes, you'll probably want to
> keep an installer for the Flash Player and/or older browsers. So they can
> be reset up on an old machine, or in a VM. Browsers, for the most part,
> have already shut down their plugin APIs.
>
>
>
> On 8/14/2017 8:26 AM, Clint M wrote:
>
>> I remember reading that browsers won't be supporting after that.
>>
>> On Mon, Aug 14, 2017 at 6:19 AM, Deepak MS <me...@gmail.com>
>> wrote:
>>
>> Let's say Adobe releases final version of flash player version 35 for
>>> instance, by end of 2019, without further maintenance or development of
>>> the
>>> plugin. Will this version continue to stay forever, whether or not users
>>> want to use it or is it that flash player will be blocked by browsers
>>> themselves? It isn't clear in the article. Or did I miss it?
>>>
>>>
>>>
>>> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
>>> nicholaskwiatkowski@gmail.com> wrote:
>>>
>>> Looks like we have a date :
>>>>
>>>> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
>>>>
>>>> -Nick
>>>>
>>>>
> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.dot-com-it.com
> http://www.jeffryhouser.com
> 203-379-0773
>
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Jeffry Houser <je...@dot-com-it.com>.
For legacy applications or archival purposes, you'll probably want to
keep an installer for the Flash Player and/or older browsers. So they
can be reset up on an old machine, or in a VM. Browsers, for the most
part, have already shut down their plugin APIs.
On 8/14/2017 8:26 AM, Clint M wrote:
> I remember reading that browsers won't be supporting after that.
>
> On Mon, Aug 14, 2017 at 6:19 AM, Deepak MS <me...@gmail.com> wrote:
>
>> Let's say Adobe releases final version of flash player version 35 for
>> instance, by end of 2019, without further maintenance or development of the
>> plugin. Will this version continue to stay forever, whether or not users
>> want to use it or is it that flash player will be blocked by browsers
>> themselves? It isn't clear in the article. Or did I miss it?
>>
>>
>>
>> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
>> nicholaskwiatkowski@gmail.com> wrote:
>>
>>> Looks like we have a date :
>>>
>>> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
>>>
>>> -Nick
>>>
--
Jeffry Houser
Technical Entrepreneur
http://www.dot-com-it.com
http://www.jeffryhouser.com
203-379-0773
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Clint M <cm...@gmail.com>.
I remember reading that browsers won't be supporting after that.
On Mon, Aug 14, 2017 at 6:19 AM, Deepak MS <me...@gmail.com> wrote:
> Let's say Adobe releases final version of flash player version 35 for
> instance, by end of 2019, without further maintenance or development of the
> plugin. Will this version continue to stay forever, whether or not users
> want to use it or is it that flash player will be blocked by browsers
> themselves? It isn't clear in the article. Or did I miss it?
>
>
>
> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
> nicholaskwiatkowski@gmail.com> wrote:
>
> > Looks like we have a date :
> >
> > https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
> >
> > -Nick
> >
>
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Tom Chiverton <tc...@extravision.com>.
However, just like with other pieces of hardware that need old versions
of Java, it's perfectly possible to keep an old version of Flash and a
browser around inside something like VirtualBox.
Tom
On 14/08/17 14:10, Josh Tynjala wrote:
> Browsers are definitely planning to remove all support for the Flash Player
> plugin on or before 2020.
>
> - Josh
>
>
> On Aug 14, 2017 5:19 AM, "Deepak MS" <me...@gmail.com> wrote:
>
> Let's say Adobe releases final version of flash player version 35 for
> instance, by end of 2019, without further maintenance or development of the
> plugin. Will this version continue to stay forever, whether or not users
> want to use it or is it that flash player will be blocked by browsers
> themselves? It isn't clear in the article. Or did I miss it?
>
>
>
> On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
> nicholaskwiatkowski@gmail.com> wrote:
>
>> Looks like we have a date :
>>
>> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
>>
>> -Nick
>>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
Re: Adobe has announced the end-of-life of the Flash Player
Posted by Josh Tynjala <jo...@gmail.com>.
Browsers are definitely planning to remove all support for the Flash Player
plugin on or before 2020.
- Josh
On Aug 14, 2017 5:19 AM, "Deepak MS" <me...@gmail.com> wrote:
Let's say Adobe releases final version of flash player version 35 for
instance, by end of 2019, without further maintenance or development of the
plugin. Will this version continue to stay forever, whether or not users
want to use it or is it that flash player will be blocked by browsers
themselves? It isn't clear in the article. Or did I miss it?
On Wed, Jul 26, 2017 at 1:32 AM, Nicholas Kwiatkowski <
nicholaskwiatkowski@gmail.com> wrote:
> Looks like we have a date :
>
> https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html
>
> -Nick
>