You might like
HTTP status code question: You send a POST request and the server is unable to connect to the database so your app errors out. Do you send a 500 or a 200 with an error message? Does your answer change if this is a GET request for a resource?
What problems do frontend frameworks solve that aren't solved by iframes?
Unpopular opinion: A search form that returns no results should have an HTTP response code of 404
It's a common enough pattern to be able to log in and log out of a site that it should be standardized beyond what it was decades ago
Can we get built-in browser auth that is actually usable? @ChromiumDev @firefox
Can we get built-in browser auth that is actually usable? @ChromiumDev @firefox
Problem: I want to be able to cache authenticated pages, but I don't want them to be viewable via back button navigation AFTER the user has logged out. What's the best solution to this?
Input type should be a CSS-level concern and not HTML elements/attributes. For example, I should be able to specify whether a list renders as a <select> would or as a <input type=radio> would with CSS
Why use javascript components when you can just use iframes as components? They are perfect for HTML, CSS, and JS encapsulation and can expose an interface to other documents if needed
Monorepo, but instead of everything landing on master, each project has a dedicated branch. Who structures their monorepo like this?
<input type=checkbox> should not have a indeterminate state. Anyone know the history behind why this is the case? Seems like a bad design decision
I'd like to have an HTTP header that allowed me to tell the browser whether or not I want a navigation added to the history stack
Put your database inside your application
Put your application logic inside your postgres database. Stop with all the edge nonsense
Case in point why it’s important to separate styling concerns (CSS) from markup (HTML). Doing so allows you to easily offer layout customization for users and easily A/B test by seeing which styles users prefer instead of ramming redesigns down their throats
You'll write better CSS if you don't try to reuse it. Use one CSS file per page and mirror the DOM. Only when clear patterns emerge should you attempt to abstract and extract CSS into other files that are then reused. When files are reused, be sure to have accompanying tests
Your CSS is hard to maintain because you don't write automated tests for it
Tailwinders are reinventing selectors it seems
Mixins for Tailwind CSS 🧪⚡️ Write classes once. Use them everywhere. tailwindcss-mixins provides a declarative API for creating reusable groups of utilities, reducing code duplication, and improving maintainability. — Check it out on GitHub 👇🏼
The Tailwind years will be looked at as a dark time in web dev history
United States Trends
- 1. CarPlay 2,942 posts
- 2. Cynthia 94.7K posts
- 3. Osimhen 36.8K posts
- 4. Katie Couric 5,921 posts
- 5. #WorldKindnessDay 14.5K posts
- 6. Black Mirror 3,901 posts
- 7. Gabon 98K posts
- 8. Megyn Kelly 14.8K posts
- 9. #LoveDesignEP7 178K posts
- 10. Massie 95.2K posts
- 11. RIN AOKBAB BEGIN AGAIN 177K posts
- 12. Sheel N/A
- 13. #NGAGAB 11K posts
- 14. Pat Bev N/A
- 15. Bonhoeffer 3,117 posts
- 16. Seidler N/A
- 17. #DirtyDonald 3,683 posts
- 18. Senator Fetterman 5,436 posts
- 19. Vine 14.4K posts
- 20. Woody Johnson N/A
Something went wrong.
Something went wrong.