deafbybeheading

6 ms·

1.
by deafbybeheading 11y ago
Only if you interrupt the actual `rm`, no? If you interrupt the main command, you won't get a 0 exit code so the `||` branch still executes. Your mechanism is clearly safer, but the user is required to clean up `foo.tmp` themselves in
2.
by deafbybeheading 11y ago
Thanks, I know `||` in general--I meant I hadn't seen the specific construction GP had used. The error handling to delete the output file in case the command failed is really elegant.
3.
by deafbybeheading 11y ago
Can you explain what the program itself is doing to do that? That is, can you explain the Coq program itself (and how it triggers the bug)?
4.
by deafbybeheading 11y ago
Oh my! That `||` is gorgeous. I hadn't seen that before.
5.
by deafbybeheading 12y ago
>Fun fact: ASCII actually reserved control characters for this stuff. 1F is the "unit separator" and 1E is the "record separator". There is even a "group separator" (1D) and a "file separator" (1C)
6.
by deafbybeheading 12y ago
A colleague uses the Dell XPS 13 and it's pretty good; I'm eyeing that for my next machine.
7.
by deafbybeheading 12y ago
Why not have Apple require apps to run usefully with just basic permissions? Anything beyond access to own files is optional. This could certainly be gamed, but scrupulous app authors could gain a ton of trust from playing ball.
8.
by deafbybeheading 12y ago
Some valid points, but GitHub's UI evolution has been phenomenal over the last two years.
9.
by deafbybeheading 12y ago
Stupid (and somewhat tangential) question: how do bypass kernels work with virtualization, if at all?
10.
by deafbybeheading 13y ago
...and a mechanism provided by the party you are attempting to secure passwords from. I use LastPass, but just sayin'.
11.
by deafbybeheading 13y ago
In about a year of using Campfire, I never saw a single bug fix or new feature. We've since moved to HipChat, and while it's not perfect, it's so refreshing to pay for a service that gets regular updates (not to mention has d
12.
by deafbybeheading 13y ago
Rollback is essentially like a fork to the past. It creates a new database, but only replays transactions up to a specific instant. It's based on the Postgres Point-in-Time Recovery feature: http://www.postgresql.org/do
13.
by deafbybeheading 13y ago
Oof, you're right--sorry about that. The addons page [1] has the right pricing, but our own pricing page is incorrect. I'll make sure we get this updated. Thanks for pointing it out! [1]: https://addons.heroku.com/
14.
by deafbybeheading 13y ago
While I agree this is not a huge engineering endeavor and Yahoo could do the Internet a solid by making this work, our free dev databases are limited to 10k rows (and, as the name suggests, intended for development). Please don't put a
15.
by deafbybeheading 13y ago
Microsoft sometimes licenses things like this and it's commonly referred to as "shared source."
16.
by deafbybeheading 13y ago
General usability is important in pretty much all interfaces, but discoverability isn't. There's a big difference between designing an interface a user will be instantly familiar with, and one that's optimally suited to the t
17.
by deafbybeheading 13y ago
Not to mention the program sigkills itself before it attempts to `exit 0`...
18.
by deafbybeheading 13y ago
That's absurd. The law of diminishing returns comes into play, and for most cases, assembly is just not worth it (whereas C or C++ is). Rust seems like another interesting take at that sweet spot, but it seems like in Go this was an af
19.
by deafbybeheading 13y ago
The default is determined by initdb, but was capped at 32MB due to the above issue. With this change, the cap's been bumped to 128MB.
20.
by deafbybeheading 13y ago
reference: http://www.ufopaedia.org/index.php?title=Elerium-115
21.
by deafbybeheading 13y ago
As a big fan of the GPL, ...I'm skeptical. I don't think Valve would benefit from keeping any potential modifications (or even plugins) secret, given that these would be far removed from its bread-and-butter. A friend once suggest
22.
by deafbybeheading 13y ago
I'll take talking to my phone as a first step. Getting simple file transfers to my SIII has been a pain, not to mention anything more sophisticated...
23.
by deafbybeheading 13y ago
Don't forget --no-preserve-root
24.
by deafbybeheading 14y ago
Why not rsync?
25.
by deafbybeheading 14y ago
Indeed. A few years ago, I worked in an Adobe Flex on a reporting front-end that had significant client-side complexity and required us to support relatively old browsers. We re-evaluated competing JavaScript solutions periodically, but we
26.
by deafbybeheading 14y ago
Sure, I was being facetious. Even with actions that are simple to execute, I'm somewhat skeptical that a black box with a single recommendation is the best answer. I think that presenting the analysis as "do this, and here is why" would be
27.
by deafbybeheading 14y ago
Then you can skip the middleman and just automate the taking-action part.
28.
by deafbybeheading 14y ago
The thing is, unit tests are another "use case" for a given piece of code. Many people here are saying, "I wouldn't do monkey patching in production, but it's not really a problem for stubbing in test code." And what happens when you want t
29.
by deafbybeheading 14y ago
>I know the warnings are in place for a reason, but why don't the affected people just bypass the warning. Not caring about certificate expiration may be a sign of not caring about other, more serious, security issues.
30.
by deafbybeheading 14y ago
> Today was my first real usage of PostGres Then let us welcome you with some pedantry! Postgres or PostgreSQL, but never PostGres or--FSM forbid--PostGreSQL. More seriously, > fdw looks easy to start, but probably hard to master it

More ›