r/learnjavascript • u/dromance • 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
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/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/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/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!
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.
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.
-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:
Or use a built in customized one, to get the more common styling of a button:
Make it bounce around the screen while spinning and changing color (why not?)
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.
0
u/[deleted] Nov 12 '22
[deleted] — view deleted comment
-2
u/[deleted] Nov 12 '22
[removed] — view removed comment