badgar

17 ms·

121.
by badgar 14y ago
> It's the sort of looseness that causes people to think cellular telephones also talk to satellites. Anyone who hasn't heard of a "cell tower" in 2013 just doesn't care about what makes the phone go. Cell phones have been around, talki
122.
by badgar 14y ago
Betting big on hoarding bitcoins? Seems smart, almost like it's part of the design. /s
123.
by badgar 14y ago
So the tl;dr from Heroku is: we can't scale single-threaded applications.
124.
by badgar 14y ago
Heroku customers don't typically do math when they do capacity planning. That's part of the Operations toolchest they're buying. They just up/down dynos.
125.
by badgar 14y ago
So, to reiterate your argument: 1. We don't matter to pg because we don't generate profit and are instead a slow drain on resources 2. Therefore this site must be a relic of the 90s written in an ad-hoc collection of mzscheme macros
126.
by badgar 14y ago
A commenting site that: - Has average latency over 500ms when not under load - Performs quite poorly under load (I hate to bring it up, but the most recent example was Aaron Swartz's passing. Anyone who used HN then to get news knows how
127.
by badgar 14y ago
> I believe iPhone 1.1 had a bug in TIFF images that people used to jail break the phone Yep, there was a buffer overflow in the libtiff. http://theiphonewiki.com/wiki/LibTiff_Exploit
128.
by badgar 14y ago
> Evidently not! I'd rather not do business with liars. Is the entire startup world this naïve, or just this particular commenter?
129.
by badgar 14y ago
Cedar doesn't fix this for Rails. It helps marginally.
130.
by badgar 14y ago
No, you are correct, and move to AWS.
131.
by badgar 14y ago
> We've been on cedar ever since it launched, and been running puma threads or unicorn workers. The idea of one dyno per request is bullshit, and I wasn't sure if they were on cedar or not. A dyno is an allocated resource (512mb, not co
132.
by badgar 14y ago
> How many dynos does Heroku have running for non-paying customers? Do these free dynos actually necessitate this random routing mesh bullshit? If not, what? Of course the random routing mesh isn't necessitated by anything, this problem
133.
by badgar 14y ago
You're right. They'd have to instead build a load-balancer that solves the problem, and that's too darn hard.
134.
by badgar 14y ago
> So heroku doesn't want these $20,000/mo accounts, just technically understaffed startups paying $1000/mo? > I think heroku does want to be a long-term technology choice. Oh, I'm sure Heroku wants to be a long-term technology cho
135.
by badgar 14y ago
> With many routers, intelligent routing has its own performance cost, the routers need to somehow synchronize state, and the simulation ignores this cost. Which is why we pay companies like Heroku to engineer clouds in which to run our
136.
by badgar 14y ago
> There's a relatively easy fix for Heroku. They should do random routing with a backup second request sent if the first request times fails to respond after a relatively short period of time (say, 95th percentile latency), killing any
137.
by badgar 14y ago
> That's one reason customers are throwing money at you to solve it, Heroku. People are throwing money at Heroku because it's really easy to use, not because it's the best long-term technology choice. Seriously - what percentage of Hero
138.
by badgar 14y ago
Story is probably 100% true. Won't argue with any of the substance, which will likely be discussed in other threads. But this writing reeks of Microsoft astroturfing. Especially the "I got #googleplayed" dig which sounds just like their "Do
139.
by badgar 14y ago
Dude... who buys weed on the silk road?
140.
by badgar 14y ago
I think most of the people saying "rip off" consider token $1k checks "ripping people off," considering implementing it correctly would require hiring talented engineers with expensive salaries. Given the giant holes punched in the original
141.
by badgar 14y ago
I wonder if the Firefox architecture would allow for hot swapping. V8 throws everything away after compiling - it goes all the way back and reparses the source if it needs to recompile anything. So I'm guessing it's already relatively well
142.
by badgar 14y ago
> Thanks. I don't think these are so much incorrect assumptions so much as things we should change if the world changes. Is that not the definition of an assumption? Something you rely on being true and not changing, and which if it doe
143.
by badgar 14y ago
> I've struggled to say this and not sound snarky, but, in the face of this, how can we not admit that there's a bubble? Is this actually a controversial statement? I don't think so. Startups can be fueled by passion but ultimately are
144.
Enough, Already(backupbrain.com)
1 points by badgar 14y ago|0 comments
145.
by badgar 14y ago
It's still scope creep. The scope of implementing a real, user-facing bitcoin client is much greater than it was when the project started. Bitcoin reimplementors or those building tooling need to either support everything or risk fracturing
146.
by badgar 14y ago
> Treat input handling computational power as a privilege, and reduce it whenever possible. A great example of this was Google's Code Search product, before it was canceled. Since full backtracking search was blowing out the tiny thread
147.
by badgar 14y ago
If all you had to do to get laid was obtain condoms my high school years would've gone quite differently
148.
by badgar 14y ago
Sounds like bitcoin requires a backup system by default, then. Because otherwise, the first virus written by some pissy kid that just deletes wallets will devastate a lot of people.
149.
by badgar 14y ago
Not returning memory is different from a memory leak. Not returning memory means the memory footprint equals peak memory footprint. A memory leak is a bug in the program which causes space complexity in memory to grow unbounded. mzscheme ce
150.
by badgar 14y ago
The website we're on is restarted every few days because memory leaks are hard.

More ›