My point is when you have 100 different ways to achieve result - it's always led to inconsistency. And it's very dangerous in large distributed app because resolution of those small differences means you have to support 50+ variation of the same submit button.

Personally I'd prefer to have up to 5-10 option of buttons for all possible cases. And it's not only visual simlicity, and not only easier to support but even help your own customers because they are not have to looking for 100+ different button styles.

I don’t believe the Tailwind approach is a stable, scalable, or reliable solution for large, long-living products.

It works well for fast delivery, prototypes, and teams optimizing for short-term speed, but over time it tends to spread styling decisions across markup, making the system harder to control, reason about, and maintain.

I agree. But also, on a broader note, I have no desire to introduce node for the sole purpose of some css niceties.

Coming back a couple of years later to a broken build system when you just want to change a colour is no fun.

I thought proton has largely solved this

yes, but it’s very hit and miss depending on your software, hardware and the humidity in the air.

Location: Kyiv, Ukraine Remote: Yes Willing to relocate: No Technologies: php, laminas, symfony, nodejs, ruby, mongodb, aws ect. Résumé/CV: https://www.linkedin.com/in/necromant2005 Email: necromant2005[@]gmail.com

I love building a big systems with a lots of data, right now my app process 2-3Tb data daily

A list of base hack like content grouping, user id, custom user properties and UX metric like page generation time and page load time

Continue discussion about using static files as database instead of default relational MySql/Postgree/Mongo

For a friend I made this: https://en.hayovasweets.com/

It’s mostly list of markdowns and images in folders. Everything else generates during deployment on GitHub:actions

It was simpler to show GitHub desktop rather than installing something like Wordpress machinery monster and spent hours to teach how to use it. Now the process is simple:

1. Create a folder

2. Put there markdown and images

3. Commit

In this short study, we will analyze the Instagram pages of five world-class musicians - Michael Jackson, Amy Winehouse, Freddie Mercury, Bob Marley, Prince.

By the way. Did anyone try to use a large sd-card as storage ?

I meant 256-512GB. In my logic it must decrease power consumption when keeping the same IO performance as external ssd connected through USB.

I am uncertain if USB can be a bottleneck there, but if I am not mistaken, SSDs offer better (more?) cache. This dramatically reduces time needed for non-sequential read/write operations.

USB - 30Mbyte/sec theoretically for RPI, but in reality somewhere around 20Mbyte/sec

SD cards - class 10 tested on RPI show the same performance 21-27Mbyte/sec

So the issue mostly in throughput performance of the interface

Face Palm? Face Down ? Face Epic Fail - after acquisition of Epic Games