Hacker Newsnew | past | comments | ask | show | jobs | submit | whstl's commentslogin

You were linking to their React-only offering above, but the actual Tailwind Plus website is this one: https://tailwindcss.com/plus

The Tailwind UI blocks are a similar offering to Basecoat, and are available in non-React format.

The "Tailwind React Templates" are not really similar to Basecoat.


Agree. The optimization caveat also applies to OOP, another example someone threw in above.

Sure you can implement OOP as a library in pretty much any language, but you’ll probably sacrifice ergonomics, performance and/or safety I guess.


HN itself is way better than people give credit to. The toxicity tends to be very isolated, and divisive topics disappear quickly from the front page.

I find that there's still a subset of users that make it worse than it should be, by making too much noise about "tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage", but that is already against the rules/guidelines.


So much is removed that it gives a false appearance of consensus and harmony.

AFAIK, not a lot in HN gets outright removed. A decent amount of stuff will get flagged (and thus becomes invisible) especially when it's anywhere near politics.

But even in those spaces, few things end up actually being flagged even when the flames are burning hot.


This is not my experience. So many comments are flagged and removed. It’s just popularity.

I think it’s fine they are hidden by default. But unt we can see all removed comments we can’t understand the debate.


> I think it’s fine they are hidden by default. But unt we can see all removed comments we can’t understand the debate.

Do you have showdead on?


Yes. It’s not enough and I’m confused why.

Then how do you know that more comments are being removed?

Because I’m participating in those threads and then they go away.

/active vs the actual front page here are two very very very different experiences.

I agree. I'd argue that if you can't start a conversation with your superior about future promotions and job goals, you're probably not gonna get that promotion anyway.

Your manager is gonna be the one asking their own manager to pay you more, and will be the one doing reviews.

Also: stepping on other people's toes can crush team morale, which can sure delay promotions. Saw it happening. Keeping the manager in the loop is a good way to avoid it.


Making HN readers angry is its own reward.

I wonder if JWZ still has the red carpet for HN users. Let’s test: https://www.jwz.org/blog/2026/01/dali-clock-in-the-wild/

EDIT: Yep, still works!


It comes from the same place as "passwords expire every 30 days".

People don't understand something and just apply the most annoying rule possible.

The craziest one I saw in Germany was "cookies are allowed, localStorage is not", that was for our app. CTO overrode the CISO on the spot and called him an idiot for making rules he doesn't understand. Interesting day.


I once had to print a form and fax to a company with a signature and the instructions said specifically that "signing with a computer and sending digitally is not allowed".

I just signed with macOS Preview, applied some random noise filter and used a one-off online fax service. ¯\_(ツ)_/¯


Agreed.

Most of the work brought to me gets done before I even think about sitting down to type.

And it's interesting to see the divide here between "pure coder" and "coder + more". A lot of people seem to be in the job to just do what the PM, designer and business people ask. A lot of work is pushing back against some of those requests. In conversations here in HN about "essential complexity" I even see commenters arguing that the spec brought to you is entirely essential. It's not.


Someone commented yesterday that managers and other higher-ups are "already ok with non-deterministic outputs", because that's what engineers give them.

As a manager/tech-lead, I've kind of been a tech priest for some time.


Which is why it's so funny to hear seasoned engineers lament the probabilistic nature of AI systems, and how you have to be hand setting code to really think about the problem domain.

They seem to all be ICs that forget that there are abstraction layers above them where all of that happens (and more).


Why would the average programmer have a problem with it?

The average programmer is already being pushed into doing a lot of things they're unhappy about in their day jobs.

Crappy designs, stupid products, tracking, privacy violation, security issues, slowness on customer machines, terrible tooling, crappy dependencies, horrible culture, pointless nitpicks in code reviews.

Half of HN is gonna defend one thing above or the other because $$$.

What's one more thing?


Say it louder.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: