brokegrammer

I tend to deploy all Python based apps using gunicorn behind a caddy proxy. Take a look at the compose.yml https://github.com/confuzeus/simple-django/blob/master/ansib...

Deployment is as simple as `docker compose pull && docker compose up -d`.

Sure, the build script would be insightful. Removing the virtual dom sounds cool. I've been sleeping on SolidJS because I've always stuck with React after being disappointed by other frameworks. If it allows me to keep my server rendered pages, SolidJS might be what I've been looking for.

I've been thinking about loading React or something similar for specific components but still not sure which method I'm going to use for that. How are you embedding SolidJS on specific pages? Or do you actually have a full build pipeline?

Sure, I could build forms with React only but I found controlled forms to have less performance when there are many fields. react-hook-forms uses uncontrolled forms with refs which has near native performance, so if I had to build that by hand it would be more tedious. AI makes this process easier, but it's still extra code that needs to be maintained and tested, when you can do the same for free if you stick with standard web tools.

I built my latest SaaS (https://clarohq.com) using HTMX, backed by Django. I really enjoy the process because HTMX allows reactivity using swaps and plain Javascript events instead of server side state management, useeffect, and API endpoints.

However, it's difficult to get things right. I spent way too much time on some basic features that I could have shipped quicker if I used React.

The issue with React though, is that you end up with a ton of dependencies, which makes your app harder to maintain in the long-term. For example, I have to use a third-party library called react-hook-form to build forms, when I can do the same thing using plain HTML and a few AlpineJS directives if I need dynamic fields.

I'm not sure if I'll ever build an app using HTMX again but we need more people to write about it so that we can nail down patterns for quickly building server rendered reactive UIs.

My experience has been the opposite with Rails because of open-ended patterns with Hotwire. Sure, Rails itself is opinionated but Hotwire provides multiple ways to do the same thing, which confuses LLMs. For example, recently I tried building a form that allows creating related objects inline using modals. Claude 4 Sonnet got quite confused by that request, no matter how much help I provided. It managed in the end but the solution left a lot to be desired for. It can build the same feature using React on it's own with basic instructions.

Same thing with other libraries like HTMX. Using TypeScript with React, and opinionated tools like Tanstack Query helps LLMs be way more productive because it can fix errors quickly by looking at type annotations, and using common patterns to build out user interactions.

There's a certain elitism in programming where people will claim that library authors are superior to programmers who can only use those libraries, which is devoid of logic. Surprising, because programmers excel at logic.

Either way, I've been using AI to help me stop relying on external packages and frameworks lately. Turns out, AI can write libraries too because libraries and end products are simply code.

AI will replace all of us eventually, no matter how good you think you are. When guns got invented, Samurai went jobless but blacksmiths still had jobs. Fast forward to 2025, I don't think anyone is considering a career in blacksmithing.

I never found coding to be fun. All I care about is shipping features. However, I do care about maintainability and user experience. That's why I use AI to write much of the "dumb" code, and then I'll spend time doing quality control.

I always hated writing HTML and CSS, so I have AI do that. I always found writing tests and type annotations to be tedious, and would usually avoid those at my own detriment. Now AI is able to do those.

AI in general has been a net positive for me. I hope that it keeps getting better and better so that I can stop coding for good and focus on the products I'm building themselves.

Wow, that's why Copilot has been acting funny on Vscode. Code quality dropped and requests keep failing. But I'm still seeing Claude models in the selector. Can't read this article because of paywall. Are they exaggerating?

SEEKING WORK | Remote | Mauritius | Full Stack Typescript/Python Developer

I can help you build full-stack apps using any of the following technologies:

- Python - Django - FastAPI - Typescript - React - HTMX - AlpineJS - TailwindCSS

My latest project is ClaroHQ (https://clarohq.com) - a time blocking and invoicing app for freelancers. I built the project from scratch using Django, HTMX, and AlpineJS. I also handle deployment using Docker to a server on Hetzner.

Basically, I can help you go from Zero to One. I'm available during Euro timezone. Visit my website for my email address (link in my profile).

Vibe coding is only a problem when non-programmers do it. As a programmer, I know how to give precise instruction to models so that they end up writing high quality code. I also have the knowledge to manually fix code that models generate.

Non-programmers can't do any of that. That's why I believe that programmers should use vibe coding to get work done faster, but non-programmers should restrict vibe coding high quality projects to their dreams only.

Engineers who speculate about currently non-existent metrics instead of getting work done while shaming others for wanting to make progress should look for employment in academia.

I would love to see some numbers then. Until then, I'll just assume that using build tools and frameworks means one is a junior developer to be bogus claim.

> your application and experience could be still even faster without compilation

I doubt it. Compilation actually improves developer experience and speeds up the process of releasing apps because you have a standardized way to release your app to production.

I seriously can't understand the hate against compilation because it's never been a roadblock for me, especially these days when most builds take a few seconds on slow CPUs. I guess it's cool to hate things for no reason.

> Frameworks also come at a substantial cost. They are highly restrictive, super massive, and almost always unnecessary.

This is highly subjective. Frameworks have been nothing but a huge productivity boost for me. For example, I can spin up feature-complete API using FastAPI in a few hours instead of spending weeks building my own framework to do the same thing.

> People tend to prefer frameworks when they lack the confidence to build without them

Doubt it. People mostly choose frameworks because they want to get work done instead of wasting their employer's money on non-profitable endeavours.

> for those of us that frequently measure things large frameworks are always a net negative

Could be that you're measuring the wrong thing. At the end of the day, engineers need to ship features so that the company can generate revenue. Frameworks are great at facilitating that process. I'm no Math expert but this seems like a net positive to me.

Once a dependency turns into a security vulnerability, you can either replace it, or write your own library like I suggested. It's more cost effective and time efficient than writing your own libraries from scratch for every project.

For example, I'd rather install React Router for routing in a React app instead of writing my own routing library. I guess some people will reply "grrr React, just use static HTML bro". Okay cool.

I could have built an web app in 2015 using C without any frameworks or build system. That doesn't mean I wouldn't want to rewrite it from scratch in 2025.

Rewriting things from scratch is something that everyone wants to do as time passes, regardless of the tech stack used initially.

1. Dependencies break your project only if added unpinned. Most modern package managers will pin dependencies for you.

Now, what if a dependency does break? Well, you can replace it with another dependency, or you can write one from scratch. Using dependencies allows you to save time earlier, and then only spend time writing your own libraries once you hit a roadblock.

2. Frameworks are similar to dependencies. They allow you to save time at the beginning of projects when you're not fully aware of your requirements, and then you're free to write from scratch when you have enough users and resources to do so.

3. Compilation is lightning fast these days because many tools are written in Rust. Projects built using Vite, for example, take a few seconds to build on a 10 year old laptop.

To summarize, these things don't result in websites that will require a lot of time and energy to maintain.

My thoughts exactly. Inference should be dirt cheap for LLMs to truly become powerful.

It's similar to how computing used to be restricted to mega corps 100 years ago, but today, a smartphone has more computing power than any old age mainframe. Today we need Elon Musk to buy 5 million GPUs to train a model. Tomorrow, we should be able to train a top of the line model using a budget RTX card.

For me, writing CSS and coming up with professional looking designs were huge bottlenecks. Now I delegate those tasks to LLMs.

I recently started working on a client's project where we were planning on hiring a designer to build the front-end UI. Turns out, Gemini can generate really good UIs. Now we're saving a lot of time because I don't have to wait on the designer to provide designs before I can start building. The cost savings are most welcome as well.

Coding is definitely a bottleneck because my client still needs my help to write code. In the future, non-programmers should be able to build products on their own.

The study seems to be incredibly flawed.

> Women with active sun exposure habits were mainly at a lower risk of cardiovascular disease (CVD) and noncancer/non-CVD death

Not surprised there because people who spend more time outdoors will typically be participating in physical activity at the same time, while people who avoid sun exposure will typically be seated while participating in sedentary activities.

If we want to see if sun exposure is the sole reason for longevity, we will have to force the subjects to sit on a couch outside.

Claiming that not getting sunlight is the same as smoking is pure garbage.

I'm having the same issue with Gemini as soon as the context length exceeds 50k-ish. At that point, it starts to blurp out random code of terrible quality, even with clear instructions. It would often mix up various APIs. I spend a lot of time instructing it about not writing such code, with plenty of fewshot examples, but it doesn't seem to work. It's like it gets "confused".

The large context length is a huge advantage, but it doesn't seem to be able to use it effectively. Would you say that OpenAI models don't suffer from this problem?

Think he means traveling to Bali and networking with western contractors working remotely there charging western rates while enjoying low cost of living.

We don't need AI to wipe out entry-level office jobs. David Graeber wrote about this in Bullshit Jobs. But now that we have AI, it's a good excuse to wipe out those jobs for good, just like Elon did after he acquired Twitter. After that, we can blame AI for the deed.

I think living in rural areas sucks because you'll end up feeling very lonely. And I'm speaking as a hardcore introvert who didn't feel lonely at all during the lock-down. But after extended periods of isolation, human connection becomes important, especially if you're young.

I'm currently living below my means in a small village in Mauritius, but I'm planning on moving to a big city in a big country ASAP because while living like this is good for my bank account, my mental health is taking a heavy toll. Not to mention how challenging it is to find a date.

As a young person, IMO the best thing to do is move to a place where you can make some good lifelong friends, and build a solid network for employment opportunities. Saving money while living frugally only served to dampen my social muscles.

It's impossible to fix the gaming industry because it's made up of consumers with low impulse control.

You can see evidence of that with the recent GPU crisis where even as prices go up, sales remain constant.

Then you have game development companies outright scamming people by releasing bug-ridden products. But gamers keep buying, which means that developers aren't being discouraged from such practices.

Basically, gamers remain in the market no matter how much they're mistreated because they'll do whatever to get the dopamine hit. There's no reason for anything to change.

What KDE needs isn't new features but less bugs.

Just use gmail because using your own domain or something weird like pm.me can freak some companies out depending on where you live. I tried using my own domain at a bank once and they started questioning whether it was a fake email or something.

Use gmail then setup a tool like imapsync to sync all your mail to another mailbox.

Asking people will give you a "faster horses" kind of answer.

What about countries like Japan then? It's a great country where any children born would live a long and healthy life. Sure beats being born in Mogadishu. But forget about having children, Japanese people aren't even dating.

More money can't solve the problem. People could live in cardboard boxes and still reproduce if they want. The reason is multifaceted.

> Living with their parents may be a benefit for arranged marriages

Yes, arranged marriages played a big role in getting people to form families. It has many disadvantages in terms of personal freedom, but it seems to be effective for population growth.

Couples also need to have children in such cultures unless they want to be ostracized from society.

The birth rate issue could very well be cultural instead of a financial one.