silon3's comments

silon3 | 11 years ago | on: Uselessd

"like" (it happened to me)

No journald. Consequently, this also means no libqrencode and libmicrohttpd integration, nor hooking coredumps to the journal. The default log target for auxiliaries is now LOG_TARGET_SYSLOG_OR_KMSG.

The main case against binary logs is their corruptibility. This happens more often than you’d think, due to not having any transaction consistency, as an RDBMS would. The advice of the systemd developers on handling this? Ignore it.

silon3 | 11 years ago | on: Wayland in Gnome: two progress reports

That's normal and a feature. Mouse pointer is driven by hardware input and rendered independently (was a hardware overlay in the old days) and is soft realtime (hopefully). Because the window manager is a normal process, operating asynchronoysly, the window frame will lag a bit (depends on system load), and the app contents even more (this can't be avoided, even if the WM/compositor was realtime). Making the window frame wait for window content is broken by design.

silon3 | 12 years ago | on: Boycott systemd

Does the old "good standard will have 2 or more implementations" apply here?

silon3 | 12 years ago | on: April Fools: migrate Apache Subversion project over to the git repo

Imo the core of git is superior, but the command line interface of SVN is much better. Git is just horribly messy. The distributed stuff push/pull had a lot of work and improvements, but the work/commit cycle is just messy, at least when compared to SVN or mercurial.

silon3 | 12 years ago | on: Generational GC has landed in Firefox

I tried the e10s nightlies and it seems to be quite usable.

The major issues is some tab confusion (phantom, unclickable tabs), many "new tab" after session restore and occasional problems with context menus. I did use Tree style tabs and some other non-content related plugins and they mostly work.

silon3 | 12 years ago | on: A 30 minute introduction to Rust

>Note that's just dereferencing: there's nothing inherently unsafe about just creating and passing around the pointers themselves.

Sure there is. Passing around multiple pointers can result in a double free and then the dangerous dereference can happen. I'm guessing the developer must be careful when writing unsafe blocks to make sure this doesn't happen.

page 2