> Paul Kinlan is a web platform developer advocate at Google
That's enough reason for me to say, f** no. Google will try as hard as possible to promote this even if it's not technically the best solution.
The browser is the sandbox
101–110 of 202 posts
Re: The browser is the sandbox
#102Earlier quoted context omitted.
> Sidenote: Flash's scripting language, ActionScript is also directly responsible for the generational design of Java-ahem-ECMAScript later on, also TypeScript too. I feel like I am the only one who absolutely loved ActionScript, especially AS3. I wrote a video aggregator (chime.tv[1]) back in the day using AS3 and it was such a fun experience. 1. https://techcrunch.com/2007/06/12/chimetv-a-prettier-way-to-...
How did you got that impression? There is the universal hate for flash because it was used for ads and had shitty security, but anyone I know who actually used AS3 loved it. At its peak, with flex builder, we also had a full blown UI Editor, where you could just add your own custom elements designed directly with flash ... and then it was all killed because Apple did not dare to open source it, or put serious efforts…
Adobe, not Apple.
Re: The browser is the sandbox
#103> Paul Kinlan is a web platform developer advocate at Google That's enough reason for me to say, f** no. Google will try as hard as possible to promote this even if it's not technically the best solution.
The title of the post is amazing, the content is not. Truly HN
Re: The browser is the sandbox
#104Earlier quoted context omitted.
> Sidenote: Flash's scripting language, ActionScript is also directly responsible for the generational design of Java-ahem-ECMAScript later on, also TypeScript too. I feel like I am the only one who absolutely loved ActionScript, especially AS3. I wrote a video aggregator (chime.tv[1]) back in the day using AS3 and it was such a fun experience. 1. https://techcrunch.com/2007/06/12/chimetv-a-prettier-way-to-...
How did you got that impression? There is the universal hate for flash because it was used for ads and had shitty security, but anyone I know who actually used AS3 loved it. At its peak, with flex builder, we also had a full blown UI Editor, where you could just add your own custom elements designed directly with flash ... and then it was all killed because Apple did not dare to open source it, or put serious efforts…
> and then it was all killed because Apple did not dare to open source it
Did you or, more likely, your phone mistype Adobe? I don’t think Apple ever had the rights to the source or even the source, did they?
Re: The browser is the sandbox
#105This is an entry on my link blog - make sure to read the article it links to for full context, my commentary alone might not make sense otherwise: https://aifoc.us/the-browser-is-the-sandbox/
You might want to add a little note to that effect to your link blog :)
I have added year indicators to my blog (such that old articles have a prominent year name in their title) and a subscribe note (people don’t know you can put URLs into a feed reader and it’ll auto-discover the feed URL). Each time, the number of people who email me identical questions goes down :)
Anyway, thanks for blogging!
Re: The browser is the sandbox
#106Earlier quoted context omitted.
Any sandbox technology works fine until it isn't. It's not like you could escape Java sandbox, but Java applets were removed from the browsers due to issues being found regularly. In the end, browser sandbox is one of the few that billions of people use and run arbitrary code there every day, without even understanding that. The only comparable technology is qemu. I don't think there are many hosters who will hand of…
> Java applets were removed from the browsers due to issues being found regularly Java applets were killed off my MS's attempt at "embrace, extent, extinguish" by bundling an incompatible version of Java with IE, and Sun's legal response to this.
They never worked nice and always felt slow, unreliable and janky at the time. It’s easy to blame MS but no one was sad to see the back of them.
Re: The browser is the sandbox
#107Earlier quoted context omitted.
> Java applets were removed from the browsers due to issues being found regularly Java applets were killed off my MS's attempt at "embrace, extent, extinguish" by bundling an incompatible version of Java with IE, and Sun's legal response to this.
They never worked nice and always felt slow, unreliable and janky at the time. It’s easy to blame MS but no one was sad to see the back of them.
I was fine with the few I used, and Java works much better on the hardware we now have. A lot better than a lot of cross platform things we have now.
Re: The browser is the sandbox
#108This is a great example of how useful the File System Access API is. On http://co-do.xyz/ you can select a directory and let AI get to work inside of it without having to worry about side effects. The Fily System Access API is the best thing that happened to the web in years. It makes web apps first class productivity applications.
> It makes web apps first class productivity applications. They won’t be first-class as long as native UI still has the upper hand.
This battle is long won in favor of webtech in every realm but 3d/video editing/audio work/things that do gpu heavy lifting like game engines.
Outside those sort of spaces it’s hard to name a popular piece of software still on native that isn’t a wrapped webapp.
Re: The browser is the sandbox
#109This is a great example of how useful the File System Access API is. On http://co-do.xyz/ you can select a directory and let AI get to work inside of it without having to worry about side effects. The Fily System Access API is the best thing that happened to the web in years. It makes web apps first class productivity applications.
Unfortunately, this feature of the API is not supported (yet?) either by Safari or Firefox.
The guarantee of web page never edit file on your disk(only create new ones) does not hold on this api though. I know
it's what makes this api useful. But at the same time, there is big risk that user never expected this and results into giant security issue.
Firefox and safari are generally very conservative about new api that can enable new type of exploits.
At least firefox and safari does implement origin private file system. So, while you can't edit file on user disk directly. You can import the whole project into browser. Finish the edit and export it.
Re: The browser is the sandbox
#110Earlier quoted context omitted.
How did you got that impression? There is the universal hate for flash because it was used for ads and had shitty security, but anyone I know who actually used AS3 loved it. At its peak, with flex builder, we also had a full blown UI Editor, where you could just add your own custom elements designed directly with flash ... and then it was all killed because Apple did not dare to open source it, or put serious efforts…
It was also leaking memory, which made it very unsuitable for anything long running (like long-running screen displays, ask me how I know).
This is a misconception. AS3 actually had great garbage collection, and solidly written AS3 code did not leak.