Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
glifchits
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
glifchits
11y ago
LaTeX
32.
▲
by
glifchits
11y ago
At least some reasonable evidence that the habit is harmful. Hard to argue that Richard Stallman suffers (productivity, or otherwise) by doing his computing in text mode ...
33.
▲
by
glifchits
11y ago
I don't really think anyone here is qualified to criticize Richard Stallman's computing habits.
34.
▲
by
glifchits
11y ago
This is pretty great! I find myself writing classes to encapsulate small bits of information, just to have this sort of functionality.
35.
▲
by
glifchits
11y ago
I think the appeal to majority goes the other way in this case. The article insists that existing technologies which dominate usage today (ie. HTTP) are good enough, and that Facebook's innovations are misguided. The authors have prev
36.
▲
by
glifchits
11y ago
These people have been attacking Facebook for a long time now. First React, and now Relay/GraphQL. Their technical arguments were never strong. Claiming that existing technologies eg. DOM, HTTP/REST are good enough is not convinci
37.
▲
by
glifchits
11y ago
I don't think Facebook ever claimed that HTTP was insufficient. They claim that HTTP/REST does not scale in large and dynamic projects, and Relay/GraphQL solves some of those scaling concerns. Given how strongly Relay/Gr
38.
▲
by
glifchits
11y ago
I disagree that Chrome gets little praise from the developer community. What makes you say that?
39.
▲
by
glifchits
11y ago
Fully agree. To call lack of conditionals a "limitation of JSX" is also very misleading. JSX is a pretty simple wrapper for Javascript function calls. The fact that you can't put an if statement in your JSX is due to the fact
40.
▲
by
glifchits
11y ago
Walmart Labs is using Scala for their data science work, according to Julia Greissl, whose talk I saw in Seattle a few days ago.
41.
▲
by
glifchits
11y ago
Seeing this comment thread, I couldn't resist the urge to shamelessly plug our own product Beagle (beagle.ai), which is a contract analysis tool. Like Ironclad, we're tackling the legal space, but where it looks like Ironclad help
42.
▲
by
glifchits
11y ago
Is "gerschnorvels" really a word in any language?
43.
▲
by
glifchits
11y ago
Yes but there's no advice on how to take it easy. It's just saying to do so, which is pretty unoriginal advice. Why recommend that someone take it hard, grudgingly, or angrily? It feels less sincere because there's no perso
44.
▲
by
glifchits
11y ago
I like this, but I also think the author did a good job of describing how the Chinese is much more heartfelt than the Western "take it easy". Maybe because its actually providing a recommendation instead of a vague directive.
45.
▲
by
glifchits
11y ago
Fascinating how a unique perspective can change your outlook on life. Not often that I hear that not much has changed in the past 50 years. I summarized my philosophy in 10 points, and I’m actually very surprised that people today,
46.
▲
by
glifchits
11y ago
We at Beagle Inc ( http://beagle.ai ) are building a product that uses NLP to make contracts easier to understand, bringing comprehension from 0 to 80% in seconds. There's also a collaborative piece which allows you to make c
47.
▲
by
glifchits
12y ago
This is an awesome idea. The example I'm most passionate about of web design I hate is an online pizza ordering site, because when I was intoxicated it was super confusing to just order a pizza.
48.
▲
by
glifchits
12y ago
General impression is the same. I'm using Reflux and quite happy with it, but this does seem pretty smart. Having built in rollback of actions is nice, and having the versatility of where-queries to invoke action handlers is interestin
49.
▲
by
glifchits
12y ago
Constructing a collection of things is just one case where a for loop is nice. Would be nice to see some more interesting examples of how we can use streams.
50.
▲
by
glifchits
12y ago
I think the speed of development gained now by leveraging all the good stuff that frameworks offer in the 10% tip of the iceberg is hugely beneficial in the short term. In the long term, thanks to initial productivity, teams will get more
51.
▲
by
glifchits
12y ago
Though this seems obvious in retrospect, this is an interesting insight: VC dollars are being spent on user acquisition despite unknown LTV of users ... I think some of the tech "bubble" is being driven by speculation in w
52.
▲
NuclearJS (Flux implementation)
(github.com)
3 points
by
glifchits
12y ago
|
0 comments
53.
▲
by
glifchits
12y ago
I experienced a lot of lags and delays between pages with no feedback as to whether or not the page is loading. The tokenized skills input list had empty tokens when I clicked Confirm. The UI looks and feels very good in my opinion but the
54.
▲
by
glifchits
12y ago
Take a closer look at the URL while you're at it. It may look like an obscure domain, but its really not.
55.
▲
by
glifchits
12y ago
It bothers me when people try to tell businesses how to improve their operations, purely for personal benefit. The point of VC firms is not to fund your business, its for VCs to generate a return on investment. VCs surely know that by not r
56.
▲
by
glifchits
12y ago
Yahoo's React/Flux projects mentioned at the end are intriguing. I have tried implementing Flux architecture in an app and found it really tedious and boilerplatey. I'm still looking out for well-implemented Flux dispatcher l
57.
▲
by
glifchits
12y ago
I included the "or whatever" to cover this case :)
58.
▲
by
glifchits
12y ago
Looking at a random file in the Flow source [0] (* The entry point *) let rec go content = let env = { file = None; modified = []; line = 0; result = [] } in let lines = split_lines content in start env
59.
▲
by
glifchits
12y ago
After seeing that Facebook's Flow tool was written with an OCaml parser, I was quite impressed by the beauty of its syntax. It makes functional programming feel much less intimidating, compared to Haskell or a Lisp in my opinion, and I
60.
▲
by
glifchits
12y ago
Clearly if Chrome had needed the memory, this would have been implemented long ago.
More ›