What I hate, and increasingly so the more experience I get, is the bandwagoning around new tech/ideas. I work with frontend development, I don't mind most javascript frameworks and I work with React at my current job. But the idea that everyone has to replace everything whenever something new happens is exhausting. Lately it's micro frontends. No, our product doesn't need to be split into feature level chunks served individually in s all over our site and bloating our bundle sizes, just because you're annoyed that we currently only do a realease once per month. Our architecture and deployment model is ass. Let's fix that before we start adding 10x complexity for 5% extra flexibility.
@@lufenmartofilia5804 Almost worse is existing tech completely rewriting itself every mayor version so you have to redo a lot of stuff to be able to update something.
For real, and everybody already knows they screwed the economy because they only do what they can, I don’t get these points either and it’s not like we had to do anything to prove the point
Something which bugs me is that frameworks often solve medium-term problems, which leaves you in the world of having arbitrary stuff injected into your build, but also having to work around and behind the framework to address issues the framework doesn't accommodate. It sure is a hard problem, but having 9 similar things solving the easier bits of similar problems is worse for the developer than if those same people threw their time into making one or two options handle deeper issues.
This is the problem with all frameworks. I first encountered this with MFC (Microsoft Foundation Classes). It solved some problems but it made others harder as we had to work around its limitations. Be very sure the framework you are using actually helps you before adopting. It will always have downsides, so be sure that its upsides are worth it first.
As person who grew up on PHP, mootools and jquery - React is pretty cool if you don't bloat it. JS on the backend on the other hand - oh boy. Just give me Rails or Laravel and let's start building actual product.
Honestly I like the "its the same bit smaller and faster" libraries. Except that for web its not leaner and faster and they often just change one shit architecture to an other - so it is a subfield skill-issue not a general problem to be honest :D
no, I started my current job having never used react or nextJS. I spent a week building a small clock app then proceeded to migrate a nextjs app over to our infrastructure and am now the main dev on it. If you understand programming concepts and are willing to dive into new stuff, you can learn most of this on the fly, at least to a good enough level that you can build something that works
I think it helps not learning something before it is something you need. So if suddenly all the jobs you are interested in requires HTMX then you should learn it, but why before unless you want to for its own sake.
Except calling it an issue of protecting employability deflects from the real problem, which was encapsulated quite well in the notorious meme of when (IIRC) React first came out and there were suddenly anecdotes of job listings asking for years of React experience. It's not about whether the dev _actually_ has knowledge or experience in such a niche specialized architecture (which, more often than not, is usually just a subset framework or library of an overarching programming language) it's that _the decision to even ask or require that specialization either in the job listing or in the project itself_ was almost certainly made by someone ignorant of the thing itself and ultimately detached from the day-to-day coding (e.g. HR, marketing, or a one- or two-degree-separated project manager) based on second- or third-hand info rather than by someone in the trenches doing the actual programming. On top of that, these decisions can often be made without consideration for what kind of development workflows and tooling are required of these technologies; React, Angular, etc ultimately require Typescript compilers and bundlers, anything Java requires Eclipse or better to dev and some Java runtime (usually Apache Tomcat/Ant) to actually run the thing, etc, and office workstations then have to be provisioned for these dev environments, often strictly and with little to no flexibility depending on company policy. And that's not even including the extra nonsense that some demand because they think they're too special to just drop into a folder and source as is, Typescript stuff included.
It’s a recognition that a large portion of the work done by established tech companies is essentially a Ponzi scheme. A new tech company stands up a new software product or service and from then on, the work is just reskinning the same product. That’s where the framework fatigue comes in. You know that switching between these new technologies won’t have a significant impact on your product. You know it won’t dramatically improve the business. The only thing it does it excite investors that want to see “real” tech work and innovation. The truth is that American tech companies haven’t done any real innovation in over a decade. And the developers know that. They know that reskinning a 15 year old app with the latest web-dev fad is a consolation prize. Sorry buddy. You were too late. This isn’t Berkeley in the 90s. This isn’t Silicon Valley in 2005. It’s 20 years later. You are the new Detroit. You are the fords and chevys that got fat on their monopolies and have gone soft.
I work serverside, and need to maintain a small maintainance UI. We run Jquery, and that's just about it. Our experiment with Angular was a failure. We spent more time satisfying the framework than building the whole thing with just jquery for dependency. React is a little better in that regard, but not better enough to consider introducing it. All we need are a few displays, nobs, dials, buttons and text fields that trigger commands to the big java server. It's been really surprising how little support there is for that.
My experience with his story at the end. Over Xmas 2023 I worked on a new product for the job without being asked to solve a problem they had for years and allowing them to monetize the product, I've been told for hundreds of thousands. I was told good job, it was then given to a different dev, and I was put on a shit job and when my annual review came, I was only given a 2% raise.
Frameworks solve someone else's problem, not yours. The time you save by not "reinventing the wheel" on the common as dirt parts you tend to spend 10x over trying to get custom logic into a framework designed to solve someone else's problem. That said, I don't have a solution for businesses that hire based on popular buzzwords other than "you'll probably hate working there anyway."
Yes BUT the changes in gorilla/http were so much better than the stdlib in terms of support for trailing slashe, URL params (not in stdlib originally) etc. that when gorilla abandoned the project, the standard library actually learned from the framework and pulled in all those features, they got merged into the stdlib. we have gorilla to thank for url params today.
It seems like new versions keep coming out and you either have to constantly upgrade or wait and be in upgrade hell. There are so many software components that are sewn together we have a lot of CVEs to take care of. It seems to be never ending.
I like the framing of "outrun your employer". If you have some conviction, you have to invest your own time to get it rolling. Don't be that guy whining that things should be different and you are never given time to fix it. Be a problem solver, not a problem.
The reason experienced devs get annoyed by new tech is that having to learn it is a tax on their time. The old tech they know ALREADY does what new tech promises to do.
IMHO the reason experienced devs get annoyed by it is that it's just always the same shit, different coat of paint. I'm expected to put in my own time to learn some new crap that does the same shit the old crap did and in 2 weeks it's the same thing again. After 20 years of this, I just roll my eyes and yes I'm fucking annoyed at the suggestion we should keep doing it. I'm not saying never look at anything new ever again, but there better be at least a half decent reason. "Shiny new toy" just doesn't cut it.
The problem is that it is _so, so difficult_ to test for competency with interviews. You can test for a very basic level of competency (can actually program at all) but finding actually good developers without just asking for prior experience is a difficult task.
@@Turksarama So do a 60/90 day trial period, and actually let go of those who don't cut it in 60 days. Companies used to do this on the regular, now for some reason if you hire someone you're stuck with them until an act of congress happens.
@@Justin73791 you don't hire someone, getting them to quit their previous job, maybe relocate, totally upending their life, unless you are PRETTY SURE they're going to pass the probationary period. Those 60/90 days are there to catch major oversights in your hiring process, not as a convenience so you don't have to learn how to interview properly.
This clown cares about you as much as he cares about Casey Muratori bare metal bullshit! He just spew whatever is trending. People wake up and don’t follow entertainers!
What are you talking about? Humans change their minds and if you stream a lot you'll find people jostling ideas back and forth, that's how opinions form. Prime switched from Rust to Go or whatever and it isn't because of what's trending he has an informed opinion because of it.
i am using vanilla go and do not know what is the framework, i do not see a point to use them, they do not really bring something new, just a syntax sugar or +/- 10% orf performance and calling something like js framework - "a new tech" is so laughable. "a new js lib" or "a new bunch of js scripts" would work just fine p.s. there is a big difference comparing C language with Zig language and comparing 2 JS frameworks between each other. One of this cases is called an evolution, the other one is called - wanking
I’m so glad I decided not to become a SWE. You guys are absolutely insane for dealing with the constant “new” frameworks, libraries and the like. It’s literally just busy work.
Another reason for raging over new frameworks: does not solve a real problem or is just a minor improvement over the existing stuff - while requiring radically different ways of writing code or having to refactor all existing code to fit a new model - all for some *minor* improvements. Also, New JS Framework frequency vs AnyLanguage New Framework frequency is VERY different, and much less of an issue.
The question is what kind of technology i want to use if i just want it to run for the next 20-50 years without having to change my code but still updating
I have zeroed my mind to 5 years minimum and 10 years maximum. And since that is now becoming a rare thing, I have chosen to start sticking to old tech/frameworks/tools so long they are not older than 5 to ten years after reaching deprecation state or after being officially unsupported. It has helped me keep my sanity and given me more peace of mind. While I keep studying, I don't worry about learning all the latest things anymore.
What really gives me fatigue in the tech world right now isn't the new frameworks per say, I need to actively select a framework, so it's up to me to do that choice. My real annoyance is the JS semantic versioning trend going on that says: minor version is a patch, major version may contain breaking changes. The breaking changes part wastes so much freaking time for me. I do a lot of maintenance work on already existing systems, and we certainly don't want to prematurely slide our systems into the area of legacy code where none of the packages has been updated for 5 years. That means that at some interval, things needs to be updated. Which means tons of broken packages with changes I don't give a crap about. Sigh. New version of the framework may require other packages to be updated, breaking changes. If the breaking changes where significant then I can understand this, but many times they're not, it's just that some package maintainer thought, "oh, we can do this thing this way, that will 'look better', so we'll do that in next major version" hence me wasting hours on unnecessary BS. I do wonder sometimes how many hours we combined waste on things like this. Breaking changes should be RARE. In Linux they have a rule: "DO NOT BREAK USER SPACE", perhaps a tad bit extreme for packages, but the general idea that it should be avoided as much as possible would make life easier for all of us. We don't just use your package, we use many different packages. Breaking changes for minor reasons is a huge waste of everyone's time. I've recently gone through a horrible maintenance cycle dealing with this, hence this rant.
Probably due for Microsoft to release another Incompatible XAML framework. Drives me nuts, I loved WPF. It’d impossible to keep up with all the other versions.
Mainly I feel like JavaScript libraries/frameworks move too quickly. When you use other languages and see how slowly things change, the JavaScript world feels almost nauseating by comparison. The node projects we have at my job feel like they’re in a constant state of needing to be refactored just so they can continue to keep their frameworks/libraries up to date. The Python/php/perl code just doesn’t feel like that.
Yep. And if you do not intend to immerse yourself in that fully, it's a complete waste of time to even look at it, because anything you do with it will be obsolete by the time you look at it next. I do not enjoy running in a hamster wheel that is the result of someone else's bad design and lack of foresight.
New tech that solves a type of problem for a new generation of programmers, to where it already exists a solution. Who really needs 20+ types of version controll?
i love the idea of "leading the employer". i've gained lasting favor with my superiors by building a solution, in the way that **I** wanted to build it. some (maybe most) will see your initiative, reward you, and let your proceed. however, there is always the possibility that they don't like it, and you will have "wasted" that time. i've had both scenarios happen to me. fewer of the latter the farther i've gotten in my career. it's a developing skill to read your managers and seniors.
Not os much new tech as much as "My glossary is b3773r than your glossary" software. Here is how I expect a creator is pitching: My marketing consulting firm told me to tell you that the service fixes your life crisis by using these buzz words and throwing my magic operators - I mean hand signals - at your screen and best of all, I don't even know what a service is. And better yet, to save space on your 16KB drive, the functions are abrevated like m-10-rox-bg-audio which is similar to THAT other software, but this one places a div in the center (pinky promise). Sometimes there are some solid languages and frameworks, but I feel like it is long between and not beneficial to be an early adopter.
it is not fully-fledged and has just too narrow purpose that probably not many people will need, especially if there are so many other websocket libs, so yeah, Primagean is right not releasing it, i would have done the same.
What I hate, and increasingly so the more experience I get, is the bandwagoning around new tech/ideas. I work with frontend development, I don't mind most javascript frameworks and I work with React at my current job. But the idea that everyone has to replace everything whenever something new happens is exhausting. Lately it's micro frontends. No, our product doesn't need to be split into feature level chunks served individually in s all over our site and bloating our bundle sizes, just because you're annoyed that we currently only do a realease once per month. Our architecture and deployment model is ass. Let's fix that before we start adding 10x complexity for 5% extra flexibility.
You are saying this on a channel that literally surf on the people that thirst for new tech and cool trend. 😂
I am totally with you on this.
@@lufenmartofilia5804 Almost worse is existing tech completely rewriting itself every mayor version so you have to redo a lot of stuff to be able to update something.
that other tech influencer theo gg is the embodiment of that person. he has a very punchable face too which makes it even worse
Okay but have you heard of HTMX? You can use it alongside hyperscript and Alpine.js.
It's not tech, it's just someone's crap library, of which there's a billion and a billion more on the way, i'm not angry i just don't care
For real, and everybody already knows they screwed the economy because they only do what they can, I don’t get these points either and it’s not like we had to do anything to prove the point
Yeah calling all libraries tech is generous af
Something which bugs me is that frameworks often solve medium-term problems, which leaves you in the world of having arbitrary stuff injected into your build, but also having to work around and behind the framework to address issues the framework doesn't accommodate. It sure is a hard problem, but having 9 similar things solving the easier bits of similar problems is worse for the developer than if those same people threw their time into making one or two options handle deeper issues.
This is the problem with all frameworks. I first encountered this with MFC (Microsoft Foundation Classes). It solved some problems but it made others harder as we had to work around its limitations. Be very sure the framework you are using actually helps you before adopting. It will always have downsides, so be sure that its upsides are worth it first.
"Designing and Evaluating Reusable Components (2004)" is a great start if you still believe libraries/frameworks are inherently costly to work with
"Super easy barely an inconvenience", deep meta cut.
Ryan George references are TIGHT!
Wow wow wow. Wow.
angery at "new" tech for getting the exact same results but with a convoluted twist and overhead like React.
Compared to what?
As person who grew up on PHP, mootools and jquery - React is pretty cool if you don't bloat it. JS on the backend on the other hand - oh boy. Just give me Rails or Laravel and let's start building actual product.
@@hungrybeaverontheleaver laravel mostly
@@hungrybeaverontheleaver wondering about the overhead part?
cgi-bin
Honestly I like the "its the same bit smaller and faster" libraries. Except that for web its not leaner and faster and they often just change one shit architecture to an other - so it is a subfield skill-issue not a general problem to be honest :D
It makes finding jobs harder. Do we really need to “know” all this shit
no
no, I started my current job having never used react or nextJS. I spent a week building a small clock app then proceeded to migrate a nextjs app over to our infrastructure and am now the main dev on it. If you understand programming concepts and are willing to dive into new stuff, you can learn most of this on the fly, at least to a good enough level that you can build something that works
I think it helps not learning something before it is something you need. So if suddenly all the jobs you are interested in requires HTMX then you should learn it, but why before unless you want to for its own sake.
I get mad at new tech thats only been out for 6m but recruiters want 5 years of experience in said tech
Except calling it an issue of protecting employability deflects from the real problem, which was encapsulated quite well in the notorious meme of when (IIRC) React first came out and there were suddenly anecdotes of job listings asking for years of React experience. It's not about whether the dev _actually_ has knowledge or experience in such a niche specialized architecture (which, more often than not, is usually just a subset framework or library of an overarching programming language) it's that _the decision to even ask or require that specialization either in the job listing or in the project itself_ was almost certainly made by someone ignorant of the thing itself and ultimately detached from the day-to-day coding (e.g. HR, marketing, or a one- or two-degree-separated project manager) based on second- or third-hand info rather than by someone in the trenches doing the actual programming. On top of that, these decisions can often be made without consideration for what kind of development workflows and tooling are required of these technologies; React, Angular, etc ultimately require Typescript compilers and bundlers, anything Java requires Eclipse or better to dev and some Java runtime (usually Apache Tomcat/Ant) to actually run the thing, etc, and office workstations then have to be provisioned for these dev environments, often strictly and with little to no flexibility depending on company policy. And that's not even including the extra nonsense that some demand because they think they're too special to just drop into a folder and source as is, Typescript stuff included.
It’s a recognition that a large portion of the work done by established tech companies is essentially a Ponzi scheme. A new tech company stands up a new software product or service and from then on, the work is just reskinning the same product. That’s where the framework fatigue comes in. You know that switching between these new technologies won’t have a significant impact on your product. You know it won’t dramatically improve the business. The only thing it does it excite investors that want to see “real” tech work and innovation. The truth is that American tech companies haven’t done any real innovation in over a decade. And the developers know that. They know that reskinning a 15 year old app with the latest web-dev fad is a consolation prize. Sorry buddy. You were too late. This isn’t Berkeley in the 90s. This isn’t Silicon Valley in 2005. It’s 20 years later. You are the new Detroit. You are the fords and chevys that got fat on their monopolies and have gone soft.
I'm so happy we're back to articles
omg why he keeps highlighting paragraphs with offset of 1 from both sides
to farm comments like this one
It's his personal off-by-one error
We got Ryan George mentioned
I work serverside, and need to maintain a small maintainance UI. We run Jquery, and that's just about it. Our experiment with Angular was a failure. We spent more time satisfying the framework than building the whole thing with just jquery for dependency. React is a little better in that regard, but not better enough to consider introducing it. All we need are a few displays, nobs, dials, buttons and text fields that trigger commands to the big java server. It's been really surprising how little support there is for that.
My experience with his story at the end. Over Xmas 2023 I worked on a new product for the job without being asked to solve a problem they had for years and allowing them to monetize the product, I've been told for hundreds of thousands. I was told good job, it was then given to a different dev, and I was put on a shit job and when my annual review came, I was only given a 2% raise.
I don't get angry. I get even. By not using the language or framework. Hence, I don't touch javascript. Brother ewww.
me
Frameworks solve someone else's problem, not yours. The time you save by not "reinventing the wheel" on the common as dirt parts you tend to spend 10x over trying to get custom logic into a framework designed to solve someone else's problem. That said, I don't have a solution for businesses that hire based on popular buzzwords other than "you'll probably hate working there anyway."
Resume driven development.
so bro actually went the harem way and chose both zig and jai. terrific.
Yes BUT the changes in gorilla/http were so much better than the stdlib in terms of support for trailing slashe, URL params (not in stdlib originally) etc. that when gorilla abandoned the project, the standard library actually learned from the framework and pulled in all those features, they got merged into the stdlib. we have gorilla to thank for url params today.
It seems like new versions keep coming out and you either have to constantly upgrade or wait and be in upgrade hell. There are so many software components that are sewn together we have a lot of CVEs to take care of. It seems to be never ending.
I like the framing of "outrun your employer". If you have some conviction, you have to invest your own time to get it rolling. Don't be that guy whining that things should be different and you are never given time to fix it. Be a problem solver, not a problem.
a lot of people just like to complain and not do anything. it is better to work together with people to solve problems than complain
The reason experienced devs get annoyed by new tech is that having to learn it is a tax on their time. The old tech they know ALREADY does what new tech promises to do.
IMHO the reason experienced devs get annoyed by it is that it's just always the same shit, different coat of paint. I'm expected to put in my own time to learn some new crap that does the same shit the old crap did and in 2 weeks it's the same thing again. After 20 years of this, I just roll my eyes and yes I'm fucking annoyed at the suggestion we should keep doing it.
I'm not saying never look at anything new ever again, but there better be at least a half decent reason. "Shiny new toy" just doesn't cut it.
Screw learning tech just to pad resumes. Employers should hire for competency but they are so lazy
The problem is that it is _so, so difficult_ to test for competency with interviews. You can test for a very basic level of competency (can actually program at all) but finding actually good developers without just asking for prior experience is a difficult task.
@@Turksarama So do a 60/90 day trial period, and actually let go of those who don't cut it in 60 days. Companies used to do this on the regular, now for some reason if you hire someone you're stuck with them until an act of congress happens.
@@Turksarama this is what coding tests are for. But everyone moans about those, too, unfortunately.
@@Justin73791 you don't hire someone, getting them to quit their previous job, maybe relocate, totally upending their life, unless you are PRETTY SURE they're going to pass the probationary period. Those 60/90 days are there to catch major oversights in your hiring process, not as a convenience so you don't have to learn how to interview properly.
@@BittermanAndyI actually really like coding tests. My problem is that it's hard to do after a long day of work, but I do enjoy them.
I am still using vanilla js and php. I'm doing great 👍🏻
This clown cares about you as much as he cares about Casey Muratori bare metal bullshit! He just spew whatever is trending. People wake up and don’t follow entertainers!
What are you talking about? Humans change their minds and if you stream a lot you'll find people jostling ideas back and forth, that's how opinions form.
Prime switched from Rust to Go or whatever and it isn't because of what's trending he has an informed opinion because of it.
i am using vanilla go and do not know what is the framework, i do not see a point to use them, they do not really bring something new, just a syntax sugar or +/- 10% orf performance
and calling something like js framework - "a new tech" is so laughable. "a new js lib" or "a new bunch of js scripts" would work just fine
p.s. there is a big difference comparing C language with Zig language and comparing 2 JS frameworks between each other. One of this cases is called an evolution, the other one is called - wanking
I’m so glad I decided not to become a SWE. You guys are absolutely insane for dealing with the constant “new” frameworks, libraries and the like. It’s literally just busy work.
Another reason for raging over new frameworks: does not solve a real problem or is just a minor improvement over the existing stuff - while requiring radically different ways of writing code or having to refactor all existing code to fit a new model - all for some *minor* improvements.
Also, New JS Framework frequency vs AnyLanguage New Framework frequency is VERY different, and much less of an issue.
The question is what kind of technology i want to use if i just want it to run for the next 20-50 years without having to change my code but still updating
Unrealistic expectation
I have zeroed my mind to 5 years minimum and 10 years maximum. And since that is now becoming a rare thing, I have chosen to start sticking to old tech/frameworks/tools so long they are not older than 5 to ten years after reaching deprecation state or after being officially unsupported. It has helped me keep my sanity and given me more peace of mind. While I keep studying, I don't worry about learning all the latest things anymore.
Use WinAPI, build 32bit windows binaries targeting Windows XP.
@ cars from 1975 still run
some software from then is actually still running as well
What really gives me fatigue in the tech world right now isn't the new frameworks per say, I need to actively select a framework, so it's up to me to do that choice. My real annoyance is the JS semantic versioning trend going on that says: minor version is a patch, major version may contain breaking changes. The breaking changes part wastes so much freaking time for me. I do a lot of maintenance work on already existing systems, and we certainly don't want to prematurely slide our systems into the area of legacy code where none of the packages has been updated for 5 years. That means that at some interval, things needs to be updated.
Which means tons of broken packages with changes I don't give a crap about. Sigh. New version of the framework may require other packages to be updated, breaking changes. If the breaking changes where significant then I can understand this, but many times they're not, it's just that some package maintainer thought, "oh, we can do this thing this way, that will 'look better', so we'll do that in next major version" hence me wasting hours on unnecessary BS.
I do wonder sometimes how many hours we combined waste on things like this.
Breaking changes should be RARE. In Linux they have a rule: "DO NOT BREAK USER SPACE", perhaps a tad bit extreme for packages, but the general idea that it should be avoided as much as possible would make life easier for all of us. We don't just use your package, we use many different packages. Breaking changes for minor reasons is a huge waste of everyone's time.
I've recently gone through a horrible maintenance cycle dealing with this, hence this rant.
Should be titled (JavaScript) Framework Fatigue.
Probably due for Microsoft to release another Incompatible XAML framework. Drives me nuts, I loved WPF. It’d impossible to keep up with all the other versions.
Mainly I feel like JavaScript libraries/frameworks move too quickly. When you use other languages and see how slowly things change, the JavaScript world feels almost nauseating by comparison. The node projects we have at my job feel like they’re in a constant state of needing to be refactored just so they can continue to keep their frameworks/libraries up to date. The Python/php/perl code just doesn’t feel like that.
Yep. And if you do not intend to immerse yourself in that fully, it's a complete waste of time to even look at it, because anything you do with it will be obsolete by the time you look at it next.
I do not enjoy running in a hamster wheel that is the result of someone else's bad design and lack of foresight.
I tend to release source-only, no packages for things I won't maintain just so others can clone, experiment, and learn from it.
All good, but now I feel challenged to write a RESTful app using CSV for communication...
RYAN GEOOOORGGEE!!!!!!!!!!!!!!!!!!!!!!!!! reference.
Wow wow wow wow wow
New tech that solves a type of problem for a new generation of programmers, to where it already exists a solution.
Who really needs 20+ types of version controll?
i love the idea of "leading the employer". i've gained lasting favor with my superiors by building a solution, in the way that **I** wanted to build it. some (maybe most) will see your initiative, reward you, and let your proceed. however, there is always the possibility that they don't like it, and you will have "wasted" that time. i've had both scenarios happen to me. fewer of the latter the farther i've gotten in my career. it's a developing skill to read your managers and seniors.
Solid 4 minutes before reading a world of the article 😂
I hate when they take something optimized and perfect. Then replace it with something bloated and slow that requires extra steps.
C# mentioned. les go
Not os much new tech as much as "My glossary is b3773r than your glossary" software.
Here is how I expect a creator is pitching:
My marketing consulting firm told me to tell you that the service fixes your life crisis by using these buzz words and throwing my magic operators - I mean hand signals - at your screen and best of all, I don't even know what a service is. And better yet, to save space on your 16KB drive, the functions are abrevated like m-10-rox-bg-audio which is similar to THAT other software, but this one places a div in the center (pinky promise).
Sometimes there are some solid languages and frameworks, but I feel like it is long between and not beneficial to be an early adopter.
This reminds me I gotta migrate our app off CRA at some point.
Hate all the breaking changes of dependencies. They really need to minimize that.
Hey! You also watch Ryan George Pitch Meetings:) Haha. Watch the Megalopolis one! Absolutely amazing
LOL Pitch Meeting is tight!
Am i the only one who can't here anything? Do you have sound?
New crappy frameworks never ready to do any actual work previous tech could do with as many bugs.
If you compare to other frameworks / libraries of same level, sure. If you compare to vanilla js, absolutely no.
What is vanilla js, but the most flexible library of them all?
just do the opposite of what prime said you will be living a good life :D
why was this posted here tho
he got too distracted playing wow. jk I don't know why either.
Flip consulted the crystal analytics ball
Well, you're here so stfu
lol Prime not releasing his websocket implementation means it doesn't work
it is not fully-fledged and has just too narrow purpose that probably not many people will need, especially if there are so many other websocket libs, so yeah, Primagean is right not releasing it, i would have done the same.
I love new tech 💙
Enough Notepad++. Time for Notepad#
hey flip! Its wrong channel
javascript is jovian af
just use java bro