Building on top of a framework that bundles a Chromium should result in a smaller application than building on top of a framework that bundles a WebKit. As an example, compare Vivaldi (Chromium) and Orion (WebKit).
Chromium has many more batteries included though, such as V8/Node.
I believe the right term here is WebView, which will use the OS's native browser framework to display the app. For Windows this would be Microsoft Edge WebView2 and for Linux webkit2gtk. I do believe Qt WebEngine (or Qt WebView) might be the better option for Linux though, although I'm guessing webkit2gtk is being used because of more readily available Go bindings.
You’re wrong in your belief. We all know what a WebView is, but what is being discussed is bundling WebKit vs. bundling Chromium (like Electron does). A solution that bundles only a WebKit engine would be smaller than one that bundles a Chromium. What is your objection, specifically?
To me, the thing that brings me back to Krita over and over is that fact that it's intuitive to use. I've been trying to use GIMP for the past 10 years and still have no idea how to resize an image/canvas or where the heck the crop tool is. In Krita those things are exactly where I end up looking for them.
Wife still uses Photoshop CS 2 on Windows, and I've basically told her that when her computer dies, she's getting Linux and open source software, or she's gonna have to figure out Windows 11 by herself and pay the subscription for Adobe. "Fine with Linux" she says, since it's installed on other computers in the house, "... but what can I use instead of Photoshop?". "Use Gimp, of course!" I say, and install it on her computer. Then I watch her get increasingly frustrated for an hour before rage quitting. It's not lack of features, it's UI, UX, workflow.
There are a lot of paths that are unique to each of them. I bet the reverse (from Gimp to PS) feels the same. My wife asked to make a logo and a leaflet, and I never offered other thing than Inkscape. She ended up using it for almost anything. After a couple of years I bet that she will find Illustrator frustrating.
The difference is that after a week of serious Photoshop training you will have at your fingertips a world class, incredibly powerful piece of software with modern ML tools for smart image manipulation, collaborative tools and cloud infrastructure for syncing documents, plus a massive ecosystem of plugins and assets available to purchase.
I say this as someone who strongly dislikes Photoshop. I wish I had a viable alternative.
You'd better test if her Photoshop works fine with Wine. If it does, nobody get frustrated, there is no need for her to relearn everything from scratch if she is satisfied with that tool and her workflow established over more than 10 years, and you don't have to pay for a new tool.
It does! Some very minor UI issues but very usable. Actually, I've got an old trial version of Photoshop CS6 (I think? Whichever was the last version they released as locally installable) and it also seems to work on Wine. But you can't buy that any more :(
You can run older versions of Photoshop (CS2 is almost certainly old enough) surprisingly well in wine. If she doesn’t like something like Krita, I’d try installing the exact version of photoshop she’s used to under wine.
Seriously? I can understand people having trouble adapting to a different layering model, but cropping? If over 10 years you haven't been able to figure out
Image -> Crop to selection
then either it's a real accomplishment they you can cloth yourself in the morning, or this is just willful ignorance.
Maybe Gimp has one of the worst UI/UX ever made? I still stand by my theory that gimp was made as a troll program to see how far people will defend opensource no matter how objectively bad it is to use.
As somebody who uses Photoshop for a living, I prefer the GIMP. The GIMP falls down on a few major features, not on usability. I can also see how Photoshop as the standard has broken people's brains so much that the concept of "intuitive" becomes entirely lost. It's not as bad as Illustrator, but features are just randomly thrown everywhere; the only reason I'm fast at it is from hard-won experience.
It's impossible to paint "Image -> Crop to Selection" as hard to find. The menu is at the same place it is in almost every other program one uses, at the top of the window.
I've never used Photoshop and gimp confuses the hell out of me. I installed krita a year ago for my simple editing tasks and never once had to search online for 'how do I....'
I've used all three, and the amount of searching from least to most goes Krita -> PS -> GIMP for me.
PS was the first I used, but I still had to search things for the entire time I used it. GIMP I just start by looking up how to do something, and Krita I just do it.
As someone who never used Photoshop before I find Gimp's UI functional and nothing worth complaining about. Especially I like the MDI interface with each widget being a seperate window.
It's been a long time, but when I was in high school I chose to use the GIMP rather than Photoshop for my photo class, which was the first time I used any photo editing software. I found it to be more or less fine.
There's exactly one thing I still prefer to do in Gimp - splitting a single image into multiple images, one per RGBA/HSL channel. There's also some image formats that Gimp supports that Krita does not. But that's it. There's nothing else I miss, and Krita is just incredibly far ahead on usability.
They fixed a font size bug that made it inconsistent between computers, but did they change the user interface for font styling? It's the second that makes it annoying - I never got far enough to notice the bug.
It depends gimp have more photo editing features but is a mess, and krita is more of painting app who have features of photo editing( more than not professionals tends to need)
I think the only real advantage of GIMP at this point is its age and stability. Gimp was around 20 years ago and it is more likely to be there 20 years from now than Krita. EDIT: my error - Krita is much older than I thought.
Moreover stability is important if you access it programmatically.
And yes, even that is not guaranteed by any means. It's just the area where Krita does not beat Gimp totally.
Krita was started in the previous millenium, too. I've been Krita's maintainer since 2004... If I have to think about what I did with my life, https://krita.org/en/about/krita-releases-overview/ comes to mind :-)
Just read this guy's vita. An entire long life of profit-oriented road rage, always using the law and presumably his connections to go after like everyone else for minor copyright and similar offenses, striving to make this planet a more miserable place for everyone else while raking in for himself. At almost 90 yo he finally got convicted for fraud and rather killed himself instead of going to jail. Not even his high-falutin name is all that real. At some point he tried to get courts deny people the right to even mention the fact that he was not born as a Von And Zu. Christ what an asshole.
I've never been able to do anything meaningful in GIMP, but Krita is relatively nice to use. It's much more intuitive than GIMP, and even things you have to look up and learn are easier to get used to and remember, because the UI actually makes sense.
This. I honestly love the f-string syntax but the fact that there is a clear separation is what makes them appealing - I find it far more convenient to have f"{v1}, {v2}, ... {vN}" vs "{v1}, {v2}, ... {vN}".format(v1, v2, ... vN), not to mention % v1, v2, ... vN.
The way I see it, currently:
* The separation makes them readable and easy to understand.
* Making them implicit will cause hell for many people who rely on user input (and I'm certain a lot would try to exploit that).
* The fact that they are readable, makes them easier to debug, as opposed to trying to figure out where did the "{hey ma look at what i can do}" SyntaxError came and who did what exactly.
Apples to oranges, really. Cockroach presents a single database view that happens to be sharded and replicated in a fault-tolerant, consistent way. ActorDB doesn't.
With ActorDB you have to design your data model to shard at a high level. For example, you could shard it by user; every user would have its own database that ActorDB will shard and replicate for you. That database is for the most part separate from everything else -- it has its own tables and indexes.
ActorDB provides tools to operate on multiple actors, but they're explicit. For example, you can query across multiple actors, but this requires a small SQL declaration at the beginning of the query to select which actors to query, a bit like a "for each <actors> do <some SQL>".
You can also do transactions across multiple actors, though this uses two-phase commit (which coincidentally is the strategy used by Google Spanner), and requires some locking.
So Cockroach pretends to be a classic RDBMS (databases have tables and indexes, but most apps just use a single database per app), allowing an existing app to be ported with little effort. It would be harder to port an app to ActorDB.
Or more like, how does this compare to any database that runs in production with non-trivial scale and load in a company. Does this database add anything to the data storage landscape that is worth to note? I am not sure. There are pretty good and reliable databases out there.
> Lightsail uses burstable performance instances that provide a baseline level of CPU performance with the additional ability to burst above the baseline.
Mostly because it has an "ignore comments" mode. A lot of non-English speaking programmers write code using English keywords and identifiers but use their native language in the comments.
With some work, it could be made language-agnostic, but that's more than I have time for right now. If comments aren't an issue, you can just grep through all your source files for the offending characters, which shouldn't take more than a simple bash script.
Edit: it looks like it leverages its own Webkit for the frontend, but then how is this more efficient than Electron ?