gtk4-rs VS neon

The only example that shedded some light on the integration was gtk4 + femtovg. So I mimicked the example, using gtk4-rs and Skia's rust bindings. I had some code similar to the following inside a subclass of GLArea to setup Skia's DirectContext, but it failed:

Hi, I am studying gtk4 with rust, now trying to check examples from https://github.com/gtk-rs/gtk4-rs/tree/master/examples some of them are building and compiling but text_viewer(cargo run --bin text_viewer) and some others are failing with the error below

I created a demo of using column view in gtk4-rs rust here...maybe be a point of reference https://github.com/gtk-rs/gtk4-rs/tree/master/examples/column_view_datagrid

To build the UI, I used gtk-rs. My experience with this library was quite pleasant; it was easy to use and there were a lot of examples. However, it isn't as widely used as, say, React, so it was difficult to find answer on Stack Overflow (I come from a JavaScript/Typescript background).

There are good GTK bindings for Rust (https://github.com/gtk-rs/gtk4-rs and https://github.com/Relm4/Relm4)

I've been following this example to get something that works for whatever the default opengl context version is, however, I can't figure out how to request a specific opengl version on context creation: https://github.com/gtk-rs/gtk4-rs/tree/master/examples/glium_gl_area

gtk4-rs itself feels like it takes very little time to build: https://github.com/gtk-rs/gtk4-rs but when you add up all the time to building all examples afterwards, it's about the same and provides the equivalent of capabilities of QT(C++ and RUST) so yes it's going to take time to build.

The gtk-rs project provides safe Rust bindings for GNOME stack-based libraries, like the GTK 3 and GTK 4 libraries. The gtk3-rs and gtk4-rs libraries provides GTK 3 and GTK 4 functionalities, respectively.

Check out the examples in the gtk4-rs repository.

If you're reading this you probably got a really steep bill from Neon after finding yourself on their "Scale" plan. If you do want to stay with Neon but avoid surprise bills then go to the Plans page and choose what you actually want.

Such is the case with Neon, a serverless Postgres service, that went generally available on April 15. Congrats Nikita Shamgunov and team on the launch. When I saw the announcement, I knew I had to try it out for myself and report back with my findings.

I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:

https://github.com/neondatabase/neon/issues/4989

If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.

Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.

To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?

Neon is an open source and cloud-native serverless database platform that focuses on simplicity and ease of use. It supports Postgres databases and offers built-in features like bottomless storage, autoscaling, and branching.

For MySQL, we've got PlanetScale, and for PostgreSQL, there's Neon.

8. https://neon.tech/As you might know not one tool fits all, I still have strong preferences for the following. It helps me get going faster and get things done right first time and helps in ease of maintenance.

Language: Typescript.

Migrated away when they removed the free tier, ended up using https://neon.tech/

Cool! At Neon[0], I work full time on our custom postgres proxy[1]. It's a very nice protocol to work with, although our usecase is quite a bit more complex compared to the ideas presented in the post.

Neon databases scale to zero, so the proxy needs to spin up databases on the fly. The proxy doesn't do that but it knows if the databases is running and asks our control plane to schedule it if it isn't. It's a fun service to maintain.

The biggest pain is error handling. Postgres is really bad for error messages and codes. The only available code we can use is usually protocol violation...

[0]: https://neon.tech/

Neon - PostgreSQL