Hacker Newsnew | past | comments | ask | show | jobs | submit | bkovacev's commentslogin

I really like the minimalistic design of the website, but I was disappointed to see Wordpress used. Does anyone know if something similar exists whether free or paid - as long as it's available as plain CSS/HTML?


Fruska gora, a mountain region in Serbia, has acquired or were gifted 5 European bisons from Poland[0]. It's always heartwarming to see a country working extremely hard to preserve any species. It was devastating news for a lot of people that one of the bisons, Djuka, passed away recently (not to be confused with a Serbian politician Vladimir Djukanovic also known as bison Djuka[1]).

[0] https://www.gov.pl/web/srbija/poljski-bizoni-u-nacionalnom-p...

[1] https://en.wikipedia.org/wiki/Vladimir_Đukanović


I'm unsure how have you not stumbled upon RustDesk[0].

[0] - https://github.com/rustdesk/rustdesk


That's neither simple nor really a web-based gateway...


Rustdesk web client is currently in beta testing:

https://rustdesk.com/blog/2024/10/rustdesk-web-client-v2-pre...


Yes, but I need to connect to existing RDP servers. No way I'm going to be able to install anything else.


This comment made my day.


Can you explain further on the performance aspect of Django Ninja vs DRF?


It is built to fully support asynchronous endpoints, and uses pydantic models for validation and parsing - lightweight and nicely fast


What seems to differentiate django-ninja over Flask or FastAPI or any Starlette derivative? You mention lightweight as well, can you expand further?


Ninja lets you use django. There's less config vs DRF


Aside from the obvious that ninja let's you use django.


The ability to use django is the main attractor. The other frameworks are great but make you reinvent Django if you require auth, orm, admin, etc


That would have been my argument exactly - I am not saying that Django fits every use case, but with my limited exposure to projects that have ended up using non-Django Python API framework, they ended up recreating the batteries included approach, with probably way too many issues waiting to be discovered with manually rolled out auth, middlewares and ORM.


It's such a shame Pyramid isn't more popular. I think you'll find what they have recreated is not Django, it's Pyramid.

The thing is, Django isn't just a web framework. Django is a CRUD app framework. It's great for building CRUD apps, but that's about it. In other words, it makes the easy stuff easy, but doesn't help with the hard stuff (in fact, it often hinders it).

I think the real reason for using Django is the "app" ecosystem. You wouldn't be able to get Django-style packages with Pyramid. It's possible with Django, though, because it's a CRUD app framework.

If you're not using "apps" then I guess the only other reason is the community support that you probably won't get from Pyramid + SQLAlchemy or similar.


The apps are a major sell like with any ecosystem. But don't forget you also get a stable, mature project, excellent documentation, a pool of developers, etc.


> But don't forget you also get a stable, mature project, excellent documentation, a pool of developers, etc.

You get all of that with any of Pyramid, Flask, FastAPI etc.

As for "pool of developers", I would expect any backend web developer to be able to pick up anything in a couple of days at most.


> You get all of that with any of Pyramid, Flask, FastAPI etc.

Yes, with fewer batteries, and so less consistency between projects, etc.

> As for "pool of developers", I would expect any backend web developer to be able to pick up anything in a couple of days at most.

Not some half-baked homegrown ORM, etc. Been there, seen it fail.


Oh but you wouldn't reinvent Django, you'd build a properly architected, simple system.


Of course you would.


Care to elaborate further? I keep reading on this, but no one actually mentions anything specific that ninja does better than DRF.


The main benefit most people see right away is the Pydantic integration & it requires less boiler plate for basic API's. Ninja is essentially FastAPI + Django.

I prefer Ninja over DRF, but I know plenty of orgs who still love their class based DRF views as once you are over the (significant) mental hurdle of understanding all the abstraction there, it does give you the common CRUD type operations on your models "for free".


DRF has more abstraction. When I was new to Django I found DRF hard to build a larger API with it and not make mistakes or have things get confusing. You're primarily working by extending classes etc.

With django-ninja you just define your APIs with annotated types as methods, there is no magic, and then you get a generated OpenAPI spec.

this was my experience anyway, I used DRF for this project [0] and ninja for this one [1]

[0] https://govscent.org/api/

[1] https://sidewaysdata.com/api/docs


I haven't used django-ninja but to me it looks like the API is a bit nicer or more 'modern' looking (i.e. declarative via type annotations) and it's faster, both due to being based on Pydantic

DRF is old and API looks more like Django forms or class-based views, more of an OOP hierarchy going on, and DRF serializers are slow


Old is a harsh word, maybe mature would be a better fit, not everything new and shiny is gold, and yet not everything old sucks.

Not arguing here about types and Pydantic being faster than the built in ModelSerializers. However, for serializer speed improvements and performance in DRF I would advise dropping ModelSerializers and either going for Serializers or plain dict. Haki Benita has a beautiful article on that [0]. I was able to accomplish sub 200 response times on a fairly large response from tables that had tens of millions of records.

I think you have no objective reason other than your styling and rather personal preference for function based views?

[0] - https://hakibenita.com/django-rest-framework-slow


I have been building something like this for myself. Is there a room for a paid software, and would you be willing to pay for something like that?


IMO there is only a B2B market for this kind of thing.

I’ve heard of a few very large companies using glean (https://www.glean.com/)

This is the route I’d take if I wanted to make a business around rag.


I'm genuinely surprised it got my accent right. Coming from Serbia, I'd never expect to get it right. My first guess was that it's geo-ip based, but I could be wrong.


a lot of my international friends tried it form the same german wifi and it got all right :)


While we are it - are there any good resources on how to best self host a Postgres database? Any tips and tricks, best practices, docker / no docker etc? I’m looking to self host a database server for my multiple pet projects, but I would love to get backups, optimizations and other stuff done well.


I find this YouTube channel[0] has a great number of videos on how to setup Postgres on a regular Linux machine, explaining how configure it and make it work for high availability. It’s easier than you’d think.

[0] https://youtube.com/playlist?list=PLBrWqg4Ny6vVwwrxjgEtJgdre...


When I self host I lean towards SQLite simply because it’s simpler. In-place upgrades, trivial backups via Litestream, etc.

Postgres major version upgrades are the main reason I don’t self host it, though maybe I should rethink my position on that!


For backups, pg_dump is good and simple for starting out.

For tuning, postgresqlco.nf[1] is great.

[1] https://postgresqlco.nf/tuning-guide


Not the answer you were looking for, but I had been shopping recently for slightly overlapping reasons (I want to ship projects, but they are all smaller MVPs that might run for a while and I didn't want to pay for 1 database service for each one on Render).

I found https://www.thenile.dev/pricing which supports which apparently supports unlimited databases.


afaik:

On promise: Use containers but the data folder should be mounted volume

On cloud/k8s: Just use a managed DB, setting up a DB in k8s is hard because the filesystem


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: