In either case, you've moved security to the user's email program which is (sadly) probably an improvement.
2,199 karma · joined September 29, 2009
I wrote Rebuilding Rails, which I think is pretty good: http://rebuilding-rails.com
Some stuff I've done: https://codefol.io https://github.com/noahgibbs https://codefol.io/portfolio
I'm not hard to Google for, if you want to.
In either case, you've moved security to the user's email program which is (sadly) probably an improvement.
Redis Sentinel's semantics are a terrible solution for things I use relational DBs for.
The fact that clustered relational systems accepts transactions in SQL and then just handle them wrong is completely unacceptable.
Redis has the advantage of making it pretty darn clear that it's best-effort, simple ops, non-transactional. If you spent all your time bragging about ACID semantics for Redis, we'd rake you over the coals at least as hard.
(And you don't. Thanks for that! Also, Redis is awesome.)
Like, tradeoffs in consistency? No transactions? That requires not implementing some important bits of SQL.
Clustered relational DBs are really remarkably hard to get right. A shocking percentage of projects and vendors don't really even make a serious try (cf GaleraDB.)
This project may or may not have done a reasonable job (no clue,) but the lack of information about how they tested it is a bad sign.
For instance, the vigorous, long-lasting and constantly denied spamming that AirBnB did off CraigsList with fake names, or some of the early Reddit fake accounts and general puffing-up (which was, to be fair, less bad.)
Maybe business tactics are explicitly not part of what PG and Jessica consider "good character"? It seems increasingly clear that they mean something different by it than I do.
Which is fair. But "is a myth so far" suggests disproof, not proof that it's not currently true. As they repeatedly show, it would be very difficult for them to prove that, since they'd have to usefully measure delta in intelligence.
You can permit the dynamic stuff as an alternative (as Java more or less does.) But if people actually use it, it screws up the tools' ability to introspect into your code.
As a result, less-dynamic formats like HTML and CSS get better tooling, as a rule, because the tools have an easier job to do. And highly-dynamic languages like JavaScript and Ruby have terrible tools support, because they make the tools' lives quite difficult because of their language and library design.
So it's understandable that users often do an end-run around what they choose.
There are a few equivalents for common SQL DBs (see LinkedIn's Databus for Oracle and MySQL), but in general, getting access to the write log is really hard. Even though it's sitting there!
It would be wonderful if there were some kind of established API or library that would let you parse the MySQL write log without doing hideous, fragile operations that change from version to version. Sure, change the format, but at least version and document it!
That era was famous for its very-indebted Yuppies (and the origin of the idea of "Yuppies" as we think of them.)
Some of this can't be blamed on the politicians. Easy credit and the rise of credit cards generally did a lot for this. But politicians did get to decide how credit regulations worked. It took awhile to outlaw live (not pre-approved -- you could pick them up and just use them!) credit cards arriving at people's houses, for instance. You could literally steal one out of somebody's mailbox and go rack up money in their name.
Not any more, obviously. But they lasted longer than you'd think. Credit was pushed very hard at consumers, and politicians do control the extent to which that's legal, even if they're not really to blame for it being possible.
Also, non-TLS web sites can potentially be hijacked in flight, so this could happen even if the site in question wasn't directly cooperating.
VCs are very optimized for "go big or go home." It's nice to not have that pressure early on, for the founders and the other employees.
It's interesting how different the feel is at different companies -- VC-backed vs private-equity-backed vs public. Bootstrapped is potentially a different feel, and a better match for some people.
Does it work out that way in practice? No clue. Never worked for one of these, though I've worked for VC-backed, private-backed and public.
He also got a nicely-ranked Hacker News post for taking apart some SSL chicanery that a hotel was doing on his honeymoon, for instance.
Doesn't mean you have to like him. But no really, he's doing this sincerely.
Also, Mike is the developer, and a pretty darn good one.
I have high hopes for Ruby on Rails -- it won't have the longevity of COBOL, but it's gonna be a nightmare of a legacy system ;-)
But if they're anywhere near an upper bound, then whether they (a well-informed first-world superpower with a huge budget and a willingness to extradite people to places like Syria where there are effectively no rules) can make torture work is very relevant.
Because if they can't, and torture is useless, then clearly the question is effectively resolved, at least in the real world. If torture is simply ineffective in real-world scenarios then the question goes away.
They are looking very hard for scenarios to justify their use of torture, and the results they have revealed (e.g. from waterboarding Al Qaeda members) aren't inspiring, so far.
It appears, for instance, that waterboarding people many times (in a few cases, 100+ times) isn't enough to keep them from lying to you.