![]() If you have a website that needs to be shared on social media and/or needs SEO then you need to serve html. Another unforgivable after thought was server side rendering. It led to N solution which seem to be rushed to the market. But truth is I always found lack of baked in state and route management completely ridiculous. No they are not they don't have the context and hooks right now. Anyways that's my short rant after fixing up a react app I made for a client before I knew about angular. You look at the code examples and think wow this is really elegant and simple this is great! Then about a dozen or so of those solutions stacked on top of each other (useEffect, contexts, redux etc.) and now you have this mess that almost feels like it will no matter what turn into spaghetti code. It has only become worse since hooks, difficult to parse and understand and difficult to get working exactly how you want them too. Not to mention react really doesn't offer many solutions to problems out of the box you have to use third party libraries for all that. I always come back to react every 2/3 months to see what is the hype I'm missing then I end up with an app that has maybe a dozen components and that even becomes a nightmare to manage. I work on a large app at work with team mates and there are hundreds of components now but we are able to split our code logically and work on pieces of the app individually as needed. I guess performance can be the real killer in angular but there are ways to optimize it. I guess it is the initial learning curve but once you get past that you realize almost every problem you run into angular has a solution and usually if you follow the general architecture they provide you don't even run into those problems. also waiting for new react like framework that does routing and state right from the get go.Įxactly this I don't really understand all the hate angular gets. Going back to class components, if functional component means this garbage. React code now reads like C -> # ? -> A F -> B->C When you are coding you wanna read code like so A->B->C same problem again complete disconnect on where it's defined, used, and imported. Hooks - with everyone rolling out their hooks, and O(N) hooks provided from react now you gotta memorize Idiosyncrasies of each hook function and write a thesis to get it. ![]() List of props grows exponentially and most of them are just passing through, deprecated or both or not even sure. so lets start with context.Ĭontext is defined in a file who knows where, gets imported in a while that is not using it but is passed to child component, oh LOOK "HOC", then code in children 10 levels deep finally access. you want to be able to follow code that others have written. When you develop, 80% time is spent reading other people's code. To me it's been downhill ever since hooks and context came out. /r/programmerhumor - (post your memes here instead)Ĭlickbait title./r/freelance (discussion related to freelancing)./r/learnjavascript (any JavaScript questions).Questions in violation of this rule will be removed or locked. Specific assistance questions are allowed so long as they follow the required assistance post guidelines. General open ended career and getting started posts are only allowed in the pinned monthly getting started/careers thread. Problem you are attempting to solve with high specificity.Research you have completed prior to requesting assistance.If you are asking for assistance on a problem, you are required to provide If you post such content on any other day, it will be removed. Sharing your project, portfolio, or any other content that you want to either show off or request feedback on is limited to Showoff Saturday. We do not allow any commercial promotion or solicitation. Please refer to the Reddit 9:1 rule when considering posting self promoting materials. Read and follow reddiquette no excessive self-promotion. Check out /r/ProgrammerHumor/ for this type of content. Specific issues that follow rule 6 are allowed.ĭo not post memes, screenshots of bad design, or jokes. For vague product support questions, please use communities relevant to that product for best results. No vague product support questions (like "why is this plugin not working" or "how do I set up X"). Beginner question? Try the FAQ first! or the WebDev Resources Post then post in the Beginner Questions thread.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |