Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gniquil
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
gniquil
9y ago
I think you miss the point of having Next.js being based on React. Although I think handlebars/htmlbars are great (I'm a big ember user), the cool thing about React is it's component based. So pretty much everything you menti
2.
▲
by
gniquil
10y ago
Haven't watched through the entire video, but the first part, analyzing dependency bottom up, and claiming version doesn't work, really reminds me of graphql. We've been doing traditional rest with /v1/..., /v2
3.
▲
by
gniquil
10y ago
I use imgix at work and love it. However, there's one more downside which the article didn't mention, is no protected or authenticated assets, Say if you only want to serve an user some image if he's logged in. Other than, it
4.
▲
by
gniquil
10y ago
Increase/decrease font size, adjust window height/width. I know you can do it with keyboard, but perhaps touch bar could make it more "natural" and free up key bindings for something else. Escape can be mapped to a doubl
5.
▲
by
gniquil
10y ago
So who's gonna be working on Sublime/Atom/Vim/Emacs integration on this. Shit, imagine all the things one can do with that bar (multi-touch, slidable, swippable).
6.
▲
by
gniquil
10y ago
I don't understand why there's so much backlash against the "bar". Personally I'm actually really excited. I'm a programmer. I can imagine all sorts of plugins and addons one can make for one's favorite ed
7.
▲
Clojure Spec Screencast: Leverage
(youtube.com)
3 points
by
gniquil
10y ago
|
0 comments
8.
▲
by
gniquil
11y ago
Got too much on my hand var OVERLAP = 2500; var RECENTLY_PLAYED_NODES_LENGTH = 21; var recentlyPlayedNodes = []; var audioDurationFix = function(audio) { if ($(audio).attr('id') === 'ive-13') { return
9.
▲
by
gniquil
11y ago
It's sad that you capitulated. I agree with your original point more. Is this thing really flexible, composable, and implementable? How long do we have to wait for people to provide solid implementations on top of all the popular progr
10.
▲
by
gniquil
11y ago
It not said explicitly, but I believe, for us, long term growth means users change their behavior. We need them to stop using Craigslist. We have the same challenge as early AirBnB.
11.
▲
by
gniquil
11y ago
perhaps the way to make it wow, is to connect 100,000 led to it, and each controlled by a separate browser socket. V8/node folks will cry a little.
12.
▲
by
gniquil
11y ago
Thanks for the comment. Our goal is to succeed in the Linkedin/Facebook sense of the word (excuse our enthusiasm, but if not this, we would self fund and be content with organic growth). But I don't want to dismiss their wisdom, a
13.
▲
YC Rejection – How much should we change to address their concern?
2 points
by
gniquil
11y ago
|
4 comments
14.
▲
by
gniquil
12y ago
Your Meet me at "noon" placeholder got cut off (reads "no" right now). Had to pull up the trusty inspector to resize the input element to see the full word... Otherwise awesome!
15.
▲
Elixir vs. Ruby Showdown – Phoenix vs. Rails
(littlelines.com)
6 points
by
gniquil
12y ago
|
0 comments
16.
▲
by
gniquil
12y ago
Great job! Like the concept. But here's another nitpick. I see when you activate a file, the animation first shrinks the file a bit and then expands it out. Is it possible to remove the shrinking? It makes the app "feel" a bi
17.
▲
by
gniquil
12y ago
And of course someone should make storify for this once it gets popular.
18.
▲
Myths, Reality, and Relationship-Building in the EdTech Community at #SXSWedu
(21stcscience.blogspot.com)
1 points
by
gniquil
13y ago
|
0 comments
19.
▲
by
gniquil
13y ago
So I just looked at the quick start demo code. Did everyone notice the irony in it? We created some fake people and some fake orders and randomly let the people see the fake orders. Then we try to predict based on this data. A bit silly isn
20.
▲
by
gniquil
14y ago
in 15 slides. :)
21.
▲
by
gniquil
15y ago
I have a very noob question. For most databases, suffix search is always super slow. However, can't someone just build an index based on the string reversed, then treat suffix search exactly the same way as prefix search? This doubles your