News for hackers. Stuff that matters.

abhijeetpbodas

Re:Git at Any Scale on Tuesday August 25, 2026 @04:21PM (#49440065)
Are there any in-depth technical write-ups on S3 that you would recommend reading on S3 to anyone who _does_ want to get into that abstraction?
Re:Arch shares its wiki strategy with Debian on Thursday August 14, 2025 @07:10AM (#44899039)
For lwn.net articles, aren't these subscriber-only links meant to be used only by the subscriber? Is sharing them on HN sabotaging lwn?
Relatedly: "How Unix Spell Ran in 64kB RAM"- https://news.ycombinator.com/item?id=42752604
Re:Python performance myths and fairy tales on Wednesday August 06, 2025 @08:19AM (#44810987)
An earlier version of the talk is at https://www.youtube.com/watch?v=ir5ShHRi5lw (I could not find the EuroPython one).
Librewolf on Linux, and IronFox on Android seem to be working very well for me based on ~ 1 week of usage, after moving away from FF.

Both work well with Firefox Sync, and also support addons, which is great.

Re:AI Killed the Tech Interview. Now What? on Thursday February 20, 2025 @11:48AM (#43116966)
> reserved for companies that are pushing the boundary of the industry

In a world where every company beleives (or wants to beleive) that they are doing some ground-breaking, bleeding edge work (see any tech company blog and you can only find hyped technologies in there), I do not think one can expect companies to do a fair assessment of if they really are doing such work.

Re:Things we learned about LLMs in 2024 on Wednesday January 01, 2025 @06:57AM (#42565509)
> ask very precise questions explaining the background

IME, being forced to write about something or verbally explaining/enumerating things in detail _by itself_ leads to a lot of clarity in the writer's thoughts, irrespective of if there's an LLM answering back.

People have been doing rubber-duck-debugging since long. The metaphorical duck (LLMs in our context), if explained to well, has now started answering back with useful stuff!

Re:WebStorm and Rider Are Now Free for Non-Commercial Use on Thursday October 24, 2024 @09:27AM (#41935276)
Specifically worth noting:

> It’s important to note that, if you’re using a non-commercial license, you cannot opt out of the collection of anonymous usage statistics.

Re:Learning about distributed systems: where to start? on Tuesday April 16, 2024 @01:19AM (#40048609)
Which OS book would you recommend? Anything similar to the DDIA style (not too academic)?
This unfortunately has `docstring-to-markdown` as one of its dependencies, which is a pain to install behind corporate pip proxies because it's under GPL.
Re:Show HN: Heynote – A Dedicated Scratchpad for Developers on Friday December 22, 2023 @10:03PM (#38741245)
I prefer the simplicity of a single `notes.md` for this,always open in vim in a terminal tab.

To do the separation, I've a keybinding to insert current timestamp, and but me on a new line:

`nnoremap <leader>t :r! date "+\%F \%T"<CR>I#<space><esc>o`

And happy 30th birthday to debian! Really appreciate all the work and effort that has gone into it.
It would have been fair to say it aged well, if the version which is currently called testing was their flagship version.

For most software, the testing version gives you relatively latest stuff. But that doesn't mean every software can advertise itself as being up-to-date.

For debian specifically, I don't think they recommend using the testing version unless you're a Debian contributor/tester.

I've tried using Sid (desktop) in the past, but ran into several version issues while installing through apt. Didn't try much to debug, and switched to stable. Been a happy user since!

> 2) Debian will contain the most up-to-date of everything.

Hasn't aged too well, I suppose.

Re:Emacs 29.1 Released on Sunday July 30, 2023 @12:40PM (#36933042)
Re:Diff Models – A New Way to Edit Code on Saturday January 28, 2023 @09:28AM (#34557779)
On a philosophical level, AI for writing code has always seemed redundant to me. Here's why:

1. Humans create programming languages which machines can understand. OK.

2. Humans build tools (LSP, treesitter, tags, type checkers and others) to help humans understand code better. OK.

3. Humans build (AI) programs which run on machines so that the computer can understand... computer programs???

Aren't computers supposed to be able to understand code already? Wasn't the concept of "computer code" created so as to have something which the computer could understand? Isn't making a (AI) program to help the computer understand computer programs re-inventing the wheel?

(Of course, I get that I use the terms "understand" and "computer programs" very loosely here!)

Interesting that their website itself uses CSS: view-source:https://kristall.random-projects.net/style.css
Very true. Reminds me of a video by Luke Smith: https://www.youtube.com/watch?v=V7lG4bont7g&t=7