Why would I want an extra gigabyte of memory usage for no benefit?
13.10651926269692
Ok, Thirteen it is.
1. Because clicking a link is quicker than `apt-get install krita`
2. Because clicking a link is quicker than: "E: Package 'krita' has no installation candidate"
3. Because clicking a link is quicker than `aptitude search krita`, seeing krita data files, but still no krita
4. Because I apparently have to open up a browser and type "Debian krita" to figure out how to install krita, so I might as well just run it in my browser
5. Because when it crashes in Chrome it's less likely to be a security risk
6. Because, unlike Linux distros, browsers have standardized on this system called a "link" to install new apps
7. Because I can run the program on someone else's machine without having administrator rights
8. Because I can run the program on someone else's machine without installing stuff to their user directory
9. Because I could probably even try it out on a kiosk where I have no rights at all (weak, I know)
10. Because, unlike Linux distros, browsers vendors as disparate as Mozilla and Microsoft were able to agree that clicking an "x" is the way to uninstall krita-in-the-browser
11. Because the web has at least two high-quality natural language search engines that I could use to discover this hypothetical krita-running-in-a-browser and they don't error out if I have typos
12. Because if I wanted to study how the GUI works I click a shortcut and an entire development environment inflates like a life raft on my machine, or someone else's machine, or any machine that runs a modern browser.
13. Because I could have spent this time using krita instead of writing thirteen fairly obvious reasons why clicking a link is preferable to screwing around in whichever Linux cult I happen to be stuck inside at the moment
In any case, as soon as Qt (with support for threading), eigen3, exiv2, fftw3, expat, fontconfig, freetype, gmic, gsl, iconv, ilmbase, libjpeg, lcms2, libraw, opencolorio, openexr, libpng, poppler, pyqt, python, sip, libtiff, vc and zlib can be built using one of the compile-to-javascript whatevers, we can take a look.
I expect it'll be some time...
given the scope of the software, I fairly doubt so. Installing it and running it in less time than it takes for some web pages to load :
sudo pacman -S krita --noconfirm 2,00s user 0,17s system 80% cpu 2,686 total
and even then it's entirely broken because people making web UI cannot fathom why I would, as an user, be able to customize fonts of my system : https://imgur.com/a/kqZGT
Do you do all your programming work inside a browser window?
I want native performance and native code, not a javascript bloat as a service.
Someone mentioned the lack of web API for stylus, which is a huge gap right now. I expect that gap will be filled sooner or later. Indeed with WebUSB it should be possible to implement drivers for the plug-in Wacom style devices for the web right now. Since getting these two great devices I haven't plugged in my Wacom once though.
The lack of a really good vector app for Android (like Autodesk Graphic for iOS) is what made me curious to check out these comments and see what Krita is about.
Yes the web has extra overheads, but it is the cross platform runtime with the broadest reach.