Live data from Hacker News

Rails is better low code than low code

radanskoric.com

131–140 of 249 posts

Re: Rails is better low code than low code

#131
post #6

I don’t want to build in a language without types, but low code is even less types than Rails. I’ve just never worked on a public app that was simple enough for Rails to feel good - Airbnb was rails but by the time I got there it was very much not simple. Internal tools in rails though, that is okay.

Ruby has types.

Re: Rails is better low code than low code

#132

Even though it is Oracle, Oracle APEX is exceptional at creating CRUD applications. The main benefit to other low code tools is that it doesn't want eliminate code but just the repetitive UI code. It still expects you to have skills in database development so you can achieve everything but generating a Report, Grid or Form from a SQL query takes as long as you need to write the query. And everything is customizable a…

> It still expects you to have skills in database development so you can achieve everything but generating a Report, Grid or Form from a SQL query takes as long as you need to write the query. And everything is customizable and maintainable in the end. Isn't this what people thought about Oracle Forms before it going the way it did?

Yes, it similarly just builds around developers storing the code in the database layer. Forms is still around, with some giant companies relying on it, but of course, it is slowly dying. APEX is also 20 years old already, but based on the web stack. This choice aged perfectly, so it went from a niche inside Oracle to now the default application framework inside Oracle around 2020. Oracle Forums[0] is build on APEX for example.

[0]https://forums.oracle.com/ords/r/apexds/community/home

Re: Rails is better low code than low code

#134
Low code tools can indeed be effective for simple use cases or prototyping, but their limitations often surface when scaling or customizing is needed. As others have pointed out, a framework like Rails offers the flexibility to expand and adapt while maintaining structure.

Building the Multiwoven product based on Rails has been incredibly helpful in balancing rapid development with the ability to scale and customize as user demands evolve. It provides a structured yet flexible foundation, allowing us to adapt quickly without compromising on quality.

It’s about knowing when to leverage low code for speed and when to transition to more robust solutions for long-term scalability.

Re: Rails is better low code than low code

#136

This post boils down to "it's easier to use something you know in and out that some new tool you're using for the first time.", so not a good argument. I think I've seen ruby code a handful of times in my life and it looks like an obfuscated form of perl to me. If you'd give me a low code tool and ruby and the same task I don't think I'll succeed with either in a reasonable amount of time. (Not that I'm a fan of low…

You can use an LLM and get quite far with Rails imo if you've been programming in a web framework of any kind. You don't have to know Ruby. Probably same goes for the low code tool, only there once you're stuck its probably because you've hit the limits of the tool.

Re: Rails is better low code than low code

#137
post #20

Earlier quoted context omitted.

More exactly, C code (hopefully MISRA C) generated from Simulink models runs much of the embedded systems in many cars. Although sometimes (cough, Toyota/Denso, cough) that generated C is then bodily assaulted by questionably competent embedded developers until it combines the worst qualities of MISRA C and low-quality embedded development, because, like many low-code solutions, getting (and keeping) everything in th…

Matlab / Simulink will doubtlessly have a very long tail, but is being overtaken by Python. For one thing, programming is gaining ground in areas that have no established loyalty to Matlab, and those are growing areas. Such as the life sciences. For another, a certain fraction of students want to test the waters and see if they can explore software development as a career option. Python is more relevant to that optio…

Python is also open source.

Re: Rails is better low code than low code

#138
post #101

I never understood the "low code" microbubble that was being inflated. We went through that era already. We called them RAD tools, and they targeted the same sort of strange, mythical end user profile. Someone so technically capable and apt that they could navigate a dizzying domain of deeply buried checkboxes, property fields, and sprawling relationships & side-effects, but who was also simultaneously unable to unde…

I think you're taking the intent of "low-code" too literal, or have not worked in an organization of sufficient size for its value proposition to be evident. It's not to solve a solutioning problem; it's to solve an organizational one. While any "low-code" is marketed as a WYSWG, business friendly solution platform, what it actually is is a way for the business to get access to capabilities IT otherwise gatekeeps as…

100% this! In some companies the 'simple app' that is described in this post will get some ridiculous quote from central IT/tech ('it will take our team 4 sprints') and then never get signed off. IT will also ban anyone spinning up their own servers due to support issues.

No code platforms manage to get around this.

Another use case - I work for a 'non-tech' consultancy. Clients typically won't like paying us to spin up some flask/django/rails app, but are happy to pay us to spin up some sort of no-code thing for them (perception is that it will be easier to self-support, which is also probably the reality compared to me developing some sort of rails app and then leaving the company).

Re: Rails is better low code than low code

#140

I never understood the "low code" microbubble that was being inflated. We went through that era already. We called them RAD tools, and they targeted the same sort of strange, mythical end user profile. Someone so technically capable and apt that they could navigate a dizzying domain of deeply buried checkboxes, property fields, and sprawling relationships & side-effects, but who was also simultaneously unable to unde…

RAD tools had nothing to do with low-code. I think you're confusing something. You still needed seasoned software developers and you weren't restricted by anything.
Post reply on HN