1,489 karma · joined February 17, 2008
Whereas github lets you get a repo up and running with just about a single click and a 'git push', and then add on features and information as you grow. So it became the place to stick all of your one-off, throwaway, or experimental code, which got developers in the habit of using it, and it also had the room to grow if once of those things grew into a "real" project.
Huh? That's just blatantly wrong, and I (and many others) have used the C preprocessor to create multi-level macros in quite powerful ways. See for example http://blog.nelhage.com/2010/07/implementing-an-edsl-in-cpp/ or the insanity Linux's tracing macros have implemented: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6...
His article has a point, but he's not doing C macros justice -- they are quite powerful and can be used in really cool ways, even if people tend to look at you funny when you do :)
If someone wants to try a port to, say, a BSD that abstracts the syscalls and ioctls into a platform-specific way, I'd be happy to take a look.
strace -o /tmp/reptyr.strace ~/src/reptyr/reptyr PID
and then send me the contents of /tmp/reptyr.straceThanks!
They're even writing their own version of Lions' Commentary for it.
typedef struct { unsigned long pte; } pte_t;
typedef struct { unsigned long pmd; } pmd_t;
typedef struct { unsigned long pud; } pud_t;
typedef struct { unsigned long pgd; } pgd_t;
That way, even though they're all represented as 64-bit values, the compiler
will catch you if you try to mix-and-match different types without doing
appropriate work.Passing small structs in registers means that Linux can do that, and pass around `pte_t`s as parameters, without having to worry about paying a runtime cost for their typechecking.
When they pre-emptively ban my user-agent because someone might steal it and spam with it, but don't apply the same rules to themselves and their partners, then I get annoyed.
No. What Twitter is asking for is that you keep that "user agent" secret, even though you have to distribute it to everyone who uses your app. And they have demonstrated that they will happily block that user agent value if you don't do so.
I would be perfectly happy identifying my app to Twitter, and I'm more than happy using OAuth -- it's technically a much better choice than plain passwords. I'm not happy that I have to fulfill an impossible requirement or have my app disabled, and more so that that requirement isn't applied to Twitter themselves or to the other large players they have partnerships with.