Deleted
Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
71–80 of 118 posts
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#72Deleted
I think this is the wrong post :)
You probably wanted to comment in the other thread about the AI language teacher
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#73Wow, what was the motivation for using this abnormal syntax for array element indexing? https://docs.fastgen.com/getting-started/variables#indexing-...
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#74Wow, what was the motivation for using this abnormal syntax for array element indexing? https://docs.fastgen.com/getting-started/variables#indexing-...
Easy parsing ? Overall I like jinja syntax the most
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#75How does this handle load ? Does each customer get their own VM to run requests against? Do you have a rare limit built in ? What if I need to do something more complex, is it possible to have a block of say Python code that executes? Honestly I'm not sure who this is meant to serve,AWS has a rather robust API offering with the added bonus of integrating with AWS services. Anything more complex than that might be bet…
Let me address each of your points: Performance: When we began planning to build Fastgen, our most important consideration was how it should handle load. Therefore, most of our design decisions have been deeply influenced by this. We have autoscaling go backends that are trimmed on performance, handling all customers together. With RabbitMQ we distribute the load and offload expensive operations to different micro se…
Thanks for the response, I definitely wish you luck but I think you're going to have to focus more on a non-developer niche. So maybe add more integrations to outside APIs. From the YouTube video it doesn't seem like this is too accessible to anyone without a strong technical background .
At that point, why not spin up your own API. That said this is a very profitable sector so I do think your company will do well. Good luck
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#76Congrats. This looks excellent. I have tried the frontend ones like Webflow and Bubble and they are all clunky, not meant for any serious work. No code for the backend actually might be the better usecase so I would love to try it out / see how it evolves. One concern I have here is local development.
At the moment, Fastgen doesn’t directly support local development. Our focus has been on providing a cloud-based low-code experience that you can access from anywhere without the need for local setup. However, we do recognize the value of local development, and we’re exploring ways to support it. That being said, we already offer an experimental feature to call your route from your local environment through for examp…
This does restrict me to build small toy apps. Because I do deep thinking and system building in my remote cottage without internet.
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#77Wow, what was the motivation for using this abnormal syntax for array element indexing? https://docs.fastgen.com/getting-started/variables#indexing-...
Easy parsing ? Overall I like jinja syntax the most
You are misremembering, Jinja uses python syntax like a sane language so it would be `{% set foo = ["alpha", "beta"] %} {{ foo[1] }}` not `{{ foo.[1] }}` like they use. I actually probably wouldn't have chirped about it if they used the alternate syntax (also supported by Jinja) of `{{ foo.1 }}` but the belt-and-suspenders of requiring the array brackets and the dot is just ... why?
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#78Wow, what was the motivation for using this abnormal syntax for array element indexing? https://docs.fastgen.com/getting-started/variables#indexing-...
Easy parsing ? Overall I like jinja syntax the most
Spot on! :) But we already have it on the roadmap as one of our next items to clean that up properly and migrate away from it
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#79Earlier quoted context omitted.
Easy parsing ? Overall I like jinja syntax the most
Spot on! :) But we already have it on the roadmap as one of our next items to clean that up properly and migrate away from it
I would suggest dropping the "you can use == or = interchangeably" since I doubt that adds as much value as "future syntax risk" it incurs
Re: Launch HN: Fastgen (YC W23) – Visual Low-Code Backend Builder
#80Earlier quoted context omitted.
Easy parsing ? Overall I like jinja syntax the most
You are misremembering, Jinja uses python syntax like a sane language so it would be `{% set foo = ["alpha", "beta"] %} {{ foo[1] }}` not `{{ foo.[1] }}` like they use. I actually probably wouldn't have chirped about it if they used the alternate syntax (also supported by Jinja) of `{{ foo.1 }}` but the belt-and-suspenders of requiring the array brackets and the dot is just ... why?
`{{ foo.1 }}` is supported and initially was the only syntax to index arrays. But with the need to index arrays with the help of other variables came the introduction of optional `[]` to encapsulate nested vars from the the top level var.
Will update the documentation page in the next hours to also showcase `{{ foo.1 }}`. Thanks for the heads up