Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rx v0.3 Released, a modern and minimalist pixel editor in Rust

rx.cloudhead.io

Post reply on HN
Print view View original

61–69 of 69 posts

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#61

Post by newnewpdro »

swsieber wrote: post #59
newnewpdro wrote: post #18

Vulkan 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 .

Correct. When I enumerate the other alternatives, there's no single backend that is free from a fatal flaw. 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…

> SDL - can it drive 4K displays?

What is this FUD nonsense?

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#62

Post by TeMPOraL »

cloudhead wrote: post #53
dang wrote: post #51

Discussed 3 months ago: https://news.ycombinator.com/item?id=21113796

Are new major releases with new content not okay to be posted?

It's OK. Unnecessarily repeated submissions get marked as dupes. But if something like this was on HN previously, it's nice to have a link to previous discussions, for context.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#64

Post by fnord123 »

tomashubelbauer wrote: post #15
fnord123 wrote: post #12

Earlier quoted context omitted.

https://github.com/rxRust/rxRust Many Rust projects are blah-rs where the rs is dropped in the crate name. So it would be normal to be confused and think Rx == RxRust. e.g. https://github.com/rust-lang/futures-rs has crate name "futures". >There's not that many good, short names. There'd be loads if the Rust community (or.. the 'rust parliamentary community' (people who actually get involved in the RFC processes and…

Namespaces are a good idea on paper, but you still need to secure the non namespaced name when you reach a bit of popularity or someone else will who will push malware there knowing people will often add a crate by the name they think it has and not necessarily the one it has.

Non namespaced crates can be io.cargo.blah and the short name can be deprecated or even changed programatically.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#65

Post by fnord123 »

HelloNurse wrote: post #35
tomashubelbauer wrote: post #5

Earlier quoted context omitted.

There's a very little overlap between the purpose and use case of the two projects. There's not that many good, short names. I personally wouldn't worry about naming conflicts with another project, unless it was a similar project in more than a name.

Short names are bad, unless somewhat sheltered from confusion (e.g. brief names of command line tools, which need to be unique only within your PATH environment variable and your installed man pages, not on the web).

Absolutely. And even ls, sed, etc are in the coreutils package. Not 'ls' package.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#66

Post by shmerl »

cloudhead wrote: post #38
shmerl wrote: post #31

> On macOS, Metal support is required. Is it using MoltenVK?

Nope, uses Metal directly through the gfx-rs backend.

I see, thanks! What's the preferable approach in Rust, to use Vulkano or gfx-rs (in case you don't need to care about Metal)?

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#67

Post by cloudhead »

shmerl wrote: post #66
cloudhead wrote: post #38

Earlier quoted context omitted.

Nope, uses Metal directly through the gfx-rs backend.

I see, thanks! What's the preferable approach in Rust, to use Vulkano or gfx-rs (in case you don't need to care about Metal)?

For working directly with Vulkan, ‘ash’ is preferred. If you want to abstract over platforms, then gfx-rs is solid, or wgpu for a higher level api. Vulkano hasn’t really delivered on its promise unfortunately.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#68

Post by baq »

gdxhyrd wrote: post #46
baq wrote: post #28

Earlier 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).

maybe i'd agree with you if i hadn't had exactly such monitors attached to my box.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#69

Post by gdxhyrd »

baq wrote: post #68
gdxhyrd wrote: post #46

Earlier quoted context omitted.

No. VRR (GSync) does not do anything if your computer can achieve 144Hz (which for a text editor any computer should).

maybe i'd agree with you if i hadn't had exactly such monitors attached to my box.

You are seeing the benefits of 144 Hz, not of VRR.
Post reply on HN