3 ms·

> Single developer projects can build to the caliber and consistency of large development teams. Yet the simple blog website static page saying that looks very

by dmantis 1mo ago

> Single developer projects can build to the caliber and consistency of large development teams. Yet the simple blog website static page saying that looks very weird and broken on the desktop firefox. How large should be a development team to make proper margins in 2026?

noir_lord 1mo ago
I was a little "what a weird nitpick" then I opened it on FF and yeah... that's awful. Normally I'd just switch into FF reader view when it's that badly done but that doesn't work either.
- alexgoodhart 1mo ago
  I looked at it on my out of date FF and it looks fine.
  - sfryxell 1mo ago
    I looked at it on firefox and it looks fine. I wonder why it's off for some people
    - quinncom 1mo ago
      Looks fine in my Firefox. The text size is smaller than in Safari, but it’s fine.
- sfryxell 1mo ago
  Could this be an extension? I already have a <meta tag name="darkreader-lock">, but I'm not sure what extensions are common in firefox
dingaling911 1mo ago
This problem is easily solved. "Check that the blog looks the same in XYZ browsers". I have LLMs align stuff for me all the time because I'm too lazy. It takes the screenshot, changes the code, code auto reloads and boom, done.
- dmantis 1mo ago
  Sure. However I have a strange feeling when I read all AI praises and how productive everyone is while seeing more and more broken things everywhere. Sometimes from the same very productive people. Otherwise we might have said that maybe broken stuff goes from AI-deniers. If everyone is doing the job of hundreds, extremely productive and everything is so easily fixed, why everything feels so slow and broken, even so basic things? That's kind of the point. I'd expect nearly perfect websites everywhere, especially from "productivity" people who mastered the flow.
  - throw10920 1mo ago
    > If everyone is doing the job of hundreds, extremely productive and everything is so easily fixed, why everything feels so slow and broken, even so basic things? This doesn't make sense. There were slow and broken things before AI. This was true even when the things were made by hundreds or thousands of engineers. If an organization doesn't care about making their app or site fast or correct, then unless they have a truly ludicrous amount of free manpower (more than is available now with AI, because review and architecture are still bottlenecks), it probably won't happen. AI doesn't change this. AI doesn't change the priorities of an organization, it just changes how quickly and cheaply they can build. And every org has a point in their priority queue where things are no longer worth it to spend resources on. If Venmo didn't care about making their login page work well with Firefox (which, in my experience, they don't) before AI, why would you expect it to be better with AI?
  - dingaling911 1mo ago
    I think what you're seeing is A LOT of moving fast that wasn't possible before. When you move fast, you break things. Where it would take 6 hours to make a first cut of a static site, you can now do that in 15 minutes. Obviously that's not going to be perfect.
- sfryxell 1mo ago
  Yes, something like this is a good skill for me to add to the critic phase. This is my first post with the blog redesign, and I will admit I am 100% using hacker news as QA. Excellent feedback, Thank you.
tokai 1mo ago
Looks fine on ff, and the same as other browsers. You sure the issue isn't in your end?
- dmantis 1mo ago
  Well, who knows, but in brave it looks alright, and ff for me has extremely narrow text with disproportionately huge images. I see a few upvotes so I assume at least some other users have the same.
  - sfryxell 1mo ago
    Direct Actionable feedback. Thank you. The text is trying to folow the seven to ten words per line rule. This is my first blog post with graphics. so your comment helps me guage proportions
lucideer 1mo ago
> weird and broken Weird, yes. Broken, I don't think so. Seems to just be a matter of taste.
- Insanity 1mo ago
  If it's not rendering as intended across all browsers, I'd call that broken. If it renders as intended and just look bad, that's taste.
  - lucideer 1mo ago
    It's hard to say since the gp didn't specify what they thought was broken. The overall layout is fairly odd & weird - but it's the same in Chrome & Firefox. There is one technical bug with the main body font-size - it uses some invalid syntax (should be invalid in both Chrome & Firefox) & Chrome seems to be accepting it (against spec). The rule: font-size: clamp( 1.125rem, 1.125rem + (1.333rem - 1.125rem) * (100dvw - 24rem) / (80rem - 24rem), 1.333rem ); Firefox drops it & falls back to the default body font, making the article text slightly smaller. But it's definitely not a layout-breaking bug.
    - yurishimo 1mo ago
      Whats wrong with the font size exactly? Im not a desktop to check it but its look fine? A bit unusual but I wouldn’t say a clamp with a bunch of math is invalid.
      - lucideer 1mo ago
        for me it's just a slight reduction in the font size due to firefox ignoring the above - which doesn't seem enough of a difference to warrant folk calling it outright "broken" It's entirely possible I'm misreading the spec on clamp() but as far as I understood it, clamp() performs math on a bunch of comma separated fixed values, calc() handles arithmetic operators - this seems to be combining those without a calc invocation, but maybe I misread & overlooked clamp arithmetic operators. Firefox just says it's invalid, no detail on why.
tjoff 1mo ago
Large development team... that is exactly the problem. The more effort and code put into it the worse it gets. Peak web was one webmaster per site, doing it by hand.
fastball 1mo ago
Do large development teams care about Firefox?

by dmantis 1mo ago

noir_lord 1mo ago

I was a little "what a weird nitpick" then I opened it on FF and yeah... that's awful. Normally I'd just switch into FF reader view when it's that badly done but that doesn't work either.

alexgoodhart 1mo ago
I looked at it on my out of date FF and it looks fine.
- sfryxell 1mo ago
  I looked at it on firefox and it looks fine. I wonder why it's off for some people
  - quinncom 1mo ago
    Looks fine in my Firefox. The text size is smaller than in Safari, but it’s fine.
sfryxell 1mo ago
Could this be an extension? I already have a <meta tag name="darkreader-lock">, but I'm not sure what extensions are common in firefox

dingaling911 1mo ago

This problem is easily solved. "Check that the blog looks the same in XYZ browsers". I have LLMs align stuff for me all the time because I'm too lazy. It takes the screenshot, changes the code, code auto reloads and boom, done.

dmantis 1mo ago
Sure. However I have a strange feeling when I read all AI praises and how productive everyone is while seeing more and more broken things everywhere. Sometimes from the same very productive people. Otherwise we might have said that maybe broken stuff goes from AI-deniers. If everyone is doing the job of hundreds, extremely productive and everything is so easily fixed, why everything feels so slow and broken, even so basic things? That's kind of the point. I'd expect nearly perfect websites everywhere, especially from "productivity" people who mastered the flow.
- throw10920 1mo ago
  > If everyone is doing the job of hundreds, extremely productive and everything is so easily fixed, why everything feels so slow and broken, even so basic things? This doesn't make sense. There were slow and broken things before AI. This was true even when the things were made by hundreds or thousands of engineers. If an organization doesn't care about making their app or site fast or correct, then unless they have a truly ludicrous amount of free manpower (more than is available now with AI, because review and architecture are still bottlenecks), it probably won't happen. AI doesn't change this. AI doesn't change the priorities of an organization, it just changes how quickly and cheaply they can build. And every org has a point in their priority queue where things are no longer worth it to spend resources on. If Venmo didn't care about making their login page work well with Firefox (which, in my experience, they don't) before AI, why would you expect it to be better with AI?
- dingaling911 1mo ago
  I think what you're seeing is A LOT of moving fast that wasn't possible before. When you move fast, you break things. Where it would take 6 hours to make a first cut of a static site, you can now do that in 15 minutes. Obviously that's not going to be perfect.
sfryxell 1mo ago
Yes, something like this is a good skill for me to add to the critic phase. This is my first post with the blog redesign, and I will admit I am 100% using hacker news as QA. Excellent feedback, Thank you.

tokai 1mo ago

Looks fine on ff, and the same as other browsers. You sure the issue isn't in your end?

dmantis 1mo ago
Well, who knows, but in brave it looks alright, and ff for me has extremely narrow text with disproportionately huge images. I see a few upvotes so I assume at least some other users have the same.
- sfryxell 1mo ago
  Direct Actionable feedback. Thank you. The text is trying to folow the seven to ten words per line rule. This is my first blog post with graphics. so your comment helps me guage proportions

lucideer 1mo ago

> weird and broken Weird, yes. Broken, I don't think so. Seems to just be a matter of taste.

Insanity 1mo ago
If it's not rendering as intended across all browsers, I'd call that broken. If it renders as intended and just look bad, that's taste.
- lucideer 1mo ago
  It's hard to say since the gp didn't specify what they thought was broken. The overall layout is fairly odd & weird - but it's the same in Chrome & Firefox. There is one technical bug with the main body font-size - it uses some invalid syntax (should be invalid in both Chrome & Firefox) & Chrome seems to be accepting it (against spec). The rule: font-size: clamp( 1.125rem, 1.125rem + (1.333rem - 1.125rem) * (100dvw - 24rem) / (80rem - 24rem), 1.333rem ); Firefox drops it & falls back to the default body font, making the article text slightly smaller. But it's definitely not a layout-breaking bug.
  - yurishimo 1mo ago
    Whats wrong with the font size exactly? Im not a desktop to check it but its look fine? A bit unusual but I wouldn’t say a clamp with a bunch of math is invalid.
    - lucideer 1mo ago
      for me it's just a slight reduction in the font size due to firefox ignoring the above - which doesn't seem enough of a difference to warrant folk calling it outright "broken" It's entirely possible I'm misreading the spec on clamp() but as far as I understood it, clamp() performs math on a bunch of comma separated fixed values, calc() handles arithmetic operators - this seems to be combining those without a calc invocation, but maybe I misread & overlooked clamp arithmetic operators. Firefox just says it's invalid, no detail on why.

tjoff 1mo ago

Large development team... that is exactly the problem. The more effort and code put into it the worse it gets. Peak web was one webmaster per site, doing it by hand.

fastball 1mo ago

Do large development teams care about Firefox?