barnacs

14 ms·

121.
by barnacs 11y ago
I think a top-down approach is pretty much the only way to do it: Start at a high level of abstraction: packages, modules, namespaces, etc and their relations. Pick one that seems related to some core functionality or central to the change
122.
by barnacs 11y ago
Who pays for the content? Noone, ads make it free! Who pays for the ads? Companies. Who pays the companies? The customers. When I check out at the grocery store, I pay for all the ads of the store, the suppliers, the factories and all the t
123.
by barnacs 11y ago
Interesting, but seems to be very basic. I still prefer using a wm. I can use different layouts, group windows into hierarchies, display them side by side, take advantage of tiling, use workspaces and have configurable keys for each of thes
124.
by barnacs 11y ago
I don't think they've solved it. I also switched to Chromium a few years ago because it felt way more responsive at the time. Then slowly over time it grew into this beast using over 7GB of memory for my ~50 reasonable tabs (nothi
125.
by barnacs 11y ago
I don't quite have that many tabs open but I find that grouping tabs into separate browser windows and taking advantage of your window manager goes a long way.
126.
by barnacs 11y ago
Honestly, most of these trendy landing pages look the same to me. I have to scroll/click to get any information other than a generic, marketing heavy one-sentence description, while most of the space on my screen is wasted. Something o
127.
by barnacs 11y ago
not parent but I have some experience with both: Gentoo was the first distro I ever tried, then I switched to arch and I've been using it ever since. I found gentoo to be way more of a hands-on distro. I configured the kernel by hand,
128.
by barnacs 11y ago
I couldn't find any compression proxy with man in the middle support so I hacked something together a while ago for personal use: https://github.com/barnacs/compy If anyone got motivated by the paper or feels like
129.
by barnacs 11y ago
Also, please don't break page up/down, home/end navigation. And don't use links/buttons that simply scroll to a different part of your way too long page. Just don't even put completely different pages (about 1
130.
by barnacs 12y ago
I prefer the more expressive journalctl -fu service-name
131.
by barnacs 12y ago
ITT: everything that is wrong with the world
132.
by barnacs 12y ago
What I was trying to imply is: just compare the HTTP/2 spec and the HTTP/1 one. The HTTP/1 has chapters like Request, Response, Method definitions, Header Field definitions, etc. All things you would expect from an applicatio
133.
by barnacs 12y ago
Even the Table of Contents looks weird in the HTTP/2 draft: 8. HTTP Message Exchanges What the hell is the rest of the document about then?
134.
by barnacs 12y ago
Why is it undeployable? I mean, we're talking about a new standard here. Anything goes. It doesn't have to happen tomorrow. Google only has influence over their HTTP client and server implementation and with such restrictions, SPD
135.
by barnacs 12y ago
Let's waste an enormous amount of resources to create Yet Another Messaging App. That's exactly what the industry and humanity in general needs to advance!