4 ms·
After using Photopea (web) as a virtually full replacement for Photoshop (desktop), I'm starting to think that these days, all interfaces and business logic sho
by crazygringo 7y ago
After using Photopea (web) as a virtually full replacement for Photoshop (desktop), I'm starting to think that these days, all interfaces and business logic should be web-first. JavaScript is fast, other languages can compile to it or WebAssembly, and HTML+CSS is a lingua franca. Obviously PWA's are required, designed to run offline.
Where brute-force performance is a #1 concern I think it diverges. For things like Photoshop filters or rendering, WebAssembly may still be fine (it depends). But for real-time processing that needs timing guarantees or more direct access to hardware (games, DSP, etc.) the code has to be native running in dedicated threads. Still, it would be nice if those operated essentially as native browser plug-ins that still interfaced with a browser environment, rather than a totally separate executable.
I'm seriously ready to let my web browser just be the GUI to my operating system. I want my file manager and terminal and system preferences just to be tabs next to my Gmail and Docs.
- heyoni 7y agoSpeed in relative terms means that JavaScript in the browser is not fast. The language runs on top of just about as many abstraction layers as possible and I do not envy this world you describe. I wish we’d move away from it.
- crazygringo 7y agoBut it's fast enough. JIT compilation means algorithms run decently fast, and when it deals with the DOM it's fast enough for everyday interface tasks. Nobody's saying it's elegant. But it's cross-platform and it's a standard that lots of people know. Wishing we move away from it seems like a lost battle at this point -- at least unless we somehow invent a brand-new computing paradigm that replaces browsers, the way browsers have replaced apps in many cases. But I can't even imagine what that might ever be.
- heyoni 7y agoIt’s not though. Not even close. And I know this partially a matter of taste but I have one of the fastest computers you can buy and I can’t even participate in text chats without input lag and delays in interaction. It’s not a good user experience for me at least but that’s ok, we’ll keep stacking more cpu power until it’s all in the cloud anyways.
- crazygringo 7y agoThat just sounds like server latency to me or some kind of bad programming like relying on polling. Obviously if you build a chat client in the browser and communicate between windows then it's instantaneous. Faster than human perception. Certainly doesn't seem to be a CPU issue to me. I mean, we run videochat in the browser which works fine. Obviously text chat can be instant.
- heyoni 7y agoI’m talking about the native slack app. I used to use the irc gateway and now go back and forth between desktop and unofficial gateways. I use keyboard shortcuts to navigate between chat windows and nothing about it is instantaneous...even when there’s nothing but text. Same thing applies to discord, and less so with WhatsApp and signal. Messages on the other hand is silky smooth, and terminal irc couldn’t get any faster.
- jfkebwjsbx 7y agoYou run hardware accelerated video, or in some cases SIMD hand-tuned native codecs. That is in the opposite side of where the abstraction that the web provides is.