centerDiv.js (europe.pub)
submitted 1 year ago* (last edited 1 year ago) by to c/programmer_humor@programming.dev

top 50 comments

sorted by: hot top controversial new old
[–] 69 points 1 year ago* (3 children)
div {
  display: grid;
  place-content: center;
}

We've come a long way...

  • source
  • hideshow 3 child comments
  • [–] 40 points 1 year ago (7 children)
  • load more comments (5 replies)
    [–] 29 points 1 year ago (13 children)

    Oh yes please. But not JavaScript. I use Rust frameworks to avoid all three!

  • source
  • hideshow 13 child comments
  • [–] 17 points 1 year ago (8 children)

    Eww Rust! I hate memory safe languages, I love torturing myself with C

  • source
  • parent
  • hideshow 8 child comments
  • [–] 10 points 1 year ago (4 children)

    You can wrap everything in unsafe and keep living dangerously!

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 1 year ago (1 child)

    Tsoding has created a few rules for writing Rust to make Rust "fun" to program in, and gave them the name of Crust.

    Here is the rule set (it may change over time):

    1. Every function is unsafe.
    2. No references, only pointers.
    3. No cargo, build with rustc directly.
    4. No std, but libc is allowed.
    5. Only Edition 2021.
    6. All user structs and enums #[derive(Clone, Copy)].
    7. Everything is pub by default.

    If you ever want to try this out for some ungodly reason, there's a GitHub repository with an example Main that shows how to use libc and other libraries (in the example, it's raylib), and with a Makefile showing how to compile your projects (remember we aren't using cargo).

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • [–] 3 points 1 year ago (2 children)
  • load more comments (2 replies)
    [–] 22 points 1 year ago (5 children)

    I worked with some pretty dumb people who mocked me for years as the guy who couldn't design a UI to save my life because the product I inherited was designed by someone in the 1990s. it wasn't pretty but it was functional.

    any time a UI request came in for the new product and I would try to take it, the PM would pull it and give it to someone else. "oh, their skillset is better suited for UI/UX." I was told.

    I got fed up with it and designed my online portfolio. used it to showcase my work and skills even documented my process from mockups to design iteration and final products.

    I then posted on linkedin my new portfolio and listed myself as open to connect. within a day the PM made a point to pull up my portfolio on standup and asked me where I got the template. told them, "no template. as you can see in the documentation I designed it from scratch using HTML5 CSS3 and JavaScript. I also included the js packages I used."

    they were stunned and immediately started to shuffle some UI tickets my way. I just said, "sorry, my skillset is better served for backend requests."

    I quit two months later after a few interviews that seemed to go well. I hated that shithole.

    moral of the story? don't discourage people from taking on tasks they aren't obviously suited for. they might just surprise you.

  • source
  • hideshow 5 child comments
  • [–] 7 points 1 year ago (4 children)

    I agree with your final take, but why would you want to take frontend tickets if you can also do backend work?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 8 points 1 year ago

    change of pace, mostly. I also like the challenge. when I'm not challenged at work I lose interest easily and can spiral into not doing my job. so it's nice to break up a long running project with some new bugs or tasks that are unrelated.

  • source
  • parent
  • [–] 19 points 1 year ago (11 children)

    JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.

  • source
  • hideshow 11 child comments
  • [–] 12 points 1 year ago (5 children)

    JavaScript frameworks actually exist for two reasons, one, vanilla JavaScript lacks ease of use (does not suck and I don't care who disagrees) and two, people love over engineering the fuck out of technology. See: technology since the iPhone came out. We have advanced systems around the world spinning up processes to make up for the fact that touch screens are hard to type accurately on.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 10 points 1 year ago (1 child)

    jQuery got popular because Internet Explorer, Firefox, Chrome and other browsers weren’t exactly cross compatible. Writing vanilla JS was risky business in that sense.

    It also supported AJAX across all major browsers, which meant the website could make API requests without reloading the entire page. It was super revolutionary to press a button and it only changed a part of the page.

    Then Angular and React took it a step forward and that’s where we are now.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 1 year ago*

    I am very aware of the progression. But you're vastly glossing over how much complexity (and feature set) was added after jQuery. If JavaScript sucks, how would you change it? Shitty browsers implementing it poorly in the past (and safari doing so today) doesn't make it suck.

  • source
  • parent
  • load more comments (1 reply)
  • [–] 12 points 1 year ago (1 child)

    OP, I don't think you've correctly linked to the post (when I visit the linked webpage, the browser tries to download an ActivityPub activity instead of showing the post in the Mastodon web UI). Please replace the link with this one.

  • source
  • hideshow 1 child comment
  • [–] 9 points 1 year ago (5 children)

    Wait until you see what they do to avoid learning SQL or Regex or JSON Pointer or XPath.

  • source
  • hideshow 5 child comments
  • load more comments (2 replies)
    [–] 9 points 1 year ago (1 child)
  • [–] 9 points 1 year ago

    I was so pleased when a brief for a thing at work was "no frameworks".

  • source
  • [–] 4 points 1 year ago

    Damn that's some spicy takes lol.

  • source
  • [–] 4 points 1 year ago

    React sucks and is way way way overdone and ill die on that hill

  • source
  • load more comments
    view more: next ›