As a backend dev myself, I totally agree with it, but I think when we're developing full blown apps we should have the end user in mind and focus on their experience using our app more than on adopting data-driven UI design.
I couldn't find a satisfying NodeJS full-stack for web app development that would be have: TypeScript, PostgreSQL, GraphQL, ReactJS, Material-UI, docker containers where the same backend image used for development would get deployed on production, while the UI production machine would be an nginx image with the assets generated at build time.
I actually started to work on this in December, but I published it a few days ago.
Please beware that in order to use it for your projects right now you'd have to be quite comfortable with the nodejs ecosystem because the whole stack is not quite tidied up.
I am also working on this! I used Node a lot 5 years ago and not much since, so I'm coming up to speed on TypeScript and various other things. I'll check your stuff out. I may throw mine away.
I love a lot of things about the Node ecosystem, but the fact that being out of it for 6 to 12 months means you fall behind is not great.
The main components I used, are: NestJS with Express as an app server, KnexJS as a query builder (because people seem to not like TypeORM that much, it lacks migrations and you have to go pretty fast to custom SQL queries), NextJS for the UI.
Yeah, I totally feel you with falling behind regarding the full-stack web dev with node/react, the pace is incredible.
I started down the road with TypeORM for my starter, and I ran into several pain points. I was reading the Knex docs last night actually, heavily considering switching. I also wrote a quick `pg.ts` file to just use node-postgres directly, but the lack of migrations is just too painful. I looked at db-migrate briefly but didn't come to any conclusion.
So that's a long way of saying, I think Knex was a good choice. Provides migrations, handles connection pooling and transactions, but doesn't deviate too far from SQL.
With the last commit in master in late 2018, SemanticUI seems a bit deserted.
Anyway, in order to change it, you should discard everything non-nextjs and non-docker related from the client/ folder, like client/common/, client/components/, client/helpers (except client/helpers/configureGraphQL.ts), client/icons, client/layouts, client/theme, client/pages/{login.tsx|signup.tsx|dashboard/}, remove the material-ui related stuff from package.json and then proceed installing the SemanticUI.
That bounty is currently at 185 billion USD.
Of course, it would be pretty difficult to sell all the bitcoins without slippage, but I guess one could cash in at least several tens of millions.
I love these kind of articles where people are transparent about their salaries. I don't quite understand the envy and the backlash the author receives. With such a negative reaction, I doubt we'll see too many articles like this in the future (who needs all the negativity?).
I'm a software developer myself for +10 years and haven't made $500k in my whole career and for some reason I don't feel any envy for him. On the contrary, I am glad that we're in an industry where people can earn this big.
I'm a (very happy) Perl (5) dev and although I've attended lots of Perl 6 cool presentations, I haven't took the time to learn it yet.
My reasons are related to the fact that there are not that many commercial opportunities with it just yet.
That is a thing which I expect to change in a relatively short time. I've already seen a few job posts looking for Perl 6 developers, which, given the language is declared 'production ready' for less than a year is a pretty amazing stuff.
Also, there aren't hat many libraries in its ecosystem yet, a thing which can be a plus for devs who want to create a name for themselves in the open source world by implementing/translating libraries with a large user base potential.
Here's a really interesting discussion about this quote and the idea behind the above: https://softwareengineering.stackexchange.com/questions/1631...
As a backend dev myself, I totally agree with it, but I think when we're developing full blown apps we should have the end user in mind and focus on their experience using our app more than on adopting data-driven UI design.