Rx v0.3 Released, a modern and minimalist pixel editor in Rust
51–60 of 69 posts
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#52Earlier quoted context omitted.
It's not strictly necessary, I chose wgpu for a few reasons: * Its backend (gfx-rs) is one of the most mature rust libraries for doing graphics * The popular "classic" 2d libraries like cairo and skia are very big and complicated to build / depend on * wgpu will eventually also work on the web, so it's a great option for broad platform compatibility * In terms of efficiency (memory, battery, cpu etc.), the modern gra…
> The popular "classic" 2d libraries like cairo and skia are very big and complicated to build / depend on It may be harder than editing a Cargo file, but it is something you do once. They are some of the most mature and tested libraries in the world. > wgpu will eventually also work on the web, so it's a great option for broad platform compatibility OpenGL works everywhere today, including the web! > In terms of eff…
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#53Discussed 3 months ago: https://news.ycombinator.com/item?id=21113796
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#54Anyone know how it compares to Aseprite?
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#55Earlier quoted context omitted.
Text editors on 144 FPS gsync monitor are noticeably better than vsync 60 FPS in a way in which a BMW door is noticeably better at closing than entry level cars. Technically both work the same and yet you can tell they’re very different.
No. VRR (GSync) does not do anything if your computer can achieve 144Hz (which for a text editor any computer should).
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#56Earlier quoted context omitted.
> The popular "classic" 2d libraries like cairo and skia are very big and complicated to build / depend on It may be harder than editing a Cargo file, but it is something you do once. They are some of the most mature and tested libraries in the world. > wgpu will eventually also work on the web, so it's a great option for broad platform compatibility OpenGL works everywhere today, including the web! > In terms of eff…
Downvoter: please explain the reason.
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#57Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#58Anyone else concerned by the decidedly negative cast of the comments? Someone shares something interesting and OP gets a barrage of nit-picky commentary; it's quite discouraging.
>Someone shares something interesting and OP gets a barrage of nit-picky commentary everyone on hn is of the belief about themselves that they're dispassionate (objective) intellectuals and so of course their criticisms aren't in bad faith. and moderators never address these kinds of comments but do often address comments like yours because they incite "flame wars" (since dispassionate intellectuals can be quite defe…
So ridiculous that I didn't even feel it deserved a response.
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#59Vulkan support required for a pixel editor? So I can't run this on my X220 despite having a dual-core 2.8Ghz i7 processor, since its integrated GPU is a generation just shy of having Vulkan support. A pixel editor .
SDL - can it drive 4K displays?
OpenGL - a shattered ecosystem, with some implementations being out of date (Windows) or significantly different (ARM + OpenGL ES)
DX11 - windows only
The only real alternative would seem to be duplicating logic by implementing it for multiple backends.
------
IIUC, the author is using a library that will eventually have OpenGL supported as a backend, so I don't think your predicament is forever, assuming that you actually want to use it and aren't just complaining to complain.
Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust
#60Earlier quoted context omitted.
I disagree with the direction of this criticism. Building and shipping is the real victory for anyone with a passion project. To cut them down because of the project name is a cheap critique in my view. Besides, given the extreme signal:noise ratio of codebases that gain notoriety most projects that share a name or acronym will only have a handful of users even aware of both's existence.
Well, it's a mistake. Due diligence, for any new project, requires searching for existing uses of the intended names and deciding whether they are confusing. It's difficult because it's easy to miss obscure social niches and name variants, and that's why most people make the task easier with an effort to find unique names. For example, a sloppy google search for "Rx" yields, in search result order: - two medical abbr…