It's very easy to explain. Even very weak companies that are located in "hot" cities have chance to catch really experienced and knowledgable talent. One good guy employed for 6 months can be an amazing catalyst of great changes, you can very quickly modernize process and technologies if you have passionate people on board. It does not matter that they will all leave in couple months, the know-how will stay. The "less popular" places are the polar opposite of this mindset. If talent is not easily available, you will find companies with no proper culture, stupidly old technologies and "old guard" not wanting to change much if anything.
> It does not matter that they will all leave in couple months, the know-how will stay.
How about no. I think there is a big divide between people who do project maintenance and those tornadoes. Most new hotness people want to put on their resume will bite you in the ass 2 or 3 years down the line. But the super hero tornado will already be 4 companies out of sight so they'll never see what the things they started ended being. And when they stumble upon an old project started by another different team of tornadoes they'll complain.
There is resume driven introduction of new technologies and then there is introducing modern source control, a CI pipeline, a modern compiler toolchain with activated warnings, a usable bugtracker... all of which is often missing in small companies that only do software on the side, or live in a slow moving market.
I work in defense contracting and version control is either non existent or dated at most companies. I've gotten very good at selling git to management.
2 months to introduce those kind of changes usually mean it will still be in the "people don't want to change their way of doing things" phase. With most of the infrastructure half deployed, the process ready to be cargo-culted and a lot of things directly copied from stack-overflow into critical parts of this process. The know-how never got shared and won't appear to fill the void.
That our hypothetical tornado managed to start introducing change during just 6 months is imho a strong sign that at least some people want to change. In my experience introducing changes takes years.
I'm a lifelong gamer (since 1996), currently have PC that only has weak integrated GPU so I cant play much, but super speedy 500mbs fiber internet connection and 80mbs LTE on the phone. I look like ideal Stadia client, right? Well, no. I'm not interested in slightest, I'm waiting passionately for PS5. Current internet technology (latency) is not enough to make cloud gaming possible, you can instantly feel this 140+ ms of delay. Other than that, Google don't know jack shit about games, you can clearly see it in Stadia announcment conference. Good luck, I give it 1.5 year and nobody will remember what "Stadia" is.
The interesting part is it could've worked if Google actually understood gaming. The PS4's remote play capability is more than usable for most games. That pretty much relies on your own uplink speed and hops over residential internet hosted on underpowered hardware.
Google is one of the few companies that could've had enough data centers geographically spread out enough where most people's latency is tolerable and game selection is curated to not be latency sensitive.
But instead they completely flub both the technical implementation and the pricing model.
Hey! I'm in Krakow, personally I'm React/C# guy, buy have couple Java friends that would love to work fully remotely. Can give you my contact www if ur willing to network
I am huge React fan, but when I see how complicated are some of the modern React codebases in some "leading" companies I have a strong feeling that we will soon need to go back to drawing board and hit some kind of reset button. As I said, I love React ecosystem, but there is something fundamentally wrong with most front-end developers today. They build bigger and bigger SPAs because they are confident that React ecosystem makes it maintainable, well good luck maintaing React/Redux/Graphql/hooks/bazillion-libs after 5 years. Abstraction is good, but it has its limits.
Sometimes frontend developers overengineer their solutions, yes.
Sometimes you need a more complicated solution for a complicated set of requirements.
Do you need GraphQL? Nope!
Do you need GraphQL for an application that needs to fetch a lot of highly relational data with nested objects? No, but it sure would be more optimal to just ask for what you need in one request in the shape you expect, instead of either:
a) Multiple REST API calls that you need to combine and coordinate in the frontend
b) A specialized REST API call that gives you all the data you need in the shape you want, but it isn't very RESTful
c) A REST API call with a bunch of `with[]` params (a la Laravel) that indicate what nested objects you'd like, but not their exact shape
So, which is more maintainable then?
—
The other wild misconception I see time and time again is this:
Of the five things you mentioned "React/Redux/Graphql/hooks/bazillion-libs", only the first one is React, and the second-to-last (Hooks) of which it is optional.
The rest are dependencies you opt for, hopefully after weighing pros and cons. You don't need to use Redux, GraphQL, react-table, whatever other dependency in your React web application.
Please separate out React from React-based codebases from code architecture. They're not one in the same.
I just don't buy this idea that there is some kind of separation between React library and React as a platform. I'm building SPAs since 2008, been to too many front-end meetups, have friends in so many different companies its hard to count. NOBODY is using React as a library. Banks, shops, news sites, you name it, everyone is using React+Redux+Typescript+bazilion-libs. Graphql is not a standard yet but it is already very popular, basically every new hired Dev adds new libs or switches to something else. It's a mess.
The thing is, I don't disagree that a large (if not majority) number of developers reach for dependencies by default, instead of carefully considering patterns first.
I don't think bundling React the view library, Redux the state management library, Typescript the Javascript superset, GraphQL the API query language, Webpack the bundler as one "React the platform" is helpful.
I'd like to see the developers that automatically merge all of these technologies together by default because everyone else does it (or worse, because X Big Tech Co does it) to start questioning and exploring other options. I'm not sure how to get there, and maybe my comment above is my contribution towards convincing readers to reconsider their understanding of the React ecosystem.
You're right though, it is a mess. I think the mess comes from people and how they code, not so much this specific library nor the language.
These new frameworks and things like "create-react-app" have made it easier and easier for junior developers to make immensely complicated apps with immensely complicated tool chains. I think that has a lot to do with how things have gotten to the point described in your comment and many of the others. As you start reading tutorials about Vue or React they tend to quickly stray into other dependencies, and webpack or whatever. The web has gotten more complex. The only way to navigate it wisely is to become wise through experience. There are no shortcuts but we've definitely made it easier for new developers to stumble into a mess.
Most of the time, the complexity comes from the app and its requirements rather than having anything to do with React. Could another framework do a better job of handling and helping you manage that complexity? Maybe, depending on the specific use cases. But my guess is the majority of those apps would be complex regardless of framework.
I agree with this. However, the only annoying thing is it copies and pastes text as a photo. I’ve stared using outlook email drafts as a place to put rough notes. They are searchable, they sync with the cloud and copy/paste works as expected. Give that a shot if you want.
It's easy. Its the same in all major cities in Europe. Entertainment is almost free, healthy food is cheap, medical care is mostly free, education is free, sports are cheap, traveling is super cheap. Everyone puts all of their money in real estate, supply is extremely restricted, demand is bigger every month, prices skyrocket.
