MindHacker9009's Posts
Nairaland Forum › MindHacker9009's Profile › MindHacker9009's Posts
1 2 3 4 5 6 7 8 ... 16 17 18 19 20 21 22 23 24 (of 115 pages)
You are the illiterate that does not know that serious companies have never used your React crap so they have not reason to return to jQuery as they have always used jQuery. ReactExpress: |
ReactExpress:None because no serious company will use those crap new frameworks you and your brothers are using to mess up frontend development. |
You are the one that learnt nothing at school and when given a calculation will only use the minus key because to you all the other key are out dated. You are an illiterate that does not have a clue of what software analysis and design is all about, all you know are the crap new frontend framework your brothers tell you to use just to help them promote their crap. ReactExpress: ReactExpress: |
I'm not like you that talk from your ass and can only setup simple hello world apps with React. These are the kinds of projects I work on that React is of no use: 1. Enterprise-Level, Long-Lived Applications with Strict Stability Requirements 2. High-Performance, Low-Latency Real-Time Applications. 3. Large-Scale, SEO-Critical Websites (e.g., News, Blogs, E-commerce). 4. Apps With Limited or No JavaScript Support (e.g., Government, Accessibility-Heavy Apps) Sultan5: |
The creators of these new frameworks just want trend and because they control the tech space they have to use you and your brothers to push their crap new frameworks on every frontend project. With these new framework crap their moto is: Move Fast, Break Stuff, Release a New Version. When was React first released and now it has quickly reached version 19, yet those on version 18 cannot migrate to version 19, meaning they have to rewrite the front-end all over again before the can move away from the issues in version 18. For Long-term stability, tell your React brothers to move to jQuery and forget about the new framework mafias pushing their crop on every project. ReactExpress: |
This is what you and your brothers projects ends up like after using React: Over a year later, what started as a simple medical appointments platform has become a cautionary tale of modern software development gone wrong. The unnecessary complexity introduced by poor technological choices has led to delays, increased costs, and frustrated developers - exactly the problems I’ve outlined above. ReactExpress: |
You just want to code like an unqualified bricklayer that just wants to start laying blocks and saying the Architect does not know what his doing, just because his is a self taught bricklayer with degree a in chemistry and feels that's good enough to be a bricklayer. This is the reason Software Engineer is broken to pieces and need urgent regulation so that all programmers must have a professional qualification if programming that will include proper understanding of software Architecture to allow for long term maintainability. Karleb: |
You are the one that can't write frontend code to save your life. See how clueless you are not to know that Instagram is owned by Facebook the creator of React, so they will stay what the like to defend their React. You have now clue of what front-end development it, you are just following your brother above without know what you are doing. Sultan5: |
That's the problem where the mafias that have taken over tech, they don't get fired. The organisation will rather protect them and let the project fail than to get the mafias fired. Also these mafias will also try to bad mouth the qualified competent developers in their team and tried to make themselves look they are the ones that know how to do the work, they do this by asking for pair programming with a qualified competent developer. Many viable projects are being scraped because the mafias without CS,SE or CE are the ones in charge of most tech teams. Even with CS,SE or CE degrees a developer would still have to develop themselves with complex personal project to be able to aply the knowledge to their organisations complex projects in order to make them successful. Three or four years in uni studying computer science (CS), software engineering (SE) or computer engineering (SE) can never be acquired elsewhere, plus self development during and after uni. With regulation there will also be CPD, Continuing Professional Development to make sure that developer keep their knowledge up to date. Revealpanda: |
If you cannot read my comments then you should forever hold your peaces in ignorance. ![]() You mates that don't want to hear of jQuery are the ones adverting them not to use jQuery, just because they want to trend by saying they are using the latest frameworks, but does not want to admit that jQuery is better. Event the Hotwire/Turbo one of them have moved to still have these issues: Turbo aims to minimize JavaScript, but some applications with complex, dynamic interactivity may face challenges when trying to fully leverage Turbo’s model. Problem: Highly dynamic UI elements (e.g., complex forms or components with lots of interactive states) that rely on client-side JavaScript may not fit well with Turbo’s server-driven approach. Impact: It may require workarounds or introducing more custom JavaScript to handle specific interactivity that Turbo doesn’t naturally support. ReactExpress: |
Most tech jobs even at Google only want experience. And for those that do coding test, well passing a coding test most people can memorise is not barrier to entry. Google collaborates with university computer science departments worldwide through various research grants, funding programs and partnerships. These initiatives support academic research, PhD students and faculty members working on cutting-edge technology. So you need to know that Google does not joke when it come to their core technologies that's why they collaborate with computer science departments all around the world. Revealpanda: |
These companies have dropped or avoided your React, but because they are been misinformed by your mates they don't want to go back to jQuery, so they are going to still be dropping the new frameworks they have moved to. 1. Airbnb (Partial Rollback of React & React Native) Issue: Airbnb initially adopted React Native for mobile development but later abandoned it due to performance issues, integration problems, and developer experience challenges. What happened? Difficulty integrating React Native with native code. Slower performance compared to fully native solutions. Issues maintaining a unified React Native codebase across Android & iOS. Result: Airbnb switched back to native development but still uses React.js for their web app. Source: Airbnb Engineering Blog 2. Twitter Lite (Switched from React to Preact for Performance) Issue: Twitter initially used React for its lightweight mobile web app but faced bundle size and performance bottlenecks on low-end devices. What happened? React’s large bundle size (~40KB) slowed down initial load times. Increased JS execution time on slower devices. Twitter needed a more lightweight alternative to improve UX. Result: They switched from React to Preact, a smaller alternative (~3KB), improving load times and performance. Source: Twitter Engineering Blog 3. Instagram (Struggles with React’s Performance in Complex UIs) Issue: Instagram, owned by Meta (the creators of React), faced performance issues with React in their web app, especially with state-heavy components. What happened? Large component trees led to inefficient re-renders. Complex animations and interactions suffered from React’s reconciliation process. Memory usage spiked when handling extensive media content. Result: Instagram had to optimize React performance aggressively and introduced server-side rendering (SSR) and memoization techniques to handle the issues. Source: Internal reports & discussions from Instagram engineers. 4. Medium (Dropped React for Preact) Issue: Medium initially used React but switched to Preact due to performance and bundle size concerns. What happened? React’s large bundle size slowed down page loads. Heavy client-side rendering (CSR) caused delays in rendering content quickly. Result: Medium moved to Preact, which provided similar capabilities with a smaller footprint. Source: Developer reports & discussions. 5. Basecamp (Dropped React for Hotwire/Turbo) Issue: Basecamp (creators of Ruby on Rails) initially used React for dynamic UI elements but found it too complex for their needs. What happened? React’s state management was overly complicated for their architecture. Too much JavaScript overhead for an app that needed mostly HTML-based updates. Result: They switched to Hotwire/Turbo, a server-driven approach that minimized frontend complexity. Source: Basecamp Blog 6. GitHub Avoids React What happened? What happened? Slow initial page loads – React’s client-side rendering (CSR) required downloading and processing large JavaScript bundles before displaying content. High JavaScript overhead – GitHub’s UI is mostly static, and React’s reactivity system added unnecessary complexity. Performance issues on large repositories – React’s reconciliation process slowed down rendering complex diffs and issue threads. Security concerns – Using minimal JavaScript reduced the risk of cross-site scripting (XSS) attacks. SEO challenges – Server-rendered HTML ensured that GitHub’s content remained fully indexable by search engines. ReactExpress: |
Revealpanda:If Medicine, Pharmacy, nursing, Architecture, Structural Engineering, have no barrier to entry like Software Engineering same way you'll have mafias with no certs in these fields controlling those sectors. Sure you'll be thanking God too if that those fields were controlled by mafias with not certs in those fields. |
All these new frameworks you want to die on are all built on JavaScript and the creators are just after making a name for themselves rather than coming out with something as stable as jQuery that can handle any task properly. These are still the issues with the latest version of React 19 you want to die on: Migration Challenges – The React 19 migration tool has bugs, making it difficult to upgrade from React 18. Some issues stem from the new JSX transform. Suspense Behavior Changes – Suspense now prevents sibling components from pre-rendering, potentially causing performance issues due to sequential data fetching. Dependency Conflicts – Some third-party libraries, like @testing-library/react, are still optimized for React 18, leading to compatibility issues. Ecosystem Compatibility – Many React libraries and tools have not yet fully adapted to React 19, causing version conflicts and upgrade difficulties. ReactExpress: |
You and your mates using React for every project without doing analysis as to which framework is best, but just use React are the ones that are ignorant and continue to show pride in your ignorance. You still cannot describe projects you have worked on that jQuery cannot do. Even with version 18: These are still the Issues Not Fully Fixed in React: Performance Overhead in complex applications (deep component trees, frequent updates). Bundle Size and dependency-heavy applications. SEO challenges with client-side rendering (especially in dynamic apps). Memory Leaks due to improper cleanup. Overhead in simpler apps due to React's abstraction. Fragmented ecosystem and tool/library compatibility issues. Handling complex forms or large UI components with high performance. Unpredictable performance with Concurrent Mode. ReactExpress: |
You are just spilling out trash dues to your ignorance. Bringing in js signals mean you don't even know what you are taking about and you are the one that had problem with English at school. Let me lecture you on React you think you know but you are even ignorant of. In React, events like onClick, onChange, and onSubmit can be seen as signals. Here are the key Downsides of React on the Client’s Machine Increased initial load time due to large JavaScript bundles. Memory consumption for rendering complex UIs and handling state. Increased JavaScript execution time can cause slowdowns on lower-end devices. Dependency on JavaScript—no fallback if JS is disabled. SEO challenges without server-side rendering. Performance overhead on low-end devices or for complex applications. Difficult debugging in larger apps with deep component trees. Fragmented ecosystem of React libraries can cause incompatibility issues. Abstraction overhead can sometimes hinder performance for simpler apps. You are running away from my question to describe what projects you have used React for that jQuery cannot do but to hide you ignorance you are jumping around to show more of your ignorance. ReactExpress: |
It you that has a problem with using jQuery in 2025. I have asked you to describe the projects you have done with React that jQuery cannot do but instead you are jumping around with your ignorance. You do even know what JavaScript signals are. JavaScript signals can be just a click or keypress, but I was referring to advance JS signals like Signals in WebSockets. Shows you don't even know what all the different types of JS signals are. I mentioned programing languages as well as they are not different from choosing the right framework to use for a project, but you were ignorance of these example I made. You are the ones the blog writer is referring to that will just use a tool they only know for a project and will end up not being able to deliver the project or will deliver one that does not me the users needs. ReactExpress: |
So you mean because Fortran, C or C++ or Java or Ruby or VBScript are old means they should not be used anymore when there are new languages out now? This is the problem with the low barrier to entry in programming and the tech world, you see someone with a degree in maths, chemistry, biology etc or no degree at all but just a coding boot camp and they are all calling themselves Software Engineers. When the word Software Engineer should only be reserved for those with a degree in computer science or software engineering or computer engineering because these are the people who will first analyse a project requirement to determine which language and framework is best for the software application before they will begin to code. But those without these degrees will just use any latest language or framework just because it's the latest not knowing what type of projects they are good for. You can use React with JavaScript Signals for real-time updates. Means your don't even know much about React you are promoting here. In 2025 you can die on your ignorance not knowing when and what each framework is good for. ReactExpress: |
Revealpanda:But you are thanking God that mafias are the ones running the tech world. Having a computer science teacher come and tech someone at home is even better than what they will learn in a lecture room. |
ReactExpress:The blog post is not mine but I agree with many of his comments. You mentioned signals in JavaScript, so describe the projects you have done with React that jQuery cannot do? |
helinues:You are the one sounding like a kiddo, since you cannot use it on yourself, record it and post it on youtube |
emperor4love:There are camera phones now, you can record it and post it on youtube |
helinues:Test it on yourself with the ring, record it with your phone and post it on youtube. |
helinues:It's done through some secretive and masterful techniques |
helinues:Actual Explanation: There is a skilled performer inside, expertly maneuvering the masquerade while remaining unseen. Through secretive and masterful techniques, they create the illusion that the Zangbeto moves independently. |
helinues:There must be someone hiding inside! |
But this empty dancing structure in Benin Republic, who can explain it? https://www.youtube.com/watch?v=jyFByfd9qoE |
helinues:Like this fake one! https://www.youtube.com/watch?v=voFDNStzd9U |
Your useless takes will not allow you to know that Bill Gates got windows technology from Xerox, which was developed by computer scientists. Mark Zuckerberg's dad hired a computer lecturer to tech him programming when he was still in school so he already had a solid programming foundation from a lecturer. https://www.youtube.com/watch?v=pQocN_c2uLI Revealpanda: |
Now with camera phones why have all the black magic disappeared? |
Babtunz:True the blog writer is wrong on that one! The use of Kubernetes should the determined by the number of different operating systems the application will deployed to which will then require containerization and not by the number of developers in the team. |
1 2 3 4 5 6 7 8 ... 16 17 18 19 20 21 22 23 24 (of 115 pages)
Just because it has 3 dashboards.
