Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dperfect
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
41 ms
·
331.
▲
by
dperfect
12y ago
From what I understand, it creates a new table with the same structure as the existing table, runs your migrations on it, adds triggers to bring live changes in from the original table while copying (in batches) the records in the old table
332.
▲
by
dperfect
12y ago
For ActiveRecord (or other Ruby-based) migrations with MySQL, I've had good luck with Large Hadron Migrator[1]. It's worked flawlessly for some of our own tables with several hundred million rows (and no downtime). [1] https:
333.
▲
by
dperfect
12y ago
Parse's solution is a great start as you say, but I can see myself running into the limits of that approach fairly quickly. And, as you say, if these solutions mature, we might have some very powerful stuff in this space in a few years
334.
▲
by
dperfect
12y ago
From the video: > Building the backend... is a lot of work. You have to build it, deploy it, and manage the infrastructure that it runs on." To me, it certainly sounds like they're trying to market this as an alternative to hav
335.
▲
by
dperfect
12y ago
Why do so many people (and companies) pretend that app backends are just (logic-less) data stores? I can definitely see the argument that some mobile games only need to store/sync some basic state information on behalf of the user, but
336.
▲
by
dperfect
12y ago
Not surprisingly, most of the results for common words/phrases seem to be unavailable. For a simple domain search, that's expected, but not so much for a suggestion tool. If I'm going to wait for a small handful of domain sug
337.
▲
by
dperfect
12y ago
As a longtime fan of Thin, I've been very impressed lately by Reel[1], which is built on Celluloid::IO. In particular, Webmachine-ruby[2] is a nice framework that supports Reel. While arguably not popular enough (yet) to be considered
338.
▲
by
dperfect
12y ago
... except we should remember the fact that exploiting this power is not an all-or-nothing choice. Some have shown that double spends and other abuses of this kind of power have already happened, yet Bitcoin survives. As long as someone can
339.
▲
by
dperfect
12y ago
These discussions seem fairly relevant now: https://bitcointalk.org/index.php?topic=393815.0 https://bitcointalk.org/index.php?topic=399313.0 "...if every bank vault in the world had a vulnerability th
340.
▲
by
dperfect
12y ago
> It's pretty easy to break delegation I'd be interested to learn how mining delegation could (in theory) be avoided. It seems to me that as long as you have a proof-of-work designed around something that can be solved with dis
341.
▲
by
dperfect
12y ago
Thanks - will do.
342.
▲
by
dperfect
12y ago
Thanks for the report - I'll check it out.
343.
▲
by
dperfect
12y ago
> No relevant domains popped up The algorithm sometimes finds very distant relationships to the word you give it. It depends somewhat on the word and whether or not more closely-related words are available. Since "resume" may b
344.
▲
by
dperfect
12y ago
This is one of my recent side projects. I'd love to get some feedback here.
345.
▲
Show HN: Endless Domains – Domain suggestion tool for new gTLDs
(endless.domains)
7 points
by
dperfect
12y ago
|
12 comments
346.
▲
by
dperfect
12y ago
I recommend Dokku ( https://github.com/progrium/dokku ) if you want something similar to Heroku. The nice thing about Dokku is that it's simple without locking you in to any particular (proprietary) cloud provider s
347.
▲
by
dperfect
12y ago
> They let me sleep at night instead of worrying about keeping my stack up to date I'm not sure what kind of stack you're running on Heroku, but if it happens to be Ruby, Heroku won't do anything (AFAIK) to update gems spe
348.
▲
by
dperfect
12y ago
Sounds like the core problem is just "Chinese web sites have yet to take full advantage". I'm really wondering how many (or what percentage of) devices actually need "a special plug-in". Seems like it would be a ver
349.
▲
by
dperfect
12y ago
Interesting. From what I can tell though, the lack of support from those TLDs seems to be deliberate rather than due to any technical challenge (the domain you register ends up just looking like standard alphanumeric ASCII with some dashes)
350.
▲
by
dperfect
12y ago
I'm surprised there's no mention here of punycode and IDNs. Is there just not enough widespread support for IDNs (the article mentions a need for plugins, but I thought most browsers already support IDNs), or are numbers really th
351.
▲
by
dperfect
12y ago
It's easy (or easier) to call your own app "stupid" when it's a single-person effort. As soon as you bring on other people to help, it's hard to call it "stupid" - not because the app changed and not becau
352.
▲
by
dperfect
12y ago
I agree. The fact that a large number of Ruby/Rails apps fall behind in terms of keeping dependencies up-to-date speaks more to Ruby's adoption than to its inherent insecurity. Without comparing these figures to other languages&#x
353.
▲
by
dperfect
12y ago
I love the idea of FPCs, but I have a hard time understanding the practical applications. Even the Wikipedia entry[1] seems to list examples, most of which don't entirely rely on the flexibility of the device. I can understand the need
354.
▲
by
dperfect
13y ago
True. This may just be due to inaccuracies in the depth map. And therein lies the problem with synthetic aperture algorithms like this: to make it look (close to) natural, you need very clean depth boundaries. There will always be problems&
355.
▲
by
dperfect
13y ago
Here's a comparison that illustrates the behavior of foreground blur (shot with a DSLR): http://i.imgur.com/986Iv2K.jpg You'll notice that on the bottom image, even though the foreground leaves are out of focus, t
356.
▲
by
dperfect
13y ago
I believe the algorithm could be improved by applying the blur to certain areas/depths of the image without including pixels from very distant depths, and instead blurring/feathering edges with an alpha channel over those distan
357.
▲
by
dperfect
13y ago
That's true. Still doesn't mean you should optimize for CTR when you're really interested in conversions. But I do see your point that in some cases - especially when starting a new campaign on a tight budget, it would be use
358.
▲
by
dperfect
13y ago
Again, if you've set up your campaign to optimize for what you really want to see (not just clicks), then why would you even need to care about desktop vs tablets? There are more and more devices every day that blur the line between de
359.
▲
by
dperfect
13y ago
So don't optimize your campaigns simply for clicks. A lot of people here are complaining that Google is doing something "shady" by making ads available to mobile platforms (mobile ads are here to stay regardless of how people
360.
▲
by
dperfect
13y ago
It's been a little while since I've used it, but doesn't Google let you do placement optimization based on meaningful conversions or other user-defined goals? It sounds like the problem here was just Google's ad placemen
More ›