Lazyweb question: Has anyone created a GTKBuilder XML to HTML converter? I went looking and couldn't find one, but something like that seems like a super-useful tool for creating apps targeted both to the desktop and the web.

> GtkSourceView is a GNOME library that extends GtkTextView, the standard GTK+ widget for multiline text editing. GtkSourceView adds support for syntax highlighting, undo/redo, file loading and saving, search and replace, a completion system, printing, displaying line numbers, and other features typical of a source code editor.

I now officially have a hate on for OpenCV…

Why? Well, how would you feel about the fact the library refuses to open a video file with one file name, but has no problem with the same file using a different name? (Both being valid file names.)

This cost me more than two days work, because it never occurred to me the file name could possibly be a problem. So I was low-level debugging trying to figure out why.

Related: I've said this before, but I'm becoming more and more convinced app developers shouldn't create GUIs for their apps! Instead they should create command line apps and provide a comprehensive API.

Then others create GUIs for those apps using the APIs and people could choose which they prefer. Such a development model would allow those who are good at UIs to focus on that part of things; allow GUIs aimed at niche users; and eventually evolve better UIs.

Show thread

> How Big Tech Runs Tech Projects and the Curious Absence of Scrum.

This is a must-read if you are a developer or manage them. FWIW, the company I work for slots *exactly* into one of his categories, structures teams *exactly* as he describes for that category, and experiences *exactly* the outcomes and lack of worker satisfaction he associates with it.

(Not to mention what he says about Jira.)

> ory / kratos – Next-gen identity server (think Auth0, Okta, Firebase) with Ory-hardened authentication, MFA, FIDO2, profile management, identity schemas, social sign in, registration, account recovery, passwordless. Golang, headless, API-only - without templating or theming headaches.

> The collapse of complex software.

> "Architects are brought in to 'fix' the system. They might wheel out a big whiteboard showing a lot of boxes and arrows pointing at other boxes, and inevitably, their solution is… to add more boxes and arrows. Nobody can subtract from the system; everyone just adds."

When you are reading the documentation for a major and widely used software library and realize the author is deeply opinionated about Open Source and the practice of software development.

Not wrong mind you, but definitely doing the opposite of hiding his lamp under a basket…

One of the most frustrating aspects of is the way one problem often masks multiple others. For example, if a build is failing due to a syntax error, the build stops there. Fix the error and now the build goes to the next file where more errors may await. Rinse and repeat.

This is true for more complex error scenarios as well; only fixing one bug might bring out other bugs or might even introduce entirely new bugs.

This is why controlling side effects in your code is so important.

tip: the command 'git help everyday' will provide you with a basic cheat sheet for common tasks.

System76 is holding a sale right now, plus their video card prices are finally dropping. Due to this I just dropped four grand on a System 76 Thelio Mira loaded up with top-of-the-line AMD CPU and GPU.

I only signed up for a year with my current company and that's over soon, so I'm planning my next software development adventure. I wanted something I could do by my lonesome, is open source, and is exciting…

So I'm going into tool development!


When you feel like you are a lone voice screaming, "Do the simplest thing that could possibly work, and then iterate!" in a world where no one's heard of Ward Cunningham or Fred Brooks.

Some Tailwind CSS links:

> Rapidly build modern websites without ever leaving your HTML.

> Wickedblocks. A free collection of Tailwind blocks & components.

Why I like Tailwind CSS: Component-first design, simple.

What's wrong with Tailwind CSS: Requires Node and NPM.

(Do I really need to go into what's wrong with Node and NPM?)

Today's hot take: Runtime efficiency is the wrong thing to optimize for, except in two use-cases at opposite ends of the spectrum:

1. Targeted to limited resource hardware–especially if it runs on stored power

2. Huge scale with crazy numbers of transactions per second

The 90% of projects on the middle of that bell curve should focus on maintainability, usability and schedule *over every other consideration*.

"But what if I have scaling issues?"

Deal with it–when/if it happens!

Today's hot take: They call this software pattern 'Reactive Programming' now, but it used to be 'Data Binding'.

So far as I can tell, the only thing they changed was the name, to make it seem more cool perhaps?

Now consider this: the big mover behind this name change without any substance was the facesite…

So, basically, it's like everything else they do.

Show older