←back to thread

Overengineered Anchor Links

(thirty-five.com)
392 points matser | 1 comments | | HN request time: 0.216s | source
Show context
LinuxAmbulance ◴[] No.43571959[source]
As a backend person, sometimes I look at what's being done for front end stuff and pull back in ever so slight horror.

It's an excellent article, and the work within is very well done, but there's a part of me that screams "Why would you introduce this much complexity for what should be a simple scroll?" (overcoming technical hurdles to produce the desired end result aside).

replies(15): >>43571970 #>>43572158 #>>43572805 #>>43573073 #>>43573171 #>>43573393 #>>43574527 #>>43574744 #>>43575824 #>>43577195 #>>43577887 #>>43579848 #>>43580668 #>>43584041 #>>43590654 #
hombre_fatal ◴[] No.43577887[source]
I don't get "as a backend engineer" comments like these.

OP is doing a basic analysis on what kind of solutions exist for a typical UX edge-case. They even provide the simple solution that most people use (margin-bottom).

And for fun they go on to see if they can solve it without the minor drawback of the simple solution.

We've got to stop acting like it's a badge of honor to avoid UX consideration. We might not be people who implement UIs, we use UIs all day and should be able to muster up a few opinions about how a UX interaction should work.

replies(4): >>43579136 #>>43579573 #>>43589031 #>>43596151 #
1. andrei_says_ ◴[] No.43589031[source]
As a full-stack engineer who also studies UX, most UI solutions span from a desire for originality, aesthetics, etc. and not improved experience.

Which is what I loved about this article - it demonstrates a sizeable effort resulting in a UI implementation that is just not much better than having callouts / figures in the text- and then admits it.