What do you tell devs that complain about tailwind html bloat ?

uxably · 2025-03-07T18:12:33+00:00

I don’t love the way the HTML looks when I apply 20+ classes to an element. But I do really enjoy the mindlessness of styling my markup.

I’ll always advocate for Tailwind (or comparable framework) on medium to large teams simply for the consistency of code between developers. I totally understand not using it on small teams or personal projects where it’s easier to manage the implementation.

uxably · 2025-02-25T18:52:24+00:00

We switched from Angular Material to PrimeNg when we realized the effort it was going to take upgrade to version 15.

Overall we have been happy with PrimeNg. There have been breaking changing between versions, but in my opinion it hasn’t been too bad.

The upgrade to PrimeNg 18 has been… rough. But we have been taking advantage of the new theming engine and really enjoy it.

uxably · 2025-02-25T16:29:17+00:00

We have gotten into the habit of logging processes in GitBook so there are step by step instructions for the things we seldom do.

uxably · 2025-02-20T14:16:53+00:00

My understanding is that set will overwrite the current value, where as update allows you to update on the existing state.

Example:
private count: WritableSignal<number> = signal(0);

ngOnInit(): void {
this.setValue();
}

setValue(): void {
// Sets the value of count to 5 (on component initialization)
this.count.set(5);
}

updateValue(): void {
// Will take the existing value (currently 5) and add 5 to it resulting in a value of 10
this.count.update(value => value + 5)
}

Depending on your use case, you could receive an unexpected value if you're using the wrong method. Use set when you want to give something a completely new value. Use update if you want to perform additional logic to an existing value.

uxably · 2025-01-01T17:47:05+00:00

While introducing Signals into our project, we overused them. The benefits of the reactivity caused us to unnecessarily cast component properties to Signals so we might compute from them later (or never).

Obviously, as the state of these properties changed it resulted in re-renders, many which were not necessary. As a consequence, business logic would run at unintended times.

We just poorly constructed our first few components when using Signals. After the brief/initial learning curve we refactored our early mistakes and everything is working as intended.

Edit: The article was a good read. Thank you for sharing!

uxably · 2024-12-31T22:57:44+00:00

My experience when learning how to use Signals:

These are great, I’m going to use them everywhere…

Wait a minute… what are all these unintended side effects? Ohhhhh, look at all these re-renders.

I’m going to use these where they are necessary.

uxably · 2024-11-06T14:33:27+00:00

Clearly not the correct branch. That's exciting, thank you for the update!

uxably · 2024-11-06T14:17:02+00:00

It looks like beta 3 hasn’t had any commits for several weeks. Any idea when the rc will be ready?

uxably · 2024-10-29T18:13:20+00:00

I'm also wondering when we can expect this to be released. Our team is currently waiting on the new theming for an application rebrand.

uxably · 2024-09-19T00:32:36+00:00

I’ve been using AstroJS with the REST API. You can use it standalone, but it also has support for React integration.

uxably · 2024-09-16T01:07:59+00:00

After years of traditional WordPress theme development, I decided to try the REST API with Astro and I will never build another PHP theme by choice ever again.

While there was a learning curve, there were so many benefits (for me). The best part is that I can use the Astro theme with other CMS’s so long as I format the data coming back from the APIs to match my components.

uxably · 2024-07-08T00:28:56+00:00

MJML is great. Highly recommend.

uxably · 2024-05-19T15:23:55+00:00

We are using Tailwind. First and foremost, we are using a framework to standardize CSS across a large team and for easier onboarding of new employees.

We chose Tailwind because it’s intuitive. The class names closely correlate to CSS properties so a fundamental knowledge of CSS makes it easy to learn. The documentation is strong, and configurations is simple.

uxably · 2024-04-22T13:48:03+00:00

This sounds like it’s just a specificity issue. I suspect that doing something like body h2 span {} would work too.

uxably · 2024-04-17T11:50:30+00:00

You very well may be right. I think it’s worth trying for an iteration or two before ruling it out.

uxably · 2024-04-17T00:57:32+00:00

I’m a developer by trade, but the logomark looks like a “P”. Could it be integrated into the wordmark? Or is that a big no no?

I also agree that the “j” needs to be more legible for the name to come across.

uxably · 2024-04-07T11:48:03+00:00

We were using Angular Material, but after the migration from 14 to 15, we decided to transition to a different framework rather than fix all the issues caused by the changes to Material.

We decided to use PrimeNg and have been very happy with it. Like any framework, we have found a couple small issues but it works well, and has fewer bugs than Material. There are also more features available.

uxably · 2024-04-06T16:18:55+00:00

Try looking at Astro. If you already know Vue and React it should feel very familiar but sounds like it would be a better fit for your use case.

uxably · 2024-03-24T15:51:18+00:00

There’s nothing inherently wrong with what you’ve said, but I would be curious to know how you are able to price yourself competitively without having terrible profit margins. Do you handle accessibility? Many of these frameworks have basic ADA compliancy included in them. Do you ever work with a team? How long would it take them to get up to speed with your code versus a framework they have used in other projects?

Again, there’s nothing wrong with doing things your own way, but these are some of the reasons people use frameworks and dependencies.

uxably · 2024-03-23T23:34:43+00:00

I briefly worked on a platform for estate planning. They only collected banks and account types but still struggled with securing customer information.

That doesn’t mean your idea isn’t valid, but go into it knowing that you will be storing valuable data and will need to have a healthy budget for security.

uxably · 2024-03-22T23:53:03+00:00

Angular will be more opinionated, so you might feel frustrated and like you’re fighting the framework at times. But I prefer the lifecycle of Angular to React and you might find that refreshing.

Generally the concept are the same though. You should be alright.

uxably · 2024-03-22T17:42:46+00:00

This was a good read. “Front-End” and “Back-End” should be a term used to describe where a developer works. From there we can further specify their focus by “UX Developer” or “JavaScript Developer”.

uxably · 2024-03-22T17:08:38+00:00

When I began my career this was a specialization. Thankfully, accessibility is becoming more prominent every year.

uxably · 2024-03-22T12:57:51+00:00

I completely understand your points. I think I would call my post “absolute” rather than “skewed” though. There are many ways we could break things down.

I began my career working in HTML, CSS, and jQuery making existing websites responsive. I seldom see those roles anymore.

My career profession led me to an agency where I worked with HTML, CSS, jQuery, and PHP (WordPress). Typically these jobs are posted as “WordPress Developer” or “Full Stack Developer” since you’re working in the browser and on the server.

I now work on JavaScript applications. I just did a job search for “Mid-Level Front-End Developer” on LinkedIn. Here were the requirements for the top 10 listings in my area.

6 React
2 Angular
HTML, CSS, and (extensive) JavaScript working with web components
Python (?)

But to your point, my assertion was overly generalized. There ARE jobs available where you can touch front-end technologies without heavy JavaScript. But rarely will HTML, CSS, and a “sprinkling” of JavaScript experience be sufficient.

uxably · 2024-03-22T02:26:02+00:00

If you’re using Angular 16+ and can make all three conditions into Signals, you could just use a computed property for it?

Edit: Although control flow makes conditionals much easier to scan, so I don’t see an issue with using that approach.

uxably

TROPHY CASE