Honestly, I would probably build it out on WordPress with a slick theme from somewhere, and the app built out as a plugin using jQuery or Backbone on the frontend. See if works and people give me money. If I get money, refactor frontend to use react/redux. On the back, if PHP/WordPress weren't a good fit, I'd rewrite in another language and have WordPress proxy the requests and cache the responses smartly (POST/DELET…
What is the default crud solution on WordPress? Do you create new objects? Are there API generation plugins? I like WordPress for a CMS (wouldn't recommend anything else for a small to midsize CMS solution) but wouldn't think of it for a crud app. That said, haven't researched it much lately, so wondering what I am missing.
Ask HN: What stack would you use to build a CRUD web app in 2018?
111–120 of 184 posts
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#112I work with startups, so I make this decision every 2-3 weeks or so. Language: Python. Python is easy to learn for those that don't know it, and all-around liked. It's not hard to find engineers with existing experience if you need to grow. Framework: Django. Django does everything you might want in a framework. It scales with larger teams, and the admin is still one of its killer features. Frontend: SCSS/SASS, and v…
Did I get the right impression, or may be I just didn't learn to use Django correctly?
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#113Earlier quoted context omitted.
>> .. and vanilla JS with some jQuery If I could I'd buy you a beer and cheers you for relieving my JS anxiety a bit. I love jQuery, and I'm tired of feeling ashamed of it, damnit!
I don't think that quote justifies your love of jQuery. The keywords are "some" and "sprinkled in". In my experience jQuery always trends towards a huge mess the more it is used. Sure, it could be used but it really shouldn't. Interacting with the DOM in a procedural way, and storing state on the DOM is always going to be harder to manage than using a reactive pattern when you trend towards more complexity.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#114Reading through all of the comments so far, I'm seeing solutions that give you a CRUD web app... and nothing else. If that's all you really need, then that's fine. For the past seven years I've been working with large companies who need Enterprise-class CRUD apps, with Enterprise-class requirements that go far beyond what you get out of the box with most of the cobble-it-together-yourself solutions being mentioned here.
Surround Accelerator is a CRUD Application Generator and Framework. To use it, you first develop an optional plugin that customizes the generator, then you run the generator and point it at your database. It loads the schema, does a bunch of analysis, and asks you a bunch of questions. Your plugin is used to govern the analysis and provide standard answers to the questions, so that you can customize the result consistently. Finally, a set of C# web services and applications are created. We're currently producing both a WPF desktop application and a fully-responsive ASP.Net MVC SPAs. Both GUIs are highly customizable; our framework is very flexible and all of the code you need to change to customize the application is part of the generation rather than locked up in the framework.
Generation isn't a one-time thing though; if your schema changes we've got tools that you can use to re-generate just the parts you've changed, or to add generation for the parts that are new. Typically, the way we've structured our code to allow for customization, it's easy to merge your customizations back into the generated code.
If any of this interests you, please visit our website. We've got a number of videos showing the process, a bunch of demos, and many case studies and testimonials from actual customers.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#115Has anyone here used DataTables, specifically the Editor? https://www.datatables.net/ https://editor.datatables.net/ https://github.com/DataTables I have a license for the Editor and have to say it works very well. They have an online Generator that makes it easy to get started very quickly.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#116I work with startups, so I make this decision every 2-3 weeks or so. Language: Python. Python is easy to learn for those that don't know it, and all-around liked. It's not hard to find engineers with existing experience if you need to grow. Framework: Django. Django does everything you might want in a framework. It scales with larger teams, and the admin is still one of its killer features. Frontend: SCSS/SASS, and v…
I always had a question I wanted to ask an experienced Django dev. After trying this framework for a couple of hobby projects (I'm a client game developer primarily and never worked on "serious" web project), I kinda got the impression that it's architecture is created for two main user roles: admins who create most of the content and have marvelous admin forms in front of them to input all the data, and users, who m…
it kinda makes sense, considering how easy it is to create form views
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#117Frontend: ReactJS
Backend: NodeJS
Database: Postgres
Hosting: AWS
CI/CD: Gitlab
Simple for me. Easy to deploy changes quickly. Fast iteration.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#118Has anyone here used DataTables, specifically the Editor? https://www.datatables.net/ https://editor.datatables.net/ https://github.com/DataTables I have a license for the Editor and have to say it works very well. They have an online Generator that makes it easy to get started very quickly.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#119Golang for api, React front-end
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#120Earlier quoted context omitted.
>> .. and vanilla JS with some jQuery If I could I'd buy you a beer and cheers you for relieving my JS anxiety a bit. I love jQuery, and I'm tired of feeling ashamed of it, damnit!
I don't think that quote justifies your love of jQuery. The keywords are "some" and "sprinkled in". In my experience jQuery always trends towards a huge mess the more it is used. Sure, it could be used but it really shouldn't. Interacting with the DOM in a procedural way, and storing state on the DOM is always going to be harder to manage than using a reactive pattern when you trend towards more complexity.