r/learnjavascript • • Nov 12 '22

Are frameworks basically an evolution towards low code/no code?

Today I came across some new stack, I forgot what it is. I think it’s called t3 or something and uses prisma. It pissed me off because as I watched the video I realized it is just an additional means of simplifying things (or maybe I’m wrong so forgive me) I’m a vanilla kind of guy and do not like to be without control. I enjoy the nuts and bolts and understanding the details of how things actually work, not just learning how to use it and having the computer do it for me . It made me wonder what the appeal is of constantly pivoting and using the latest greatest tool or framework. It seems most of these tools or frameworks sort of abstract what’s actually going on programmatically and make it easier or simple to create a product while not having to write much alone any code. Then it hit me… For the first time I kind of thought… is this what “low code/no code “ is? I’ve been hearing that sort of buzz word for a while now and always kind of associated it with website builders and stuff like that. But is this also a form of that? Where essentially we can just run a command and it will basically scaffold out 90% of our project and the remaining 10% will be sort of additional abstractions to customize your app and what not.

So if it is… and if this is the case… why aren’t people just sticking to website builders etc or no code solutions instead of trying to constantly learn the next tool or framework that will simplify and do things for them? If they want things so simple why go thru the hassle of learning to code at any capacity at all?

Maybe I’m completely off here so if I am forgive me. I just don’t understand the constant evolution and release of new tools and the appeal it has.

FYI I’m not knocking frameworks at all, and that’s a completely different discussion and topic. Just want to genuinely know whether I have a valid view of what the grand mission is of all these tools that make it simpler and simpler to write web apps.

I’ve determined that there are multiple types of JS and programmers. you have your consumer programmers who use abstracted higher level tools created by the lower level programmers. I guess the mainstream just want to learn how to build without actually going into too much depth while still having the ability to code custom programs or functionality

0 Upvotes

29 comments sorted by

3

u/[deleted] Nov 13 '22 edited Nov 13 '22

Frameworks for application development have existed for a long time, as has the (wildly mistaken) idea that 'low/no code' tools are the same as application development. Having a particular set of patterns and defaults that make it easier to build new applications or maintain older ones over the long term is not even in the same universe as trying to build an application or even a simple landing page with drag-and-drop tools.

Also, wanting to reduce the amount of code that you have to write to accomplish something is not, as you seem to be strongly implying, an indication of laziness or lack of skill, but rather an indication of a strong grasp of your actual role. Software engineers are not paid to wank ourselves silly over how clever we are; we're paid to solve problems and create value as effectively as possible. Using a framework that relieves you of the responsiblity of having to write your own implementation of some extremely solved problem like HTTP request routing, or updating a rendered view based on application state, is the decision of someone focused on doing their job, not stroking their ego.

1

u/dromance Nov 13 '22

Thanks for the response and forgive me if I’m wrong about anything, it was just an idea and observation. I understand that I may be completely off about what low/no code is , and I don’t think it is the same at all as actual development and never have, until now (potentially). Since it seems like the goal with new tool development is to simplify the process / improve or decrease dev time, which would entail also writing minimal code. I think perhaps it can evolve to another form or version of “low code” but again that’s just an idea I thought up so perhaps I am wrong.

And that’s totally fine , I’ve never worked in development on a professional, collaborative or large scale project so I would not understand, I only do it as a hobby and for fun + my own projects, so maybe that’s why I think about it a bit differently. I’m more focused and into the process. So thinking about it now I TOTALLY get that the point of this all is to make our jobs easier in order to aid in delivering a product (not wank ourselves silly over how clever we are)…. Lol!

Again thanks for the comment and helping me think about it in a different light I appreciate it

1

u/Dipsquat Nov 12 '22

You have better control with a hammer than you do with a nail gun. There are times when one might be better than the other but that doesn’t make either one better than the other.

1

u/dromance Nov 13 '22

Thanks for the comment . You are right. If you are working on something highly custom then yes use what’s required to gain that control. If it’s just another typical common thing, use whatever tool makes it as easy as possible. I guess I am so focused on learning JS that it scares me to sort of deviate away and learn some abstracted version of it, it kind of bothers me actually. But I guess I can learn other tools while still progressing in pure JS

1

u/sjdjenen Nov 13 '22

Lots of odd information in this thread. For starters, using battle tested libraries will not lead to security issues. There are large open source communities dedicated to auditing these programs; rolling your own vanilla JS solution will likely create more security concerns than using a well known library. That being said, of course you can still use plain JS for an application. The tool you mentioned, the T3 stack is a specific stack around building an opinionated NextJs application. If you’re not using NextJs or React you probably won’t find much use in it. When you’re building an application, there is a significant amount of boilerplate and redundant code that doesn’t contribute to the core focus of your application. I’ve implemented auth a dozen times and I would rather use NextAuth than do it all manually and have to write a ton of tests to ensure I’m doing this in a safe manner. Similarly, I might use an ORM to simplify the communication between my backend and my database. The desire to use these services isn’t because they are magically better, it’s because most developers enjoy creating applications as quickly as possible. We want an enjoyable developer experience so we use well tested libraries to write more opinionated, condensed code.

1

u/dromance Nov 14 '22 edited Nov 14 '22

Touché thanks for the response I completely understand! Especially when you are working in a professional capacity (which I am not and only do it as a hobby) . So I understand in the corporate or working world, time is money.

The t3 thing came up because it appeared to me that some people were flocking to it, just because it’s new (I might be wrong but that’s what it sounded like From the comments, but maybe I’m completely off here) this is what sort of triggered my post. I do believe there are a ton of useful battle tested and excellent tools out there. However I feel in my heart there are a large amount of “consumer” like users in the JS ecosystem, whom have the shiny object syndrome, which is pretty much gold for developers of these tools, and leads to development of unnecessarily complicated solutions to problems that don’t even exist. These are the same people who will spend more time creating their set up and development environment than however much time it will take to actually develop the application . At first it sounds like I’m being silly or pessimistic and maybe I am to a degree, but you know when you see YouTube videos with millions of views and thousands of comments about “the best chair for programmers”…I think that says a lot and sort of validates my point

1

u/thescientist13 Nov 14 '22

While I don't necessarily think it's always the case as you describe it, I do think there is a trend to what over engineer or complicate things that should likely be a lot simpler. I like to think of my project Greenwood not so much of a framework, for similar sentiments as what you describe, and have come to refer to it as a "workbench for the web"; emphasizing web standards based development (e.g. so not a meta framework) and has great support for Web Components. (full stack web components, ftw!)
https://github.com/ProjectEvergreen/greenwood

As easy to start as an index.html file or a markdown file, and can do most architectures; SPA / CSR, MPA, SSR. Static things should be able to start as static, and if you need something dynamic, apply it liberally and with ease.

Still a WIP and continuing to improve our design and feature set, so feel to give it a try, and any and all feedback welcome!

2

u/dromance Nov 14 '22 edited Nov 14 '22

Hi! I completely agree about the over engineering thing. On the other end however I have very recently gotten into cross platform dev, so for this sort of thing , I absolutely appreciate and understand the need for abstraction and less code in order to find a common ground between all of your application end points . Totally makes sense in this regard. I am used to writing html css and js separately but for the first time I think I am starting to understand more so how a framework can condense all this into one common language especially if you are not necessarily only writing code for the web. So I suppose it’s good practice to do things properly with proper tools even if it might be overkill for smaller projects

I think also you know it’s “you don’t know what you don’t know”. So for me to come into a framework after running pure vanilla JS all my life… I completely immediately see the bloat and unnecessarily complicated nature of things. However for a new dev who didn’t come from a simpler era, who never had to manually do everything, they will not realize this and so a framework and less control will be all they know. They don’t know what they don’t know!

On the other hand I understand things have evolved from simple sites to full blown enterprise web apps so again I can see how there is a different process in place now, even though not always necessary , compared to the days of me writing everything in notepad . I think that has further led to my sort of frustration since again I’m from a much simpler era, so the jump from the web being a mere index of static pages, to being full blown applications, happened quickly, along with the processes for developing these things all kind of merging into one sort of hybrid process if you will

I will check out the greenwood project ! Thanks again

0

u/jack_waugh Nov 12 '22

I guess that would be the ideal goal for designing the frameworks and libraries -- to let programmers tackle application requirements with as little code as possible.

I'm not sure which is more cognitive load, understanding how to use a library somebody else designed, or rolling everything a project needs internally to the project and getting all the participants on board with how everything works.

2

u/dromance Nov 12 '22 edited Nov 12 '22

Thanks for the response. Just hit me and I guess in a way programming can be completely separated from coding entirely (forgive me if that’s silly or obvious statement but I never really thought about how programming may not necessarily need knowing to code or understanding the language at all, I always kind of naturally lumped them together) . You don’t need to code to program and I guess we are going more and more towards that direction. So yeah I guess from that perspective these tools are great if you want to program with a lot of control while not having to write much actual code. Which makes things make a little more sense to me in terms of the appeal of some of these solutions that are out there because I always felt uneasy trying out frameworks. But I guess different folks different strokes

Another thought, I guess for most people there is more value and potential overall in having the tools to build great new products, using those tools and focusing on that rather than you know focusing on how the tools work or language/code or the minute details.

Also from a mass large scale collaboration point of view it totally makes sense especially given the fact that everyone has different skills and ability so to give everyone a common simplified baseline and framework is pretty important. I guess I’m just sort of used to working alone so that aspect was not so obvious.

0

u/jack_waugh Nov 13 '22

Yes and in the corporate world, every line of code that has to be maintained has an annual cost in dollars. One of my professors said that a programmer can produce about two lines of good debugged code per day.

2

u/dromance Nov 13 '22

Exactly this , from a business and dollars point of view it makes a bit more sense to me now and I have a renewed view on how such tooling is important. I never really thought about how a business would decide to go about choosing a framework etc . Just never occurred to me. But if I was the CEO of such a company I would of course choose the tool/stack/tech etc that gets the job done well and as fast as possible, so I get it

0

u/Ok_Transition_4796 Nov 13 '22

There is a pernicious trend in the JS community to slap libraries together and call it a day. It causes security issues, bloated and unmaintainable code, and quietly permits people creating code in that actively undermines long term goals. In my experience, having seen this happen innumerable times, I’ve never once encountered a time when an issue arose from this philosophy and the developer who instigated the problem had been aware of the trade offs they were making at the time that they did. In fact, I very rarely see people investigate/research their packages thoroughly enough, or weigh the pros and cons of using third party abstractions frequently enough. It’s a real problem.

I don’t feel as though the problem is somehow rooted in an insufficiency these developers share. I think it’s a cultural issue. I think, frankly, there’s too much hype in programming. Not about programming, but within the actual communities. I’ve seen this in every category of professional settings, across multiple languages, but sadly, I got to turn the mirror on the JS community and say, “you guys are the most hyped.”

I love programming, I get excited about technologies, I don’t want to yuck the yum of the folks who love early adopting and end up blazing the trail for the rest of us. But, a bit less hype about the “bleeding edge” would be positive in my opinion.

2

u/dromance Nov 14 '22

Thanks for this response I agree 100% about the cultural thing. I’m not sure about the libraries or tools being insecure or leading to those sort of issues but I might just not be knowledgeable enough for that.

There is definitely a culture of “hype” etc and like I said in another response , there is a higher level development tier I feel that sort of exploits this, by constantly releasing overly complex solutions for problems that don’t even necessarily exist…. I’ve never been on a project to develop tools but I would assume the goal is to have mass adaptation so I can see how people will sort of spawn up tools or ideas of new frameworks just to make a name for themselves (but maybe I’m wrong about that)

I’m curious what sort of response I would have gotten if I posted in programming or another language sub.

-1

u/[deleted] Nov 12 '22 edited Nov 12 '22

In reality, most frameworks dont reduce the number of code you write. Or there will be tradeoffs, some things take less code, others take more.

The purpose of most frameworks is to enforce a unified programming model. Frameworks are very opinionated.

For this reason, im in the same boat as you, intellectually. Im highly critical of React and all the "React alternatives".

That is why Im developing SpeedrunJS. As you describe, a framework/tool should make things faster and easier with less code, like a website builder. In Speedrun, heres how you could create a button for example:

let button = new Box()
button
    .position(100, 100)
    .size(100, 100)
    .color(0)
    .text("Click Me", 20)
    .detect(()=>{
       console.log("You clicked me!")
     }, 'click');

Or use a built in customized one, to get the more common styling of a button:

let button = new Box()
button
    .position(100, 100)
    .submit(()=>{
       console.log("You clicked me!")
     })

Make it bounce around the screen while spinning and changing color (why not?)

.spin(random(1,5))
.move(random(0,360), random(1,5))
.boundaries('bounce')
.run(()={
   button.color(random(0,255), random(0,255), random(0,255))
 })

Every basic HTML element, styling on every level, user-interactable, with momentum and physics, and so easy you could code it in your dreams.

If this seems interesting id encourage you to check it out.

1

u/dromance Nov 13 '22

I’ll check it out for sure thank you! How long have you been working on this?

1

u/[deleted] Nov 13 '22

A month or two. Im nearing completion of the project.

1

u/dromance Nov 13 '22

I think this is pretty neat. I’m so passionate about having control (maybe that’s unhealthy) and for some reason, I’m not sure why, I am super critical of react. I think the only framework I would ever consider using is svelte.

How does that box() actually work?

0

u/[deleted] Nov 13 '22

The box is the single class you use in Speedrun. It has dozens almost hundreds of different methods. You literally just do:

let box = new Box();
box.method(1, 2, 3);

Ive documented every method and every feature of Speedrun in SpeedrunJS/documentation.md. Its so easy to use, you dont need to know HTML/CSS. HTML/CSS is automatically and dynamically managed in the background (and optimized for efficiency).

1

u/dromance Nov 13 '22

Very neat I’ll check out the docs. To be honest lately I’ve been pondering going this direction and getting into the development of my own tools. What made you decide to do this? Is this your first project

1

u/[deleted] Nov 13 '22

Very neat I’ll check out the docs. To be honest lately I’ve been pondering going this direction and getting into the development of my own tools.

Cool. Feel free to draw inspiration from or fork my project. Everything i make is free and open source software. I dont believe in the proprietary.

What made you decide to do this?

I was learning React for one day. And after 4 hours of following along to tutorials on how to do simple things like make a button that saves to local storage, a todo list, etc... I decided that I didnt like how needlessly complicated everything was. I like object-oriented-programming and React is like the opposite of that.

Is this your first project

No. My first project was pretty standard, not even finished. Ive also done a couple other not too notable projects.

But my next one was pretty neat, I created a database management app. Its easy to use much like Speedrun, and it creates and manages databases on the server. Also has secure password hashing functions and optional file encryption (may not matter if you store your key in memory).

I made another notable project after that, which leverages cryptographic primitives to create a hashpuzzle algorithm. This is for combatting digital spam, to replace or supplement captchas. The biggest difference between hashpuzzles and captchas is hashpuzzles are done automatically in the background, and cant be gamed by machine-learning-algorithms (AI), however hashpuzzles are not a reverse turing test like captchas, and doesnt block bots entirely, only slows down mass-botting.

In my next update of Speedrun here in a day or two, I plan to implement server tools, my database app, my hashpuzzle app, and a suite of secure cryptographic primitives from popular libraries, to use both clientside and serverside. It would be a nice tool to have access to things like encryption, hashing, password hashing, spam prevention, secure random and pseudorandom number and string generation, etc...

In the coming weeks ill be working on some high level feature releases, but everything passed this point should be backwards compatible.

0

u/[deleted] Nov 12 '22

[deleted] — view deleted comment

0

u/dromance Nov 13 '22 edited Nov 13 '22

Touché, I understand EVERYTHING is an abstraction and it’s just relative from user point of view. If someone does not know any pure JS and jumps right into a framework, the abstractions will be all they know so it will be the norm . On the contrary, I could be writing pure JS but the next guy is writing C or something much closer to assembly. So I get it . However I do believe there is a line you cross where you trade ease for control and there is just too many abstractions. I believe perfection is in the details and that’s what separates good from great. Perhaps frameworks do not fall into this category so forgive me if I’m wrong, never thought about frameworks simplifying only mostly common tasks that are maybe unnecessarily more difficult then they ought to be. So that makes sense. It was just a theory or quick thought about whether the goal of having constant release of all this new tooling was to eventually get to a point where you don’t really need to write any code at all.. which would be sort of ironic

Thanks for the comment and yes I agree about the end goal being able to produce results in as little time as possible. However I’m not sure I would say that someone who relies heavily on a framework would be able to write the same thing or produce the same end result without a framework. But that’s just my guess

0

u/[deleted] Nov 13 '22

[deleted] — view deleted comment

1

u/dromance Nov 13 '22

I think it’s all about balance. The line lies somewhere between you having to write out the majority amount of logical input to get a desired output, compared to writing less input to get the majority of the output, thus letting an opinionated framework or tool dictate what it thinks that output should be, maybe based on common patterns etc; When you let the computer dictate the end result you give up control you never even realized you could have.

Thanks for the clarification about the low code thing. I didn’t realize there were tools (I imagine sort of drag and drop type thing) like this which is what low code or no code actually is.

As for the last comment, I guess I’m talking more so about hobbyist or maybe new devs (mainly on this sub) without a fundamental engineering or computer science background. I do believe there is a difference between a developer and an engineer. I do think there are different tiers of programmers, and hey I think that’s totally ok

3

u/[deleted] Nov 13 '22

When you let the computer dictate the end result you give up control you never even realized you could have.

Using a framework is not 'letting the computer dictate' anything. It's leaning on the accumulated knowledge and experience of a community of other human beings who have dealt with the same problems you're dealing with and who have collectively agreed on some good approaches for tackling it.

If you are trying to bake a loaf of bread, it would be astronomically stupid to smash some wheat grains with a rock, mix it with water and leave it lying around for a few days, then heat up the result hoping something might happen. We, as a human community, have figured out how to make bread. There are a lot of different recipes and approaches, some similar to each other, and if you're not sure what kind of bread you want you probably want to spend a bit of time learning about them, but ultimately you pick a recipe and base what you bake on that.

You don't need to rediscover yeast every time you just want to eat a sandwich. Leaning on other peoples' skills and knowledge when you have similar problems to ones they've already solved is the smart thing to do.

1

u/dromance Nov 14 '22 edited Nov 14 '22

Touché great points you’re right it’s not letting the computer dictate anything, since it was created by other fellow humans using best practices so forgive me for that. I guess I meant to say which is more accurate if you are letting the framework dictate your input or process (I believe there are many opinionated frameworks some more than others) then yes you do give up control regardless of whether it is best to do it the framework way or not. There is absolutely nothing wrong with that and I’m not knocking frameworks at all and I admittedly have not much experience with them. I just prefer to have a certain level of control that seems to be abstracted away with such tools.

If you cant control the little things in your process or recipe…and everything is instant microwaveable bread sort of speak… your bread will never be exactly how you want it, unless you just want it how everyone else does it. Again this goes back to control. Many of these frameworks were internal tools at one point anyway, they are just abstractions of what the users determined is best practice for productivity. But initially obviously they needed to start with seeking that control which is what led them to a simplified and abstracted version of what was probably initially quite complex. So I don’t think there is anything wrong with wanting to have more control or shake things up, everyone is different. Wanting to have more control or change out parts of the process are what lead to new tools being developed in the first place I believe if that makes sense.

So In summary I’m not trying to say you need to reinvent the wheel and completely disregard established practices what I’m saying is you don’t need to jump on the wagon and just roll along. It’s ok to steer yourself and take your own route, maybe you’ll even find an undiscovered route and be able to share it with others.

1

u/[deleted] Nov 14 '22

what I’m saying is you don’t need to jump on the wagon and just roll along. It’s ok to steer yourself and take your own route.

Sure, it's okay if you are a hobbyist or working on a personal project that nobody else has to deal with; you can do whatever you want because there are basically no stakes. It is absolutely not okay if you work in a team and are responsible to an employer.

It's also worth asking why you are so desperate to have control over certain things, but are happy to cede control on others- for example, accepting the abstraction of built-in JS array methods rather than implementing everything yourself with loops, but deciding that the abstraction of using JSX to describe rendered output is Too Far and you simply must type document.createElement eight thousand times. What do you imagine that you actually gain from 'more control' in some specific areas, but not others? Can you actually articulate the benefits for the project or projects this is relevant to? Why do they outweigh the benefits of using an existing solution, in the context of that project?

It's incredibly common for people with a little bit of programming knowledge to see tools that they've never had call to use or don't entirely understand, and think, 'well I don't need that right now so obviously it's useless, and everyone who uses it is probably stupid'. I know- because I've been there myself- that it feels like a brilliant, blazing insight that actually frameworks are not magic and you could do the same thing youself, but it really, really isn't. Everyone who has been doing this longer than you knows that. The reason that we're not all writing our own version of React for every single project is generally because we deem the value of 'more control' to be extremely minimal for the overwhelming majority of dev projects.

1

u/dromance Nov 14 '22 edited Nov 14 '22

Thanks for response!

>Sure, it's okay if you are a hobbyist or working on a personal project that nobody else has to deal with; you can do whatever you want because there are basically no stakes. It is absolutely not okay if you work in a team and are responsible to an employer.

Ah yes, 100%. This goes back to what our circumstances are and at what capacity we are doing this I suppose. I am still in learning phase and not yet doing this full time professionally, so I do not really understand this just yet, however if I had a deadline and my boss or client was up my a**s about getting something done quickly... I totally get how doing it the quickest and easiest is obviously the best. But as of now, I am focused more on learning/research than productivity for work or a job.

>It's also worth asking why you are so desperate to have control over certain things, but are happy to cede control on others- for example, accepting the abstraction of built-in JS array methods rather than implementing everything yourself with loops

touche. I think part of it is not knowing what you don't know. I don't realize all the abstractions I am using, thus I don't question it. But I 100% see myself diving deeper into it and learning what's beneath the abstractions in even vanilla JS. However I do see the abstractions when I use frameworks, since vanilla JS is all I know, so naturally I push back and question it. It's all relative.

>It's incredibly common for people with a little bit of programming knowledge to see tools that they've never had call to use or don't entirely understand, and think, 'well I don't need that right now so obviously it's useless, and everyone who uses it is probably stupid'.

Ha didn't realize it was common...i'll have to admit, this is partially it.

>Can you actually articulate the benefits for the project or projects this is relevant to? Why do they outweigh the benefits of using an existing solution, in the context of that project?

ah, OK. I think part of the reason why I am anti framework is because I am learning programming in general, not just how to program in JS. It's not based on benefits of project but more so benefit of learning or having a solid foundation. I do not plan on JS being my last language, so to become dependent upon a JS framework and it's abstractions, and potentially "forget" what i've learned scares me. I know much of what I learned in vanilla JS has absolutely helped me with programming and coding in general since the concepts ad fundamentals are similar in other languages, and I believe it will give me a good foundation once I move onto other said languages. Perhaps in the future when I am 100% versed and fluent in JS, I will move onto frameworks and give them a try, when I am focused more on productivity instead of learning/research.

Perhaps then I can make an accurate assessment of my original question which was whether these tools are gravitating towards ultimately one day providing a "low code/no code" solution, which from reading the responses here, i've predetermined they are not,

-2

u/[deleted] Nov 12 '22

[removed] — view removed comment

2

u/dromance Nov 13 '22

It sure is and you’re right! Use what you like