Just reached 100+!!

Anyhow. I started coding prettymuch 365 days ago. My mate decided to launch his company and figured it was a good idea to start it with good friends who knew fuck all at coding.

Fyi, the dude can code 15 hours straight everyday for about a year (no shit thats what i saw).

Since he taught me html css javascript(even if i still suck abit at js). He made me remake the whole bootstrap in react by adding this new lib styled-components and test everything(95% coverage :)).

He also taught me webpack and rollup. Json schma forms，http requests redux， redux logic， and all the routing shit...he obliged me to i plement RR4 on release and is now making me overlook the merge requests of my other collegue (yes he made me a git pro，almost).

And now i have to work long distance by studying java， spring， oauth2 and start working on our api.

O yeah，and i went from microsoft to full on linux!!!

To be honest i thought i was gonna die this year. (Also have a kid on the way :)).

Devrant has been like going to the psychologist :) everytime shit hit the fan i realized every one has the same problems :)

Thanks to the community i can also now even give out nerd jokes :)

(L)Devrant

You know who sucks at developing APIs?

Facebook.

I mean, how are so high paid guys with so great ideas manage to come up with apis THAT shitty?

Let's have a look. They took MVC and invented flux. It was so complicated that there were so many overhyped articles that stated "Flux is just X", "Flux is just Y", and exactly when Redux comes to the stage, flux is forgotten. Nobody uses it anymore.

They took declarative cursors and created Relay, but again, Apollo GraphQL comes and relay just goes away. When i tried just to get started with relay, it seemed so complicated that i just closed the tab. I mean, i get the idea, it's simple yet brilliant, but the api...

Immutable.js. Shitload of fuck. Explain WHY should i mess with shit like getIn(path: Iterable<string | number>): any and class List<T> { push(value: T): this }? Clojurescript offers Om, the React wrapper that works about three times faster! How is it even possible? Clojure's immutable data structures! They're even opensourced as standalone library, Mori js, and api is great! Just use it! Why reinvent the wheel?

It seems like when i just need to develop a simple react app, i should configure webpack (huge fuckload of work by itself) to get hot reload, modern es and jsx to work, then add redux, redux-saga, redux-thunk, react-redux and immutable.js, and if i just want my simple component to communicate with state, i need to define a component, a container, fucking mapStateToProps and mapDispatchToProps, and that's all just for "hello world" to pop out. And make sure you didn't forget to type that this.handler = this.handler.bind(this) for every handler function. Or use ev closure fucked up hack that requires just a bit more webpack tweaks. We haven't even started to communicate to the server! Fuck!

I bet there is savage ass overengineer sitting there at facebook, and he of course knows everything about how good api should look, and he also has huge ass ego and he just allowed to ban everything that he doesn't like. And he just bans everything with good simple api because it "isn't flexible enough".

"React is heavier than preact because we offer isomorphic multiple rendering targets", oh, how hard want i to slap your face, you fuckface. You know what i offered your mom and she agreed?

They even created create-react-app, but state management is still up to you. And react-boierplate is just too complicated.

When i need web app, i type "lein new re-frame", then "lein dev", and boom, live reload server started. No config. Every action is just (dispatch) away, works from any component. State subscription? (subscribe). Isolated side-effects? (reg-fx). Organize files as you want. File size? Around 30k, maybe 60 if you use some clojure libs.

If you don't care about massive market support, just use hyperapp. It's way simpler.

Dear developers, PLEASE, don't forget about api. Take it serious, it's very important. You may even design api first, and only then implement the actual logic. That's even better.

And facebook, sincerelly,

Fuck you.

I AM SO FUCKING TIRED OF BUSINESS MOTHERFUCKERS USING TECHNICAL FUCKING BUZZWORDS LIKE THEY KNOW SHIT ABOUT TECH! THEY TRY TO BE FUCKING SMARTASSES AND ARGUE WITH DEVELOPERS LIKE GOD KNOWS WHY THIS FUCKING DOUCHE IS NOT THROWN IN /dev/null YET!

Ugh. He try to sound smart and argued with a unity game developer why the dev is not using "react" and "redux" in his game, purely because "since its the hype in 2016"... I was like really nigga?? FOR FUCKS SAKE Do some research before you say! Then he argued with a senior full-stack web developer on why they're using ES6 and not ES7, purely because he heard that ES7 is newer. When we try to explain we're not using decorator syntaxes since we use pure functions in our codebase, or how we haven't installed any ES7 babel plugins to transpile our code, he kept saying ES7 is newer and cooler and we must use it somehow... More to rant but i am fucking tired right now...

Here is a tutorial on how to create a contact form in React / Redux.

!rant

I built a decently large project at work, and everything works perfectly. It's beautiful, it's fast, it's light, it's organized and clean, and deploying is a breeze. I'm very proud of it.

The biggest reason, though, is that it uses exclusively technology I had never touched before:
• React
• Redux
• ES6/Babel
• Webpack
• Express.js
• Material Design
• Apple lappy (I'm a linux girl)

I was completely new to all of these, including my dev machine. Every single aspect of the project was outside my skillet.

But it went from my first experimental `import React from 'react'` to production-ready in three weeks. I'm really proud 😊

So I put a very strict eslint configuration to a 6 month old project
..
..
..
..
924 errors in 27 files
..
..
..
..
..
I removed eslint from the project

Please make an entire webshop with animated shopping cart in react + redux within a week 👍

We will then reject you for the position and thank you for rewriting our tech stack for the frontend 😂 K THX BAIII

true story

Miss those days when web development used to be easy...

Now the react, react-router, redux, server-side-rendering, redux-form and nodejs...making me crazy.

And oh how can you forget the fucking webpack.

Someone please kill me.

Background: I'm not drunk yet, BUT I'M WORKING ON IT.

okay.

I just finished a second sprint on my React app. The first was to build a merchant onboarding flow. The second was to do substantial cleanup as I learned more about react/redux, and to create a "supply order" flow -- basically purchasing marketing materials and services. I finished that in a week, and I'm pretty proud. api-guy wanted it done in a day. i laughed. he probably could have, but it would have been a copy of the code in a new repo with some lines changed.

ANYWAY. it's all done and It's super pretty and works amazingly well. It has both the onboarding flow and the ordering flow, with a nice pop-out sidebar for navigation, namespaced actions, etc. Everything is pretty clean. I even added a cart to the ordering (despite everyone telling me not to) because wtf, what if someone wants to order TWO items? dumbasses. So I made that. it's sexy.

Anyway, it's all done and shiny and fancy and wonderful and I'd *love* to share screenshots if only it didn't give away where I worked. :<

... but the point of the rant!

After the first sprint, I made a copy of the repo so I could rework it and add more functionality without touching the original. (Hey! That's what a branch is for, right? Why didn't I branch it up?
well, read on)

I knew we were going to have multiple separate flows for this app: onboard, ordering, merchant tools, admin tools, support, etc. So, I wrote its server portion (the webpack builder + http server) so it would serve the same app at whatever url the user hit, and set a cookie containing that host+url. This allows the app to serve different content (basically showing/hiding content) based on the URL and future login roles. If someone hits /order, it would hide everything but the order flow. If they're a merchant, it would show all the merchant views plus ordering, etc.

tl;dr This way I can use the same codebase for multiple sites, drastically simplifying development, branding, and what have you. This new app could obv also be a drop-in replacement for the original onboarding project because of the above.

HOWEVER. this apparently isn't good enough for api-guy. He's terrified that adding/updating future components will affect all the existing content somehow.

so.

now we have three repos for basically the same codebase. 1) onboard aka "surfboard", 2) ordering, 3) merchant tools, aka "ferrari" (the "future" app).

Except.
1) "surfboard" is a very old version of the code. 3) "ferrari" is also old, since 2) "ordering" has newer content in it now.

... and somehow this is better?
fuck if i can figure out how.

His reasoning is "well, you won't be touching surfboard or ordering for 6 months, so now you don't have to worry about it." Sure, except, you know, it'll be a pain in the ass in 6 months now when I have a crapton of code and branding to redo. ffs.

Oh. We also have three Heroku pipelines for these three repos. for the same codebase.

and now you know why i'm drinking.

preface: swearing.
because anger.

So. I'm trying to use Material Design with Material UI. The components and UI look *great*.

It's from google, though, which really pisses me off. but I like what I can do with the UI.

HOWEVER.
I really want a grid system for responsiveness. because obviously. besides, i really hate doing all the responsive shit myself. it sucks and i hate it.

Material Design does not include a grid system. okay, it includes a grid component, but it's not for site layout. it's for making a grid of images. or something.

What it does include is a lot of very lengthy documentation on what you should do, complete with fancy graphics saying "THIS IS HOW YOU MUST DO IT OR YOU'RE DOING IT ALL WRONG" -- but they don't actually support it! you must do it all yourself.

Why oh why would they tell you how you must do things if they don't provide the tools to make it possible? fucking google.

You might decide it's a grand idea to interject at this moment and say: "there are plenty of tools out there that allow you to do this!" And sure, you'd be right. however -- and i think this might just barely might be worth mentioning -- THEY REALLY FUCKING SUCK. Hey, let's look at some of the classes! So clear and semantic! This one was nice and simple: "xs4" -- but wtf does that mean? okay, it apparently means 4 columns as they'd appear on an extra-small layout. How does that work on a large layout? Who knows. Now, how about "c12"? okay, maybe 12 columns? but how does that display on a phone with a layout small enough to only have 4 columns? i don't know! they don't know! nobody knows!

oh oh oh oh. and my particular favorite: "mdc-layout-grid__cell mdc-layout-grid__cell--align-bottom" WHAT. THE. FUCK. I'm not writing a goddamn novel! and that one claims to be from google itself. either they've gone insane or someone's totally lying. either way, fuck them.

SO. TERRIBLENESS ASIDE.

Instead of using Material Design v0.fuckoff that lacks any semblance of a grid layout, I figure I'll try v1.0 alpha that actually has one supported natively. It's new and supports everything I need. There's no way this can't be a good idea.

The problem is, while it's out and basically usable, none of the React component libraries fucking work with it. Redux-Form doesn't work with it either because it doesn't understand nested compound controls, and hacking it to work at least triples the boilerplate. So, instead, I have to use some other person's "hey, it's shitty but it works for me" alpha version of someone else's project that works as a wrapper on top of Redux-Form that makes all of this work. yeah, you totally followed that. Kind of like a second-cousin-twice-removed sort of project adding in the necessary features and support all the way down. and ofc it doesn't quite work. because why would things ever be easy?

like seriously, come on.
What i'm trying to do isn't even that bloody hard.

Do I really have to use bootstrap instead?
fuck that.

then again, fuck this significantly more.

UGH.

My friend and boss，told me he would teach me code 2 years in a half ago.

I didnt know what css or html was and i used to call java javascript.

I can know create my own module with webpack， have my automated doc， use react， redux， he taught me linux， git，unit testing， databases，docker， and so on...

Im not an expert in any of it butbi know what they are for and can play with them more or less comfortably.

The best advice he ever gave me was:

“coding is not about coding. We are like the greath painters of history. They were great at painting but even more at creating. If you have no creativity， you can paint as well as you want， its worthless.”

I'm editing the sidebar on one of our websites, and shuffling some entries. It involves moving some entries in/out of a dropdown and contextual sidebars, in/out of submenus, etc. It sounds a little tedious but overall pretty trivial, right?

This is day three.
I learned React+Redux from scratch (and rebuilt the latter for fun) in twice that long.

In my defense, I've been working on other tasks (see: Alerts), but mostly because I'd rather gouge my freaking eyes out than continue on this one.

Everything that could be wrong about this is. Everything that could be over-engineered is. Everything that could be written worse... can't, actually; it's awful.

Major grievances:
1) The sidebars (yes, there are several) are spread across a ridiculous number of folders. I stopped counting at 20.
2) Instead of icon fonts, this uses multiple images for entry states.
3) The image filenames don't match the menu entry names. at all. ("sb_gifts.png" -> orders); active filenames are e.g. "sb_giftsactive.png"
4) The actions don't match the menu entry names.
5) Menu state is handled within the root application controller, and doesn't use bools, but strings. (and these state flags never seem to get reset anywhere...)
6) These strings are used to construct the image filenames within the sidebar views/partials.
7) Sometimes access restrictions (employee, manager, etc.) are around the individual menu entries, sometimes they're around a partial include, meaning it's extremely difficult to determine which menu entries/sections/subsections are permission-locked without digging through everything.
8) Within different conditionals there are duplicate blocks markup, with duplicate includes, that end up render different partials/markup due to different state.
9) There are parent tags outside of includes, such as `<ul>#{render 'horrific-eye-stabbing'}</ul>`
10) The markup differs per location: sometimes it's a huge blob of non-semantic filthiness, sometimes it's a simple div+span. Example filth: section->p->a->(img,span) ... per menu entry.
11) In some places, the markup is broken, e.g. `<li><u>...</li></u>`
12) In other places, markup is used for layout adjustments, such as an single &nbsp; nested within several divs adorned with lots of styles/classes.
13) Per-device layouts are handled, not within separate views, but by conditionally enabling/disabling swaths of markup, e.g. (if is_cordova_session?).
14) `is_cordova_session` in particular is stored within a cookie that does not expire, and within your user session. disabling it is annoying and very non-obvious. It can get set whether or not you're using cordova.
15) There are virtually no stylesheets; almost everything is inline (but of course not actually everything), which makes for fun layout debugging.
16) Some of the markup (with inline styling, no less) is generated within a goddamn controller.
17) The markup does use css classes, but it's predominately not for actual styling: they're used to pick out elements within unit tests. An example class name: "hide-for-medium-down"; and no, I can't figure out what it means, even when looking at the tests that use it. There are no styles attached to that particular class.
18) The tests have not been updated for three years, and that last update was an rspec version bump.
19) Mixed tabs and spaces, with mixed indentation level (given spaces, it's sometimes 2, 4, 4, 5, or 6, and sometimes one of those levels consistently, plus an extra space thereafter.)
20) Intentional assignment within conditionals (`if var=possibly_nil_return_value()`)
21) hardcoded (and occasionally incorrect) values/urls.

... and last but not least:
22) Adding a new "menu sections unit" (I still haven't determined what the crap that means) requires changing two constants and writing a goddamn database migration.

I'm not even including minor annoyances like non-enclosed ternaries, poor naming conventions, commented out code, highly inefficient code, a 512-character regex (at least it's even, right?), etc.

just.

what the _fuck_

Who knew a sidebar could be so utterly convoluted?

I went on an interview was given an algorithm to solve, solved it in 30 mins and they had allocated 20 mins for it. So I guess I suck. I build shit, I don't do algos that often so I'm obviously rusty.

interviewer: so why should we hire you over a CS graduate.

me: cause I can get shit done.

... akward silence

interviewer: what do you mean by that? like html and CSS?

me: as you can see, I have built large scale real-time web apps with React/Redux (the stack they supposedly use and the position they're hiring for!) the knowledge I have is practical, it can't be learned from books, and it can't be learned from a course. Only building, breaking and rebuilding over time will teach you this knowledge. So essentially a CS grad, who hasn't committed the same amount of hours as I have, can't possibly match me. But they probably can better explain the real world applications of using linked lists...and won't have to Google what Pascal's triangle is like I had to....

interviewer: I see. we will be in touch.

lol well I guess they'll be in touch..

From my last job interview (which I got hired btw)

Lead developer: "so we see quite a lot of frameworks that you listed for php, Laravel,cakephp, codeigniter, we really like the idea of them but have not had the opportunity to use them since as you might know by know our pages run over basic and small scripts, you also listed some cool front end frameworks, react looks amazing and I do have somr experience. Tell me, if given the choice, which framework would you use for php?"

Me: Really depends on the project, but the ones that you have described previously seem that they would not really benefit from them, we should not use them if they are overkill or will not expand to anything else on the future"

Him: "But given the choice?"

Me: my own framework, completed it a couple of days ago, it has its own routing system and everything made by yours truly, used it before on some projects in which the developers work with it with no need to ask me about stuff, the documentation is sound and the code rather simple. Php is and can really be all you need depending on what we are talking about."

Him: **stands up, moves closer to me and fist bumps**
"All right now moving on, i was wondering abouy redux, what are the benefits of..."

Walked out of there like a boss, it got interesting when we started talking about Lisp, apparently they are interested in putting some Clojure to test in small things since they want to learn new things and apply them. Yup, this gon b good!!

My tech stack progression:

Started with PHP without any frameworks, using a homegrown MVC architecture. Used to use `mysql_` functions everywhere. And only jquery + vanilla CSS in the front end.

Then moved to use PDO functions in PHP and Backbone.js + Less CSS in the front-end.

Then moved to Django in the back-end. Did not like Django very much as it is too opinionated and not flexible (although it's damn good for rapid development if you buy into their type of things).

Then moved to Flask + SQLAlchemy and using a home grown architecture. This is a sweet spot for me in terms of back end and stayed in this spot for the longest time.

Moved to Postgres from MySQL as I fell in love with Postgres.

Then learnt React+Redux. Liked it. Made most sense to front-end development this way. Moved front-end stack to React+Redux.

Learning Haskell and been working with Scotty and eyeing Servant for a while now.

Let's see where it goes from here.

PS: this is my personal journey through various tech stacks in various products at various companies I have worked. I'm not talking about moving a product through these many tech stacks. That doesn't make any sense.

The brief history of Facebook open source:
- FB releases React under an oppressive licence that tells "woopsie, can't sue FB if you use React"
- a lot of money goes into making React popular to gain leverage from mass adoption
- VMware bans React in their company
- FB releases Flux to bring state management. It flops. Replaced by what some Russian student wrote in several evenings (Redux)
- Preact is released. It's faster than React, and it has MIT licence. Vue beats React in GitHub stars.
- Under mass pressure, FB changes React's licence to MIT. Initial plan to gain leverage fails spectacularly.
- FB releases Flow Types. It flops. Replaced by TypeScript.
- FB releases their own app market for React Native. It flops.
- FB releases Relay. It flops. Replaced by Apollo.
- FB tries to push React.Suspense for the whole JS landscape to obey and comply to how it works. Community says "Fuck You".
- FB releases react-native-web. It flops.
- Web Components are out in all browsers, adopted as a standard. React doesn't support them.
- Google releases Lit, a virtual DOM framework on top of Web Components to fuck with React. It's a massive success.
- React 18 is out. Still no Web Components support.
- (you are here)

First of all, I hate crammers so much. These people kill the industry without even understanding it. They turned interviews into exams, missed the point of hiring, and saw no distinction between knowledge and information all the time. They don't understand that if you can google an answer in five seconds, it's not knowledge. It's information.

They don't understand that questions like 'what will Python do if you delete an item from a dict while iterating over it' are complete nonsense. They don't understand that it's not 'dig deep'; it's just a bad practice that leads to errors, thus must be avoided. The fact of remembering 'RuntimeError: dictionary changed size during iteration' means that you haven't been avoiding it enough.

One more example. Which signature is correct?
- ApplicationListener<ContextRefreshedEvent>
- ApplicationListener<ContextRefreshEvent>
- ApplicationListener<RefreshedEvent>
- ApplicationListener<RefreshEvent>

Second. What's the point of forcing you to write compilable code in google docs? Do they really expect that one could possibly remember 'import org.springframework.beans.factory.annotation.Autowired;'? Seriously?

Third. Why do they expect me to know Spark, Java, J2EE, Spring Boot, Python, Kafka, Postgres, React/Redux, TypeScript, and work for miserable 70K EUR?

What's wrong with the European IT job market? Are they fucking nuts?

Material-UI.

I'm exhausted, so I'll keep this short.

I changed a TextField to a TimePicker, and noticed my className prop didn't apply anymore.

I thought it was my mui/redux-form wrapper for that component since I had just written it, but that was basically a straight copy/paste from the other wrappers, and both receives and passes the prop just fine.

After a lot of fighting, I finally found a workaround: if I add a `data-work-you-piece-of-garbage` prop alongside it, only then will the className show up on the rendered element. Why? I have no freaking clue. I tested it three times and got the same results. I looked through the MUI source and it still doesn't make any sense.

Fucking whatever, only three hours wasted.

Enjoy this ultra⁻DRY piece of React-JSX-Redux-form component

Just refactored this only for the sake of my eyes..

!rant

... ahem.
I CAN TYPE IN THE BOX
AND IT SHOWS UP
AND IT STAYS THERE

WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!

I seriously do not understand the rants against Windows.

I love Windows 10 (got as free upgrade from MS), and have no issues with MacOS or Linux OS. I use them as well but do all serious work on Windows.

All my life, I have worked on business / commercial side and picked up Web development in last couple of years. I started using computers on DOS in 1992, and shifted to Windows 3.0 in 1995. There was no Mac or MacOS back then.

For serious work, I purchased a old Dell Precision M4700 workstation grade laptop with quad-core i7, at throwaway price, got 32GB RAM, 2.4TB (1x2 TB + 400gb) of SSD on super sale online, and installed it myself. It easily supports dual 4k monitors.

Git-bash on windows allows all the necessary linux command line on windows. Though not tried, Windows 10 allows embedded Ubunutu with linux terminal. Web development tools like - VSCode, git, github / bitbucket clients, NVM/Node, React / Redux / Webpack / Gatsby / Jest, REST clients, GraphQL client and server, Graph Server, Chrome PWA / Chrome Dev Tools, http/Websocket/WebRTC interception, Google Firebase SDKs, AWS sdks, cloud utilities, CI/CD tools work flawlessly. Windows even has its own package manager for applications.

Not using redux, really in a bad state now.

I was MEAN developer and moved to MERN developer.
My thoughts:

Angular very good framework BUT react + redux fucking awesome

Welp, I dunno about the rest of you folks, but I had a splendid day making a really sexy data viewer with React, Redux, ImmutableJS, react-virtualized, and Radium. And it works fast in IE!

And! Now I'm in a pub, sipping a beer in the summer evening breeze, waiting for my partner so we can order food.

Cheers!

Fucking Redux..

FUCK YOU BUSINESS GUY
FUCK YOUR SCOPE CREEP
SOLO DEV AINT GIVING U 20 FEATURES IN ONE MOTHERFUCKING WEEK

Seriously, though. Being a solo full-stackq developer who can do both frontend (react, redux) and backend (feathers, node) does NOT mean you have twice the manpower to accomplish all of your shitty shit. Just because you have an idea does NOT mean I have to implement all of it. You don't even have a motherfucking specifications for me, yet you expect me to deliver shitloads of complete fucking feature in a fucking week. This is not a fucking joke. I am NOT your mother fucking tool. I need time to build my stack, design and perfect the interface. I don't want a shitty motherfucking product on my fucking portfolio.

*dies inside*

Me and my team has been creating React components for the last two months. Today we realized that not a single component is done the Redux way (as pure functions), which means we have to refactor every component and the tests.

That's what you get for trying out new technology..

First website with React JS:

After a month of studying on React I am finally building a commercial website with it. When I started learning React with redux and react router it felt so unnecessarily complex.

But trust me guys, all it takes is patience. Once you learn it creating a Web app is a breeze. And everything eventually makes so much sense. I'm so glad that I didn't give up and if you in the same position , DON'T GIVE UP. You'll eventually realise how amazing react is.

This is legit how I look when I go about exaining webpack, react and redux to people

BE GONE CLOWN!!!! MAY YOU BE CAST BACK UNTO THE DEPTHS FROM WHICH YOU HAVE SPRUNG!!!!!

🪄✨

👻👹👺

🤡

can't wait to be absolutely fuck you rich while the clowns continue to fumble around in the sandbox for the next 5 years 🪣⛏️😂😂😂

all those years, crouched over a laptop, learning React, then TypeScript, then PostgreSQL, then .NET, then React Hooks, then Redux Toolkit, then Golang, then GraphQL, and even RabbitMQ and gRPC mixed in... more and more and more............ IT'S TIME TO SPREAD MY WINGS AND FUCKING FLY BABY!!!!!

why work for clueless clowns when your own technical know-how is literally 1000x (or perhaps infinitely) theirs? Was I an idiot? Yes, I was! Way too nice and I bought into the hype fake idiot brain culture, but now I've finally woken up. Time to ascend to the stars by myself.

Cheers devRant, this 🤡 is finally going to transform into a 👨‍🚀🚀

You may not hear from me for a while sadly, but I'll be sure you guys get the first shoutout - see you on 🪐

Apart from having a baby which is the hardest in the world，i think the hardest project is to learn to code.

I studied philosophy and anthropology but gamed a lot. Me and a good mate decided to work together and he told me hed teach me coding.

The guy is a genius but he is a reckless rebel genius who tells everybody to fuck off.

So，after 1 year in a half of intense coding where i had to learn linux， networks， and im not shitting you html and css as well and of course javascript.

He has now put me on， for the last 2 month， in charge of our front end backoffice. I have to design forms that do the right http requests，do the unit testing， play with redux-form， react-redux and he has thrown me into the basic java backend so i can begin working with entites and how i serve the data and link it to the database and even create tables.

Every time i fail hemakes me remake everything.

I actually came on devrant to study the dev community (i always gamed a lot but this is a whole different community). The dev community is pretty awesome and unique.

Anyhow， i remember when i saw him as me to complete an exercise and i didnt event know which words were the reserved language ones and those i could use myself. It was like fucking magic.

Why the fuck this moron thought it was a good idea to set a global onClick event in a react component and make it have the desired behavior for EVERYTHING instead of the only click he wanted to get?

7 places you can click were triggering redux dispatch and ajax calls that should only work on one place... Fucking hell...

I’ve come to the conclusion that developers who like react have never used it for anything even remotely complicated.

Because here’s reacts dirty little secret; it doesn’t scale. Not even a little. It’s flexible, but that leads to every developer writing their code in a different way.

It’s simple and easy for simple side projects, but as soon as you have to pass state to a child component, you’re fucked. And god help you if you’re modifying the state in said child component. You can try using redux, but that’s a bandaid solution to the real issue.

There are better alternatives, namely Vue. There’s no need to write unintelligible code that’s a mutated hybrid of html css and js. We as web developers realized mixing these technologies was a bad idea a long time ago.

React simply doesn’t scale. It’s flexibility, complexity, and the awful code quality it leads to makes it a nightmare for large projects with multiple developers

Some of its concepts are interesting and useful though. It’s functional concepts allow for easy code reuse, among the other benefits associated with functional programming

I sincerely hope that the hype around react dies out, and a new framework emerges that takes the best from react and fixes the glaring issues it currently has

Worst code I ever had to touch: a React application, createClass era, before redux was a thing, that had everything in one fucking component.

Every fucking thing.

This was a simple video chat application, but still. The component's code included:

- Views (contact list and video call screen) and logic to switch between them;
- All application state;
- API calls;
- Websocket message handling;
- WebRTC logic (getUserMedia and p2p streaming).

This app was built by one person in one month for a demo. That person left the company after the demo and I had to maintain that mess without zero React knowledge (I was doing angular at that time). On his last day he gave me a crash course and an overview of how the app worked.

Around that time I attended a few meetups and a conference with talks about React. That, my curiosity and ability to learn by refactoring helped me a lot when I had to add new features and fix bugs in that app.

It’s really painful how non technical people think all technical stuff is the same.

The amount of times I’ve been brought in to help someone with a printer or WiFi network.

I didn’t do a computer science degree for this.

I’m also pretty sure my last two bosses think fixing the printer is the same as creating large scale systems.

My last boss wanted me to build a Vr chatbot despite spending the last few years building web servers and react/redux apps. I mean I can probably figure it out and it’ll be fun, but don’t think I’m gonna get this done in a week with all my other responsibilities too.

My new boss wants me to singlehandedly build a massive marketplace system that would probably take a team of ten, several years.

Fed up of being around non technical managers who don’t listen to me with my feedback.

Time for a new chapter in the new year.

A (work-)project i spent a year on will finally be released soon. That's the perfect opportunity to vent out all the rage i built up during dealing with what is the javascript version of a zodiac letter.

Everything went wrong with the beginning. 3 people were assigned to rewrite an old flash-application. Me, A and B. B suggested a javascript framework, even though me and A never worked with more than jquery. In the end we chose react/redux with rest on the server, a classic.

After some time i got the hang of time, around that time B left and a new guy, C, was hired soon after that. He didn't know about react/redux either. The perfect start off to a burning pile of smelly code.

Today this burning pile turned into a wasteland of code quality, a house of cards with a storm approaching, a rocket with leaks ready to launch, you get the idea.

We got 2 dozen files with 200-500 loc, each in the same directory and each with the same 2 word prefix which makes finding the right one a nightmare on its on. We have an i18n-library used only for ~10 textfields, copy-pasted code you never know if it's used or not, fetch-calls with no error-handling, and many other code smells that turn this fire into a garbage fire. An eternal fire. 3 months ago i reduced the linter-warnings on this project to 1, now i can't keep count anymore.

We use the reactabular-module which gives us headaches because IT DOESN'T DO WHAT IT'S SUPPOSED TO DO AND WE CANT USE IT WELL EITHER. All because the client cant be bothered to have the table header scroll along with the body. We have methods which do two things because passing another callback somehow crashed in the browser. And the only thing about indentation is that it exists. Copy pasting from websites, other files and indentation wars give the files the unique look that make you wonder if some of the devs hides his whitespace code in the files.

All of this is the result of missing time, results over quality and the worst approach of all, used by A: if A wants an ui-component similar to an existing one, he copies the original and edits he copy until it does what he wants. A knows about classes, modules, components, etc. Still, he can't bring himself to spend his time on creating superclasses... his approach gives results much faster

Things got worse when A tried redux, luckily A prefers the components local state. WHICH IS ANOTHER PROBLEM. He doesn't understand redux and loads all of the data directly from the server and puts it into the local state. The point of redux is that you don't have to do this. But there are only 1 or 2 examples of how this practice hurt us yet, so i'm gonna have to let this slide. IF HE AT LEAST WOULD UPDATE THE DATA PROPERLY. Changes are just sent to the server and then all of the data is re-fetched. I programmed the rest-endpoints to return the updated objects for a very reason. But no, fuck me.

I've heard A decided (A is the teamleader) to use less redux on the next project and use a dedicated rest-endpoints for every little comoutation you COULD DO WITH REDUX INSTEAD. My will is broken and just don't want to work with this anymore.

There are still various subpages that cant f5 because the components cant handle an empty redux state in the beginning, but to be honest i don't care anymore. Lets hope the client will never find out, along with the "on error nothing happens"-bugs. The product should've been shipped last week, but thanks to mandatory bugfixes the release was postponed to next week. Then the next project starts...

Please give me some tips to keep up code quality over time, i cant take this once more.
I'm also aware that i could've done more, talking A and C about code style, prettifying the code, etc. Etc. But i was busy putting out my out fires, i couldn't kill much of the other fires which in the end became a burning building (a perfect metaphor for this software)

Fuck the JavaScript ecosystem; Fuck React, Redux, and a big special fuck you to React-Router. And fuck interviews that give week long assignments.

The whole fucking JavaScript community makes the simplest things so complicated just so that they can tell Backend and Mobile Devs “Hey our job is difficult too”; fuck you, it isn’t! You made it difficult. and so that they can write corny emoji-laden medium articles about it to supplement their meagre income. What’s more the articles are outdated in less than a week.

Fuck JavaScript; APIs changes everyday a week and it’s documentation is updated every decade.

Found this in create-react-app...

True comment!
😂😂🤣🤣🤣

That feeling when you were so happy about react-native, and was pretty sure at the beggining about the achitecture of your app and js libs you are about to use.

Im here sitting with redux, reselect and still dont know why I cant just do a REST call and format data in the container component.
Why react is so hard, or am I dumb?

Thought I'd try out Asp.Net Core + React + Redux, at first I got shocked from the TypeScript shit I saw, but an hour later, I like what I'm seeing :P

There was a time when backend engineers used to make fun of frontenders and tell them 'you arent a real software engineer', nowadays frontend is getting so complex and cool that even backenders are now starting to learn frontend. I am so happy that because of new tech and frameworks frontend has gained such a massive respect.

Today on "You're wasting your life by not writing typescript"

Union types

The value with redux, among other things, is incredible

It’s really painful how non technical people think all technical stuff is the same.

The amount of times I’ve been brought in to help someone with a printer or WiFi network.

I didn’t do a computer science degree for this.

I’m also pretty sure my last two bosses think fixing the printer is the same as creating large scale systems.

My last boss wanted me to build a Vr chatbot despite spending the last few years building web servers and react/redux apps. I mean I can probably figure it out and it’ll be fun, but don’t think I’m gonna get this done in a week with all my other responsibilities too.

My new boss wants me to singlehandedly build a massive marketplace system that would probably take a team of ten, several years.

Fed up of being around non technical managers who don’t listen to me with my feedback.

Time for a new chapter in the new year.

#whosHiring?

i was hired to join a team of old devs (40+) in an unnamed European country "yay goodbye 3rd world it's time to enjoy the quality of life" assist with enhancing already existing software and creating new solutions.
prior to my arrival most things were slow and super buggy, looking at the code base it shouldn't be a surprise, amateur hour everyone, logic implemented that is not needed, comment driven development, last time code review was done back in 1996. lots of anti patterns.
i swear there is a for loop that does nothing but it loops through a 100+ elements list, trunk based development with tfs since git is "not really needed"
test projects are not there.
>enter me an educated fool, with genuine passion for the craft and somehow a decent amount of knowledge.
>spent the last year fixing stuff educating people on principles and qualities.
> countless hours of training and explaining. team is showing cooperation, a new requirement comes in to develop with react.
> tear my ass creating reusable shit and self explanatory code with proper naming etc using git with feature branching, monday is first deployment day.
> today a colleague was working on an item submit a pull request and self approve it
> look at the code..... WTF the dumb fuck copied and pasted the whole code from different kendo components but somehow managed to refractor the name to test component, commented out all the code that he didn't use did the api call directly from the component, has 2 useeffects that depends on the a fucking text box changes for no reason, no redux implementation, the acceptance criteria is not achieved, and it doesn't work it just look right.
> first world country shit cannot scold, cannot complain, lead by example.
>asked him why you did this, the response was yeah probably i shouldn't have done that, i really didn't understand anything in the training but didn't want to waste time!!!!
> rest of the team created a different styled disaster with different flavors they don't even name their shit the same way.

fellow developers I'm stuck in a spaceship with a bunch of imposters, seriously i never cried in my entire life now I'm teary and on the verge of a break down.
talk with management "improving needs time" and offers me to join a yoga session to release the stress as if reaching nirvana would deliver shit on monday.
i really don't know what do is this a rant, is this a cry for help, I'm not sure, any advice is welcomed.

I feel like I'm too stupid to understand the Redux pattern. It makes me want to quit programming.

# Retrospective as Backend engineer

Once upon a time, I was rejected by a startup who tries to snag me from another company that I was working with.
They are looking for Senior / Supervisor level backend engineer and my profile looks like a fit for them.
So they contacted me, arranged a technical test, system design test, and interview with their lead backend engineer who also happens to be co-founder of the startup.

## The Interview

As usual, they asked me what are my contribution to previous workplace.
I answered them with achievements that I think are the best for each company that I worked with, and how to technologically achieve them.

One of it includes designing and implementing a `CQRS+ES` system in the backend.
With complete capability of what I `brag` as `Time Machine` through replaying event.

## The Rejection

And of course I was rejected by the startup, maybe specifically by the co-founder. As I asked around on the reason of rejection from an insider.

They insisted I am a guy who overengineer thing that are not needed, by doing `CQRS+ES`, and only suitable for RND, non-production stuffs.

Nobody needs that kind of `Time Machine`.

## Ironically

After switching jobs (to another company), becoming fullstack developer, learning about react and redux.
I can reflect back on this past experience and say this:

The same company that says `CQRS+ES` is an over engineering, also uses `React+Redux`.
Never did they realize the concept behind `React+Redux` is very similar to `CQRS+ES`.

- Separation of concern
- CQRS: `Command` is separated from `Query`
- Redux: Side effect / `Action` in `Thunk` separated from the presentation
- Managing State of Application
- ES: Through sequence of `Event` produced by `Command`
- Redux: Through action data produced / dispatched by `Action`
- Replayability
- ES: Through replaying `Event` into the `Applier`
- Redux: Through replay `Action` which trigger dispatch to `Reducer`

---

The same company that says `CQRS` is an over engineering also uses `ElasticSearch+MySQL`.
Never did they realize they are separating `WRITE` database into `MySQL` as their `Single Source Of Truth`, and `READ` database into `ElasticSearch` is also inline with `CQRS` principle.

## Value as Backend Engineer

It's a sad days as Backend Engineer these days. At least in the country I live in.
Seems like being a backend engineer is often under-appreciated.
Company (or people) seems to think of backend engineer is the guy who ONLY makes `CRUD` API endpoint to database.

- I've heard from Fullstack engineer who comes from React background complains about Backend engineers have it easy by only doing CRUD without having to worry about application.
- The same guy fails when given task in Backend to make a simple round-robin ticketing system.
- I've seen company who only hires Fullstack engineer with strong Frontend experience, fails to have basic understanding of how SQL Transaction and Connection Pool works.
- I've seen company Fullstack engineer relies on ORM to do super complex query instead of writing proper SQL, and prefer to translate SQL into ORM query language.
- I've seen company Fullstack engineer with strong React background brags about Uncle Bob clean code but fail to know on how to do basic dependency injection.
- I've heard company who made webapp criticize my way of handling `session` through http secure cookie. Saying it's a bad practice and better to use local storage. Despite my argument of `secure` in the cookie and ability to control cookie via backend.

Now the real question is are you even allowed to put React in your cv if you've never worked with redux, don't know the concept of HOC and still make pull requests with componentWillReceiveProps ?

Me: Oh, man, there are hooks for react-redux now? I don’t have to wrap components in a higher order component to get information from the redux store and dispatch actions? Could this solve the problem I’m having with data fetching and consistency in the app I’m working on?!

Spends entire Saturday writing a basic server, connecting to an mLab instance, filling said instance with dummy data, starting a create-react-app, writing a reducer, action creators, components, etc. just to test how useSelector(), useEffect(), and useDispatch() would work in an application that isn’t just a simple counter (why is it that like every example is always the counter example?!). Bonus, react-router now ALSO has hooks, so got to play with useHistory() and useParams()

Conclusion: Maybe. It does appeal to me to not have the cascade of virtual DOM that you always get nesting HOCs, but I’m also wary of appearing too willing to jump on it just because it’s the new thing.

Has anybody else played around with react-redux hooks? Your thoughts?

Also, yes, I know, not every app needs redux. It had it when I was brought on and I don’t really have the ability to change that implementation detail now.

My boss: now that the other project is stable, you can start working on this new one. It has to be built from scratch in Angular.
Me: is there any particular reason we have to make it in Angular? Last one in React+Redux worked very well and I am getting used to it.
My boss: Just to give it a try.

And Angular steep learning curve is not even the worst part. Lack of design and direction is.

its 2:30 here and ill have to wake up for work at 7:00 and im trying to figure out what the hell is redux

For state management, we use:
React state
Redux state
Local storage
Session storage

That’s it 😊

Gentlemen, I know React and Redux..
But I have no idea how to create a radio button!

Hey guys, quick question regarding employers and stuff.

I'm 14 and I've been learning and making things in PHP for around 1 and a half years now. I quite like PHP as, despite the code being quite messy sometimes, it's super easy to learn, and has plenty of features for any use case. My biggest concern is that, when I end up getting a job, whilst 5 and a half years of experience using the language is good, do you guys think PHP will still be in-demand, or should I look towards learning a new stack? Perhaps I should use Ruby on Rails, or Express - React and Redux, or maybe Django? With so many options available for developers, I'm finding it difficult to choose a stack that will stay in-demand in the future. Could anyone help me out with this? Thanks.

Edit: I've been learning Laravel, too.

Reasons why we use redux in Angular:

- React has it
-
-

I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux I hate Redux

I hope I did not make the wrong decision here:
Been working on a side project using React Js for a year now. After getting to know more about Vue, I just started rewriting it and moving it to Vue, to speed things up I'm using core JS classes for network stuff and validations ...etc just rewriting Redux to Vuex and React Components to Vue Templates

If I made the wrong decision I'd appreciate if anyone tell me about it before I go deeper in the rewrite process lol

It is not that I found speed difference both perform the same from what I've seen for my scenarios. But the output code of Vue is soooo much cleaner than what I found in React, either I failed to write a clean react code no matter how hard I try to optimize it, or Vue really takes the short way and keeps things clean.

I am a Technical Lead in the department in my company that writes code for our clients that have money but doesn't have the technical expertise to handle the complexities of our own software.

Part of my tasks involve taking care of a few projects written by employees that have left after using third-party tools rather than using our own software. No one else in this department knows these third-party tools, they only know our own, and my *still limited* web development experience means I get dumped these things in my lap.

And I'm SO pissed at these projects and their authors and the manager that let these ex-employees write these things. There is this one project that was managed by two different "developers" (I don't know they deserve this title) at two different times, and it is so riddled with different technologies it makes me want to throw up almost daily.

Don't believe me? Here is a complete list of the dependencies listed in the package.json of this project: babel-polyfill, body-parser, cookie-parser, debug, edge, edge-sql, excel-to-json, exceljs, express, html-inline, jade, morgan, mssql, mysql, pug, ramda, request, rotating-file-stream, serve-favicon, webpack, xlsx, xml2js

What this doesn't even show, is that one part of this project (literally one page) is made using react, react-dom, react-redux, and jade. The other part (again literally one page) is made using Angular and Pug. In case you missed it while picking up your jaw, there's also mssql, mysql, edge and edge-sql. excel-to-json, exceljs, xlsx.

Oh you want *more* juicy details? This project takes the entire data object used by the front-end, stringifies it into JSON, and shoves it into the database *as a single field*. And instead of doing WHERE clauses in the SQL queries, it grabs the entire table, loops, parses the json, and does a condition on it. If even one of those JSON entries gets corrupted, the entire solution breaks because these "developers" don't know what try/catch is.

The client asked for a very simple change in their app, which was to add a button that queries the back-end for a URL, shows it in a modal dialog, after which a button is clicked to verify the link by doing a second query to the back-end before modifying a couple of fields in the page.

This. Took. Me. Two. Months*. Save me. Please, save me.

*between constant context switches between this and other projects that were continuously failing because of their mistakes.

I fucking love Asynchronous Action creators in Redux.

I little more work upfront makes for a well thought out application and makes things like loading screens stupid simple.

The mobile application my company is developing is beginning to fail in a prod environment because the third party tool we purchased to sync our 3 databases in the background isn't working as expected, so I have been assigned the task of rewriting the entire application. I chose to do it in react-native/redux which I have never heard of until two weeks ago, and I have never enjoyed programming so much in my life. Shit just clicks and works the first time more often than not. Android Studio had me banging my head against my desk daily. Kudos to these technologies 👌

Hell yeah! Just learned React/Redux. Implemented it into a view;
1 file changed, 34 insertions(+), 282 deletions(-)
rewrite app/views/landing_page/property.slim (96%)

Feels good! :D

Reducers in redux is just like making caramel, you boil (action) the sugar (payload) until the sugar is fully dissolved into golden color (state). That's why the process of making caramel is also called reduction.

I'm about to take full responsibility for front-end solutions plus doing UI/UX design, and I've pretty much completed the official React and Redux tutorials.

In my defense I only said I was interested in UX but I have a creeping suspicion they think I'm a UX God.

I also used AngularJS for years and I feel that React speaks to me in a completely different way. It's exactly how I want to do things. Big fan of functional programming as well... So I think I'll thrive with React/Redux and friends if I can get some hours in before things kick off. It's just enough pressure for me to put in the work without feeling overwhelmed... for now.

It's thrilling though. I'm somewhere between excited that I'll get to show off my skills and scared that I'll be exposed as a fraud. I have a mild case of impostor syndrome though, so I think it'll work out in the end.

Stop writing motherfucking state management libraries every week that are supposed to "take the pain out" of redux. Fuck this. If you find redux hard, I don't think we should work together. Shit, there are so many difficult concepts regarding web development, but redux? Redux is hard? Fuck you, stupid bitch!

Planning to make a github list of usefull links on topics related to javascript,react,react native,redux etc . Drop usefull links if you have any. They can be tutorials,articles, talks,repos,packages etc.

Redux and ngrx look like a good way to do what you already do in a more verbose way and with a lot of boilerplate.
I love the idea of keeping the state of the whole app and the single source of truth, but... why so verbose? It's almost more the time spent to write boilerplate code than the time spent writing "productive" code

If I learn React, Redux, Mongo, Express and Node, will I be able to build a full web application?

Walking in a shop. Using my react native todo app with redux i made for personal product. Feels good man

Recruiter bot just emailed me with some offers, let's take a look...

"Hand-on Experience with SQL and NO-SQL Databases preferably Redux"

Whew! I was worried for a second, thank god they are using a Redux database and not one of those really crappy React databases! I'll really consider applying now.

smh

If you feel it’s time to change I have a great job offer for you…
proceeds with offer with maximum wage that is half what you earn and by the way you need to know React, TypeScript, NextJS, Redux, NodeJS, ES6, Webpack, RESTful i GraphQL API
Nice to have is Python and Go

Girl you need to decide if it’s great offer or technology mishmash.
Hell no, glad you didn’t mentioned young and dynamic team cause I clearly see some dynamic technology stack there.

Company helps people find medical treatment clearly forgot about treatment on their stack.

Someone needs to tell them their tech leads are complete morons but since you’re not looking for head of technology it won’t be me lol.

Bored at the office. Company is done for. I'm spending my last days here, doing nothing, waiting for my new position to start. There's only that much you can read on devRant, and SO MUCH MORE you could do writing code. But I just can't decide what to do and as a result sit here doing nothing. Help me out please! Answer with the most points will be the thing I'll start with on Monday, while today I think I'll just crack open a cold one.

My initial variants:
1. Learn Electron by playing with Electron React+Redux basic boilerplate, in order to make a simple personal blogging app.
2. Complete some of the 20 courses that I bought on Udemy 6 months ago.
3. Write the back-end logic for my Raspberry PI controlled systems at home (to control it remotely I'll make a hosted API that RPI will access to get input for it to decide what to do).
4. Solve problem 51 on projecteuler.net with an algorithm that runs less than 20 seconds.

Other suggestions are welcome.

The datepicker saga

Part one

So I begin work on a page where user add their details, project is late, taking ages on this page

Nearly done, just need a component to allow users to put in some date of births. Look for react components.

Avoiding that one because fuck Bootstrap.

Ah-ha, that looks good, let's give it a go.

CSS doesn't exist, oh need copy it over from npm dist. Great it applied but...

... WTF it's tiny. Thought it was a problem with my zoom. Nope found the issue in github.com and it's something to do with using REM rather than EM or something, okay someone provided a solution, rather I saw a couple of solutions, after some hacking around I got it working and pasted it in the right location and yes, it's a reasonable size now.

Only it's a bit crap because it only allows scrolling 1 month at a time. No good. Hunting through the docs reveals several options to add year and month drop downs and allow them to be scrolled. Still a bit shit as it only shows certain years, figure I'd set the start date position somewhere at the average.

Wait. The up button on the scroll doesn't even show, it's just a blank 5px button. Mouse scroll doesn't work

Fucking...

... Bailing on that.

Part 2

Okay sod it I'll just make my own three drop down select boxes, day, month and year. Easy.

At this point I take full responsibility and cannot blame any third party. And kids, take this as a lesson to plan out your code fully and make no assumptions on the simplicity of the problem.

For some reason (of which I regretted much) I decided to abstract things so much I made an array of three objects for each drop down. Containing the information to pretty much abstract away the field it was dealing with. This sort of meta programming really screwed with my head, I have lines like the following:

[...].map(optionGroup =>
optionGroup.options[
parseInt(
newState[optionGroup.momentId]
, 10)
]
)...

But I was in too deep and had to weave my way through this kind of abstract process like an intrepid explorer chopping through a rain forest with a butter knife.

So I am using React and Redux, decided it was overkill to use Redux to control each field. Only trouble is of course when the user clicks one of the fields, it doesn't make sense in redux to have one of the three fields selected. And I wanted to show the field title as the first option. So I went against good practice and used state to keep track of the fields before they are handed off to the parent/redux. What a nightmare that was.

Possibly the most challenging part was matching my indices with moment.js to get the UI working right, it was such a meta mess when it just shouldn't have taken so stupidly long.

But, I begin to see the light at the end of this tunnel, it's slowly coming together. And when it all clicks into place I sit back and actually quite enjoy my abysmal attempt at clean and easy to read code.

Part 3

Ran the generated timestamp through a converter and I get the day before, oh yeah that's great

Seems like it's dependant on the timezone??!

Nope. Deploying. Bye. I no longer care if daylight savings makes you a day younger.

When someone asks me how implement React, Redux and a lot of those stuff on their projects I answer:

If you don't have any idea what it is you might not need them.

With unlimited time I would come up with needlessly complex solutions with fancy names that do not address the needs of the developers I could no longer identify myself with, open-source it and create stunning promo and marketing pitches then get sponsored by Facebook.

Ah wait someone already got there

I don't like React Redux. Big and lots of boilerplate code just to get working. I prefer RxJs and Context API.

But between Context and RxJs, I will choose RxJs for global state management

Which JavaScript library guys are using? React or Vue? Or any other?
Writing React + Redux needs lot of boiler plate code :(

Did anyone ever think redux actually comes from the word redox reaction where there's a reduction(reducers) and oxidation(actions) and it's a unidirectional thing.

Learning Redux, or React in general, is making me a more complete JS developer.

Not knowing what persistence was and copying JS objects with JSON.parse(JSON.stringify(...)) trying to make it “pure immutable”.

Fml.

I am a fresher in web development. I have already learnt to use nodejs, react, angular, vanilla js and made many projects. Majority of the work I feel is just CRUD based, sure there are some exciting things but they are only of a small percentage.

All that innovation HAPPENING is just glorified way of making a CRUD APP ONLY.
Oh mvc worked great on server side let's bring it to client side
OH mvc is such a mess, who thought about doing this.
Oh react redux is so revolutionary let's remake our app using it,,
Oh es6 fuck yeah, Babel, webpack sure, now my crud app is super performant.
Oh graphql, motherfucking cutting edge CRUD APP......

I need to know what's next, is there any breaking of this cycle

This is so true

For 10 years I've been a back end developer. Now I'm going full stack with react and angular4 front end development in my new job.

Unused to the new dev ui I just spent 3 hours debugging a redux state issue when I realize I used uppercase in the name of the value.....

N00b front-ender.

remember that company that ghosted me after I spent 2 hours taking 2 "aptitude" tests for them?

or the EIGHT HOUR challenge I wasted my time on because the guy said I didn't know enough redux, even though they were the ones completely overcomplicating (and frankly bastardizing) its usage? oh also imagine using sagas in 2023... fucking 🤡clowns🤡 get with the program, glad i wasnt hired by you, good luck finding a competant dev

yeah, was good times...

I can now appreciate some design decisions behind react-redux after witnessing some angular OOP clusterfuck.

I am sure there is some clean/correct way to code in angular, but everyone is treating angular as java.

Some angular application (the one I have to work with) is littered with network calls. It's difficult to spot duplicates. People usually resolve promises everywhere. In services, in a top-level component, or in for loops. In react, people use apollo/redux-query or redux-saga to handle network calls. Since these libraries prevent duplicate network calls internally and reassigning apollo network call function or redux action function is always useless, it's easy to spot all network calls in a component tree.

In angular, it's difficult to trace data mutations when data can be updated everywhere. In react, you can easily find UI state updates by tracing state hooks/dispatch/apollo usages.

In angular, it's difficult to trace data pipeline. Since everything is imperative by default, people need to add update functions in data subscriptions. With all the littered mutations. Soon you will lose track of what the fuck is going on.

I hope angular get the agonizing death it deserves and fuck everyone who codes JS OOP clusterfuck UI.

ALL REACT-REDUX DEVS PLEASE UNITE!

I need help..

Just joined a new company this week. They have react, redux, and all sorts of libraries checked into their repo. Code looks like someone puked all over it. Should I quit? Or stay and clean it up?

Sighhhhhh.
SIGHHHHHH.
been looking for days now and can’t still figure out how to sort with redux.

Can someone just teach me this? I’m starting to feel “special”

So does React Fiber mean all my Udemy courses i was 'getting to' are now useless? Either way, Redux should still be relevant

Holy fuck why is redux so over engineered. How did everyone let it get this far.

Just got reminded wgy switch statements are usually frowned upon.
Forgot the breaks; i spent quite possibly, an hour trying to figure out why my button wouldn't update with my state properly 😭😭

Here is why developers should be involved in project planning.

I had a meeting with a Product Manager and a backend dev about rolling out a new rewards program. My employer has a primary website and a lightweight app that’s can be used in an iframe. It has a hard deadline because the contract for current rewards vendor is expiring.

Me: So is this new rewards program also being rolled out in the LW app?

PM: Users earn rewards on the LW app?

Me: Yes.

We’re in a video call and I can’t see the PM’s face, but I know he’s thinking “fuck.”

Me: So are we going to bring in another front end dev to code the FE for the LW app since we have a hard deadline?

PM: [clearly sounding panicked] Another dev?!

Me: Well, I’m effectively coding the frontend twice. Sure both use React, but they use it in different ways. LW app uses React Redux. I can’t just code one and copy and paste it into the other.

To be fair, this PM wasn’t the point person for the LW app. But this is why devs need to brought in on planning.

React + Redux + Router is do fucking awesome stack. Love It much more than angular 1.x. App works so fast, is scalable and easy to maintain.
Reactive paradigm for the winner!

There is a project: multi step form. It has login form, text field, date, upload. It is written in jQuery, Zend and oracle. I need to rewrite. I can use my familar jQuery, PHP skills. Or I can go for react redux, build API with Zend. The issue is that I only have 2 months. Very basic knowledge of react, redux webpack. So I need to learn and build the project. Should I go for new tech. I am not sure I can reach deadline, as there are many things to learn. Advice? If i use the new tech, how do I learn quickly?

I used to manually pass form fields to Redux and back 😖

Of course I discovered redux-form later but now I’m using final-form and it’s a breeze

Feeling the need to know everything about web dev (frontend for now) already yesterday, though not having a clue, what to look at first, as it's its own universe. Everything has a million ways of implementation, combination and features worth looking at.
Already have worked with basic HTML, CSS and JS, had a short look a Typescript, being confronted with React Typescript + Redux + thunk, SASS, learned some basics of all.
Feeling lack of motivation to build smth to learn, yet I want to explore. Afraid to get stuck in tutorial hell, although I know, changing smth here and there in the projects is a must for learning. Feeling the lack of understanding the bits and pieces of what can be styled with CSS in which way. Understanding how npm, webpack, the strange parts of JS, ES6, work.
So ... freaking ... much ....

Created redux store, wrote two reducers with multiple actions, thunks, couple of react components to dispatch some actions, bound state to props, bound actions to props, worked 4th time!

Result!

Guys, normal state management is so good in React!! Why should we learn redux? its scary, the stores, actions, reducers what the hell :p

Teamleader : just add TypeScript.
Me: Uhm okay?, someone has expirience with that?
Teamleader: No, just do it .

After 15h of trying adding TypeScript to the React / Redux App I ve to tell him that i couldnt do it.

So now I think that i am stupido as fucko..

Hey guys, I'm have just started a job (been 3 months). I am made to do a lot of front end stuff. Even though I don't like front end, I am still doing it because I get to learn about react and redux. The pay is good. However, I feel like this isn't the place for me because I don't like the domain in which this tech is being used. I am getting a job offer at a startup wherein I can dive into anything, be it ML, Full Stack development, and so on. However, the pay might not be so good. Do you think I should switch?
P.S. I'm a fresher.

As I started learning React, I found the allure of declarative style of programming appealing. I try to avoid maintaining multiple state variables for data that can be derived from the base state itself that's stored in the redux store. It works wonders when I have to change something; as I just need to make changes to one function in the utils folder and that change is implemented across the whole app, rather than change the instances everywhere as was the case when I initially started working on this project after the previous dev left.

But I see myself redefining a lot of computed values everywhere, and if I just try to define them in the root component, I'll end up with a huge list of props being passed to a couple of components. Shifting it to the utils folder helps a bit, but then I find myself defining even the simplest of array filtering methods to the utils folder.

Is this need to define computed values everywhere a trade-off that you need to accept when you write declarative code, or is there a workaround/solution I am missing? As of now, the code-base is much better than how it used to be when they had a literal Java dev work on React with their knowledge of Java patterns being used in a framework that is the polar opposite of OOP, but I still feel like there's room for improvement in this duplication of computed values.

So this "senior" programmer tells me that redux should only connect to the upmost react component and then IT should pass props down..... Like why even use redux then? WTF

The most annoying question, that has been asked many times through centuries.. here it goes again:

What Editor would you choose for Web, React.js, React Native and Flutter on Mac:

Atom || VSCode

learn to use redux with async actions and find out that there redux-sagas and re-read more documentation.

Okay guys now real deal.
I am planning to move to Portugal or something like that.
I think I’m gonna need full time remote work, seems like that one is not happening with me now(part time)
Soo I do react, and all kinds of node selenium, bash stuff . But want to improve on redux and go to react native also.
Long story short shoot the work on me :)

I've been trying Flutter the past 2days. I liked how amazing Flutter framework is but I also hated how UGLY the Dart language is. First of all, I've been doing Java(Android) and JSX(React). So, after coming from these languages, Dart seems awful. Here are the things that I hated the most:
1. JSON parsing: The worst part of Flutter/Dart. No GSON/Jackson equivalent. not even possible to make one as described in the doc
2. Redux for flutter. I tried and I hated it. So, Tried some other state management libs
3. the way static functions are written in a class
4. Widgets hiarachy
5. Ambiguity - "this context is not the context we need, we need that one to make it work. so, pass that even when you don't have it" (if you have used flutter, you will know what I mean)

I like react, I really do. But one thing I hate about it, is the number of decisions I need to make, I get so fucking confused whether to use redux thunk or sagaas, inline styles or styles components, redux or flux, even to judicially choose whether to use a state management library or not. It just lack of my own experience or don't know what. But this thing sucks

Pro tip. Don't start to learn react and redux when you have to Support 6 fcking Apps in jquery, plain Javascript and this bad boy Razor. You will kill yourself when you have to work on it. I nearly cried today because of this...

node,express, react native, redux = paradise

Does anyone have a good 'getting started documentation' for react redux with typescript. youtube videos and official documentation are mostly ES5.

Do any of you wonderful devRanters know of good links that cover the topic of best practises when deploying a React/Redux (or any modern web app) to production?

I’m pretty sure I have found all the boxes to check through personal experience but maybe there are tips out there I am unaware of.

🍻

FUCK ME!#@$%@ 6 hours now, trying to make a production build of my react/redux app but FUCKING envify sets NODE_ENV after the imported libraries are transformed!! IT WORKED TWO DAYS AGO WHAT HAPPENED :((

Say what you will but React JS development is utterly exhausting. Every React project is a totally new stack and there is no consensus in the ecosystem.That is how I feel after having worked on 5 big SPA React JS projects over the course of 5 years.

The structure of these projects was all but similar: most used HOC's, some render props, functions-as-a-child, hooks or rather component lifecycles, some used container-components, some Redux, others sprinkled business logic & state all over, and yet others use a mix of server-side rendering and "hydration"...

I dangerouslySetInnerHTML on LazyExoticComponents, and dared not useEffect on the DO_NOT_TOUCH_OR_YOU_WILL_BE_FIRED root property. Hooks embrace functions, but without sacrificing the practical spirit of React, you see.

I didn't make this up. It's verbatim from the code and the docs.
This is not web development, this is at best a tedious fantasy multiplayer game or at worst, a costly joke.

WHY IS REACT SO POPULAR FML

Fuck Redux and sagas. Why can't you just be normal MVC?

I have 5 months working on a project that I was assigned and I have already worked with React with Redux, Sagas, Reselect, React Native, Jest, Protractor and PHP.

Pretty sure my team isn't following best practices in terms of managing state with redux and react... We are already having to rewrite most of the project because they were mutating the state EVERYWHERE. Glad they got the css looking decent so they could hide behind that for a couple of months.

Just learnt React and now learning to use Redux with it. When I start any YouTube Series for Redux, they question the viewer weather they have followed the React videos before starting. It gives me doubts weather have I really competed the React concepts 😑

finishing existing projects, resurrecting abandoned projects with dev friends from uni (where we had actual customers calling us and saying they wanna pay us, but we are idiots and couldn't come up with effective pricing)

meanwhile learn proper JS (and node.js, also getting from noob to pro in vue.js/vuex and react/redux)

also getting better in linux server management

It seems they mistaken me for italian giving me spaghetti all over the product. Go to frontend to check the app, react with weird jQuery, no routes, pages summoned by the templates that have concatenated values and html in vanilla js, changing screens/pages with jQuery, no router... ok lets see the other app, react, redux, offline capabilities and tought myself niicee hut nothing work as intended with clusterfuck of hacky workarounds that makes app look like it is working but with hardcoded data. Offline means automatic sync when you get the network back, right? Oh backend never developed any sync, so you guys can do it, we have to fix and patch some important stuff! I don't like php but whatever, let's see what is going on there... So much spaghetti bolognese there that Bologna actually called to ask if they can buy some, they are out of stock because of us!

This is just like that song mess.css from stdout, but in any file you open!

Living on deserted island eating grass and coconut for the rest of the life doesn't seem so bad atm!

so I have both PyCharm and VScode running for the same project. It’s React Redux Django so my servers and stuff are running through pycharm while i edit and code on VS cause PyCharm is crap for react and javascript.

But VS cant seem to run my crap without additional steps which PyCharm does for you automatically like the virtual env

Is there a better way to do this or is this my life now?

Is it fine to manage React states on your own ( kinda lifting up the state way ) in a medium size application? I've built 70% of the application without a lot of trouble. The only problem is there's no way to pass states to the sibling components without lifting up the state and lifting up the states decreases the modularity of the code. A lot of functions (handlers) have to be re-written in different components.

Would I be better off using Redux, etc. Thoughts?

Learning React and Redux for work ... fucking hell Redux is a lot to set up! (But easy to extend 🤔)

Redux!!
Is there any way to update the store and not change the view of UI?

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

Rewriting my Swift app in React Native and being told I should get familiar with Redux now...

I have written some REALLY complex stuff in my career, but I simply cannot wrap my head around "state," Redux, or why.

After adding in Redux and converting to it's folder structure, adding a random action, type, container, and reducer, and my app still works the same way I'm left wondering: "why did I need this?"

I need little bit help. I am noob in react native.

I am creating a app which show pdf, all pdf are store in a web server.

I want to start downloading all those PDF in background when app start. So user does not have to wait it to download when he/she/it click on it.

Also, I am not good with redux yet. I am still learning it. And this application does not have redux implemented.

So please, can you explain how can I achieve this?

Why the fuck do consultants / noob types LOVE using fucking props in react components. This app is complex, just make a fucking redux slice and use that. I'm not passing 23904 props to a component to get it to render. God

You know what is awesome. React with Redux. It is such a clean and scalable pattern for building UI. Conceptually not that easy but on once you have it. So much better than any other pattern I have seen.

But what fucks me off is working with other librarys with it not hard just fucking annoying.

Recently I completed a whole year in programming. Holy jebus, I have no idea I could make it through.
I started thinking I was "decent" at this because I had taken a half dozen courses in python plus some algorithm logic in school lol @ innocent me
I'm an applied math student and I hereby declare I was the most incompetent dude you'll ever see.
I've been through so much shit I didn't realize I had a shitty boss, because one would think it's normal for a beginner to approach everything in programming because I was told to do so. Full blown restful apis, stateful redux react apps with responsive CSS using Google's material design. Don't forget to dockerize everything and deploy the swarm on Amazon cloud all the while having to run integration unit tests, make sure all the rules on your nginx are correct we don't want exposure do you know how to write a visualization tool on JavaScript so we can 3d-fy some x-ray prints and good luck balancing tight schedules with your school and girlfriend ye right lul
My manager would ask me to deliver new shit to an app I was developing mostly by my self in react (I barely even knew what RFC or ES6 was by the time I started).
I got fired from this project because I couldn't deliver by myself what 5 experienced dudes could (debatable, but still... Cuz they couldn't when they took over. Boss wanted to rewrite the whole app in a week and a half)
Turns out I got called back by the same company but to contribute in another project. This time to automate some shizzle with python.
Feelsgoodman but I want out ASAP can't stay sane for longer

The state of state management with react sucks ass. The boilerplate for a store with a type parameter is absurd.

I have just witnessed hell given shape.

Imagine having react + redux

And finding component which just pass an argument to the children.
‘’’(children, param) => children(param)’’’ An argument which is stored in the store. Without even changing it. And it’s a standard around the codebase.

This is why we don’t deserve nice things.

Any react-native developers here? How's the experience so far?

At first I got this crappy project which 400 users HAVE TO use but NO ONE WANTS to use - with ASP.Net MVC, ASP.NET MVVM (Yes, both!), KENDO MVVM, KENDO UI, JQUERY and not a single line of typescript or modern web framework...

After I told them, that was not why I was hired and not what I was promised, they told me in summer I will get this brand new project, not a single line of code written.

Every new project of my company in the last 2 years was in React / Redux / Typescript and ASP.Net Core WebAPI - So I invested a bunch of weekends to get into it to be able to lead such a new project!

Today I recieved a Email from my boss, that because "we have to be on the same stack as the sister-project" we will use jquery and kendo mvvm....

What the fuck...

Once a React aficionado, twice the frustration we endure,
In the realm of libraries, React's problems seem impure.
With Svelte's elegance and grace in our sight,
Let's vent about React, as day turns into night.

Boilerplate Overload, a monotonous affair,
Classes, constructors, lifecycle steps we declare.
In Svelte's simplicity, we find a breath of fresh air,
Just markup and magic – a coder's love affair.

Complex State Management, React's Achilles' heel,
Redux, Mobx, and their massive code appeal.
Svelte's state handling is a cinch, for real,
No more tangled webs of logic to conceal.

Unnecessary Re-Renders, React's performance woe,
Countless updates, like a never-ending show.
Svelte updates what's needed, like a pro,
Efficiency and speed, in its radiant glow.

Verbose Syntax, JSX's verbosity on display,
HTML in JavaScript, causing dismay.
Svelte's concise template syntax lights our way,
No more endless tags, just code that's here to stay.

Lack of Truly Reactive Behavior, React's hurdle high,
Hooks to wrangle, state to satisfy.
Svelte's reactivity, no need to question why,
It just works, oh my, oh my.

Ecosystem Complexity, React's sprawling sprawl,
Choices galore, making us bawl.
In Svelte's world, simplicity is the call,
A coherent ecosystem, it has it all.

Learning Curve, React's mountain to climb,
Classes, hooks, context, a hill of time.
Svelte's gentle curve feels sublime,
A smoother path to code, so fine.

Tooling Overkill, React's complex array,
Build tools, linters, configs in disarray.
Svelte's streamlined setup leads the way,
No more intergalactic code buffet.

Debugging Headaches, React's mysterious realm,
Complex state, intricate components overwhelm.
Svelte's predictable model, a soothing helm,
Debugging becomes a peaceful realm.

In the end, React, a complex labyrinth we explore,
Svelte's elegance and simplicity we adore.
If only React could learn, its problems to deplore,
A brighter future, for React we'd implore.

React, redux and electron. Why can't you be simple 😂.

Might consider writing a yeoman generator when I find something that works!

I fucking hate it that "front end developer" came to mean "data flow for react engineer". It seems most frontenders now don't understand shit about HTML and its standards, don't know anything about basic accessibility and proper content structuring.

It's even worse with the styling. Cascade? The fuck is cascade? Scope everything! And, of course, write that CSS as a JS object because how else. Fluid typography? If by fluid you mean 16px, sure. Any more advanced techniques? Lol forget you're getting rounded boxes with a shadow and you're gonna like them.

But yeah, I'm glad they're overengineering Redux again because their reactivity model is fundamentally broken. That's exactly what """frontend""" should be about.

Luulz
I hate react, ok it is now a knows thing about me...
But i have to maintain a huuuuge app made on react.
And the old developer mixed the nodejs backend with the frontend... And it is already a russian doll mess in components, cuz he seems to develop it during 2 years and only after one year he discovered redux !
Gosh... For a lil simple feature there is so many files involved... Gonna go crazy !
Happy that at least client pay big money for that

I hate react-redux boilerplate code and NgRx boilerplate codes too. How to avoid boilerplate code or minimize it?

I've heard about zustand but it is quite new. Legacy apps mostly use react-redux with lots of boilerplate codes.

Once you start thinking in react and flux/redux, there's no going back

Learning Falcon right now. Coming from strong front-end background having learnt Redux, React and stuff,
Falcon is what a backend framework must be! Why do you need templating in backend these days?

Hi react developers. Noob question, I am making a new (my first) react+redux toolkit+axios website…
So umm, what folder structure is best, and where does the user authentication part , the web services go?
Currently I have
-src
-pages
-index.js
-app.js
-about
-index.js
-stores
-common

!rant
I'm probably going to work on lots of projects in React Native, and a friend told to learn either Flux or Redux. He says they're different and equal ate the same. Which one would you consider I learn first? 😵

Guys is that the case, that it is such a hassle to work with forms in React-Redux application?! Hell, it takes a lot of time to just create a simple form with like 3 lines of inputs.

Everytime I need to setup bunch of those Actions that will fire on a field value change, than selectors to pick from the state and send to the backend with redux-saga. OMG OMG OMG.

Redux-forms kind a struggle to setup too at first, but I guess I have to go for it anyway?

What do you guys recommend to read when starting Electron project with React and Typescript. I'm kinda stuck. :/

I've already make a simple Electron app with Js, but few people recommended me to try React, Redux and Typescript. But idk where to start.

P.S: Tried the boilerplate, reading docs.. I need something that explains what does what and how.

[opinions welcome]
I'm just furious right now!!!

So I'm on this project where we have to make a whole *very old* website look like it's brand new.

Thing is, the whole point of the project is to make exactly the same pages as on the existing website smh. No UX or UI suggestions.
Just put the navbar in a component that looks like a tab bar, who cares anyway!?

Btw, I'm in charge of the UI.

My colleagues and I (mostly my colleagues) made a react components library and we use it for this project.
Fucking inputs get thrown into tables and all that, but hey, that's what the client asked for.

So here I am with my shiny new page, and I just hand it over to the front-end dev who just arrived.
She's supposed to feed in the data.
I don't give a fuck you use flow or redux or whatever fancy tooling.
Just call your back-end, get the data, format it and feed my damn table with it. That's it.

So today, after 5 weeks she's in, she calls a meeting where she's screening a presentation to the team complaining about how long it took her to understand what I did and change it completely.
Pieces of code on screen, saying it's crap and it shouldn't be like that.

I'm not responsible for inputs in fucking table, the client is!
Of course I have nested components with data passed through all the way: it's a series of fucking radio buttons within a table within a form!

During 5 weeks, yoy didn't even come to me once saying it's not what you expected or you're having trouble with my work!
And there we blaming my job like I'm the bad guy?!

Tonight, everyone's going home thinking I'm no good at what I do and completely lost, all because of her.

If you got this far, I'd like to hear from you on how I should act with her and how to tell her what she did is awfully wrong?

Learning react/redux after my experience with angular ... I miss 2 ways data binding already

Okay so I’ve decided to learn React with TypeScript. I’m a backend dev and doing .net core. I know with React people use JSX. But it looks like typescript is becoming the norm. Also hear redux is outdated and the hot new thing is hooks. Lol. Don’t know man. Is this a good place to start? I’m gonna learn a little but of typescript, the. Jump to React. Not gonna do JSX.

i don't understand redux thunk

We are building an application using react and redux and now they need the JavaScript profile of the app. Can some one suggest me the guide or docs for understanding flame graphs in Chrome. I searched but things were not clear in the official chrome docs.

React native devs, how do y'all persist data on different screens without using redux-persist and redux at all?

I mean, I need to navigate through different screens without having to lose data on the previous screen. Help!

Gggrrrr!!! React native and redux!!
God damn error city. Feck! 😫
But yet I love it.
Anyway, happy new year from Ireland!

Task: Research how to refector our grid component to be usable with Redux

Result: The next sprint will be used to replace Angular 5 by React

what happend? Not that I am not happy with the decision but this was a quite unexpected result.

Redux-saga is really one of the most ingenious ideas.. Love it

Anyone free and willing to help me with a react code review?

I’m stuck somewhere and not sure where i went wrong

!rant
Angular2 vs React + redux?

What database you suggest to use in a React web app? You think firebase can be a good choice?

To all React developers out there:
have you ever used the "so famous" Redux Time Machine Debugger capabilities?

Every now and then I see articles praising that as "one of the greatest things in Redux", but I either didn't understand the feature enough to see usage, or my applications are "way too CRUD"(?) to warrant time-traveling debugging.

Please, someone enlighten me :)

want to dispatch an action from clicking a button, but dispatch() doesn't exist

add @connect to make dispatch() exist

other stuff crashes because @connect is actually a macro for a wrapper instead of the decorator it pretends to be

get locked in stalemate because both features kind of need to not crash

What I thought:-

Leaning React:- Awesome State Management System. I love Web Development.

Leaning React + REDUX:- Can I be a Web Developer? Should I switch to something else?

Please I need advise on new technologies - Language, framework to learn? Currently I am proficient in Ruby,JavaScript - REACT JS/REDUX/ RUBY ON RAILS/ for web application.
Please you suggestion will be very helpful 🙏🏻

Anyone using Redux Thunk with a router? Can I cancel a promise on location change like in Redux Saga? Occasional setState warning appeared to me and it's annoying

marry a girl if she knows react, redux ...