4 ms·

When browser vendors killed Flash, it was like someone killed YouTube and forced all amateur video creators to deal with portability themselves. It "professiona

When browser vendors killed Flash, it was like someone killed YouTube and forced all amateur video creators to deal with portability themselves. It "professionalized" the field and drove away untold numbers of people who just wanted to show their interactive doodles to the world, not run the JS fashion treadmill for the rest of their lives. And programmers congratulate themselves on that! It looks like your browser will not be able to run Construct 3. The world craves a Flash replacement suitable for amateur creators, but it will need to take portability more seriously than every JS framework in existence.

swiley 10y ago
Java applets were pretty great in retrospect. Everything was more or less contained to one page element, the run time is open source (and often you can run the applet without the page) the language was (comparatively) nice. If only the security was handled better...
AshleysBrain 10y ago
You just need Chrome 57+ which is already on the stable channel. Just go to Help -> About Google Chrome and it should work.
- deleted 10y ago
  [deleted]
joshwcomeau 10y ago
Hitting the same message, as my Chrome is 1 version behind. Most people will not be willing to change their browsing habits to use your web application. The onus is on us, as software developers, to ensure our code runs in the user's browser, not the other way around. Ultimately it's up to you to decide where the line is drawn; nobody supports IE7 anymore because it's hardly used. But I suspect you'll lose a tremendous amount of potential users by not supporting Firefox, Safari or recent Chrome. I'm sure you guys are aware of preprocessors; is there a reason you haven't used them to implement things like HTML imports or CSS variables?
- MichaelBurge 10y ago
  > The onus is on us, as software developers, to ensure our code runs in the user's browser, not the other way around. I assume the exported games are portable and can run in older browsers. So the users shouldn't have to worry.

swiley 10y ago

Java applets were pretty great in retrospect. Everything was more or less contained to one page element, the run time is open source (and often you can run the applet without the page) the language was (comparatively) nice. If only the security was handled better...

AshleysBrain 10y ago

You just need Chrome 57+ which is already on the stable channel. Just go to Help -> About Google Chrome and it should work.

deleted 10y ago
[deleted]

joshwcomeau 10y ago

Hitting the same message, as my Chrome is 1 version behind. Most people will not be willing to change their browsing habits to use your web application. The onus is on us, as software developers, to ensure our code runs in the user's browser, not the other way around. Ultimately it's up to you to decide where the line is drawn; nobody supports IE7 anymore because it's hardly used. But I suspect you'll lose a tremendous amount of potential users by not supporting Firefox, Safari or recent Chrome. I'm sure you guys are aware of preprocessors; is there a reason you haven't used them to implement things like HTML imports or CSS variables?

MichaelBurge 10y ago
> The onus is on us, as software developers, to ensure our code runs in the user's browser, not the other way around. I assume the exported games are portable and can run in older browsers. So the users shouldn't have to worry.