1. 75
  1. 52

    This Graphite should not be confused with:

    1. 28


      1. 9

        I’ve always scratched my head at people naming their stuff to set themselves up for increased difficulty in trying to get search engine rankings, as opposed to choosing a relatively unique name or respelling.

        1. 4

          The other end of that is letting your password manager decide the project name.

          1. 4

            …Honestly I should try that sometime. KBbO=D?.53l+q"Q+=UcwD?Ip* has a nice ring to it, and you sure won’t find a duplicate of it on Google… We can call it KBbO or “kibbo” for short.

      2. 15

        Holy crap! This is the first web application in this field that I tried and it actually feels good to use!

        When I read the opening paragraph and saw it was free and open source, my first reaction was crap, I just know this is GTK-based and the Linux version will look nothing like the screenshot because the panes will be three times larger and I’m gonna have to scroll around an 800x600 image like it’s 1997 but nope!

        Also holy crap it’s fast, I’m trying it on a pretty ancient laptop and the UI is literally less laggy than Explorer’s!

        I will never say anything bad about web UIs again probably continue to bitch and moan about web UIs but not as adamantly…

        1. 11

          “non-destructive”? You have my attention.

          I’ve been waiting a long while for GIMP to get non-destructive editing.

          1. 1

            Have you tried Krita?

            1. 2

              Yes, but it’s a bit of a different beast. More for art than image manipulation, it seemed.

              1. 1

                That’s the focus, but the image manipulation basis is better than GIMP. Some specialist features might be missing, but I wouldn’t know.

          2. 8

            This web app feels as responsive as a desktop Inscape. How is this possible?

            1. 14

              Looks like they’ve written substantial parts of it in rust, compiled to WebAssembly (which is well within an order of magnitude of native performance these days).

              Most likely that’s issuing draw commands to a webGL context, in which case the only thing done in javascript is passing resource handles around.

              1. 5

                The buttons etc seem to be legit HTML: https://imgur.com/a/ZU3lK7L

                1. 9

                  Sure, but HTML is more than fast enough when it’s just used to display buttons and report clicks back to a fast backend. That’s just not a bottleneck. After all, how many buttons can you click per frame? 2?

                  Rust has a plethora of libraries aimed at making HTML<->JS<->Rust-Compiled-To-Wasm interactions easy.

            2. 7

              Wow… Simply wow… If it delivers on its promises, this is genuinely impressive. The node graph composing being the killer feature. I’ll test it this weekend. I’m always happy to see momentum in opensource image editors.

              1. 5

                An artist friend of mine had this comment:

                “a node graph but it can just be layers”… yo someone get the Blender Foundation and beat them around the head with this please

                1. 3

                  Somewhere in the ballpark of 7 years ago I was telling a friend that I thought Adobe’s transition from Creative Suite to Creative Cloud was at great risk of further leaning into an Innovator’s Dilemma ~problem of ceding too much room downmarket for challengers to establish themselves in and eventually challenge Adobe’s position as the clear default in this space.

                  What I meant by that is that, as I finished undergrad, I was able to talk myself into spending several hundred dollars on a full copy of Creative Suite at student pricing, even though I only needed access to Photoshop, Illustrator, or InDesign a few times a year. They probably saw this as ~cheating internally, but it meant that I spent the next 8 years (until I stopped using Windows) using CS for any graphics/typesetting work I needed to do and building on my knowledge of it in the process.

                  There’s absolutely no way I could talk myself into shelling out for an open-ended CS subscription that I needed so rarely, and at any given moment the decision to start a monthly subscription would only make financial sense if it was for a paid project.

                  Even without the growing list of strong challengers, I can’t imagine letting it perpetually take up space on my devices anymore. I still use it once in a blue moon, but I install it for a work project, finish, and remove it again.

                  It’s exciting to see another challenger :)