Preferences

JimDabell
Joined 12,112 karma
British tech entrepreneur living in Singapore.

You can reach me by emailing my first name at my last name, on the .email TLD.


  1. > In many respects 2025 was a lost year for programming. People speak about tools, setups and prompts instead of algorithms, applications and architecture.

    I think the opposite. Natural language is the most significant new programming language in years, and this year has had a tremendous amount of progress in collectively figuring out how to use this new programming language effectively.

  2. ColdFusion used to work this way:

    https://en.wikipedia.org/wiki/Adobe_ColdFusion

    What surprised me is that when I went to look at the Wikipedia page for CF, apparently its latest release was this year! I haven’t heard anybody mention it in a very long time.

  3. And then you make a global index of those skills available to models, where they can search for an appropriate skill on demand, then download and use them automatically.

    A lot of the things we want continuous learning for can actually be provided by the ability to obtain skills on the fly.

  4. You’ve got to learn how to disagree with people without insulting them.
  5. There is no single organisation that has done more to push the mobile web forward than Apple. Seriously, name one.

    Nobody gave a shit about the mobile web until Apple launched the iPhone, where one of its main selling points was a “desktop-class web browser”, where Steve Jobs told announced that if they wanted to run apps on the iPhone, they should be web apps.

    Then suddenly everybody started demanding “iPhone-compatible websites” overnight. Nobody was asking for “mobile websites”, which until that point were shitty WAP/WML things, or – in the best case – cut back m.example.com microsites. People wanted “iPhone-compatible websites”.

    And then all the other phone vendors used Apple’s open-source WebKit code (open-source thanks to KDE, useful on mobile thanks to Apple) to release their own browsers, and the mobile web took off like a rocket because suddenly it was useful because people could use real websites.

    And let’s not forget Steve Jobs telling people to avoid Flash and use open web standards instead.

    There is a very clear before/after with the mobile web, and it’s the launch of the iPhone and all the work Apple put into making WebKit work well on mobile that provided that watershed moment.

    Apple were championing the web in the time period you claim they were “intentionally undermining and artificially crippling it”.

    Now, you may be underwhelmed by their performance in more recent years, but it’s simply factually untrue that they have had a 20 year campaign to undermine the web.

  6. > We held a vote that you weren’t aware of and decided that masonry was out. If you cared, you should have participated in the vote that you were not aware was happening. It’s too late to change it.

    I think that’s an exceptionally uncharitable description of what happened. This is a decision the WebKit team has been repeatedly publicly asking people to participate in for over 18 months.

    > Help us invent CSS Grid Level 3, aka “Masonry” layout

    > P.S. About the name

    > It’s likely masonry is not the best name for this new value. […] The CSSWG is debating this name in [this issue]. If you have ideas or preferences for a name, please join that discussion.

    https://webkit.org/blog/15269/help-us-invent-masonry-layouts...

    > Help us choose the final syntax for Masonry in CSS

    > We also believe that the value masonry should be renamed.

    > As described in our previous article, “masonry” is not an ideal name, since it represents a metaphor, and not a direct description of its purpose. It’s also not a universally used name for this kind of layout. Many developers call it “waterfall layout” instead, which is also a metaphor.

    > Many of you have made suggestions for a better name. Two have stood out, collapse and pack as in — grid-template-rows: collapse or grid-template-rows: pack. Which do you like better? Or do you have another suggestion? Comment on [this issue] specifically about a new value name (for the Just Use grid option).

    https://webkit.org/blog/16026/css-masonry-syntax/#footnote-1

    > [css-grid-3] Renaming masonry keyword

    https://github.com/w3c/csswg-drafts/issues/9733

  7. How about following the precedent of all of these users of /.well-known/

    https://en.wikipedia.org/wiki/Well-known_URI#List_of_well-kn...

    robots.txt was created three decades ago, when we didn’t know any better.

    Moving llms.txt to /.well-known/ is literally issue #2 for llms.txt

    https://github.com/AnswerDotAI/llms-txt/issues/2

    Please stop polluting the web.

  8. I’ve implemented a search crawler before, and detecting and switching to the WordPress API was one of the first things I implemented because it’s such an easy win. Practically every WordPress website had it open and there are a vast number of WordPress sites. The content that you can pull from the API is far easier to deal with because you can just pull all the articles and have the raw content plus metadata like tags, without having to try to separate the page content from all the junk that whatever theme they are using adds.

    > The reality is that the ratio of "total websites" to "websites with an API" is likely on the order of 1M:1 (a guess).

    This is entirely wrong. Aside from the vast number of WordPress sites, the other APIs the article mentions are things like ActivityPub, oEmbed, and sitemaps. Add on things like Atom, RSS, JSON Feed, etc. and the majority of sites have some kind of alternative to HTML that is easier for crawlers to deal with. It’s nothing like 1M:1.

    > Investing the effort to 1) recognize, without programmer intervention, that some random website has an API and then 2) automatically, without further programmer intervention, retrieve the website data from that API and make intelligent use of it, is just not worth it to them when retrieving the HTML just works every time.

    You are treating this like it’s some kind of open-ended exercise where you have to write code to figure out APIs on the fly. This is not the case. This is just “Hey, is there a <link rel=https://api.w.org/> in the page? Pull from the WordPress API instead”. That gets you better quality content, more efficiently, for >40% of all sites just by implementing one API.

  9. Something that is 97% accurate is wrong 3% of the time, so pointing out that it has gotten something wrong does not contradict 97% accuracy in the slightest.
  10. McDonalds were recently criticised for an AI-generated Christmas advert:

    https://www.theguardian.com/business/2025/dec/11/mcdonalds-r...

    It seems like an excellent advert because it got everybody talking about McDonalds. Even this thread talks more about McDonalds than the “French supermarket’s” ad. The “French supermarket” isn’t even named in the title. The people who came up with the McDonalds ad were wildly successful in what they set out to do; they even have all the people who hate AI talking about their new ad, even when attempting to showcase somebody else’s ad.

  11. Google has something similar:

    https://google.aip.dev

  12. > people will continue to use it how they see fit.

    And whenever they do so, this pointless argument will happen. Again, and again, and again. Because that’s not what the word means and your desired redefinition has been consistently and continuously rejected over and over again for decades.

    What do you gain from misusing this term? The only thing it does is make you look dishonest and start arguments.

  13. No, according to the commonly accepted definition of open-source.

    Whenever anybody tries to claim that a non-commercial licenses is open-source, it always gets complaints that it is not open-source. This particular word hasn’t been watered down by misuse like so many others.

    There is no commonly-accepted definition of open-source that allows commercial restrictions. You do not get to make up your own meaning for words that differs from how other people use it. Open-source does not have commercial restrictions by definition.

  14. They are claiming something is open-source when it isn’t. Regardless of whether you think the deviation from open-source is a good thing or not, you should still be in favour of honesty.
  15. Yes, Claude Opus 4.5 recently scored 100% on SvelteBench:

    https://khromov.github.io/svelte-bench/benchmark-results-mer...

    I found that LLMs sometimes get confused by Lit because they don’t understand the limitations of the shadow DOM. So they’ll do something like throw an event and try to catch it from a parent and treat it normally, not realising that the shadow DOM screws that all up, or they assume global / reset CSS will apply globally when you actually need to reapply it to every single component.

    What I find interesting is all the platforms like Lovable etc. seem to be choosing Supabase, and LLMs are pretty terrible with that – constantly getting RLS wrong etc.

  16. I remember seeing a co-worker stuck on trying to debug Netscape showing a blank page. When I looked at it, it wasn’t showing a blank page per se, it was just taking over a minute to render tables nested twelve deep. I deleted exactly half of them with no change to the layout or functionality, and it immediately started rendering in under a second.
  17. Why use the “creative writing exercise” euphemism that obscures the dishonesty? Call them liars, fakes, frauds, or whatever.
  18. You might like Jujutsu – you commit without being on any branch and then later you can decide where and how you put things onto branches.

This user hasn’t submitted anything.