Skip to main content

两款绘图软件比较 Gimp vs Krita

配好了绘图板之后,手一直痒痒的。 之前看着Photoshop绘图教程,在Painter上作画,感觉还不错。 但是一直是想转移到Linux下面来的,指示软件硬件一直都没有配好。现在硬件好了,还是看软件。

首先得说一下我的情况,这代表我的立场。我主要应用是徒手作画,图像处理方面则不怎么要求。 我常用的工具就是画笔,喷枪和涂抹。 另外我当然希望软件对绘图板能够很好得支持, 事实上我对Painter对绘图板的支持不是非常的满意,我的手写板最近才更新了一次Vista驱动,修正了若干bug,包括lag。

两个软件我都就自己的需要尝试了一下,版本为
Gimp 2.4.6
Krita 2.0a6

那么分别说一下各自的优缺点吧

Gimp:
优点:支持文件格式多,工具多
缺点:总觉得界面不够友好

Krita:
优点:绘图板响应虽然有点慢,但是出来的线条非常好看,比如Pixel Brush
缺点:适合手绘的工具较少,也没有我喜欢的三角形+环形的颜色拾取器。 使用RGB模板经常Crash

当然了也很有可能我对软件的挖掘还不够。 目前暂时考虑用Gimp画一幅试试看。

Comments

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...