Live data from Hacker News

Form to DB

formtodb.com

91–100 of 129 posts

Re: Form to DB

#91

Earlier quoted context omitted.

sometimes it is: https://htmx.org/essays/a-real-world-react-to-htmx-port/

Yeah until a manager comes and says "well great, it works, now let's do a mobile app like that"

https://hypermedia.systems/hyperview-a-mobile-hypermedia/

https://hyperview.org

https://htmx.org/essays/splitting-your-apis/

https://htmx.org/essays/two-approaches-to-decoupling/

https://htmx.org/essays/mvc/

Re: Form to DB

#92

These types of projects always remind me of MS Access. Access is forms on a database, and really easy to use. It obviously has its drawbacks but nothing has come close to it. I've never understood why MS didn't capitalise on it by extending and improving it.

I never saw an Access database that didn't become a regretful mess after a couple of years - the person that made it left, no-one knew how to update it. Fancy validation built into the form that just got in the way when requirements changed. Thus I came to the conclusion that any Access database is probably better off being a spreadsheet, even with all the chaos that not having forms as a front end and not having rel…

Most Access-based apps turn to shit because they're made by non-developers. The tool itself isn't to blame. I've seen Access used to great success when coupled with scripting to dump schema and code to text files for version control and code review.

Re: Form to DB

#94

These types of projects always remind me of MS Access. Access is forms on a database, and really easy to use. It obviously has its drawbacks but nothing has come close to it. I've never understood why MS didn't capitalise on it by extending and improving it.

Because the single-system paradigm doesn't work any more. However, modern replacements do exist, Airtable is one of the first; it's basically the notion of a "spreadsheet with more structure", and then building forms and such on top of that. I've recently been playing with Grist and like it, although it is rough around the edges. https://www.getgrist.com

Airtable also has a surprisingly small hard row limit. 50k rows is very easy to hit quickly.

Re: Form to DB

#95
post #7

Hi all, engineer who worked on forms @ Retool here. Excited to get HN’s feedback on a new product I’ve been working on: Retool Forms. There are a ton of form builders out there (e.g. Typeform, Google Forms, Airtable Forms, etc.) and honestly we weren’t really looking to build another one. But as a developer, I wanted my data in my database, not in another SaaS app (which probably has a shoddy API, like every example…

There is no download link, so how can this be self-hosted?

You can self-host here: https://retool.com/self-hosted. Most people deploy it as a docker container on an EC2 instance but there’s various options

Re: Form to DB

#96
post #63

Earlier quoted context omitted.

Because it is. It can be very frustrating not to be able to fill a form on mobile with a 3G connection just because some random dev decided that downloading 150kb of JS to render a simple form is fine. I mean it’s a form; we already have all the HTML elements already; why do you need React for? This is why nowadays we end up with Electron apps that take 6GB of RAM to display a chat.

It's really not that simple. What about complex validation rules? Do you really think it's user friendly to require them to send the whole form just to tell them "sorry no" 10 times over until they get it right? What about multi-value selects, potentially with rules? E.g. form field like "choose up to 5 locations in the radius of 10km". What about form fields like "pick a point on a map"? Etc. Don't act like every fo…

> What about complex validation rules?

I wpould use my server-side form and database library, Bozen[1] to do this.

>

[1]: https://github.com/cabalamat/frambozenapp

Re: Form to DB

#97
post #93

How new is this Retool product? The idea that OpenAI, Amazon, NBC, Mercedes, and Doordash all use it seems dubious.

See comment by the CEO: https://news.ycombinator.com/item?id=39476663 Retool is very widely adopted by major companies.

Sure, but that feels like validation for Retool rather than Form to DB.

I may very well be nitpicking unfairly here, those marketing "trusted by" blocks on brand new products just always rub me the wrong way.

Re: Form to DB

#98
post #88

Earlier quoted context omitted.

Detractors of the "html over the wire" movement are always talking about it as if the people working on this stuff didn't live through the jQuery days and are blindly repeating them.

What's wrong with jQuery? All my homies (favorite websites) are jQuery.

jQuery is still viable in many situations! My comment is directed at people who say you can't sanely build bigger things without React.

Re: Form to DB

#99

How new is this Retool product? The idea that OpenAI, Amazon, NBC, Mercedes, and Doordash all use it seems dubious.

Retool is popular for building internal dashboards on top of you data. It has been there for many years

Retool has sure, but I'd expect the Form to DB homepage to be validating this product rather than the team behind it.

I said this in a sibling comment too, I may just be unfairly nitpicking here but these "trusted by" marketing blocks just rub me the wrong way when the product is brand new.

Re: Form to DB

#100
post #63

Earlier quoted context omitted.

Because it is. It can be very frustrating not to be able to fill a form on mobile with a 3G connection just because some random dev decided that downloading 150kb of JS to render a simple form is fine. I mean it’s a form; we already have all the HTML elements already; why do you need React for? This is why nowadays we end up with Electron apps that take 6GB of RAM to display a chat.

It's really not that simple. What about complex validation rules? Do you really think it's user friendly to require them to send the whole form just to tell them "sorry no" 10 times over until they get it right? What about multi-value selects, potentially with rules? E.g. form field like "choose up to 5 locations in the radius of 10km". What about form fields like "pick a point on a map"? Etc. Don't act like every fo…

> Don't act like every form is 5 simple text inputs.

Well to be honest 99% of forms are 5 simple text inputs with a select. What was the last time you had to implement a "choose up to 5 locations in the radius of 10km", really?

> What about form fields like "pick a point on a map"?

Same thing: of course there are rich forms for which you need JS, but they are the exception, not the rule.

Post reply on HN