[wolframhempel]

Blender, in my view, is one of the best arguments to develop native desktop applications over web view wrappers like Electron. Everything is responsive and instant, you can open new 3D view windows by just sliding them open at 60 frames a second, performance is stable even with multiple windows open and the download size is a reasonable 334MB.

[aurareturn]

>Blender, in my view, is one of the best arguments to develop native desktop applications over web view wrappers like Electron.

Different class of products.

For Electron apps, often it's the choice of having a desktop app or not having one at all.

[daemin]

I would prefer they do not make an electron app and just have people use the web-app contained in a browser like it was meant to be.

[aurareturn]

So don't download the desktop electron app? What's the problem?

[daemin]

Web versions don't work with all browsers, they also want you to use the app, and heavily promote using the app, even though the app is just a web page in a browser that's not your browser.

If they want you to use an installed app then they should just build a native app that can be installed.

[zztop44]

But what’s stopping you just using the web page (in a browser that it works with)? Yes, they want you to use the app, but you can still do what you want.

[swiftcoder]

There is usually critical missing functionality from the web version (mostly around native filesystem access). Also, most sites that offer an Electron app paster annoying banners advertising this fact across their web version...

[daemin]

I have done that in the past, though it was more that certain features were just broken in a browser rather than the whole website not working.

If I needed to run another entire browser just for this website I wouldn't bother.

[McDyver]

In my opinion, the actual problem is the focus on making everything web first.

> For Electron apps, often it's the choice of having a desktop app or not having one at all.

Maybe it would be better to have none at all. Having an electron app is an excuse to say "we already have a desktop app, so we won't make a native one".

[flohofwoe]

The reason why Electron has won is because native platforms couldn't be arsed to agree on a standardized native UI framework integrated into the platforms (and not just Microsoft, Apple and Google (via Android), but also 'Linux on the desktop' which is still the same fragmented mess as it ever was (arguably worse after Wayland will replace X11 any moment now).

Electron's success is strictly to blame on the desktop platform owners/maintainers dropping the ball, consistently and repeatedly for the last 3 decades (Microsoft's UI framework 'evolution' is especially hilarious, who in their right mind would write an application against a widget library that's going to be deprecated in 3 years).

[aurareturn]

  In my opinion, the actual problem is the focus on making everything web first.

I don't think this is a problem. Many class of products require a web version over a desktop one. The desktop one is a very nice bonus.

[rounce]

I wonder if this relationship will invert as wasm and web guy and their tooling matures, to the point where these types of applications where drawing performance is a must are being targeted desktop first and then thrown through a OSFA wasmification step to run on the web.

[flohofwoe]

It notably doesn't use any 'standard' UI framework though, which is frowned upon by some people just as much as using Electron (but for different reasons - usually missing accessibility features and not looking consistent with 'system applications').

[jbggs]

I think that's the smoking gun for why most UIs are terrible. it is definitely cheaper to use a framework, but maybe, sometimes, doing something yourself (for 25+) years is worth it

[bzzzt]

As if there's still a consistent option. It doesn't matter if you use Microsoft, Apple or an OSS desktop: all offer multiple UI toolkit options with varying amounts of consistency, maturity and hardware support.

[InDubioProRubio]

Should be separated out and reused by many Electron apps in my opinion

[flohofwoe]

To bear clear, Blender is not an Electron app (reading my comment again it could be read as such I guess). Blender is a native application sitting directly on the operating system's 3D API and window system (with the UI being rendered through the 3D API, not through operating system widgets).

[exe34]

it could probably work well under webgl...

[swiftcoder]

The WebGL API is sadly two decades behind state-of-the-art for modern rendering, and even the will-be-ready-for-adoption-any-day-now WebGPU spec is ~5 years behind.

Between that and the overhead of running the whole thing in WASM+Javascript, I don't think we'll see a pro-level DCC tool running on the web anytime soon.

[KeplerBoy]

It's not html/css/js though.

[cultofmetatron]

> and the download size is a reasonable 334MB.

I remember when it was 2 MB!!

[ideasman42]

I remember downloading it from my library on a floppy disk (hoping the librarian wouldn't hear it the floppy drive working - since it wasn't allowed). :)

It's in fact still quite small if additional 3rd party libraries are disabled.

It's possible to make a much smaller download that removes OpenCollada, FFMPEG, OpenEXR, OpenImageDenoise, OpenVDB ... etc. However it's a hassle to distribute a second version at a time when the current size is manageable for most users.

[lucsky]

How in the everlasting love of rollerblading Jesus is a post about a new version of Blender devolving into a squillionth bullshit nonsensical rant about how boo-fucking-whoo Electron is so bad. My mind is blown. You guys are absolutely exhausting.

[cageface]

Of course there are still categories of app that should be native. That doesn’t mean there isn’t a place for things like Tauri and Electron too.

[lukan]

Electron apps can be very responsive as well. But a 3D designer is definitely in the category of needing all the performance you can get. So yes, native makes sense here.

[raincole]

3D DCCs are very different from todo lists.

[geenat]

It's not a web view

[flohofwoe]

That's what the parent is saying, I also had to read twice though ;)

[demarq]

Please check out plasticity, this “electron bad” argument is pretty outdated and never evidenced. There is absolutely nothing that says browsers can’t do 60fps with multiple 3d views.

[divan]

"electron bad" argument will always be valid. I wish people could "see" what actually happens in the app they running. Electron is essentially a hidden browser that runs a web app.

It doesn't matter if it can or can not do 60fps. Installing yet another copy of the browser just to run that small web app is just wrong.

[aniviacat]

I assume most people who dislike Electron dislike Tauri too, even though it doesn't need to ship a browser.

[flohofwoe]

There definitely are a couple of annoying details. For instance visual mouse lag (when dragging items around) in WebGL and WebGPU can be higher than in a well written native application (just one or two additional frames of latency make a huge difference). Then there's WebGL2 being stuck on a GPU feature set from ca 2 decades ago, and WebGPU starting at a feature set from about a decade ago (and not being quite ready yet anyway).

Then there's also annoying differences between browsers when capturing the mouse - which is needed for camera controls (all browsers show some sort of popup while the mouse is captured, with Safari even shifting the canvas around).

TL;DR: it's possible in theory, but can be very annoying when actually trying to do it, mostly because most web APIs are badly designed (WebGL2 and WebGPU are notable exceptions, but they still lag far behind native 3D APIs).