• 5 Posts
  • 238 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle




  • Ephera@lemmy.mltoProgrammer Humor@lemmy.mlDesigners cry quietly
    link
    fedilink
    arrow-up
    45
    arrow-down
    3
    ·
    5 days ago

    I, unfortunately, have to use GitHub at $DAYJOB and this is me. I navigate most of the webpage via the URL bar now.

    Basically, let’s say I’m working on a repo github.com/tomato/sauce/ and want to navigate to the Releases page.

    Via the webpage:

    1. Type github.com into the URL bar.
    2. Don’t find tomato/sauce/ in the list of recent repos, even though it’s the only repo I work on.
    3. Click on some other repo that’s at least in the tomato/ org.
    4. Navigate up to the tomato/ org.
    5. Find the sauce/ repo in the list.
    6. Traverse half the fucking screen to hit the “Releases” heading in the middle of the About-section.

    Via the Firefox URL bar:

    1. Type gi→t→s→r→.
    2. Hit Enter.

    I admit, it’s hard to compete with the latter, but I wouldn’t know how to navigate that way, if the former wasn’t so terrible.










  • Not sure, if I stopped listening to mainstream music around that time, but uh, both of my examples are from 2011, apparently:

    • Kind of a classic response to this question, is “Pumped Up Kicks” from Foster The People. It’s got that upbeat melody, and the lyrics are this:

    All the other kids with the pumped up kicks
    You’d better run, better run, outrun my gun
    All the other kids with the pumped up kicks
    You’d better run, better run, faster than my bullet.

    • And my other example is “The A Team”, apparently originally from Ed Sheeran, and apparently also with an upbeat melody. I think, I only ever listened to a cover version. But yeah, it’s about drug use and sex work, and how those kind of necessitate each other…

  • We’ve got a WebAssembly web-UI at $DAYJOB. Implementation language is Rust, we use the Leptos framework (although other mature frameworks are available for Rust).

    Pros:

    • Same language and similar tooling as in the backend. Most libraries work the same way (obviously excluding libraries that read from the filesystem, for example). This is especially good, if you’ve got lots of “full stack” devs.
    • Same model classes as in the backend. If you change a field, the compiler will force you to fix it on both sides. It is compile-time guaranteed that backend and frontend are compatible.
    • Rust is a nicer language than JS/TS. I find especially Rust’s error handling via Result and Option types + pattern-matching works really well for UI stuff. You just hand the Result value over to your rendering stack and that displays either the value or the error. No unset/null variables, no separate error variable, no ternaries.
    • Having a strict compiler makes it less bad when you’re lax on testing, and frontend code is a pain to test.

    Cons:

    • If you’ve got pure frontend folks, or people who are deep into React or Angular or whatever, those are not going to be as productive.
    • The JS ecosystem is massive, you just won’t find as many component libraries for Rust, which can definitely also reduce productivity.

    With me being in a team with few frontend folks, I would definitely opt for it again.