Live data from Hacker News

Photoshop’s journey to the web

web.dev

41–50 of 203 posts

Re: Photoshop’s journey to the web

#41
post #8

Well, I certainly don't like where this is going. Mind you, I suspect I'll not be alone and by the time Adobe transition to a fully web-based subscription lock-in, Affinity et al will be better positioned to entirely fill the void. Sod Adobe.

Maybe, but AI tooling is becoming relevant and if Adobe plays their cards right that will let them maintain a premium edge for another decade or two.

For sure, though, sod Adobe.

Re: Photoshop’s journey to the web

#42

Earlier quoted context omitted.

It is not different from compiled machine code.

Biggest difference is probably more people have the means to debug something when it runs in the browser. So technically the same, but it may be more available to look at.

I think that's because most things that run in the browser aren't using web assembly.

Re: Photoshop’s journey to the web

#43
post #25
post #13

Only Chromium/Blink browsers are supported, so no Firefox or Safari. This is bad for the web.

Two very underfunded teams there trying to play catch up. Only one of them has an excuse though, the other is literally the most profitable company in the world who is strategically trying to make the web into a subpar platform for their own commercial interests.

Hey, I don't think you should discount all of the great work Apple has done on Safari lately, such as... making tabs ugly and hard to use

Re: Photoshop’s journey to the web

#44
post #26

I would love to see Photoshop in browser as a self-hostable option. I have many tools setup on my LAN and slowly been porting applications over to my local server so I can access all my applications on all my devices.

I’m not sure if you’re only accessing applications through a browser in this case but if you’re using Remote Desktop then why not Gimp or similar FOSS alternative?

Oh no, it's all in-browser apps. I use it when at work by connecting to my server through chrome and using those apps. We only have chrome access at work, in fact all port besides 80/443 are blocked.

Re: Photoshop’s journey to the web

#45
post #25
post #13

Only Chromium/Blink browsers are supported, so no Firefox or Safari. This is bad for the web.

Two very underfunded teams there trying to play catch up. Only one of them has an excuse though, the other is literally the most profitable company in the world who is strategically trying to make the web into a subpar platform for their own commercial interests.

Firefox isn't even playing catchup. Mozilla aborted what scant work it's done on PWA support.

From the horse's mouth: https://bugzilla.mozilla.org/show_bug.cgi?id=1682593

Chrome and its variants have already won the PWA space, not by some brilliant strategy or sinister ploy on Google's part, but by default of its competitors.

Re: Photoshop’s journey to the web

#46
post #3

Really cool to see what's possible in desktop browsers these days. Photoshop coming to our browsers is a huge achievement and milestone. But it also makes me kinda sad that none of the mentioned examples properly work on mobile. If even big web companies can't pull that off, is it impossible? (Mainly thinking about Gmail and Google Docs here). Or have we given up on web applications on mobile?

I'd assume that Gapps wanted native for the same reason FB did: more access to details on the device directly

Re: Photoshop’s journey to the web

#47

WebAssembly is coming for games next. Near native performance, players can join with just a link, and no 30% cut that developers have to deal with.

It's pretty clear you haven't worked in that industry. Per your logic, no one should have that issue now, you can sell your games on your own site without issue (in fact you can sell your own Steam keys without the 30% fee).

Re: Photoshop’s journey to the web

#48
post #25
post #13

Only Chromium/Blink browsers are supported, so no Firefox or Safari. This is bad for the web.

Two very underfunded teams there trying to play catch up. Only one of them has an excuse though, the other is literally the most profitable company in the world who is strategically trying to make the web into a subpar platform for their own commercial interests.

Seeing Firefox teams callous take on a critically important Native file system feature [1], it comes at no surprise that major products are dropping Firefox compatibility.

[1] https://github.com/mozilla/standards-positions/issues/154

Re: Photoshop’s journey to the web

#49
I'm not at all looking forward the future where "conveniences" provided by operating systems (like consistent GUI styling, preferences, accessibility, etc) are thrown by the wayside and each application effectively re-implements a GUI targeting a canvas "framebuffer".

Re: Photoshop’s journey to the web

#50
post #28
post #25

Earlier quoted context omitted.

Two very underfunded teams there trying to play catch up. Only one of them has an excuse though, the other is literally the most profitable company in the world who is strategically trying to make the web into a subpar platform for their own commercial interests.

I'd like to support Firefox with a donation as I'm sure many others would, but I don't trust Mozilla foundation to allocate it to something that actually matters.

I do trust the foundation and make a monthly donation, but those donations are not used for Firefox, and I'm not even sure they legally could be the way the foundation is structured. I too would really, really, really like a way to fund Firefox development. I don't use any of the features they make money from (search partnerships, sponsored suggestions, Pocket), and if I'm forced to I will stop using Firefox.

I don't understand why they can't do a pay-what-you-want model. Keep the browser free, but encourage people to pay $20 or something if they like it. I would.

Post reply on HN