Protobuf is a great format with a lot of benefits, but it's missing one that I wish it could support: zero-copy. The ability to transport data between processes, services and languages with effectively zero time spent on serialization and deserialization.
It appears possible in some cases but it's not universally the case. Which means that similar binary transport formats that do support zero-copy, like Cap'n Proto, offer most or all of the perks described in this post, with the addition of ensuring that serialization and deserialization are not a bottleneck when passing data between processes.
I know an update isn't available for OS X yet, but did anyone else get notified of an upgrade of their OS X version? The most recent OS X version of the Flux.app file says it was created Oct 4, 2013. I'm pretty sure this update has caused my Macbook Air to hang momentarily when trying to put it to sleep. Kind of annoying.
I prefer the /etc/hosts hack, putting in entries like `127.0.0.1 twitter.com`. That way, when I actually want to visit Twitter, I have to `sudo vim /etc/hosts`, enter my password, comment out the host entry, save, go to Twitter, and then uncomment the entry, save and quit when I'm ready to block it again.
The inconvenience of the action is what makes it work. If I only had to type `workmode stop` I'd have that committed to muscle memory by the end of a work day or two.
I'll be 100% behind this project when it has as much control over a device as Tasker does. Recipes in JavaScript and not having to "program" on the device itself are exactly the kinds of things I wish Tasker could do. The modeOfTransport monitor is pretty attractive too.
Beyond all that, I'm curious about on{X}'s battery usage. That's a huge selling point for always-on processes like this.
Great article. This expresses better than I ever could have at age 20 why I quit my CS degree since I already had a job. At the time, the university was experimenting with a "software engineering" degree, but it was new and not yet accredited so it was too early to know if it was worth it.
Lately I've been re-discovering the value of the ORM and putting as much business logic on your models as possible. This, after spending way too long writing out lots of query logic in views instead. It's amazing how you can many times reduce complexity from 10-20 lines to 2-3 lines, and gain reusability, just by putting business logic where it belonged in the first place.
Not trying to add one more "VIM IS BETTER" comment like happens on every thread about editors, but I have an actual, for-real question: who wants to help make a Vim workalike version of this? Because I would donate to that (in time, meager Vimscript skills, money) in a heartbeat.
Agreed. It's one thing to say "x is faster than y" wholesale rather than considering the endless possible configuration options for each that could affect performance.
Seems like it'd be a lot more constructive to say, "Hey, it's not true out of the box, but here are settings you can fiddle with that, if they work in your situation, could make Apache a better option than Nginx." Anybody want to write that blog post? :)
My thoughts exactly. I wrote a line of plain text and it thought it was .vbs. It got a .py right, but only because I made sure it was distinct enough from Ruby for it to know the difference.
This is a great idea. I, too, often end up coding if I'm not tired when my wife is going to bed, but it often ends up being a marathon until 1:30 or 2 in the morning. Restraining myself to 2 hours a day, but doing it every day, seems like a good discipline.
It appears possible in some cases but it's not universally the case. Which means that similar binary transport formats that do support zero-copy, like Cap'n Proto, offer most or all of the perks described in this post, with the addition of ensuring that serialization and deserialization are not a bottleneck when passing data between processes.