Comments URL: https://news.ycombinator.com/item?id=38445660
# Comments: 8
Comments URL: https://news.ycombinator.com/item?id=38433358
# Comments: 134
Comments URL: https://news.ycombinator.com/item?id=38378776
# Comments: 87
Comments URL: https://news.ycombinator.com/item?id=38438261
# Comments: 40
Comments URL: https://news.ycombinator.com/item?id=38445747
# Comments: 31
Feel free to tell what you plan on doing this weekend and even ask for help or feedback.
Please keep in mind it’s more than OK to do nothing at all too!
Hey Lobsters community! 👋 I’m diving into the world of PostgreSQL and curious about the tools fellow developers use to interact with this fantastic database.
1- What are your go-to tools or software for managing, querying, or interacting with PostgreSQL databases?
2- Any particular GUI clients, command-line tools, or libraries you find indispensable for your PostgreSQL workflows?
3- Are there any lesser-known or niche tools you’ve discovered that have made your PostgreSQL experience smoother or more efficient?
Looking forward to learning from your experiences and recommendations! Thanks in advance for sharing your insights! 🐘✨
Comments URL: https://news.ycombinator.com/item?id=38145625
# Comments: 48
You just take some normal HTML markup, wrap it with a custom element, and then write some JS to add capabilities which you can then style with regular CSS! Everything’s of the Light Side of the Web. No need to pierce the Vale of Shadows or whatever.
I think Eric’s approach here should be the default for most web components: you probably don’t need to mess around with the shadow DOM, and you should definitely be wrapping your web component around existing HTML instead of witing opening and closing tags with nothing in between.
Augment, don’t replace.
This is a follow-up to a comment I wrote a few months ago that caused some heated reactions and, now that I look, seems to have reduced my activity on this site. In the months since, I’ve spent some time thinking about why my comment rubbed people the wrong way, and coming up with a less threatening phrasing. I know, terrible social timing. But I think it’s an important conversation to have. So here it is, a do-over:
I’m very happy to receive the work people put in to reduce the number of seams in my experience. But if a website lays out wrong with text overlapping with text, and then fixes itself after I resize a little and rejigger the fonts, I try to put that out of my mind. I want to focus on the important stuff. Is this website or app giving me useful information, is it respectful of my attention, is it relaxed around me (not squirming, squirming to get its tentacles deeper into me). A seamless experience can’t compensate for failings in these areas, and it is all too common for seamless experiences to hide all manner of deeper malfeasance. When we push for more seamless experiences we’re also encouraging the organisms we interact with to grow more tentacles (hiring! HR!), make them more muscular (growth team!), use them more ceaselessly in search of advantage (an ad protruding slickly from the bottom of the pane! Marketing materials persuading people to not organize!)
Let’s cut the mild grasshopper some slack; hopefully then it won’t turn into a locust.
Open source should absolutely try to improve its UX. I don’t want to encourage complacency. But any comparison purporting to judge the “best” apps is useless if it’s not holistic. Accountability and trustworthiness (admittedly not perfectly correlated with open source! but correlated!) too belong on the credit column, and with far more weight.
Comments URL: https://news.ycombinator.com/item?id=38404426
# Comments: 46
Comments URL: https://news.ycombinator.com/item?id=38265773
# Comments: 8