You must log in or register to comment.
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?
Why not? Both needs skills to accomplish very well.
I’m not a frontend guy, but I like to mess with frontend stuff once in a while!
Flex is so fun!
Managing css masterfully is a skill in itself!
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.
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.
Obligatory https://justfuckingusehtml.com/
I’m totally going to bookmark this & also I’m going to insert this as well.<br> https://www.htmlhobbyist.com/
That was wonderful, thank you for sharing. When it’s done well, I really enjoy this style of prose.
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
You don’t just zoom?
Not on desktop
You can’t just hold control and scroll the mouse wheel?
I don’t like reading big text. I’d rather have small text in a smaller area
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.
You misspelled nesting tables
My man right here. Y’all ever want to code some HTML emails? Nested tables as far as the eye can see!
Wait until you see what they do to avoid learning SQL or Regex or JSON Pointer or XPath.
Wait until you see when they refuse to learn anything but SQL.
Not something I’ve encountered.
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 was so pleased when a brief for a thing at work was “no frameworks”.
Oh yes please. But not JavaScript. I use Rust frameworks to avoid all three!
Flutter like a butterfly, sting like a Dart.
Eww Rust! I hate memory safe languages, I love torturing myself with C
You can wrap everything in unsafe and keep living dangerously!
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):
- Every function is unsafe.
- No references, only pointers.
- No cargo, build with rustc directly.
- No std, but libc is allowed.
- Only Edition 2021.
- All user structs and enums #[derive(Clone, Copy)].
- 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).Oh boy, now I can stop missing C++
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.
Yew* Rust
FTFY
Nah, they had it right
Knew someone would say that, lol, gold project, sad that it’s gone unmaintained and my man started working on home-manager at home
…wait
Yeah I gotta get my workplace to get on board with it. Rust->Webasm is simply amazing
Men really out here inventing entire JavaScript engines so they don’t have to learn Rust/C/C++/whatever
Meanwhile women are hand-coding in assembly, like God intended.
JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.
Most pages don’t need dynamic loading.
True
My menus need to be dynamically reloaded!
Dynamically loading pages suck too.
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.
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.
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.
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
Immediate mode rendering and components seem to be why people use them. And you know what? The web should natively support those but doesn’t (well it kinda bad components, but ehhh). Otherwise I agree, the frameworks are overcomplicated.
It’s still Javascript.
React sucks and is way way way overdone and ill die on that hill
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
real ones learn dhtml
Do you remember the dhtmlguru? The site had the bronze man holding some kind of ball over his head and would magically move when you hovered over the navigation menu.
Damn that’s some spicy takes lol.
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 :(
Wait till you see what they do for a bit of concurrency
