The art of Front end Engineering

Post by krychu » Sat, Jun 12, 2021, 6:48 PM UTC

echelon wrote: post #14

austincheney wrote: post #11

There’s a deep understanding of the tools they use every day. They may use a framework as a starting point, but they also understand the JavaScript that makes the underlying work. They leverage CSS like a fluent language, manipulating DOM elements to their will. They see browser APIs as the foundation of their process rather than puzzling concepts pulled from Stackoverflow answers. I wish that were true, I have not s…

By the time you build your solution in native DOM, you've missed the market. 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.

Post by augustk » Sat, Jun 12, 2021, 6:56 PM UTC

throwawayboise wrote: post #19

leephillips wrote: post #16

I felt alienated by the first paragraph. “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…

The phrase "delight the user" has always rubbed me the wrong way. I cannot recall ever being "delighted" by software. Frustrated often, yes. Not frustrating != delightful. Sometimes I have even been impressed, but that's different from delight. Mostly the phrase "delight the user" is a red flag that the speaker is spouting buzzwords.

Post by nawgz » Sat, Jun 12, 2021, 7:15 PM UTC

austincheney wrote: post #11

There’s a deep understanding of the tools they use every day. They may use a framework as a starting point, but they also understand the JavaScript that makes the underlying work. They leverage CSS like a fluent language, manipulating DOM elements to their will. They see browser APIs as the foundation of their process rather than puzzling concepts pulled from Stackoverflow answers. I wish that were true, I have not s…

Post by nawgz » Sat, Jun 12, 2021, 8:36 PM UTC

jiofih wrote: post #27

nawgz wrote: post #26

Earlier quoted context omitted.

I’m not sure I agree with your takes on frameworks. It definitely depends on what you’re building, but in React to have composition and reuse for free immediately sets it apart from any bespoke solutions. I’m also struggling to imagine how you propose to out-scale the React framework with early & tough design decisions... these are Facebook engineers that made those same decisions, and they managed to scale the frame…

Facebook, the product, did not use React until very very recently. Do you use FB? If Facebook’s interface represents the “UI leaders of the world” we’re in troubled waters!

Post by austincheney » Sat, Jun 12, 2021, 9:15 PM UTC

echelon wrote: post #14

austincheney wrote: post #11

There’s a deep understanding of the tools they use every day. They may use a framework as a starting point, but they also understand the JavaScript that makes the underlying work. They leverage CSS like a fluent language, manipulating DOM elements to their will. They see browser APIs as the foundation of their process rather than puzzling concepts pulled from Stackoverflow answers. I wish that were true, I have not s…

By the time you build your solution in native DOM, you've missed the market. 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.