faceyspacey

14 ms·

61.
by faceyspacey 10y ago
It's a class thing. Young aspiring tech entrepreneurs in SF are living a completely different reality from the minimum wage earning people in Las Vegas. Whoever he's hanging out with in SF is much closer to that crowd. So yes, of
62.
by faceyspacey 10y ago
Yea I agree. It really looks like he just took the datalog language, put it in a browser, and added an in-browser IDE (basically like he did with clojurescript and Light Table). Not that this might be incredibly useful, and not that his vis
63.
by faceyspacey 10y ago
Chris Granger's Eve is based on Datalog. Perhaps his work is finally what breaks out the logic programming prolog paradigm.
64.
by faceyspacey 10y ago
In short, it's my opinion Famo.us decided to start an agency that utilizes a sub-set of the features they developed because they realized full on applications could not be developed with Famo.us. Why else would you start an agency usin
65.
How Famo.us Refused to Admit They Could Not Achieve Native Rendering After All(techcrunch.com)
5 points by faceyspacey 10y ago|2 comments
66.
by faceyspacey 10y ago
you call the action creator and dispatch its results to you redux store before rendering. For "arbitrary" routes, you design your application in a way that just by the pathname, query parameters, etc, you know exactly what data to
67.
by faceyspacey 10y ago
You populate redux with all the data your app needs (if you're using setState to store state fetched from APIs on components, stop). Then you simply render your app in one go.
68.
by faceyspacey 10y ago
debugging is the best I've ever experienced. Webstorm debugging was problematic for me a year and a half ago. Visual Code has surpassed Atom by far as well, which weirdly does NOT support client side debugging for javascript (and that&
69.
by faceyspacey 10y ago
constructor() { super() this.state = { isConnected: Math.floor(Math.random() * 10) > 5 } }
70.
by faceyspacey 10y ago
It didn't need to happen in componentDidMount with multiple calls to setState. If it's not getting info that it would only know after mounting, it could have happened in the same line that isConnected is initially defined within t
71.
by faceyspacey 10y ago
start doing stuff, stop going to school. don't "believe you'd like to be in the industry." BE in it to find out.
72.
by faceyspacey 10y ago
exactly. a real genius wouldn't go to harvard. real geniuses don't need "stamps" of approval. fake geniuses do, and not to shit on Y Combinator startups, but these days they aren't that ground breaking. Though now t
73.
by faceyspacey 11y ago
It's misleading and almost innacurrate. But yes I understand how time consuming and painstaking it is to build basically anything substantial. I'd just do more with realtime before u go comparing yourself to Meteor. Also the meteo
74.
by faceyspacey 11y ago
It has something close to 1% of the real time features meteor has. No doubt u have plenty of code to make up for that missing 99%.
75.
by faceyspacey 11y ago
Except, claiming you guys are "Real Time" just because you offer a basic websockets implementation and positioning your offering as anything that compares to Meteor is a sham. You don't have real time. You have web sockets th
76.
by faceyspacey 11y ago
Yet there are others with deep wisdom of the nature of authority--that when it gets to a certain size (especially where there is no larger authority to check it), there is always risk for it becoming self-serving. It's the nature of th
77.
by faceyspacey 11y ago
When thinking about Meteor's value proposition, it's been neck and neck between what you're saying (which is that of a "universal build tool") vs. it's full stack reactive subscription capabilities. Both of whi
78.
by faceyspacey 11y ago
The point is that Meteor will be handling the subscriptions side of things, the reactivity. There's a near-endless amount of work there to get it right. GraphQL and Relay don't even have an interface for subscriptions yet. The pla
79.
What “Reactive GraphQL” Means for Meteor…(medium.com)
3 points by faceyspacey 11y ago|0 comments
80.
by faceyspacey 11y ago
So awesome, thanks for the link. Guess we could probably reuse a lot of clojure code.
81.
by faceyspacey 11y ago
also, i think the real opportunity here lies in making it open source and making it all programmable. so literally you can program and enhance the damn thing as you use it--at least be able to one-click import extensions from NPM and github
82.
by faceyspacey 11y ago
Cycle.js would make for the perfect view framework for this giving the streaming nature of loops and observing new hits added to the grid: http://cycle.js.org We should use Meteor, RethinkDB or ClojureScript + Om Next + Datomic
83.
by faceyspacey 11y ago
also, what libraries and tools did you use to make this?
84.
by faceyspacey 11y ago
this is utterly amazing. whoever the programmer is, holler at me, I'd love to help you make it a collaborative realtime beat-making engine, i.e. so people can contribute to the same song at the same time. I'm sure you've alre
85.
by faceyspacey 11y ago
does anyone know how challenging it is to add Datomic subscriptions to Om Next?
86.
by faceyspacey 11y ago
So open source it so others can contribute
87.
by faceyspacey 11y ago
yea I made up. But if you've been in any Meteor forum topics about NPM and support for modules etc, it would would make more sense. Meteor exists as a layer on top of NPM. It has done a lot of harm to its marketability. "Bare meta
88.
by faceyspacey 11y ago
oops, yea.
89.
by faceyspacey 11y ago
yours isn't a full stack reactive platform. great work though.
90.
by faceyspacey 11y ago
My assumption is that Meteor is moving towards becoming like any other app you can build on NPM. That means Meteor will be the wrong tool anywhere NPM/node/javascript is the wrong tool. That's a fine agreed upon limitation. C

More ›