gulugawa

5 ms·

31.
by gulugawa 3mo ago
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.
32.
by gulugawa 3mo ago
Who is this new Mark Zuckerberg?
33.
by gulugawa 3mo ago
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.
34.
by gulugawa 3mo ago
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.
35.
by gulugawa 3mo ago
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
36.
by gulugawa 3mo ago
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
37.
by gulugawa 3mo ago
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
38.
by gulugawa 3mo ago
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.
39.
by gulugawa 3mo ago
https://htmx.org/essays/paris-2024-olympics-htmx-network-aut...
40.
by gulugawa 3mo ago
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
41.
by gulugawa 3mo ago
Great paper. QA's role in software is underrated.
42.
by gulugawa 3mo ago
Never
43.
by gulugawa 3mo ago
Its going to cost a lot more than $200 once LLM subsidies run out.
44.
by gulugawa 3mo ago
I asked the bot questions about competitive Pokemon and Game of Thrones which it answered.
45.
by gulugawa 3mo ago
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 plausi
46.
by gulugawa 3mo ago
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
47.
by gulugawa 3mo ago
Exactly, except that it wouldn't query models running on the public Internet.
48.
by gulugawa 3mo ago
As someone who frequently travels to Virginia, this is great news.
49.
by gulugawa 3mo ago
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.
50.
by gulugawa 3mo ago
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.
51.
by gulugawa 3mo ago
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.
52.
We should reduce the amount of generated information(bponnaluri.com)
15 points by gulugawa 3mo ago|6 comments
53.
by gulugawa 4mo ago
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
54.
by gulugawa 4mo ago
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
55.
by gulugawa 4mo ago
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 st
56.
by gulugawa 4mo ago
What options?
57.
by gulugawa 4mo ago
React is an overcomplicated mess made popular by manufactured consent.
58.
by gulugawa 4mo ago
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.
59.
by gulugawa 4mo ago
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 comp
60.
by gulugawa 4mo ago
Fable is aptly named for a something that is another scam.

More ›