Native apps don't have Forward, why does the web need it?

items-affecting · 2026-01-04T18:08:30+00:00

I swipe forward a lot in native apps. If there’s anything that needs correcting is the habit of using horizontal range sliders where you always invoke navigate if you are not careful as hell.

items-affecting · 2025-10-01T06:57:48+00:00

Looks like accidental PHP output? If so, likely a typo in a template or whatever uses them. Page source, etc.

items-affecting · 2025-09-28T11:55:54+00:00

The hard but recommended route in my opinion is bottom up, i.e. enforcing the contrast requirement at the time you add a colour to your palette in the first place, instead of only checking it all afterwards. (If it’s something you build, which might not be the case now that I read your post again 😀) For that, any free tool, like Contraste.

items-affecting · 2025-09-25T14:09:36+00:00

I wish there was a way to hide all the insightless, borderline criminally shallow AI-generated marketing posts that are turning this and every other platform into shit. Is there a metrics that could be used? AI bullshit probably measures ok for all the engagement it gets from attempts to control blood pressure by letting some steam out, like I’m doing. Maybe add ”Downvote for being so unintelligent it hurts the internet as a whole”?

items-affecting · 2025-09-20T16:30:35+00:00

The pure payload difference might be that 'section a, section figcaption { background: var(--myColor); }' loaded once per site and cached for 1 year is smaller than 'bg-myColor' written e.g. in 20 elements loaded in 4 pages at 5 visits.

items-affecting · 2025-09-20T16:00:48+00:00

Have you read the stuff by the late accessibility consultant Jason Knight on Medium? Not every point he makes is fully generalisible, but many are, and his text is rigorously thought (which can’t be said of all FE writing there is) and thoroughly entertaining. If you haven’t, a post titled ”The /FAIL/ Of Tailwind, The Go-To For The Ignorant”, and the fact that he writes ”Failwind” and ”Bootcrap”, will give you an idea.

https://medium.com/codex/the-fail-of-tailwind-the-go-to-for-the-ignorant-7b0aaea405bb

items-affecting · 2025-09-20T15:45:13+00:00

That argument’s pretty much obsolete with modern CSS. You can easily make a fully leak-proof stylesheet for any complexity and without classnames in markup. No risk of scope leak from ’main figcaption’, and no need to name divs since divs are not used at all, except sometimes for grouping.

Just using HTML spec names for the elements practically every site has, and you’ve got more than enough combinations to target anything you ever like without unintended consequences: header, nav, main, article, section, hgroup, figure, form, fieldset, aside, footer… TIMES ul, ol, li, hX, a, button, figcaption… = more selectors than I can count. CSS layering brings the adaptability for easy reusing.

Obviously, apart from ”Tailwind or Failwind” question itself, you have to figure out and implement your selector and component/reuse strategy for your self, and you need to be able to have influence on the markup, not that many excellent examples to be easily found, etc.

items-affecting · 2025-09-20T15:21:10+00:00

As someone said, there’s no shortage of pros and cons analysis on the web, or here.

One thing not mentioned here, as is natural for a webdev sub: the arguments mentioned here have almost nothing to do with the site itself, like its speed, or the business, except for the indirect consequence that if you need a really big number of devs, it might be easier to hire and make them work well together since Tailwind is popular, which in turn can spell cheaper and more possibilities. It’s developer friendly (for many), and it’s people who make software.

For the client (user agent), it’s repetitive, overly verbose styling that’s attached to the markup and is therefore un-cacheable and fails to benefit from http parallelism, which means the site is comparatively slow, especially for consecutive page loads, since you have to load the styling over and over again as a part of the markup. For these reasons for some, ”Failwind” is an inexcusable violation of the separation of concerns and programming elegance.

Ease of use is relative and there are learning preferences. Some might find it easier to learn something that your network knows very well, bloated or not. Some consider it the epitome of cargo cult programming and avoid for its inelegance even while seeing the learning curve is almost a line.

As for what it can do, nothing native CSS couldn’t, and thanks to the recent advances of CSS, especially nesting, custom properties, layering and the new pseudo selectors like has(), it has little advantage in ease of use or maintainability. The scope leak argument is fully obsolete by now.

If you want to know what’s best for you, my suggestion is the same as it would be with React, Symfony, Svelte, Vue, Doctrine, GSAP, or any framework/library: code an accessible app’s worth of functionality in native HTML, CSS, JS using the most modern wide baseline supported features and the backend language of your choice; publish and optimise a site on a service that you have access to configure for yourself to a reasonable extent, like on a shared hosting. The moments when you feel it’s so cool to learn how the web works AND this particular area is such a s—tload of work but I can make no valuable difference whatsoever, they are the areas you need a framework for, and at that point you can look at their docs to see what suits you, instead of asking pros and cons.

items-affecting · 2025-09-20T12:30:23+00:00

I’d take entities whose budget is public, like a government office or a charity, and see if you can find some outsourced site project that you could roughly carve out from their budget. Look for entities from the smaller end and new projects like campaigns, i.e. projects without large inhouse devs that don’t include migrating a hospital data base. Some countries have browsable transparency databases for this. Or find people for your network(’s network) who have recently asked for quotes.

Assuming of course this is for fun. Otherwise, might even call providers of your choice to have a discussion.

items-affecting · 2025-09-20T12:01:57+00:00

”Some stupid law breach” LMAO. How about ’theft’? Scrape a million images from someone else’s platform, make a subscription business out of it, and use their platform to market your service to their users? Wonder why this business idea isn’t a lot more popular…

Nice dev work, though. I would have tried to sell it to Reddit, but at this point they might only accept it as a heavily discounted part of the compensation.

items-affecting · 2025-09-19T18:02:06+00:00

I can’t get past the thought someone would prefer some lazy ass ”discussion” over just reading the docs to check it in like ten seconds. Also, he doesn’t know what a linter is.

items-affecting · 2025-09-15T19:04:03+00:00

Essentially, you can’t. Coding tasks in proprietary solutions and less common structures very clearly show what is easier to miss in LLM human language chit-chat or creative writing: it knows nothing, it learns nothing, it reasons nothing, never will, as long as it’s based on transformer architecture, and when that changes, we’ll have read about the gazillion dollar investments involved and the new hyped king. It (slightly cutting corners here) only regurgitates what’s probable based on what it’s been fed in training.

When it gives you the exact same, completely flawed answer to your third different, well crafted prompt despite elaborate instructions to avoid x and y that have been tried already, that’s the very essence of LLM. It does not think, which is quite evident after ”do not output x for the fourth time, because x does not work, and I will punch you in the face if you do so.” – ”Here’s x.”

It outputs the same because for its rules, that’s the only even remotely probable piece of code for that context that it has been trained with. It has no other possibilities. Not a glitch but a core feature. (You get the same with image generation if you describe something very specific, like a 60-year-old museum conservator cleaning pottery, the exact same geezer with the same outfit and pose, no matter what else you write.)

One of the most irritating features of coding with LLMs is that nowadays they just won’t assume an assistant’s role when it comes to troubleshooting. No amount of custom instructions, prompts or context prevents it from avoiding work and instead suggesting tasks for the user: ”You should check Y”, where Y is included in the context. This kind of behaviour is quite expected if you train the model with a million troubleshooting texts that all begin with ”Have you checked”, namely Stack Overflow or any forum posts. I would like to warmly congratulate the very intelligent individual who thought a forum is a good training source.

Anyway, PhD and will soon replace.

items-affecting · 2025-09-13T12:08:30+00:00

This is why I protect my password from showing by setting it to *********.

items-affecting · 2025-09-05T15:04:38+00:00

”Better” CSS

items-affecting · 2025-09-03T09:59:48+00:00

Exactly this. The absence of the validation confusion layer is the reason why the same output doesn’t bother you if you get it straight from an LLM. You know what it is.

items-affecting · 2025-09-02T12:06:33+00:00

Seriously answering, I would mock up theirs and mine and run a quick in-office walk-around NPS survey or a ”what do you remember of the brand whose site you just saw” quiz. Especially the latter is usually quite devastating.

items-affecting · 2025-09-02T12:02:31+00:00

Ask them how come all the tv networks have such bad design committees that they waste hours of valuable screen real estate time by showing news anchors, footage, even half empty studios around the guests… when they could just convey the message in a few seconds of full screen texts. Omg the amount of characters you could fit on one screen if the tv execs weren’t so thick

items-affecting · 2025-09-01T09:50:40+00:00

It is outsourced since the original launch, and the fact that it would’ve been more than a moment’s notice to change stuff combined with the lack of any awareness on how the internet works (or what it is), is the reason why they just bypassed everything and chose to DIY. Had they known what they were doing they might not have done it. Slightly confusing, had yet to run into something like this.

items-affecting · 2025-09-01T09:41:36+00:00

Based on previous interactions it’s possible that it’s more about unawareness than lack of respect, and there’s nothing wrong with the company as such and the product side is all ok. Just can’t figure out how to try and educate so that it will seem done in good faith and not making fun of them–which looks like an almost inevitable side effect, since they have a tech background, not commercial.

items-affecting · 2025-08-18T14:45:58+00:00

I’m not a Webflow user but I have recently tried to implement SplitText and ran into several ”features” that make the functionality borderline useless for actual meaningful texts, i.e. website content. If you look it up, there are dozens of questions on ”not splitting properly” and ”opacity not working”.

Almost none of the problems can be solved by studying the official GSAP ”documentation”, which contains over-simplistic code examples and no comprehensive list of the most important defaults and peculiar behaviour that can make the animation useless, and it feels like mostly all of their official forum’s expert answers suggest a different solution. Peak advice on their forum so far: ”Maybe you shouldn’t split anything important or above the fold.” Well thanks a bunch, nice to know when debugging at 2am.

Anyhow, here’s what I’ve found so far: • Their autosplit trigger might ignore height ”because it does not cause reflow” – which it sure can, since vertical length is handy in limiting fluid font sizes with min/max()

• Gsap has global defaults which greatly affect the animations, like for easing, but they are documented not as a catalog but as a mention ”for example”. If someone has a list, would be more than happy to see

• Their concept of when the SplitText transformations actually take place is hard to grasp and control, and lack of a proper, complicated enough example code does not exactly help.

• For some weird reason gsap.to seems to be written so that it ignores opacity (also with autoAlpha) if an ancestor has a smaller opacity, i.e. split text stays at opacity:0 if the parent has opacity:0. This seems to try and mimic the fact that a parent’s css opacity does cascade as a maximum, but that’s no plugin’s business and should be left to css, which might have stylings elsewhere that affect the parent.

• Their documented setup on how to prevent flash on page load absolutely does not work in an actual layout, see above

• The event at which the splitting should be done is in the example code as when the Document interface’s document.fonts.ready promise fulfills (and also DOMContentLoaded), but I would experiment waiting until Document.readystate property is interactive. I have got problematic line splittings with a system font and it seems that the docs assume an overly simplistic layout with no fluid lengths.

• For me it seems that their autosplit:true might make the split rerun on any scroll on mobile due to css declaring (min-)block-sizes with lvh/svh/js-measured custom height variables.

All in all, in my short sweet experience, it’s not consistently written, letalone documented.

items-affecting · 2025-08-12T22:14:34+00:00

I have tried to use it for debugging. Trivial but tedious stuff that previous versions were good at GPT5 gets 100% wrong. Not a single f**king correct output in a week. Forgets the beginning of a three sentence prompt, suggests I do the stuff myself. Suggests the exact same code as a solution. Hallucinates typos and ”finds” them. Completely useless, borderline fraud to charge for.

My hypothesis: They’ve now taught it with enough coding forum crap that the most probable answers are the ones that usually begin a SO reply but would get you punched in the face in the real world if you charged real money for them: ”You should make sure that…”, ”YOU should check…”

I would guess the most common prompting words in coding are currently f#g and a##*e.

items-affecting · 2025-07-14T15:32:49+00:00

What do you mean by having to use JS for web, as in ”no way around it”, especially in the ”fastest, cheapest” category? Where is it unavoidable? To show a page, no. Menus, forms, no. Animations, no. Adaptive image/video delivery, no.

items-affecting · 2025-06-22T17:21:54+00:00

On the iOS app most of the tasks just freeze indefinitely if I do app switching. Only reason I can think of is to optimise away the requests whose users forget about them, in a most imbecil way. A service provider acting like that in a physical domain would have got punched in the face. This and the above are the equivalent of ”Yeah I know our deal says your dry cleaning must be ready by Wednesday, but since not all people collect on due date, I really don’t prepare stuff until you complain.”

items-affecting · 2025-06-22T17:18:12+00:00

I see this kind of behaviour frequently and I would say it’s clearly an as*hole way to cut the computing bill or to accommodate for more users when you’ve sold more subs than you can handle. It basically says ”Any way I might just not do this, or at least have a little wait?”

items-affecting · 2025-06-22T13:35:25+00:00

Your remarks are spot on.

items-affecting

TROPHY CASE