Web Development

5581 readers

3 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Follow the programming.dev site rules
Keep content related to web development
If what you're posting relates to one of the related communities, crosspost it into there to help them grow
If youre posting an article older than two years put the year it was made in brackets after the title

Related Communities

Wormhole

!cool_github_projects@programming.dev

Some webdev blogs

Not sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

https://frontendfoc.us/ - [RSS]
https://wesbos.com/blog
https://davidwalsh.name/ - [RSS]
https://www.nngroup.com/articles/
https://sia.codes/posts/ - [RSS]
https://www.smashingmagazine.com/ - [RSS]
https://www.bennadel.com/ - [RSS]
https://web.dev/ - [RSS]

Credits

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

snowe@programming.dev

erlingur@programming.dev

Ategon@programming.dev

Vacant@programming.dev

The DX shift no one noticed: Web interoperability (blog.logrocket.com)

submitted 2 days ago by codeinabox@programming.dev to c/webdev@programming.dev

5 comments fedilink hide all child comments

These days, developer experience (DX) is often the strongest case for using JavaScript frameworks. The idea is simple: frameworks improve DX with abstractions and tooling that cut boilerplate and help developers move faster. The tradeoff is bloat, larger bundles, slower load times, and a hit to user experience (UX).

But does it have to work like that? Do you always have to trade UX for DX? And are frameworks really the only path to a good developer experience?

you are viewing a single comment's thread
view the rest of the comments

[–] fruitycoder@sh.itjust.works 3 points 1 day ago (1 children)

Mozillas vision of phone apps was this. It's one reason PWAs were made and part of why WASM is where it is. One of the largest barriers to adoption against it is that apps allow for tight control from the dev, not just technically, but also from a legal standpoint. For that reason I would rather have PWAs myself, a lot of apps actually suck and are just full of dark patterns.

[–] ghodawalaaman@programming.dev 2 points 1 day ago (1 children)

So basically dev develop app to have more control over you which simple website simply not provides

[–] bitfucker@programming.dev 3 points 1 day ago

Correct. The degree that a native app could invade your privacy on the desktop is insane. For mobile, thanks to sandboxing it has a much smaller surface but still annoying nonetheless when an app could just be a web. Especially if all they do is just a glorified form filing app.