neon VS musikcube

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

Nord theme for Musickube

Turns out someone already made an issue about this upstream, and even made a working ebuild, although it was published to his/her overlay which is not listed on overlays.gentoo.org yet sadly. If you're curious what was wrong and how it was fixed: the github issue

If it's just for music and you dig the look of TUI apps then musikcube has built-in server functionality. You install it on both the server and clients but keep the library on the server. It's light and works well, including for giant collections. There's apparently an android app too, musikdroid, but I haven't tried it. I haven't tried the windows or mac client apps either, so I can't vouch for any of them, but it's great on linux.

VLC can be used to play a file from the command line, but there is no user interface. Players like cmus and musikcube have a text based interface and library management.

Well, there's Musikcube. I think it's a solid choice over cmus.

music player: musikcube

Dont know about the rest but the top left music player looks like musikcube with a skin on it. https://musikcube.com/

I use https://github.com/clangen/musikcube on a daily basis

Musikcube, a cross-platform, terminal-based library, player and server\ (16 comments)