Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This will change soon though

This brings us to the roadmap of Neo and to when we can be sure that our customers can use our sites written in Neo.

What I see now is "For the best user experience, you need to use Google Chrome with the following browser flag: chrome://flags/#enable-experimental-web-platform-features". Maybe this means that we should only wait for Chrome 80+ to be on most desktops.

Firefox: all I got there is a number of "SyntaxError: import declarations may only appear at top level of a module". Which version of Firefox do we have to wait for?

Safari: I don't own any device from Apple but a number of my customers do. I wonder if Neo works there.

Other browsers: I assume that all the chromium based browsers are going to be covered by the compatibility with Chrome 80.

Mobile: "The online demos are not optimised for mobile yet, please use a desktop browser!" Is it only a matter of CSS or is there something about webworkers on those platforms?



Let me shed some light into this: Chrome 80 will most likely get released in January, since Chrome Canary already no longer needs the flag.

You can run the dist/development and dist/production versions of neo inside FF & Safari right now, the performance should be close.

Having 1 browser which fully supports it is enough for a great debugging experience. Obviously it would be nice if other browsers do catch up.

Mobile: I need to add support for touch events inside the main thread, which should be easy. On my todo list after the real world 2 app is done (want to focus on this one first, since it is meant to be a good starting point for new devs to get up to speed). The multithreading performance will be amazing on mobile.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: