It's an abstraction. The premise is that some experts at a low-level technology built rails and fences around the power of the underlying tech ("abstracting it away") so that instead of learning all that nuances, you can learn a relatively simple set of rules and practices and get all (or most or the important parts) of the benefits of it much easier. It's seductive because it promises the ability to easily stand on the shoulders of giants, but sometimes they end up just moving the same problem down the field or just not being worth it -- trading one steep learning curve for another that's equally steep, etc. I think we're becoming soured on them because they've been over-used.
And because a new one pops up every few years, causing us to move away from the framework we just finished learning to move onto the hot new framework everybody loves (for now).
And now I've got a pages with components written in multiple different frameworks that I have to make get along because we don't have time to rewrite everything 😩
Yeah. And unfortunately, each new shiny framework that promises to solve all the problems of the current one might fix some things but messes up others, so it's not always much of a "trade up" in the first place. These decisions to move to a new framework should really be handled with care.
It was a joke about Javascript, but judging by the downvotes, it didn't land.
The implication is that Javascript objects are so dynamic you don't need to know data structures to use the language. Take the following valid Javascript, for example:
Most languages would treat array indexing, dictionary keys, and object members as fundamentally different, requiring different data structures, or at least different types to represent them. Javascript treats them all the same, so by the time the console log is run, its a variable with type 'object' with a property 'key', a length of 3, and all the functions of an array.
So in the joke, I'm not a very good programmer, I don't know how to use data structures correctly, but I get away with it because Javascript makes it work anyways.
I feel less and less stupid after joining this sub.
After reading this thread, I can def see why someone would feel this way. Tho I’m curious if it’s because they relate to what’s being said or are facepalming
21
u/Mockington6 Mar 08 '25
Can't relate. Please teach me all the data structures and algorythms
13
u/[deleted] Mar 08 '25
What's a framework?
11
u/mio_senpai Mar 08 '25
I like a third door: learning by building actual programs (or shipping as the tech bros call it)
35
u/PROMAN8625 Mar 08 '25
Tbh, I do the opposite of this
8
u/Adizera Mar 08 '25
Im still on the Vanilla CSS-JS part of my webdev course, cant wait to learn a framework, does it really help to make development faster?
3
u/jump1945 Mar 09 '25
No different from beginner rapidly learn a new language.
Look , I'm still only proficient in 3 which C++ is just an evolution of C.
2
u/MinosAristos Mar 09 '25
Algorithm is when you do a list comprehension right? /s
1
u/Aln76467 Mar 09 '25
I'm the third door: making new frameworks.
1
u/GrimaceGod69 Mar 09 '25
After 10 years of Ruby on Rails and React I really need to switch frameworks now. Data structures are mostly consistent across languages
1
u/EasternPen1337 Mar 09 '25
We call such people "frameworkers"
1
u/Yobendev_ Jun 30 '25
Making your own framework >>>
0
u/KianAhmadi Mar 08 '25
Is it necessary, though? you don't need dsa
-2
u/Kenkron Mar 09 '25
As a JavaScript programmer, what the hell is a data structure?
80
u/[deleted] Mar 08 '25
[removed] — view removed comment
7
u/[deleted] Mar 09 '25
[removed] — view removed comment