Actually, the Git data model supports empty directories, however, the index doesn't since it only maps names to files but not to directories. You can even create a commit with a root directory using --allow-empty, and it will use the hardcoded empty tree object (4b825dc642cb6eb9a060e54bf8d69288fbee4904).
Since the first time that I saw this here in HN I've been sharing it with several people around me. This including CS students, CS professors and non-technical people who only asked "how does a computer work?". I only say "just type 'cpu.land' and read that". This is one of the best things that I've found here.
I'd like a DE/theme that aims to do what the Win2k shell did. File explorer, basic window management, app switching, app launching. Back before every single UI widget had to integrate 47 types of OS feature-of-this-year's-product-cycle functionality.
Chicago95 isn't far off looks-wise. Something slightly more polished than Xfce, but way less than the behemoth that KDE is. I really feel like the modern basic desktop UI was pretty close to complete in 2002-2005, and the moment we tried to make your contacts list available for use in every single application we fell onto a slippery slope from which we have never recovered.
Cool! But the title made me think that "cigarette smoke effect" made me think that it was about health issues, and I clicked because I was curious about how shaders could be related to that.
> Maybe consider putting your energy into a good documentation inside the repository.
Commit messages are documentation.
If you have a good commit history you don't need write tons of documents explaining each decision. The history will contain everything that you need, including: when and who changed the code, what was the code change and why the code exists. You have a good interface for retrieving that documentation (git log, perhaps with -S, -G, --grep, -L and some pathspecs) without needing to maintain extra infrastructure for that and without being cluttered over time (it will be mostly hidden unless you actively search that). You also don't need to remember to update the documents, you are forced to do that after each commit.
A surprisingly large amount of devs, do the work to record data into a VCS (probably because they are told to by colleagues or superiors), but never seem to use them. Then they tell you that generating proper commits isn't all that important. Well, that's because they never actually use the VCS. By my book, only generating commits isn't really using a VCS, that is the information generation part, you also need to do queries on the collected data, otherwise yes it would be quite useless.
I think they somewhat do care about the history, but only as a backup and list of older versions and as bunch of potential merge bases. But they do not care about the history as in the evolution and causality. It really depends on what you see as the history, so it is a manifestation of a somewhat philosophical problem.
Of course, people shouldn't be forced to bring or even have a laptop powerful enough for using during the classes or finishing their tasks.
reply