It appears to only be useful for React, and there are many other tools used for frontend development.

When I think of AI, my mind goes towards automated Metro trains that do a great job of driving on fixed routes. On the other hand, it's obvious that the train can't do something like generate dinner recipies.

I tried uploading a .tex file created earlier this year and was able to see a PDF preview without any additional configuration.

As someone who has a local TeX setup, I'm a fan of your approach to loading dependencies on demand with a service worker. The installation process on my computer took a while because it was downloading a bunch of dependencies I didn't need.

First of all, coding speed is not the main bottleneck. I've been working on my own JavaScript framework. Most of my work is talking to people about challenges they have with web development, doing research on existing tools, and thinking about features to add.

Coding more slowly without LLM usage is a benefit because it helps me understand every line of code. The slower pace also helps me think about making things intuitive and reflect on my experiences with React.

While my framework is outperforming React, that isn't particularly impressive. On the other hand, it demonstrates how ignoring LLMs improves quality. Also, my monthly token spend is $0.

https://gomakethings.com/guides/?filter=html

Frankly, I think we should move to have harnesses do 100% of the work. In my view, the key is the fact that harnesses are deterministic tools created with a clear sense of intention.

I plan to publish an updated version soon.

Here is an example of a template used to render a list of events.

const EventItem = () => {

  EventItem.eventTime = (eventData) =>{
    if(eventData.isRecurring){
     return `${eventData.dayOfWeek}s at ${eventData.nextEventTime}`;
    }
    return `${eventData.nextEventDate} at ${eventData.nextEventTime}`
  }

  EventItem.url = (eventData) => {
    return `/html/groups/event.html?id=${eventData.eventId}&groupId=${eventData.groupId}`
  }

  EventItem.location = (eventData)=>{
    return  `${convertLocationDataForDisplay(eventData.eventLocation)}`
  }
    
  return `
    

      
       
       

       
       

       
 
      
   `;
 }

 BaseDynamicComponent.defineTemplate(EventItem,"EventItem");

Also, I'm planning to release my changes as a framework that can be used for a variety of interactive websites.

Is was successful because I didn't use any sort of LLM assistance.

I used to be a scrum master who helped manage the team JIRA ticket board. When running into the inevitable problem during a meeting, I would sarcastically make a comment about "JIRA's monthly downgrade". By the time I stopped using JIRA in early 2025, it had become noticeably slower and had a bunch of UI clutter that made it difficult to do basic tasks.

I checked the homepage for Atlassian, which owns JIRA, and it has a headline saying: "Unleash your teams and their agents"