Marmelab Blog

Is "Agentic Engineering" is the new name for "Agent Experience"? If so, and even though I love Simon's contributions, there are many other guides to making codebases more welcoming to agents... Shameless plug: I wrote one. https://marmelab.com/blog/2026/01/21/agent-experience.html

React-admin[0]? Doesn't read openapi from what I could gather but solves similar problems in a best-practicey kind of way. [0] https://marmelab.com/react-admin/Readme.html

I've been evaluating potential replacements for the Django admin to provide a path for progressive evolution as apps outgrow Django, and have found https://marmelab.com/react-admin/Readme.html -- anyone got other generated admin platforms they like for handling CRUD / mutations? I think the Django admin is great, I use it a lot and recommend it for new/small projects, but it's tightly coupled to the Django ORM which can be restrictive in some usecases.

marmelab | Paris, Nancy FRANCE | INTERNS & REMOTE | Fulltime We are looking for web developers, at least 2 years of experience no matter your diplomas, to work in our Digital Innovation Workshop. If you are interested in learn a lot of stuff and make things done on innovative projects with very modern technologies you can apply at [email protected] Here is a list of technologies we use on a daily basis: React/Redux, Cordova, React-native, Node.js, Koa.js, mostly JavaScript. The only requirement is to live on a radius of ~1h30 from Paris. For further informations: http://marmelab.com/ http://marmelab.com/blog/ https://github.com/marmelab

So what's the answer then? Before the internet almost all journalism was "paywalled." You either bought a subscription or an individual copy of what the organization has to offer. Ad-supported journalism is a joke in a society that abuses advertising so thoroughly. Using an ad blocker is more than a convenience, it's a security measure. Arguably it's also better for the environment [1] [2]. One article [3] argues for "non-reformist reforms," which try to mitigate the commercial pressures on journalism. However the article's solution seems to be to switch to public media models and/or government funding. As the article puts it: "Therefore, any initiative that erodes the commercial and anti-democratic design of existing media institutions—by transitioning them into nonprofit outlets, facilitating public media partnerships, unionizing newsrooms, and establishing media cooperatives—can help radicalize news workers and engage communities while laying the groundwork for more transformative change in the future." I honestly don't know how well that'll work, but it's also basically what the article suggests to pay for journalism for a year: "They can enlist foundations or other sponsors to underwrite their work. They can turn to readers who are willing to subscribe, renew their subscriptions, or make added donations to subsidize important coverage during a crucial election." Stengel's article also says, "A large percentage of these Americans see media as being biased. Well,…

Thanks! > Can you elaborate how this compares to some open source solutions, for example react-admin? I would say that ... React-Admin is a programming framework that a skilled React programmer can use to produce an application with great features that are limited only by the skills, drive, and dev time of the programmer. It looks like a very impressive and powerful programming framework to me. DataSpeeder, on the other hand, is not a programming framework. It is a finished application that is ready to run immediately, can be deployed by a non-programmer, and has intentionally simple features that were designed to solve a specific problem ... Providing an instant end-user web GUI for MySQL. To see the differences in how the tools are used, you can take a look at this (very nice!) React-Admin tutorial ... https://marmelab.com/react-admin/Tutorial.html And then take a look at the DataSpeeder "Create an Application" video tutorials ... https://www.dataspeeder.com/support I hope that helps!

If you're going to use Makefiles as a top-level build wrapper you might be interested in self-documenting targets. https://marmelab.com/blog/2016/02/29/auto-documented-makefile.html

It would be good to know how this compares against React Admin Enterprise ( https://marmelab.com/ra-enterprise/ )

One of the listed benefits of just is "Recipes can be listed from the command line." There is a nice trick that gives makefiles this ability: http://marmelab.com/blog/2016/02/29/auto-documented-makefile.html Adding .PHONY targets and so forth is a bit inelegant, but I can share a makefile with confidence that any Linux/Mac OS/BSD user can use it without needing additional software, and I will never have to worry about make becoming unavailable or no longer maintained. Just my personal opinion.

Give react-admin [0], the post author’s react framework, a glimpse. If you develop an ERP/CRM like react app, you‘ve probably rebuilt parts of react-admin already, but you did it worse. Ah, and their source code is a breeze of fresh air. [0] https://marmelab.com/react-admin/

Tie between Julia and Haskell, for different reasons. Julia has an intuitive and expressive syntax, while having good flexibility and the ability to work in multiple paradigms. Also, being a scientific programming language, it lends itself well to much of my work. Haskell is rigid enough to force good design; this "higher barrier" generally results in better mental models by front-loading the understanding of a problem. Honorable mention to a non-language, the Makefile. Especially with things like help targets[1], it's a very good accelerator for picking projects back up after they have sat on the shelf a while. [1] https://marmelab.com/blog/2016/02/29/auto-documented-makefile.html

I've been using the free, open-source React Admin https://marmelab.com/react-admin/ framework for this use case, and I really like how it works and how little code I need to write. I used it to quickly build an internal CMS, and it handles relational stuff well. For instance, if I have pieces of content, each of which can have multiple tags, it handles all the tag lookups using typical REST API calls. Also integrates well with our existing auth system (AWS Cognito). There are some other low-code tools that have similar premises and offer things like ETL tools. We evaluated one called Retool https://retool.com and it seemed pretty cool, but because it's a per-user pricing model, the costs can be pretty substantial when you have a lot of people using the tool.

Could you compare to react-admin (https://marmelab.com/react-admin/)?

Check out Retool: https://www.ycombinator.com/companies/1564 A wswig for internal UI/dashboards has a lot of value for companies that don't have a dedicated internal tools team. My company had an internal tools teams at one point but it got killed because of other business priorities. We use https://github.com/sferik/rails_admin, that still requires development time and frontend knowledge, but the framework is terrible. https://marmelab.com/react-admin/ is much better but also required development time and frontend knowledge.

Hasura can stand up almost of your backend without a single line of code on top of Postgres. The parts that Hasura can't handle you implement with your back end language of choice. - https://marmelab.com/react-admin/ - https://github.com/hasura/ra-data-hasura

This even has a name, "monkey testing". Basically some software that pretends to be a monkey in front of a computer and mashes random buttons and keys to make the application behave badly. Usually you only care about the application not breaking in monkey tests. Can be used similarly to "fuzzing" but for UIs as well, see Gremlins.js: https://marmelab.com/blog/2020/06/02/gremlins-2.html

Given https://github.com/jupyter/docker-stacks Docker might be appropriate. No matter which route you decide to take: make it easy. If you are using pipenv or poetry do so while offering a Makefile or documentation on what commands to run. A Makefile with a decent "help" target would be perfect even if you do use Docker. I'd suggest looking at https://marmelab.com/blog/2016/02/29/auto-documented-makefile.html to spare you some work with maintaining the help target.

Your technical stack should not be frozen. During years, it will probably evolve, either to use some promising features of new technologies, or to still be able to hire. For instance, hiring some Cobol developers is really hard (and then expensive) these days. More important than technologies is testing. If your whole app is well tested (with both unit and E2E tests), you won't be reluctant to upgrade some part of your system because it doesn't answer your needs. Moreover, it would bring a lot of reliability and would be self-documented. That's the biggest point IMO. For nowadays mood, we are really glad using React, Node, GraphQL and PostGreSQL for all our apps. Note: we wrote a blog post about one of our long running customer story, which may interest you: https://marmelab.com/blog/2018/03/28/1859.html

Thanks, appreciate the pointer - the idea of adopting something potentially a future standard through a polyfill is appealing. @pvg I take your point about lack of browser support, but that's what polyfills are for after all! :) In the meantime since asking I also came across restful.js (github [1], blog [2]) - it's new, but looks like a good framework-neutral alternative, if a little heavy at 27K minimised/uncompressed. Edit: Actually, fetch.js + es6-promise-min.js = 26K, so not much in it. [1] https://github.com/marmelab/restful.js [2] http://marmelab.com/blog/2015/03/10/deal-easily-with-your-rest-api-usi…

Depends on what "look great" means. And I've seen Delphi apps; I recently worked on one. In my experience they don't look great. Maybe you've done a lot of work to theme the controls; if so, wonderful. But what I'm familiar with just brought up Windows dialogs, and ... well, that's functional but I wouldn't say it looks great. But here are a few examples of ways you could create 150 fields in a day on a web app and have them look great: Arrays of control types: https://formik.org/docs/examples/field-arrays for simplicity of creating the controls plus something like https://chakra-ui.com/docs/components/input to make them pretty. Spreadsheet look (with spreadsheet functionality!) in one control: https://www.npmjs.com/package/react-spreadsheet Want to build the form by hand and customize it? https://www.form.io/ Form should follow a database schema and automatically display database records? https://marmelab.com/react-admin/ (I used this approach to bring up an admin panel for more than 150 fields, though spread over a couple dozen pages, because of course that looks better than trying to bring up 150 fields on one page.) The standard way to create a large form (or any data table on a page) today is to iterate over the fields you want and add them to a page. There are frameworks like Chakra that can help you make everything look attractive--and you can theme the result in whatever color scheme or styles you like. I really don't want to have to touch Delphi ever again;…

PostgREST: https://github.com/PostgREST/postgrest and http://postgrest.org/en/v6.0/ Sample PostgREST apps: http://postgrest.org/en/v6.0/ecosystem.html React-admin: https://marmelab.com/react-admin/ and https://github.com/marmelab/react-admin React.js: https://reactjs.org/ Combinations: - https://github.com/tsingson/ra-postgrest-client - https://github.com/raphiniert-com/ra-data-postgrest - https://reactjsexample.com/a-react-web-application-to-query-and-share-… - https://github.com/tomberek/aor-postgrest-client - https://github.com/priyank-purohit/PostGUI - https://awesomeopensource.com/project/priyank-purohit/PostGUI?category… - https://www.reddit.com/r/learnpython/comments/bzrr1c/how_to_create_dyn… More links: - https://github.com/topics/postgrest - https://duckduckgo.com/?q=%22postgrest%22+%22react%22&t=ffab&i… - https://duckduckgo.com/?q=%22postgrest%22+%22react-admin%22&t=ffab… - https://react-admin.com/docs/en/ecosystem.html I'm sure you can find more! Yeah, there's not one solution. There are many. Many are open source. PostgREST is amazing. The rest is up to you, but there's tons of tools out there.

Previously discussed: 7 years ago: https://news.ycombinator.com/item?id=9927771 3 years ago: https://news.ycombinator.com/item?id=21435195 2 years ago: https://news.ycombinator.com/item?id=25159097 1 year ago: https://news.ycombinator.com/item?id=29389576 It's an insanely cool project, but I've yet to find a truly fitting use case for it. In theory, PostgREST combined with something like https://marmelab.com/react-admin/ should give you a free back-end and admin panel for most projects, but in practice, I've always found that all kinds of 'small details' won't be quite right out of the box, and that customization is really hard...