I wish that were true, I have not seen this in the corporate world and it appears absent in the job opening details of startups.
My experience tells me this:
* If you are really good you can be up and running a new project in something like React in 2 or 3 days.
* If you are really good you can be up and running without any framework at all in about 2 weeks.
* If you don’t use a framework you are forced to make tough design decisions early. This is critically beneficial and pays interest over time. Those decisions allow you to scale in ways frameworks cannot.
* The value of frameworks is over estimated for the wrong reasons and under appreciated for reasons developers don’t immediately see.
* Working directly to the DOM (even without query selectors) is amazingly easy, but it takes practice (just like writing CSS). The value is not the data, but the relationship between the nodes. That line of thinking reminds me of this board game called Othello.
* State management is less easy but still not challenging. https://github.com/prettydiff/wisdom/blob/master/state_manag...
I specifically tried to avoid talking too much about stuff like React, Next, Tailwind, etc.
Do you use FB? If Facebook’s interface represents the “UI leaders of the world” we’re in troubled waters!
What would you suggest for interactivity and JS; e.g. in a dashboard application with crud records/posts?
Instead focus on services. Get the content you need. I recommend web sockets so that the updates come to the browser asynchronously without polling the server.
Once you have what you need you will figure out the most ideal user interactions.
Similar to reasons Java became so popular in the enterprise
This is why we don't write applications in assembler.
If performance is your only metric, write Rust and target WASM. But that's probably not the right solution for 95% of cases.
If you think that’s the same as writing assembly you probably aren’t the right guy to drive the success of a startup.
“As the web continues to expand, the tools we use for work and leisure have become synonymous with a URL in the browser.”
No, they have not. I rarely use web tools.
“The need for applications that marry the best in design and development has never been so high.”
I have no idea what this is supposed to mean.
“A frontend engineer brings these pieces together in an interface made to delight with every interaction.”
Even if I used web tools, I’m not ready to have sex with my word processor.
“So, what makes a great Frontend Engineer and why is it so special?”
I can’t parse this. What is “it”?
Mostly the phrase "delight the user" is a red flag that the speaker is spouting buzzwords.
>Even if I used web tools, I’m not ready to have sex with my word processor.
I was thinking delight used in the same way a foodie uses it.
Apart from front end, this in general is the mark of people who are fun to work with. Especially so when the XXX in question is something I don’t have facility with myself.
I’m very glad that programming has become less an obscure art known only to the adepts. Nevertheless I personally prefer to work with those with deep knowledge of their domain.
