Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kwamenum86
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
kwamenum86
15y ago
Web workers are not well-supported yet: http://caniuse.com/#feat=webworkers The most important omissions from that list are IE < 10. Using web workers if present and falling back on a different strategy are probably the right way to
92.
▲
by
kwamenum86
15y ago
You should rewrite a "pseudo-non-blocking" implementation of these filters. Right now they block the UI thread for too long, which limits how useful these can be. Web workers in one option, although it's not widely supported. The better
93.
▲
Tips For Standing Out During the Interview Process
(blog.meebo.com)
9 points
by
kwamenum86
15y ago
|
1 comments
94.
▲
by
kwamenum86
15y ago
Ha. That's actually pretty funny. To state the obvious: that's impossible. If the list omits itself, it's incomplete. It it includes itself, it's invalid.
95.
▲
by
kwamenum86
15y ago
As someone else in this thread mentioned, the page has a link to itself in the L section, which means that we can't (and don't need to) go a level up. Like any good metalist, this list contains itself.
96.
▲
by
kwamenum86
15y ago
The idea is to get traction before the original company can. The idea has already been validated in one market and in theory introducing it to another market will work as well. When the original company is ready to expand to those other m
97.
▲
by
kwamenum86
15y ago
"code to the standards and to hell with anyone who breaks them" I think bug in this case just means that the software does not work as intended even though it follows the spec.
98.
▲
by
kwamenum86
15y ago
"Bing: A Microsoft & Yahoo Production?" This reminds me of mistakes I've seen semantic analysis engines make. I'm not totally sure if this is a triumph of computing or a failure of Congress.
99.
▲
by
kwamenum86
15y ago
gosh i hope you don't get sued
100.
▲
by
kwamenum86
15y ago
Cool. But I think most people would be able to guess who sent the text based on who is likely to be buying shoes for them.
101.
▲
by
kwamenum86
15y ago
Instagram's Mike Krieger actually wrote quite a bit of code at Meebo (he is listed solely as UX). But point taken.
102.
▲
by
kwamenum86
15y ago
Watch from tokyoflash.com. Nice.
103.
▲
by
kwamenum86
15y ago
Yes and no. If you have a templating solution that works well on the client and server then this shouldn't add much complexity. Rendering the initial view on the server has the added advantage of supporting javascript-disabled clients too
104.
▲
by
kwamenum86
15y ago
"I can envision a time when full page refreshes are the exception and that isn't a bad thing." Agreed. Different clients should get different views. I don't think we're that far off from having to support the js-light "web crawler" view,
105.
▲
by
kwamenum86
15y ago
If you render the initial view on the client you still get indexability. Twitter actually still uses the old version of their site for this purpose.
106.
▲
by
kwamenum86
15y ago
"All the pages can be rendered on both the client side via JavaScript as well as the server. How this work I cannot tell you" There are plenty of templating engines that have been ported to Javascript. Mustache is the first example that com
107.
▲
by
kwamenum86
15y ago
buggy but cool
108.
▲
by
kwamenum86
15y ago
Comes off as a marketing trojan horse...
109.
▲
by
kwamenum86
15y ago
This is, at the very least, and opportunity for arbitrage.
110.
▲
by
kwamenum86
15y ago
"I would posit here that nothing I could do in best practice (manual front-end testing, unit testing, error handling, etc.) would have caught the offending line." Running your code through JSLint (or something similar) would have been helpf
111.
▲
by
kwamenum86
15y ago
Really sweet hack
112.
▲
by
kwamenum86
15y ago
His interview was underwhelming but a couple years he spent a lot of time (at least half an hour) in the hallway afterward talking to a handful of attendees (~8), which is pretty awesome.
113.
▲
by
kwamenum86
15y ago
I think one lesson of the Dropbox story is that you can build a company around a feature of minimal product if you have a savvy team and crisp execution.
114.
▲
by
kwamenum86
15y ago
Is this something that you find compelling? Does sharing sound intrinsically valuable to you? Do we need a social network just for sounds? I don't get it.
115.
▲
by
kwamenum86
15y ago
Is it me or is a social network just for sound obviously a bad idea?
116.
▲
by
kwamenum86
15y ago
Far from conclusive evidence here. And my intuition says something different to me. A controlled experiment would involve showing the mobile UI on the desktop and vice versa. You might also want to control for things like page load time
117.
▲
by
kwamenum86
15y ago
Clever logo but butt ugly.
118.
▲
by
kwamenum86
15y ago
Git can be a beast conceptually speaking if you don't learn it the right way. This was undoubtedly a bug but the author's story surfaced some suboptimal git habits.
119.
▲
by
kwamenum86
15y ago
What's difficult about long polling? It's a solved problem. There's an abundance of battle-tested frameworks available and it's a proven technique. Also, Facebook already has the infrastructure in place - they have the expertise in-house
120.
▲
by
kwamenum86
15y ago
web sockets or, in most browsers, long polling. long polling is easy to implement and they must already have the infrastructure built out since they have chat...silly Facebook. [edit] just took a closer look at the network activity. this
More ›