przemoc

True, but even though you can set:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
    "RealTimeIsUniversal"=dword:00000001

It isn't flawless in practice, unfortunately. Internet Time Update no longer works then.

~8 years ago I was using LD_PRELOAD to be able to (s)fdisk fixed-size VDI image (VirtualBox Disk Image) outside of virtual machine.

https://gist.github.com/przemoc/571086

Don't know if it still builds and works flawlessly.

NetEm seems to be rarely known and used traffic control feature available on Linux.

The linked script allows you to delay sending DNS requests (IP packets with destination port set to 53) on given interface. Normally it is useless, but it may be useful for debugging some hard network-related cases in your software.

The script may also work as a base for other network-related experiments using netem. You can read more about it here: http://man7.org/linux/man-pages/man8/tc-netem.8.html

Just out of curiosity (it's not my field), what are those 3 renderers that matter right now?

Somehow I read your comment as V-Ray is not among them as being last-gen. I remember that years ago there was a lot of buzz regarding Arnold (and it was justified to some extent AFAIR, at least judging by opinions of pleased 3D crowd), but maybe it's last-gen too now? Many years ago there was Brazil, but quick googling shows it's only for Rhino now? I haven't heard about Redshift till now, though.

Somehow title lost @ at the end. Is it some kind of forbidden character?

Can be useful. Thanks for sharing!

I usually used sxc.hu so far, which became FreeImages.com some time ago.

Similar thoughts. :)

He's author of great stuff out there, but I think his works should be treated more as showing the way of doing this or that than making you stick to his particular implementations (I'm not implying they're bad, though). For instance I prefer runit over daemontools, but quite likely without daemontools there wouldn't be runit. (Actually I want to try s6 [1] soon, as it seems another step in evolution of process supervision tooling.)

But his "build system" is actually unnecessarily non-standard and clunky. I am against autohell, but carefully crafted handmade Makefiles are really nice.

  [1]: http://skarnet.org/software/s6/

It's MLT, not MELT.

And it's a base for other video editor, which is getting stronger each year, seems more stable than the others and already looks IMHO the best among FOSS video editors:

http://www.shotcut.org/

I think that metastore will become much more valuable tool, when some planned stuff will be implemented.

https://github.com/przemoc/metastore/issues/6

https://github.com/przemoc/metastore/issues/7

Drafts described there are not finalized and my view on some matters changed a bit. I'll try to update descriptions one day. metastore needs also some modularization to provide better OS-dependent stuff like xattrs.

All in all metastore will need more or less substantial reworking, to the point where rewriting it and providing converter from binary format may be a simpler solution and leading to cleaner (and thus more maintainable) code.

Let me quote README file first:

    It was originally written as a supplement to git, which does not store
    all metadata, making it unsuitable for e.g. storing /etc in a
    repository.
    
    metastore can also be helpful if you want to create a tarball of a file
    tree and make sure that "everything" (e.g. xattrs, mtime, owner, group)
    is stored along with the files.

You may use it to store stuff on filesystem that doesn't support perms, owner & group for instance, like FAT, yet still be able to restore it later. Well, FAT doesn't support lot of things, so it's maybe a bad example. Anyway, I did use metastore to store metadata of some ext4 filesystem tree before backuping it on NTFS. It worked quite well.

metastore was used in etckeeper in the past.

https://joeyh.name/blog/entry/announcing_etckeeper/

In less than half a year it was replaced with find scripts.

http://git.joeyh.name/?p=etckeeper.git;a=commitdiff;h=a9ce99...

And I cannot blame etckeeper. Using binary format for storing metadata, i.e. owner, group, perms, xattrs, mtime, makes it too opaque for many use cases, especially in VCS.

metastore v1.1.0, as you can already read, was meant to give metastore (from 2008) a proper release, with fixed bugs and small improvements only. There are plans to make metastore more useful in the future, though.

I guess that some mod intervened here (by bringing this closer to the front page), because even a few hours after posting there were only a few points and it was rather deep in HN. Thank you!

Post title has been also changed, and it's fine. I no longer remember mine, but it was maybe too clunky. But.

metastore should be written using all lowercase letters.

Code::Blocks was definitely better than horrendously buggy Dev-C++, but since Qt Creator I never looked back (ok, I do use vim very often, but it's a different thing). To be fair I haven't checked Code::Blocks for years (8 years at least), so maybe nowadays it gives more than notepad+syntax-highlight+tabs feeling.

BTW Everyone, please write "Qt Creator" with space between "Qt" and "Creator". I don't know how spaceless variant got so widespread.

There was another mail sent to ML regarding v1.1.0:

https://www.freelists.org/post/metastore-announce/metastore-...

Allow me to answer by pointing to what I wrote some time ago:

https://news.ycombinator.com/item?id=7854080

(Oh, it's already ~2 years since I first thought about writing my own SC API front-end. Time sure flies...)

I haven't checked Soundnode App yet, but any attempt to sanitize the way you interact with SoundCloud should be appreciated, because SC web UX is bad.

Soundnode App UI looks nice. I'd add screenshot for each main view on app's home page, even if they're all similar, though. UX remains to be tested.

The only (apparent?) downside is that this app seems to be a bundled web app with web browser. I'm not that fond of such solutions. But. If it wasn't open source and GitHub page wasn't shown there, then there is a high chance I would not notice that it's built like that, at least from screenshot alone.

Writing SoundCloud client is on my ToDo list, as it would be a good way to brush up and enhance my Qt skills. Maybe I'd finally embrace QML along the way, as I'm postponing QML tinkering for far too long I guess. I'm also considering fiddling with PyQt5, as it could possibly quicken prototyping, but I'm not sure about it in my case, as I have only minor Python experience and no PyQt experience at all (well, it's like incentive to change that). There is also SoundCloud python package, so going python way is quite tempting, but I always prefer native compiled apps over scripted ones.

Changing topcolor in settings from ff6600 to something else (like ff6601) brings back the right^TM color.

Far Manager is the first application I run in Windows. Always.

Lately I've noticed that my Far and plugins set diverged slightly on different computers, so I decided today to create kind of bootstrap script, so I could easily recreate them.

It's maybe not the cleanest script and lacks a bit of scaffolding to even further ease adding plugins, but it's already usable.

Currently following plugins are added:

  - Integrity Checker
  - Regular Expression Search
  - Renewal
  - Renewal-supported plugins, i.e. FarPlugs:
    - Audio Player
    - CoderCalc
    - Disk Menu Editor
    - File Unlock
    - HashCalc
    - Hexitor
    - Hunspell
    - Image Viewer
    - JClassInfo
    - Media Info
    - Name Editor
    - PE Analyzer
    - PortaDev
    - Sniffer
    - Sqlite DB
    - Sudo
    - TextConv
    - Torrent Info

I've created also topic for it at Far Manager forum:

http://forum.farmanager.com/viewtopic.php?f=28&t=9835

While it's true that Michael generates lots of merge commits, if you click the link in LWN article to Andreas Cadhalpun's mail [1], then you can read that following commands were used to generate statisticts:

  Libav:
  $ git shortlog -ns --no-merges v11..HEAD | head -n15
  FFmpeg:
  $ git shortlog -ns --no-merges n2.4..HEAD | head -n15

  [1] https://lwn.net/Articles/650830/

About what "Lossy FLAC" you're talking about? Do you mean perhaps [1]?

If FLAC would ever gain a lossy mode, it would be a disaster, because it would be instantly (ab)used and it would be misleading to a lot of users. "FLAC is not Lossy" [2] and it will hopefully remain that way forever.

(Of course it doesn't prevent people from encoding audio into FLAC from lossy formats, but it's a completely different matter.)

  [1] http://www.hydrogenaud.io/forums/index.php?showtopic=55522
  [2] https://xiph.org/flac/features.html

FWIW, Google Maps are generally noticeably slower and laggier in Firefox when compared to Chrome.

If you're *nix user, you can quite easily perform this kind of stuff using date, or at least using date from coreutils.

    $ date -d 'today + 6 weeks'
    Mon Aug 24 13:15:54 CEST 2015
    
    $ TZ=America/New_York date -d 'now + 2 hours'
    Mon Jul 13 09:16:17 EDT 2015

It always felt natural to put this dot at the end of (what antirez nicely called) commit synopsis, so AFAIR I always (or at least since I started using git and when was not forced by particular project's rules to do some other way) put it there and found advices to avoid it quite strange. The only exception (beside forgetting about full stop yet pushing to public repo, it does happen sometimes) I have is when the commit is sole version-bumping/releasing one, because then I usually go with following style

    PROJECT_NAME [v]VERSION

There are some half-broken SCM managers that always display whole commit message (sometimes even without respecting paragraphs) and then such synopsis without full stop yet followed by another sentences looks rather awful. YMMV

As some commenters here already wrote, it's not a grave matter, but it's good to have consistent style. It goes without saying, that having relatively short commit summary in one sentence separated with blank line from further details (if they are necessary) is far more important matter than the period or lack thereof, as it immensely eases groking commit log.

Thank you for such a prompt answer.

EDIT:

Quick googling revealed that Rust doesn't work with musl libc yet. It will be really nice when it will be fixed.