Recent submissions

Comment · 3 months ago
SDL3 has been around for 1.5 years. I can't help but wonder about the choice of SDL2 over it. I started using SDL from its 3rd version. Don't I know about some advantages of SDL2?
Comment · 3 months ago
It's fair to mention that DOD is not only getting the most out of the hardware. It also allows the busy work to be avoided. I caught myself a couple of times, when I wanted to make a set of types united by some interface. However, in reality what I could do (and I did eventually) is having several instances of single SOA (one per type) which were processed differently. The addition of a new "type" turned from a good hundred line patch to 20-30 lines
Comment · 3 months ago
Comment · 4 months ago
you're right. The problem is with my Android application. Clicking the link through the website leads to a page
Comment · 4 months ago
I'm surprised that Vim is not on the first place here. Great TUI application. However, the about the TUI applications which I use is extensibility. For example, FZF is just a picker, but it has a ton of extensions. Another TUI I like is the interactive mode of Khal (calendar). However, apart from TUI it allows to be used through CLI which allows you to make your scripts on top of it.
Comment · 4 months ago
The link is 404
Comment · 4 months ago
When I was a student I had to make quite a few Qt application with C++ (for Linux). However, I bring the food on the table doing web (recently only the backend). During that time, the languages for web were something like Python - concise, convenient in terms of ecosystem and distribution, but bloated in terms of memory consumption. "Hello World in Java almost doesn't hang" he-he. Anyway, my first thought when I found Rust I dreamed to make a GUI application.

Unfortunately, I had the expectation that it should be as simple as making an HTML page. My failure to find a library or a framework to make GUI application made me learn a lot about how GUI works. I realized that making GUI for browser and for desktop are quite different problems. Browser makes easy what's difficult having a desktop oriented GUI framework - text rendering. However, the situation is fair the other around. GUI framework makes easy what's difficult in a browser - drawing arbitrary shapes. As a result, a web-frontend programmer struggles to figure out how to write some text having something like Qt, a GUI programmer tries to find the API to the bitmap in a browser.

It's fair noticed in the previous comments that a GUI framework brings a lot. That's because the problem is complex:

1. Create a window

2. Communicate with the window compositor (you do in WinAPI too btw). How to access the system tray and the child window.

3. Communicate with the operating system.

4. Handle the user input. Callback vs event streams. The user has 4 keyboards for some reason.

5. Rendering. Subpixels, shapes, different DPI. The user has 6 monitors.

6. Text rendering.

7. Widgets. Where probably the most difficult part is to make a textbox, because it involves the solutions of all previous steps.

The steps above touch only the visual part. There's also audio, accessibility, somebody wants the GUI framework to solve the networking.

After all of this research, I picked simply SDL for my project.

1. It's easy to compile.

2. It's small.

3. It relies on the subjectively common dependencies.

4. It's fairly straightforward to upgrade. Given that, you have to create a lot from scratch the part with updating is smaller comparing to a Qt-based solution.

5. It has batteries. My favorite is SDL_ttf which allowed me recently to implement selection of the text which is quite a bit through towards a textbox.

Having a project on SDL requires a lot of knowledge, but not a lot of code.

Comment · 4 months ago
This one looks good to me. https://matklad.github.io/. Coincidentally the author has recently posted about CSS for blogs https://matklad.github.io/2026/06/04/css-unavoidable-bad-par....

I have my own blog, but I'm unhappy with its design as well; therefore I'm not sharing it. Nevertheless, I find particularly challenging two things: 1. Make tables readable from a smartphone. There are a few tricks which allow you to make a responsive table. However, those tricks implies that you use <ul> or <div> instead of <table> which defeats the point of having a table. 2. I had an article where I needed to put a tiny mind map. Eventually I put it as a picture, because the solutions to draw a mind map with JavaScript made the page as twice as heavy.

Comment · 5 months ago

    Location: Ireland
    Remote: Yes
    Willing to relocate: No
    Technologies: Rust, Go, C/C++, Postgres, RabbitMQ, Redis, GNU/Linux, Docker, Python.
    Résumé/CV: https://alexmarkov.xyz/resume-long.html
    Email: [email protected]
Senior Software Engineer with 15+ years of experience with strong system design skill. Deep knowledge of GNU/Linux to build high-load web systems serving millions of requests.
Comment · 8 months ago
You know, that new inline Vim's diff algorithm looks really tempting. I wish I had it in my Neovim
Comment · 8 months ago
Well, the article is old, but it's good enough to deserve one more link to it :)
Comment · 8 months ago
Comment · 10 months ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton