centerDiv.js
-
wrote on last edited by [email protected]
got it from here https://front-end.social/@elly/114668957184577014
-
got it from here https://front-end.social/@elly/114668957184577014
wrote on last edited by [email protected]div { display: grid; place-content: center; }We've come a long way...
-
got it from here https://front-end.social/@elly/114668957184577014
Oh yes please. But not JavaScript. I use Rust frameworks to avoid all three!
-
got it from here https://front-end.social/@elly/114668957184577014
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.
-
Oh yes please. But not JavaScript. I use Rust frameworks to avoid all three!
Eww Rust! I hate memory safe languages, I love torturing myself with C
-
got it from here https://front-end.social/@elly/114668957184577014
JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.
-
Eww Rust! I hate memory safe languages, I love torturing myself with C
You can wrap everything in unsafe and keep living dangerously!
-
Eww Rust! I hate memory safe languages, I love torturing myself with C
Yew* Rust
FTFY
-
JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.
Dynamically loading pages suck too.
-
got it from here https://front-end.social/@elly/114668957184577014
real ones learn dhtml
-
Oh yes please. But not JavaScript. I use Rust frameworks to avoid all three!
Yeah I gotta get my workplace to get on board with it. Rust->Webasm is simply amazing
-
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.
-
Most pages don’t need dynamic loading.
-
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.
-
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.
wrote on last edited by [email protected]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.
-
You can wrap everything in unsafe and keep living dangerously!
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. -
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.
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.
-
Yew* Rust
FTFY
Nah, they had it right
-
Nah, they had it right
wrote on last edited by [email protected]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 -
div { display: grid; place-content: center; }We've come a long way...
You misspelled nesting tables
