13 ms·
Rails is better low code than low code
- deleted 2y ago[deleted]
- namaria 2y agoThe low code space has been well explored. Excel is the flagship product in that space. You tell me if you want to be involved with a long lived and non trivial collection of spreadsheets.
- deleted 2y ago[deleted]
- rqtwteye 2y agoNot sure if Excel is low code. It has a pretty full featured language behind it: VBA.
- ebiester 2y agoRetool has JavaScript. This is common for low code to have full languages attached. The point is that you can do 80% of the presentation by wiring things together and only rely on coding for the most complex tasks.
- stefan_ 2y agoI don't know if that is the case. Here is a low code flagship product few people have heard of: https://mathworks.com/products/simulink.html https://mathworks.com/products/simulink.html It runs your car engine.
- cpgxiii 2y agoMore 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 the low-code model is hard and the built-in escape hatch to a real programming language is not always a good fit to the problem at hand. (As a nit, I suspect that Simulink is known and deservedly disliked by the vast majority of people with non-software Engineering degrees, given the omnipresence of Matlab in academic contexts.)
- analog31 2y agoMatlab / 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 option than Matlab. But Simulink does continue to rule its own roost. I think the users see themselves more as engineers than as software developers. And engineers are more inured to using awkward tools.
- miohtama 2y agoPython is also open source.
- analog31 2y agoIndeed, and that's an attraction even despite Matlab being effectively "free" due to generous academic site licenses. But people are catching on that open source means more than "free" as in beer. I think it has also encouraged what we've seen, the flourishing ecosystem of libraries, tools, tutorials, etc., that really make Python what is. People don't want to pour their heart and soul into something that somebody else owns.
- robocat 2y ago> People don't want to pour their heart and soul into something that somebody else owns. Plus the soul of academia is openess and sharing (perhaps trending towards closed IP and privatisation).
- IshKebab 2y agoI don't particularly want to be involved with a long lived and non trivial collection of Ruby code either, if my experience of the Gitlab codebase is anything to go by. I agree with the author's point, if you replace Ruby with something less awful (Deno, Go, etc.)
- BowBun 2y agoThis feels like the exception that proves the rule. Gitlab has one of the largest Rails codebases on earth. It's also been built by a decentralized remote engineering org from the start. I think that explains a lot. Compare that to my personal experiences and that of my colleagues who work heavily with Rails: We show up to a new job at any level of seniority, spend a week or two learning the codebase, and immediately have a firm grasp of all the major components of the application. And I want to stress _firm_ grasp, since everything from the model structure to the ORM to where you can expect to find tests is standard. Obviously no framework or convention will hold perfectly in the extremes
- kayodelycaon 2y agoSame here. I’ve basically made my career as a rails developer and it’s never taken me very long to figure out the many applications I’ve worked with. Some of them are quite complicated. Some of the older stuff built around rails overdid the meta-programming. Makes unraveling things a little more difficult, but you generally know where to look. And every time I see a nontrivial state machine using a state machine gem, I know I’m in for a world of hurt. But I know exactly what mistakes I will be fixing. :)
- lordofgibbons 2y agoThat's AN example, idk if I'd call it the flagship product. Another example is: https://www.sidefx.com/products/houdini/ https://www.sidefx.com/products/houdini/ which uses node based programming with small amounts of code for edge cases. It's used in a lot of movies very successfully.
- ryukoposting 2y agoI'll never understand why more devs don't learn Excel. Yeah, it's ugly. It's also the only thing you know you can use to develop a tool, slap one file into an email, send it to whoever needs the tool, and they'll immediately know exactly how to open it and use it. No 5-step lists of instructions, no dependency hell, no need to subvert the IT department. Excel is the lowest-friction platform for developing internal tools, period.
- analog31 2y agoAt my workplace, they do, for all of those reasons.
- grogenaut 2y agoWe use sheets all the time at work for all sorts of processes, essentially an internal tool. But it doesn't really even need code, the human is the code. I had to strongly suggest to some of our TPMs and actually a principal in the last year that no they didn't need a tool, they just needed a spreadsheet. But this is so low code that people likely don't even think of it as a low code solution, it's just a spreadsheet. That said other than managing and sorting lists of work to do, I break the limits on sheets and excel all the time so for anything with customer scale data I can't use it.
- nickjj 2y agoYep, even the most basic knowledge such as knowing how to do math on a few cells can be useful to build things. It's really good for one off internal tools to do comparisons. For the first 5 years of selling courses I handled affiliate payouts by sorting and summing rows in a spreadsheet. It only took 5 minutes once a month. I eventually automated what I used to do manually with a script that reads the CSV file because I like coding and it was fun to me, plus I wanted to remove one point of human error.
- zamalek 2y agoSomewhat of a tangent: As much as us engineers hate it, I consider the fact that Excel monstrosities are commonplace high praise for the product. Being hated by engineers because your product is so common is exactly where you want to be (double points if you stir up some consulting/certification for migrating to actual solutions).
- simplemindedbot 2y agoSo low-code is faster to get started with little programming knowledge but isn’t expandable. OTOH, a language and framework that you’ve taken the time and effort to learn takes a little longer to get started but is ultimately more suited to more complex tasks. I think the takeaway from the narrative here is knowing when to switch from the low code platform and call it a PoC. I’d have cut that off around the point that the custom lambda came into play. That way you’ve used the low code environment for what it’s good at, creating something “they” can react to and easily explore basic functionality. While at the same time you’re taking those learnings and building the more robust solution.
- ljoshua 2y agoI agree that the main takeaway is knowing when to switch. Having a mental model for this makes many future discussions and decisions much easier, because this seems to be a conundrum that comes up frequently (even for me inside of a large tech organization!). Based on my experience, I'd suggest the pivot point occurs before even starting: it should pivot around who is building and maintaining the system. If you have the experience needed to quickly develop a solution in code, do it in code. If not, because this is a non-technical team without technical resources, do it in low code. Simple as that.
- rqtwteye 2y agoI usually go straight to the full language. It's pretty hard to find the point when to switch from low code to something else when there is time pressure. Same with bash vs python. People say you should switch from bash once you have more than 100 lines or so. But at this point you already have some complexity in bash which makes the switch to python non trivial. So you usually end up patching the bash script in small increments as needed. It gets messier and messier but nobody wants to/can spend the effort for a full conversion
- maleldil 2y agoBetter to immediately switch to Python (or anything else) once you have any non-trivial control flow in your bash script. Loops, non-trivial conditionals, and argument parsing are all easier in Python. Bash is for simple scripts that just chain commands.
- jitl 2y agoI 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.
- darepublic 2y agoI expect low code that can be translated into typed clean code. The low code side of it is just with more assumptions baked in. And with llms you can perhaps have a lot of leeway to in fact customize and allow low or no coders to specify somethinf exportable to readable typed code
- ajayvk 2y agoThis is what I am trying to solve for with https://github.com/claceio/clace https://github.com/claceio/clace. Allow internal tools to be built with regular frameworks, while making it easy to add gitops, SSO, secrets management etc which are required for internal tools.
- wordofx 2y ago[flagged]
- Zambyte 2y agoRuby is strongly typed. Dynamic typing and inferred typing are not the same as typeless. B and Forth are examples of typeless languages.
- lolinder 2y ago"Strongly typed" is not a well defined term—it basically means "I'm personally comfortable with the level of guarantees offered by the language", which is a purely subjective measurement. In context it's obvious that what OP meant is that they wouldn't want to build in a language without statically-checked types. That there are languages that provide even fewer statically-analyzable guarantees than Ruby does not make Ruby a suitable candidate.
- Neywiny 2y agoIt would be nice to get a brief definition of "low code." Otherwise great article. I've found myself using "low code" frameworks when they setup my environment for me and can generate the code files. Key example was a Minecraft mod maker. Within a minute I was fed up with the scratch style programming, but it had all the Java build stuff ready for me to just edit the files myself. No setting up gradle or anything.
- p1necone 2y agoI think this is the key to them actually being useful - generate a sane project in some widely used language under the hood, and let people give up on the low code solution when they outgrow the guardrails. Otherwise you're just dooming yourself to an eventual rewrite as soon as you need some feature that's not supported.
- Klonoar 2y ago“Ejecting” is the key term here I think, or at least the one I’ve always used - for when you need to shed the handlebars for more control.
- bloomingkales 2y ago“Low code” means you do not have to go beyond the tool to solve problems. In fact, there should be entire problems you cannot even create with low code tools. Programming could mean an endless rabbit hole through several technologies, same with designing (you are concocting designs that may use several different technologies). If the tool lets you make a circle button and change text in it, then that’s all you have to worry about.
- jameslk 2y agoBoth low code and Rails have become a lot less relevant since LLM assisted coding became the norm. Low code became less relevant because 1. LLMs solved many of the problems low code solves with better control over the output, and 2. you can’t use many low code platforms as an output from LLMs or other types of models (yet). Rails became less relevant because Ruby is dynamically typed, and this poses a challenge for LLMs due to hallucinations. You don’t want to find out at runtime what things were complete bs from the model. Static typing isn’t a panacea to hallucinations but it’s a significant enough advantage, especially against such a dynamic language as Ruby. Even mere mortals struggle to understand the magic in meta programming DRY golf that many in the Ruby world have chosen to embrace. EDIT: Any down voters care to explain why you disagree?
- bravura 2y agoWhat are the best static languages + frameworks for shipping CRUD web apps?
- dallasg3 2y agoASP.NET and C#
- valiant55 2y agoI'm currently building an internal app with Pico CSS, htmx and ASP.NET minimal APIs returning Razor components and it's a joy. I'm a Developer DBA with no perfessional front end experience but I feel really productive and the final results look great.
- WuxiFingerHold 2y agoNot to forget Entity Framework Core. It has become one of the best (if not the best) ORM over the years. Bit of a learning curve, but for CRUD ideal.
- jameslk 2y agoThis is going to be largely dependent on your needs, but a factor I would consider if you're using LLMs for coding is which models have been trained the most on which languages. The more a model has been trained on a particular language, the less it will hallucinate
- xrd 2y agoI got stuck when he said he wrote a lambda function for the no-code project. How did a lambda function get categorized as no-code? </snark> (I think I'm aligning with his point in the article. No-code really does not offer much long term. And, IMHO, no-code will never truly be no-code, so why not start with "Yes! to code!" and build from there)
- game_the0ry 2y agoI am not a rails dev but have looked into it for some side projects that I am considering. IMO, I think it hits an excellent balance between rolling-your-own framework and no-framework-low-code. Rails itself handles so much configuration and wiring up so you that most of the code you do have to write is business logic. Lambda functions and firebase are convenient and compelling but come with their own tradeoffs that are not as well-tested in the real world compared to rails.
- 0xDEAFBEAD 2y agoI think Rails is good for a consultant who wants to pump out a lot of relatively generic apps. You pay a constant upfront cost to learn the Rails magic and the conventions, and once you know that stuff, it makes greenfield development faster. If you're doing a single big project, Rails is less attractive. The upfront cost is amortized over just one project, and the magic makes it a bit harder to stray from the beaten path when you need that.
- abid786 2y agoCould you give some examples of what the use cases are where Rails makes it hard to stray from the beaten path?
- rafamvc 2y agoIf you work on an older and large rails code base, you can easily find the programmers who came from more "formal" languages like java. They build layers and layers of code to "isolate" rails and end up with big ball of mud. Once you do that you have to keep wrapping and adapting, and commanding, and querying and it takes a gang of more than 4 developers to maintain a feature set that could be done with 1 good rails dev. Code is liability. Features are the asset. Well written rails has one of the best bang for the buck for lines of code per feature.
- afuchs 2y ago> Could you give some examples of what the use cases are where Rails makes it hard to stray from the beaten path? Rails is amazing for greenfield projects. It will automatically do things for you which will greatly reduce the amount of boilerplate you need to write as long as you follow the framework's conventions. However, Rails has a less than stellar reputation from those who have maintained long lived projects which use it. Rails' conventions encourage the use of fat models where business logic is implemented in the models themselves. With the default scaffolding Rails provides, every single model and all of this business logic ends up in the project's app/models/ directory without any separation between different features. Because the default doesn't cleanly separate business logic with well defined boundaries this means that Rails apps tend to evolve in a way where everything starts to become tightly coupled with everything else. When the business requirements for the application inevitably change this tendency towards tight coupling between models makes it difficult to make major changes to existing code. I've also seen hacky workarounds used in Rails based apps which exist to make complex business logic work (e.g., saving one model doesn't implicitly trigger hooks for business logic on other related models). These hacky workarounds usually break the conventions Rails uses and ends up requiring extra boilerplate to be added elsewhere in the application. Some developers try to avoid this by hand rolling more architectural layers (e.g., "Java/Go/Node.js/OOP like") on top of Rails to try prevent this, to varying degrees of success. Other frameworks (e.g., Django) try to encourage developers to separate different features into distinct modules to try and prevent them from being tightly coupled with each other.
- stana 2y agoCode is cost. Low-code is getting a vendor to generate code for you (cost again) and putting into a black box you can't access. i.e. lock in.
- jumpoddly 2y agoBetter headline: The framework you know intimately is better low code than low code. What programmer “believes” in “low code” solutions?
- MattGaiser 2y agoThe real pain point low code seems to solve is boilerplate. Say that I am getting Django ready to go. To get started, have to Dockerize, swap to Postgres, add linting, swap out of the User model, etc. But once all that is ready to go, it is about as fast as low code in my experience.
- weitendorf 2y agoSufficiently advanced "low code" is indistinguishable from a framework or a library. The main difference in practice is that most software that markets itself as "low code" obscures how it works and tries to lock you in to charge rent. Though to be fair, there is generally not much of a market for proprietary/non-OSS libraries and frameworks anymore, so if you want to monetize your library/framework low-code (or an API) is probably the way to do it. Aside from that, I do think the "low code" label can be genuinely helpful as a way of communicating towards semi-technical users that the software they're using is intended to be usable with their level of technical sophistication. IMO this has been a perpetually underserved market, and it's growing over time especially as computer science/programming gains popularity in schools. There are a lot of people out there who understand basic programming and took maybe a couple CS classes in their life, and want to do something entrepreneurial or practical for their non-SWE jobs, but aren't skilled enough to dive right in to doing things the way experienced SWEs would do it.
- threatofrain 2y agoThis makes me think about Microsoft Access and why it never took off. It helps people create databases, forms, and reports. One might call it a no code solution as opposed to merely a low code solution. There are a lot of businesses that's ostensibly in the right place for Microsoft Access. In my view there are certain aspects of app building that's hard. Some of it is in code, some of it is in design, some of it is in domain modeling. Every once and awhile you get stuck and your low-code solution is suddenly paralyzed at that one point. ChatGPT unblocks you until you REALLY need a programmer. Low or no code did not make sense until ChatGPT.
- paxys 2y agoThis can be generalized to - whatever language and framework you are very familiar with is best for the job.
- Spivak 2y agoI don't think this is always true, so they are saying something here. It might not be super profound but: > the advantage of 'low-code' is an essentially flat learning curve, if you have expertise in the field you're being asked to prototype in your strongest stack will be faster and better. It's at least actionable by developers who might feel tempted by these tools for a throw-away project.
- em-bee 2y agothis story is missing the third option: use something complete and ready to run like wordpress. or reuse the CRUD backend from your previous project. the ultimate low code option is to use something that is already written. i am building all my sites on the same generic backend, that has all the features any website would want, object storage, user management, access control, sync and async messaging like IRC, XMPP, email..., database, various APIs, the works. for most websites i don't even have to touch the backend code anymore. it's like a database. when did you last have to make changes to your DB? i had one customer who had a demo of a complex app without a backend. the frontend was fully functional but no data was being saved. we were able to integrate that frontend with our reusable backend and we had the whole thing actually working in a very short time without any custom coding beides adding things to the API and adapting the frontend to use it.
- light_triad 2y agoNo code is easy to get started but difficult to customize. Code is a pain to set up but easy to modify. It really depends how much flexibility you need: if you have to experiment, change on the fly, possibly pivot then the initial investment is usually justified with code. If your requirements are fixed and fit within the existing functionality then a no code platform might be best (for example if you’re building an app version of an existing site that’s close to templates)
- meiraleal 2y ago> Code is a pain to set up but easy to modify. How I wish this was true. Code is a joy to set up using the new shiny tech and people get promoted before the pain to modify comes bite them.
- langsoul-com 2y agoArticle is more like, low code is only good for the most simple of simple apps. And this MUST NEVER CHANGE, the second it changes, or isn't how the low code platform is designed for. Basically it's a massive and near impossible hack job.
- ethagnawl 2y agoWhat is "low code"?
- stana 2y agoStuff like MS Power Apps. More traditionally MS Access. Basically drag and drop App builder - UI form builder, connectors to connect to public API-s and even store data.
- ethagnawl 2y agoThanks. Yeah, Wikipedia claims it become a term of art in 2016, so I don't feel too bad about not being familiar with it.
- ahodgkinson 2y agoLow code initially works quite well until you hit the limits of the low-code framework. If you just need a throw-away proof of concept, or a personal utility, or the like, low-code solutions can be quite efficient. However, implementing anything significant that's expected to be extended and improved, particularly when there are users that request changes, improvements and new features, low-code "is like climbing a tree in order to reach the moon". You'll will very quickly run out of tree and further progress becomes almost impossible. To a lesser extent the same thing also occurs with web development frameworks, but the limits are less constraining and there are often mechanisms that allow you integrate your own code, that implements whatever it is that the framework doesn't provide. Low code, frameworks, and "build it totally from scratch", can all be a valid solutions, but the right choice often depends on a bunch of specific considerations (technology, user & quality expectations, organizational capabilities & constraints, etc.) My recommendation is to keep an open mind about alternative technologies and approaches, and to pick solutions that are appropriate for the environment in which they will be developed, extended and operated. And that requires experience, which you normally don't have in the early phase of your career (e.g. good judgement comes from experience, and experience comes from bad judgement)
- brightball 2y agoOne of the perks of Rails is that Ruby itself makes it more compelling. When you need to get to something that the framework doesn’t expose, Ruby makes it easy to get to it without having to rewrite the framework, extend a class and replace it in multiple places or fork it just to use your modification. This applies to the entire gem ecosystem too. Over the years this ability has saved me numerous headaches with only a few lines of code. IMO it’s the real super power of Ruby.
- it_citizen 2y agoI agree. But with great powers comes great responsabilities.
- Gigachad 2y agoRuby is my least favorite part of Rails by far. The lack of type checking makes every single gem and rails update extremely dangerous in ways that are incredibly difficult to predict. For example the redis gem updated to return an int from exists() instead of a bool like it did before. This doesn’t raise any exceptions because all ints work in if statements. They just always return true. Silently breaking all of the code using it. You can read all of the change logs and search your own code base, but will constantly run in to situations where another gems code is using the method that just changed. As well as the fact that almost every method has one param “options” where the available options are never listed in the documentation and are impossible to find without reading the source code. Rails itself I quite like for being an all inclusive framework that just works out of the box, but untyped languages should be avoided at all costs these days when we have much better options like typescript.
- downrightmike 2y ago[flagged]
- shallichange 2y agoBring back 4GLs like Clipper / dBase etc
- djaouen 2y agoOr, you could use Elixir/Phoenix, which has Flame. *hint hint*
- andruby 2y agoI've done a lot in Rails and a bit in Elixir/Phoenix. I haven't dipped my toes into Flame yet, although I did like the presentation. Have you used or seen it used successfully? Just to learn from, not to knock it down.
- djaouen 2y agoI haven't personally used Flame, but I have extensively used Elixir and Phoenix and contend that, even without Flame, they compete well with so-called "No Code" solutions (like the article contends with Ruby/RoR).
- throwaway42668 2y agoI 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 understand source code or program structure. When using them you would quickly hit a point where making changes to relatively simple things would take mounting an archeological dig of GUI controls that would have otherwise been a few simple find & replace operations on code in a regular environment.
- gonzo41 2y agoEverything you just said also applies to all ETL and workflow management tools as well. There's a level of complexity that's never going away.
- stoat_meniscus 2y agoYes, Informatica was the one that came to mind. We inherited some Informatica ETL workflows once at work. Nice at first glance with good logging, but peel back the surface a little bit and it was a dizzying level of hidden complexity. Some of this was business logic which was inherently complex, but it was so deeply buried in menus and abstractions with no easy diffing or version control... Like the comment starter mentioned - who are these tools designed for?
- disgruntledphd2 2y agoThey're designed for purchasing departments and VPs, unfortunately.
- jayd16 2y agoLow code tooling is alive and well in the entertainment industry. Node graphs are becoming very popular in game engines, shaders, procedural modeling software etc. The king of low-code, spreadsheets, are still quite popular as well.
- th0ma5 2y agoThe comments here are great and show that even if LLMs seem to provide an ability to need to code less, we actually can't stand that for me reasons either.
- quantadev 2y agoThe problem with LLM-generated code is you can't trust it. It might be fun for games and non-mission critical stuff, and I agree it's coding sills (Claude namely) are amazing, but it often totally misses edge cases, or creates stuff that seems to work, until you scrutinize it and find tons of bugs. The qualify of software worldwide is about to begin to plummet as developers get lazy and start trusting AI generated code. That's super dangerous. Never trust it.
- est 2y agoI once joked that PHP was the best serverless language/platform https://news.ycombinator.com/item?id=41358020#41364190 https://news.ycombinator.com/item?id=41358020#41364190
- dzonga 2y agopeople like to shit on document databases - but man oh man - the expressivity you get working with document databases combined with Ruby is unmatched. I know someone is gonna reply all you need is postgres - but yeah jsonb queries don't match mongo queries. & after all - most of the places I have worked the database writes / queries hit one or two tables and work loads got migrated to dynamodb. that includes socia media ingestion, iot streams and metasearch. yeah if you need kimball style queries i.e olap then yeah use postgres with rails etc
- anonzzzies 2y agoPeople like to shit on mongo not so much on others as far as I have seen. They were bitten by it I guess. I guess they are harder to grok after the initial ease of use: performance is harder to reason about; things can suddenly grind to a halt even though you 'didn't do anything different' etc.
- hks0 2y agoLow code starts failing when one expects it to go turing complete. I also experienced the reverse (unfortunately) a couple of times until I gave up: Can we teach basic python to non-programmers in a 1-week workshop, so they can automate boring tasks without needing the developers? Answer: No. And once I switched from trying to teach python, to just using click-clicky through Zapier or alike, people started to be way more productive without having to deal with us pesky programmers directly. Zapier does have big limitations, but people got creative on how to overcome them. Python would've consumed all their mental energy leaving no room for this. And they did create some hard to maintain horror in the UI, yet it had lower cost thanks to people's self sufficiency. The article's conclusion says: > Also, if you’re not a programmer, then absolutely, low code is great. But if you’re reading this article, you’re probably a programmer. So, why are you even thinking about it? And I would like to add: If you _are_ a programmer, then absolutely, coding is great. But otherwise, why are you even thinking about it?
- andrewstuart 2y agoRails is no different to any other modern programming language. It’s no more productive. I don’t know why people treat it like it’s more productive than other things.
- jstummbillig 2y agoFor starters, it's not a programming language, but assuming you are aware: The completeness of Rails still not that common (for example, NextJS needs a lot of additional packages for stuff that integrated in Rails). Curiously, what makes Rails more interesting to me right now are LLMs: Rails is so stable that you can trust the models to know about (most) features, which makes ai assisted development so much more effective.
- vundercind 2y agoWhy was it ever popular? It promoted a productive code organizational pattern, basic hygiene like migrations that were absent in a lot of web dev at the time, had a very productive non-totally-dogshit ORM, and some good deployment tools for the pre-container (and, hell, pre-popularization-of-IAC) era developed alongside it. It’s mostly the ecosystem making it popular these days. Same reason Python’s a juggernaut in several spaces—the ecosystem, not the language or tools (or, in Rails’ case, framework). You can slap a few gems together and have a site with all the basics (user accounts, admin, OAuth, file uploads, user roles, et c) in minutes. The gems are widely-used enough that they support most things you might need for whatever-they-do, and you probably won’t run into some feature that you really need but has been broken for two years and nobody realized it because nobody’s using that feature. (For the record, I’ve sworn off rails after seeing so many codebases that were total dumpster fires that I decided it attracts too many budget-minded-to-a-fault companies and owners for me to want to work with it again, plus I fucking hate ungreppable magical defined-nowhere metaprogramming symbols and magical imports that leave one unable to figure out WTF is happening without running the code, but I can see why it’s popular)
- phartenfeller 2y agoEven 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 and maintainable in the end.
- KronisLV 2y ago> 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?
- phartenfeller 2y agoYes, 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 https://forums.oracle.com/ords/r/apexds/community/home
- quotemstr 2y agoIs it me, or is that forum site very slow?
- bigfatkitten 2y agoA former employer of mine banned Microsoft Access, because they didn't want critical business functions running from random desktop machines. I imagine they'd take the same view today to home made LLM-generated Rails apps. They instead said "if you need to write your own little CRUD apps, use our APEX instance that we support and have backups for."
- brap 2y agoWas there ever a Node/TS alternative to Rails?
- sandruso 2y agoThere are maybe some but not as popular as Rails. I think everybody in node/js community advocated to build your own stack with libraries and write glue code yourself.
- miohtama 2y agoMany, but not yet as successful as Rails.
- gherkinnn 2y agohttps://adonisjs.com/ https://adonisjs.com/ Adonis.js is just that. I have never used it beyond a quick test though so I can't say what it is like in production.
- iforgotpassword 2y agoThis 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 code or anything.)
- weatherlite 2y agoYou 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.
- maximus93 2y agoLow 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.
- twen_ty 2y agoWhat is low code anyway in 2024? For example, is AWS Amplify or Firebase low code?
- jve 2y agoPower Apps https://www.microsoft.com/en-us/power-platform/products/power-apps https://www.microsoft.com/en-us/power-platform/products/powe... Uses excel and excel like formulas for stuff. Not bad for power users that can/want hack their app together.
- niam 2y agoPowerApps would not catch me endorsing it for anything beyond a year of use, however. Either a replacement needs to be on its way, or it's for a project with a defined end date. Otherwise, "there's nothing more permanent than a temporary solution".
- jve 2y agoI see low code tools are suitable for power users (citizen developer) and less for programmers (pro developer). Like a farmer hacking together some stuff for their needs instead of waiting for official solution. Power users automate their way to gain efficiency when programmers are busy doing their stuff.
- Sammi 2y agoAlso, is a headless CMS low code?
- user432678 2y agoSome managers at my current consultancy job think that ChatGPT is a low code solution worth selling to the customers as a service. I wonder if it’s a 4d chess approach to sell traditional programmers once clients realise that ChatGPT slop of code now needs way more than LLM-powered developers to maintain it.
- jokethrowaway 2y agoNo Code > Low Code > Large framework that does everything > Small framework > Library > No library Every item is faster to implement and less configurable than the next one. Until the set of features you need to implement fit your current choosen setup, you're good. If you need to dig deeper, you'll be in pain. You may get some relief with some hooks. I've experienced my fair share of pain with RoR, it's definitely not a magic bullet. I was amazed at things like Rails Admin a decade ago but overall it does way too much for what I typically need.My sweet spot is a low level server, eg. node.js + express (actually, rust + axum these days).
- Sammi 2y agoThere's a solution between low code and rails like frameworks, which is headless cms. You get most of the backend infrastructure pre-packaged, but you still get to customize the data model and data flow.
- glutamate 2y agoIf you are asking "well we could build this in 2 hours with low-code or 8 hours with rails" - then you are not the target market for low-code. To be able to build a rails app in one day takes years of skill and education and maturity. A lot of people or organisations want to build apps but don't have that expertise. Also, I don't see what is wrong with the outcome that at some point you have to rebuild with code. You have spent not very much time to develop a prototype that was able to get some feedback and come up with new ideas. Maybe that very revolutionary idea about the reservations app the author describes would never have imagined if they didn't have a prototype to play with? And don't even get me started on the risks of traditional software engineering. How many projects never even got to a viable prototype because devs decided to rewrite everything in flavour-of-the-month every 3 weeks?
- glutamate 2y agoAlthough i have to say i always found the concept of low-code silly. All code should be low code, and i think rails is actually a very good example of that.
- bryanrasmussen 2y ago> How many projects never even got to a viable prototype because devs decided to rewrite everything in flavour-of-the-month every 3 week this part sounds pretty fanciful, my experience is at the worst six months for new library in your chosen language, and that you can generally talk them out of; 1-2 years rewrite fever in some is almost overwhelming. on edit: in short I think even the least self-aware dev is not going to do rewrite cool new tech every 3 week, maybe once but not twice. So sounds a bit hyperbolical.
- glutamate 2y agoI admit it was an exaggeration for comic relief, but many projects have definitely not gotten to working prototype because devs wanted to use something fancy
- another-dave 2y ago> If you are asking "well we could build this in 2 hours with low-code or 8 hours with rails" - then you are not the target market for low-code. To be able to build a rails app in one day takes years of skill and education and maturity. A lot of people or organisations want to build apps but don't have that expertise. Exactly, low/no code solutions have their limitations, but I think the space they're useful for is — "they" need a simple CRUD app so they build it themselves in No Code solution, figure out what they really want & what the pain points are and _then_ bring on board a developer if it needs expansion, but with a real todo list in front of them. Or (just as useful to the business user), realise it's not what they need and bin the project before engaging a dev at all.
- rsynnott 2y ago... Wait, are 'low-code' things a _thing_, again? Thought those died out in the noughties.
- mkl95 2y agoRails / Django / etc. are already low code in the eyes of a Go / Rust / etc. developer. No need to stretch the concept, really.
- indymike 2y agoGreat software works well when it enables people to do things they could not before. Low code works well when the use case is isolated to something where you can focus on simplifying or putting training wheels on writing logic or configurations. When things get complex you end up with what amounts to Xcode or Visual Studio - something that clearly does help professional go faster. When you try to replace an entire language and multiple libraries with visual editor, you end up with something really complex, and often beyond your user's abilities to learn with the limited time/attention they have.
- october8140 2y agoI have experienced this just in the last year. Thank you for validating my feelings.
- aenis 2y agoMost existing front-end frameworks are already low-code by any standards, I'd say. Most backend, integrations, automations require some degree of business logic, which requires algorithmic thinking, and this in turns requires engineers - there aren't many people who 'think algorithmically' and can't code. Engineers, in turn, hate low code frameworks, as they are useless on the CV and annoying to work with for reasons mentioned by others here. Proprietary s*ht tech that always, inevitably, leads to custom code. And, it's expensive. We had mulesoft, outsystems, boomi and replaced it all with general purpose stuff shaving approx. 9M/yr in license costs. We have lost no velocity, and the great thing about the alternative (in our case: simply standardizing the toolset and going with GCP 'serverless' stack) is that its super easy to find devs who will willingly work on that. That hasn't been our experience with the low code frameworks.
- anonyfox 2y agoI don't know. I recently am drawn more and more in pure Go code, which is conceptually as simple as it gets, yet I can achieve basically everything imaginable in it without hitting walls/limitations. Add some (embedded) SQLite for small/quick/cheap things or postgres for when it gets more involved or critical (horizontal scaling, backups, ...), and everything is quickly possible. Now with LLMs, its outright trivial to make them generate functionality at will immediately, and (pure) Go is exceptionally friendly with LLM codegen, due to the language being stupid simple and the stdlib being "complete" for years. Essentially I prefer staying at the "you need to be a coder" abstraction level, but the general tooling nowadays makes becoming one very easy. Once you mentally lift the requirement that something needs to be configurable by some non-technical end user or even needs an UI at all, 90%+ of all dev effort can be saved directly. Plus there are no showstoppers in capabilities or usual barriers like too bad performance/config hell of "no code"/"low code" I encountered quite often. And if you don't use the latest webdev fads, things can be maintainable for decades (looking at Go compared to NodeJS). Rawdogging basic programming (yes, also no framework if possible) made more "business" projects first succeed (and then stay alive easily) much more than either a web framework or any kind of lo-/no-tool, at least the things I encountered in the wild. Even bad spaghetticode monstrosities can now uploaded to an LLM and refactored into sanity quite efficiently. The worst kind of projects (with lots of pain and regret) have been either JS-based, mis-used framework projects (including rails!) or Salesforce setups. Often you're stuck in a dead-end here.
- carsoon 2y agoSame thing I have settled on. Sqlite for quick and easy postgres for scaling. For simple frontends I just use the built in go templates. If I need complex frontends for larger apps I use sveltekit/svelte5 for frontend data I just export a single instance of a class that has state/derived fields for data and an isInitialized field that returns a promise for loading the data. Then methods for reloading data, changing data or any actions I need. So all i have to do is await classInstance then use the class data in whatever way I need. Everything is reactive and simple due to states. you can use and update the fields directly like regular js but with global reactivity built in. The data automatically loads the first time the module is imported. due to how esmodule files work. I just have a classInstance.LoadData() after the export. Svelte5 isn't as good with LLM's but with some small instructions about how states, derived, and effects work it works pretty well.
- deleted 2y ago[deleted]
- bobm_kite9 2y agoGood article but this misses the obvious - but slightly more distant - eventuality: the no-code vendor goes bankrupt meaning no further support or security fixes, or is bought out by some other firm which means exorbitant future licensing costs and no further features. Again, some people might not care about that but it seems kind of a biggie to me.
- cess11 2y agoI find Elixir and Phoenix have most of the niceties of RoR but a more rigid handling of databases with Ecto and very few of the drawbacks.
- deterministic 2y agoYou can turn any programming language into a super productive “low code like” development platform by adding the necessary libraries/frameworks. I personally use a code generator to generate more than 90% of the C++ and Javascript code that a typical biz client/server application needs. Protocols, Database support etc. Using libraries to do what isn’t application dependent. And when I occasionally (rarely) need a new feature not supported by the code generator or libraries, I simply add it as needed. I highly recommend building your own code generator/libraries. Yes it takes a bit more time up front, but you get a solution that is tailored and perfectly shaped to your (team) needs. And you don’t end up depending on some open source project that has been abandoned or changed in a direction that you don’t agree with.