Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
twerquie
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
twerquie
12y ago
I'm just conceding that these argument cannot be won. Tomes have been written and the argument becomes unproductive very quickly. It's like people who believe in God arguing with those who do not. It's not about JavaScript or
32.
▲
by
twerquie
12y ago
I've responded there, sorry for the noise.
33.
▲
by
twerquie
12y ago
I'm no zealot, and don't think these are absolute truths by any means but I've worked extensively on enterprise solutions in both C#/.Net and Node.js and can respond to your points below. 1. It turns out the reactor patt
34.
▲
by
twerquie
12y ago
Care to back up any of your assertions? If your main complaint is popularity, your argument comes off as elitist.
35.
▲
by
twerquie
12y ago
This pattern is commonly called "materialized path", if anyone is trying to search for it.
36.
▲
by
twerquie
12y ago
I really enjoy that trend. Tech is a dry topic with typically uninspiring presenters.
37.
▲
by
twerquie
12y ago
I agree with this. The surface area of most modules is small enough to be covered in a README.md, which is displayed prominently on npmjs.org, github.com and a copy of it is in your ./node_modules folder. As said earlier, the core Node
38.
▲
by
twerquie
12y ago
If your application is largely fetching a bunch of external resources, say from something slow like a database or a web API, mashing them up and returning a response to a client, you need async. Node has a very beginner-friendly primitive f
39.
▲
by
twerquie
12y ago
Or your needs are so insanely complex - as in project management - that modelling the problem in any detail leads to a million features and an inflexible solution.
40.
▲
by
twerquie
12y ago
Either I'm interpreting this too simplistically or they're doing a great deal better than I expected.
41.
▲
by
twerquie
12y ago
This is a broad social generalization so please take it with a grain of salt, but I do think there is an element of truth to the notion that Japanese people take good care of their elderly maintaining their dignity and keeping a healthy res
42.
▲
by
twerquie
12y ago
I wonder it could be split up, and the necessary segment(s) could be dynamically loaded based on OS language preferences?
43.
▲
by
twerquie
12y ago
I was indeed.
44.
▲
by
twerquie
12y ago
I appreciate that the author distilled his thoughts about software down into porno terms we can all relate to.
45.
▲
by
twerquie
12y ago
You are fighting a losing battle.
46.
▲
by
twerquie
12y ago
For the same reasons you're writing in English.
47.
▲
by
twerquie
12y ago
What's wrong with just using Bower?
48.
▲
by
twerquie
12y ago
I used public transit, taxis and car sharing services exclusively until I started a family. At which point setting up the carseat every time became prohibitively cumbersome and I bought my own car. Children's car seats are very persona
49.
▲
by
twerquie
12y ago
I would argue that Google's job now includes executing javascript and evaluating dynamically loaded content. Break the web.
50.
▲
by
twerquie
12y ago
I think my point is clear when you read what I wrote as a whole instead of dissecting parts. I'm allowed to editorialize a bit, am I not? I'm not a robot nor am I writing my thesis on the subject, we're just talking here.
51.
▲
by
twerquie
12y ago
It is true though that many js deficiencies have turned out to be factors contributing to node's popularity. A lack of namespaces, standard library and import/require come to mind. I'm not interested in arguing about technica
52.
▲
by
twerquie
12y ago
Different yes, conflicting no. ES6 standard promises have landed in v8 ( https://code.google.com/p/v8/source/browse/trunk/src/promise... ) so it's only a short matter of time until the "
53.
▲
by
twerquie
12y ago
Because bolting reusable libraries together is 90% (meaningless number alert) of what we do when assembling modern applications. And in this respect, Node is perfectly suited to the job, boasting a) A small core API instead of a sprawling s
54.
▲
by
twerquie
12y ago
The writing here is very nice. I wish my writing carried itself as well. Beyond the style and structure, the tone of the article is remarkable and lovely. Cynicism wrapped in love and hope and nostalgia. Nice work.
55.
▲
by
twerquie
12y ago
It would be great if this was published as an npm module.
56.
▲
by
twerquie
12y ago
Sure, why not? See the "asshole vacuum" scene in HBO's Silicon Valley S01E02.
57.
▲
by
twerquie
12y ago
DHH does have a point, but he makes it in a manner that is hyperbolic, accusatory, narrow-minded, stubborn and often rude. I find him to be a negative voice in the community and a dangerous leader. I am happy to fight fire with fire where n
58.
▲
by
twerquie
12y ago
> I'd like to see someone form a well constructed argument for why that statement is inaccurate, over-stated, or otherwise unfair Here's his statement again, rewritten without the Fox News-style editorialization: "Test-fir
59.
▲
by
twerquie
12y ago
> Test-first units leads to an overly complex web of intermediary objects and indirection in order to avoid doing anything that's "slow". Like hitting the database. Or file IO. Or going through the browser to test the who
60.
▲
by
twerquie
13y ago
It is owned by a single corporate entity who is also its primary sponsor, Typesafe. This is similar to how Joyent owns node, and how they sponsor it's development, along with NodeJitsu, Microsoft, Heroku and others.
More ›