centerDiv.js
-
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.
people love over engineering the fuck out of technology
Exhibit A: 2.85 Million packages, as of mid-2023
-
div { display: grid; place-content: center; }We've come a long way...
The collective man-hours this would have saved people, if we had it back in 1999, would be staggering.
-
got it from here https://front-end.social/@elly/114668957184577014
Damn that's some spicy takes lol.
-
got it from here https://front-end.social/@elly/114668957184577014
React sucks and is way way way overdone and ill die on that hill
-
got it from here https://front-end.social/@elly/114668957184577014
Obligatory https://justfuckingusehtml.com/
-
got it from here https://front-end.social/@elly/114668957184577014
Wait until you see what they do to avoid learning SQL or Regex or JSON Pointer or XPath.
-
people love over engineering the fuck out of technology
Exhibit A: 2.85 Million packages, as of mid-2023
Unless those are mostly overly complicated, it doesn't speak to what I'm saying. But I guess it means people like doing their own engineering better than relying on others
-
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.
got it, my bad
-
Obligatory https://justfuckingusehtml.com/
That was wonderful, thank you for sharing. When it's done well, I really enjoy this style of prose.
-
got it from here https://front-end.social/@elly/114668957184577014
I use plain HTML along tachyons.io, it's pretty neat.
-
Obligatory https://justfuckingusehtml.com/
I had to resize my browser window in order to read that how dare you not simply read my mind and select my preferred column width instead
99% of users, probably
-
got it from here https://front-end.social/@elly/114668957184577014
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.
-
Oh yes please. But not JavaScript. I use Rust frameworks to avoid all three!
Flutter like a butterfly, sting like a Dart.
-
I use plain HTML along tachyons.io, it's pretty neat.
On mobile the header has overlapping content- not the worst but shows very little attention to detail for a CSS toolkit
-
unsafedoesn't deactivate memory safety. It only allows you to then create raw pointers and whatnot, which you could use to circumvent memory safety, but all the normal language constructs still do enforce it.I know, but it does let you sled off a cliff if you choose to.
-
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.
I agree with your final take, but why would you want to take frontend tickets if you can also do backend work?
-
I agree with your final take, but why would you want to take frontend tickets if you can also do backend work?
Raw spite. If you're upset enough to build a whole LinkedIn profile, you've already mentally moved on to the next company.
-
Raw spite. If you're upset enough to build a whole LinkedIn profile, you've already mentally moved on to the next company.
With me too, my employer has to start worrying once I put my current position into my linkedin profile.
-
Wait until you see what they do to avoid learning SQL or Regex or JSON Pointer or XPath.
Ugh, i've had to write some Selenium tests where I had to come up with weird ass Xpaths because not a single fucking element had an ID and over half would spawn something in a different div
-
I agree with your final take, but why would you want to take frontend tickets if you can also do backend work?
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.
