gulugawa

My websites are not as big as Google or Reddit, and I take steps to block bot scraping.

I'm not interested in paying bandwidth costs for bots that don't care about what I posted.

Who is this new Mark Zuckerberg?

Good luck. I look forward to hearing about future progress.

I strongly agree with the approach of making programming more accessible with a simple, deterministic feature set.

I built a mini frontend framework with components, state management and backend data fetching.

It is designed to have a minimal learning curve, and has faster performance than React due to the use of web components.

One key part of good frontend engineering is picking tools to effectively solve current challenges your product is facing. Thinking about theoretical problems that may not apply to you is a waste of time.

I don't currently use use HTMX. However, that doesn't invalidate the use of htmx by others when it is a better fit for their experience and use cases.

The overwhelming majority of websites are small projects that don't need complex tools to provide interactivity.For those websites, complexity is more likely to come from planning for complexity that will never exist.

Using a tool such as htmx is an effective way for them to solve current challenges while minimizing complexity.

I designed my own mini-framework Places.js that you might be interested in looking at. https://codeberg.org/createthirdplaces/places-js

Places.js supports component based rendering, and state management integrated with backend data fetching. It also has faster rendering performance than React due to the use of vanilla JS web components.

Places.js is also designed to dynamically render parts of a page while making sure the rest of it is statically rendered. HTMX can be used on those parts, and be used to enhance HTML generated by components through the htmx.process() method. https://htmx.org/api/#process

An islands architecture can be implemented with web components when hydration is needed.

Writing vanilla JS to manage state and backend data loading can be done with a script that is less than 2kB zipped. The script can then be reused.

While I prefer to stay with an approach of using web components for my current work, HTMX seems like a good option to consider for future work.

I think the design of HTMX acts as a complexity limiter by encouraging less JS. One can make the argument that manually writing JS instead of HTMX would be easier and more maintainable. However, I've found that JS code often trends towards becoming increasingly complex over time.

Also, I'm glad to see that htmx can be installed without npm. I think the ability to install npm packages can incentivize too many dependencies.

Great paper. QA's role in software is underrated.

Never

Its going to cost a lot more than $200 once LLM subsidies run out.

I asked the bot questions about competitive Pokemon and Game of Thrones which it answered.

I don't code with LLMs, and think you might be right.

However, Postgres is a tool with clearly defined functionality and doesn't have ambiguous requirements that are seen in user facing software. As a result, it is entirely plausible that the author created a working Postgres replacement for certain use cases.

I personally want to see more evidence about the quality of the tool after it is in a finished state.

This the type of AI generated tool I'm interested in seeing more of. I'm a fan of how the quality is verified using clearly defined quantitative measurements for performance and correctness.

I'm still skeptical about LLMs and don't use them, although I can be convinced by more demonstrated examples of success.

Exactly, except that it wouldn't query models running on the public Internet.

As someone who frequently travels to Virginia, this is great news.

Interesting. Since GLM-5.2 can run locally, I'm wondering how challenging it would be to fine-tune multiple GLM-5.2 instances and run a collection of self-hosted agents.

I think agentic AI would be improved if it was a collection of smaller models that are working together. This has the potential to make costs significantly cheaper and improve accuracy.

I'm inclined to agree with the post, although it feels strange. In my experience at tech companies, not having public engineering levels improves collaboration and improves product quality.

I tried using Jotai, and thought it was a great way to manage state. In contrast, useContext seems like an overcomplication with less control over rendering from state updates.

Is your action framework open source? I'd be interested in taking a look at it.

Facebook spent a lot of effort marketing React, and there are widespread misunderstandings about React that made it popular. One of the most hyped features of React was a "virtual DOM" that supposedly improved rendering speed, but actually did not significantly improve performance.

Rendering a UI should be quite fast, even for a complex web app. Noticeable slowness in the UI is due to poorly optimized rendering, or logic that has nothing to do with rendering.

Nowadays, it is considered a default choice for a UI framework.

How do you decide to use useContext, useReducer, useState, or a third party management tool to manage state?

(I know useContext isn't great for state management, but I've worked on a web application where useContext was used to store complex global state).

What options?

React is an overcomplicated mess made popular by manufactured consent.

I agree that Meta is not uniformly bad, but I would not consider React to be a great tool. Every React project I worked on has turned into an unmaintainable pile of spaghetti.

As someone who quit their corporate tech job to focus on community building work, I don't think finding better job is that simple.

Nowadays, when I look at job listings, practically all of them are for companies that are ethically compromised in some way. They are overusing generative AI or building products that are having a negative impact on society.

One of the worst examples I saw was a software engineer job posting from my previous employeer that builds cloud-based physical security systems for buildings.The job requires the use of AI. I wouldn't trust a security system that randomly decides to unlock the front door to my house because of a hallucination.

Fable is aptly named for a something that is another scam.

A Javascript framework called places.js for creating interactive UIs using web components. It has support for cross component state management, backend data fetching, and web scraping protection. https://codeberg.org/createthirdplaces/places-js/src/branch/...

Here is a website I made with places.js for DC area board game events. https://dmvboardgames.com/