Live data from Hacker News

Ask HN: Easiest way to build a CRUD app?

news.ycombinator.com

131–140 of 239 posts

Re: Ask HN: Easiest way to build a CRUD app?

#131

I’m surprised nobody had said MS Access. You don’t need to learn any programming languages, it comes with everything you need, and every Access app has lasted way longer than anyone wanted it to. ;)

> Yes you do. If you want to have buttons and tables and do something above of only showing the data you'll need to learn VBA. Also SQL implementation for MSAccess has some peculiar stuff in regards to LIKE or how datetime is handled. So you'll learn 2 programming languages actually - VBA % the variaton of SQL that MSAccess has. And you can't scale up from single user to multiple users as MSAccess is not a server lik…

MS Access works just as well on an SQL Server database as on its internal database, so your scaling works just as well as on any other established database server, and then the SQL dialect is T-SQL, which is reasonably standards compliant.

Re: Ask HN: Easiest way to build a CRUD app?

#134

Your requirements are contradictory and incomplete: - No single language can do all of that successfully, unless you ditch GUI and client-server models - Without external dependencies you will either be reinventing the wheel or adding lots of layers - All software will require maintenance, more layers equal more maintenance - All software can be compromised or hacked, more layers equal more attack surface - If it has…

Typescript/JS React FE + Node BE - one language.

Re: Ask HN: Easiest way to build a CRUD app?

#135

I’m surprised nobody had said MS Access. You don’t need to learn any programming languages, it comes with everything you need, and every Access app has lasted way longer than anyone wanted it to. ;)

> Yes you do. If you want to have buttons and tables and do something above of only showing the data you'll need to learn VBA. Also SQL implementation for MSAccess has some peculiar stuff in regards to LIKE or how datetime is handled. So you'll learn 2 programming languages actually - VBA % the variaton of SQL that MSAccess has. And you can't scale up from single user to multiple users as MSAccess is not a server lik…

Can also say that the SQL implementation in Access is reprehensible in terms of silent errors and other weirdness.

Re: Ask HN: Easiest way to build a CRUD app?

#136

I would consider Django and just using its Admin framework for building your UI, you can achieve so much very quickly with almost no code. I believe it’s a brilliant tool for building internal CRUD type db apps. Knowing how to use the admin framework well is basically a developer super power. You won’t need any external libraries, it has brilliant docs and important tools like database migrations are built in.

I use django-cookiecutter [0] for most of my projects as it sets up a myriad of things, saving an incredible amount of time if you need your app to be production ready quick. May be better suited for those experienced with django though.

[0] https://github.com/cookiecutter/cookiecutter-django

Re: Ask HN: Easiest way to build a CRUD app?

#137

If this isn't a business application, ignore this entire comment. If it is a business application, you probably shouldn't build a CRUD app, at least not the way that's commonly understood. Stick with me for a minute. First off, you must never delete business data (except per GDPR, retention policies, or other legal requirements). I'm sure someone will pipe in with a contrived use case where you would want to, but in…

Excellent comment.

I will say this: as someone who has to interact with a system where nullifying and deleting data is a legal requirement for privacy reasons, I desperately wish that weren’t true. Auditing, tracing, even basic production robustness…everything just seems to fall apart when one can’t follow your model.

Re: Ask HN: Easiest way to build a CRUD app?

#140
If you're going to be doing anything more complex than form validation and CSS animations on the client, you're going to need JS. If it's a constraint that there must only be one language then you have to use JS on the server too.

Nowadays the best experience with full stack JS is a full-stack framework like Next.js, Next or the one I recommend, sveltekit. You can easily write client pages & server routes Next to each other, with all the standard client side features like components and use tried and tested JS libraries like node-postgres. It's great and is unlikely to break for years, or decades if dependencies are updated.

Post reply on HN