Hacker News .hnnew | past | comments | ask | show | jobs | submit | ddrouin's commentslogin

SEEKING WORK - Montreal/Remote

Freelance iOS developer. Generalist programmer with 8+ years of professional experience.

I am driven by the final product first and foremost. I have a strong technical background but I believe technology should be seen as a tool before all. Getting things done in a balanced and pragmatical way is my priority. I have strong interest in UX design and project management as well.

Passionate. Quick learner. Great communication. Used to remote work. You're more than welcome to inquire.

http://linkedin.com/in/ddrouin


SEEKING WORK - Montreal/Quebec City/Remote

Freelance iOS developer. Generalist programmer with 8+ years of professional experience.

I am driven by the final product first and foremost. I have a strong technical background but I believe technology should be seen as a tool before all. Getting things done in a balanced and pragmatical way is my priority. I have strong interest in UX design and project management as well.

Passionate. Quick learner. Great communication. Used to remote work. You're more than welcome to inquire.

http://linkedin.com/in/ddrouin


There is nothing ironic about it. His whole point is that sharing should be something the user chooses to opt-in, which is the case with that "share on" bar.


For reference, Mike Chambers is the principal product manager for the Adobe Flash platform. You can read this as Adobe's officialish reaction on this whole debate.


I want the same with chess. Please.


There are more possible games of chess than there are atoms in the universe


I think he was being facetious.


It's a funny situation, in the sense that Microsoft did exactly the same thing on the ECMAScript 4 standard on which Actionscript 3 is based and managed instead to stall the evolution of the ES standard...

http://whydoeseverythingsuck.com/2008/08/ru-roh-adobe-screwe...


Everyone focused on Microsoft at the time but Yahoo and others also dissented. I think for good reason; ES4 is nearly completely different from normal Javascript (static types, class-based inheritance).

Also Adobe was getting a standard that was what they already had and Mozilla had a AS3 VM runtime from Adobe. Microsoft would have been starting from scratch. I don't blame them for blocking it.

(EDIT: If you look at this Apple also marked red to much of ES4: http://spreadsheets.google.com/pub?key=pFIHldY_CkszsFxMkQORe...)


The best compromise would be to trust a given application after its first (or first few) review(s) and allow its developer to update it without going through the review process afterward. This would keep the gate for spammy applications and establish a relation of trust between the devs and Apple.

Of course, this is unlikely to happen as Apple is using the review process to make sure the apps are not calling private APIs or violating whatever rules Apple decides to apply. But giving up this last layer of "security" for Apple to allow for better developer AND user experience would be the best move Apple could do to improve the whole App Store frustations from developers.


Well, the problem of filtering private API usage would be easy to fix. They're already using an automated tool to detect it, so why not just scan the app right when the user uploads it? That would actually be better than the current system. Right now, if you upload an app that uses private APIs, you have to wait for however long it takes to actually get to a human reviewer (2-14 days) and then they run the tool, wasting a lot of time.


I do not believe they should just blindly get rid of the review process of app updates, but I do think that there should be some priority given to them. I believe that a developer should be able to push updates out to their apps with relative quickness compared to getting a new app approved. This would even benefit Apple for the applications that are teetering on making a decent amount of sales but are lagging in the sales due to some kind of problem/stability issue.


Haven't been able to make it work in Chromium either (launching it in webgl/no sandbox mode).

Has anybody sucessfully ran the demos?


It worked for me with chromium-bin-5.0.308.0_p37385 on 64-bit Gentoo.

The one thing I had to do (besides launching it as 'chromium-bin --no-sandbox --enable-webgl', as you mentioned) was to create a symbolic link from /usr/lib/libGL.so to /usr/lib/libGL.so.1 .


For your information, Grant Skinner has been one of the most well known Flash developer and entrepreneur for the last decade. This post brings a very interesting and down to earth perspective on the current Flash debate.


It is nice indeed to see a perspective on this that isn't either smugly dismissive, jumpy and defensive, or in denial.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: