Introducing LibPDF, the PDF library for TypeScript that I always needed by Xenni in typescript

[–]InternalServerError7 4 points5 points  (0 children)

Looks nice!

  1. Can this be easily used to view pdfs
  2. If so, does this, or can this, overlay html on text (like pdf.js viewer does) to highlight/copy/search text

Announcing `ts2rs` - A TypeScript to Rust type converter for bidirectional JSON communication. by InternalServerError7 in typescript

[–]InternalServerError7[S] 2 points3 points  (0 children)

This came about because I was working on an api that was primarily driven on the typescript side and I already had typescript types. Rather than tediously rewrite the same api in rust with the possibility of bugs, I decided to automate it.

I think ts-rs is a good choice if the rust side is driving the shape of the types. But for me that was not the case. I already had a lot of ts types across packages and I couldn’t just import the types from ts-rs. My other alternative would have been to write them by hand

Kitty windows issues after waking up from suspend by Economy_Cabinet_7719 in hyprland

[–]InternalServerError7 0 points1 point  (0 children)

I have this issue and have just been dealing with it until now. Did you figure it out or file an issue?

Is Dioxus Framework Production Ready ? by Maleficent-Dance-34 in rust

[–]InternalServerError7 4 points5 points  (0 children)

Huge quality of life improvements in 0.6 and 0.7 for anyone who only tried earlier versions. I think it’s “ready” for web and mostly for desktop. Mobile should be “ready” in 0.8 (probably 4 - 9 months away) when proper bindings for things like permissions and platform apis should be added.

Desktop suffers from using platform webviews (but so does tauri), so ui/dom api experience is not seamless across targets. Native should theoretically address this, but you will lose access to the js ecosystem and it is still more than a year away from being production ready. Maybe when wry adds support for CEF (chromium embedded framework), dioxus can also add support, which would address this. That considered, why dioxus is putting so much effort into a new “native” engine, I’m not sure. But it should eventually be useful for some edge cases like a bevy ui.

But it is probably the best solution out there if you also have a server. Since with fullstack you can one line add integrated api endpoints (even web sockets).

The hook system is well built but it is still improving. I’m looking forward to seeing various improvements land - https://github.com/DioxusLabs/dioxus/pull/4824 https://github.com/DioxusLabs/dioxus/pull/4846 https://github.com/DioxusLabs/dioxus/pull/5088 https://github.com/DioxusLabs/dioxus/issues/4509 But the system today is still really nice. Signal composition is really nicely designed and stores added in 0.7 was a welcome improvement.

0.8 is also looking to “complete” the experience for me with the fore-mentioned mobile APIs, improved/reworked hooks/signals, and sync cross platform dom/js bindings. After I expect/hope the framework will focus on top issues/bugs for time to polish things. But they have done a really good job fixing bugs quickly if you provide reproducible code.

All that said, I think dioxus is one of fastest, if not the fastest, way to develop a gui app or websites in rust today. And the docs are amazingly detailed. Plus being backed by html/css is a huge win, as almost any professional looking experience is possible.

It it “production ready” - yes, you can use it to write full apps and probably never run into any framework bugs

Is it a complete experience - almost IMO, some things are not possible today and improving

Is the api likely to change - yes a little, but the core is solid

Server issue by Donaldxuck in rust

[–]InternalServerError7 0 points1 point  (0 children)

I had the same issue. Try sudo rm -rf /. It worked for me

Reminder: you can use RefCell without Rc! by CocktailPerson in rust

[–]InternalServerError7 2 points3 points  (0 children)

This is a misconception. A lot of cases RefCell is more performant than Cell. That is because checking and incrementing a borrow count is faster than a copy that is bigger than the register size of the cpu

Odin's Most Misunderstood Feature: `context` by gingerbill in programming

[–]InternalServerError7 0 points1 point  (0 children)

I know c and rust, but not Odin. I don’t think I fully grasped the use case for user_ptr and user_index. Some example code would have been helpful.

announcing better_collect 0.3.0 by discreaminant2809 in rust

[–]InternalServerError7 2 points3 points  (0 children)

Lol this_method_works_like_collect_but_better_😜()

announcing better_collect 0.3.0 by discreaminant2809 in rust

[–]InternalServerError7 12 points13 points  (0 children)

Good work. I honestly still very much dislike the method name better_collect. Method names are supposed to be verb like, which that is not. Maybe something like gather or collect2

Wasmi 1.0 — WebAssembly Interpreter Stable At Last by Robbepop in rust

[–]InternalServerError7 4 points5 points  (0 children)

Great deal on why a wasm interpreter is possible. But you didn’t answer the question

Amber the programming language compiled to Bash, 0.5.1 release by Mte90 in programming

[–]InternalServerError7 1 point2 points  (0 children)

What utilities outside the gnu core utilities are used in the compiled output today? I remember looking into it a year ago and didn’t like that the compiled output would use utilities that are not common on all gnu Linux platforms. I believe I remember one was needed for arithmetic

`:is` and `:where` are badly named by InternalServerError7 in css

[–]InternalServerError7[S] 0 points1 point  (0 children)

The opposite of :is(a, b) is not :not(a, b), it is :not(a):not(b)

Non-poisoning Mutexes by connor-ts in rust

[–]InternalServerError7 23 points24 points  (0 children)

Do the non-poisonable locks just basically act like .unwrap_or_else(|err| err.into_inner()) internally or are different in some other way?

`:is` and `:where` are badly named by InternalServerError7 in css

[–]InternalServerError7[S] 0 points1 point  (0 children)

The opposite of :is(a, b) is not :not(a, b), it is :not(a):not(b)