Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mean Stack

mean.io

Post reply on HN
Print view View original

51–60 of 97 posts

Re: Mean Stack

#51

Post by sanderjd »

PommeDeTerre wrote: post #35
adeaver wrote: post #27

Earlier quoted context omitted.

You are so right. Why try new things and test new ideas. Everything we have is perfect as it is! No need for a car, walking will get you there! We don't need moving pictures, books are fine! Do you even know anyone that works in Javascript? I happen to like JS but pull out PHP or Python or whatever I need to get the job done when I have to. And I'm not an exception.

I've seen your flawed argument used more and more often around here lately. It's pretty disappointing to see. Somebody speaking out against deeply broken technologies or bad ideas that have received a lot of hype lately does not mean that such a person "hates progress" or is "resistant to change" or any utter nonsense like that. Likewise, adopting so-called "new ideas" or "new technologies" does not necessarily mean…

I always seem to see you in any thread involving "new" technologies that you find "inferior", most of which are not very new and, like all technologies, are tough to put on a precise inferiority/superiority scale in an objective context-insensitive way. I'm beginning to move past annoyance to pure curiosity - why do you care so much what technologies other people find useful? In what way does people's enjoyment of Ruby/Rails, Javascript, NoSQL, etc. harm you so much that you have decided to come and be nasty any time anybody speaks positively of them?

Re: Mean Stack

#53

Post by pekk »

drhayes9 wrote: post #48
10098 wrote: post #45

Earlier quoted context omitted.

I can tell you why I dislike programming in JavaScript (those aren't necessarily faults of javascript itself): 1. Complex code usually contains some horrible callback spaghetti, which is not pleasant to debug at all. 2. General flakiness, or, as I call it, the "WTF happened?" syndrome. I run into this all the time. Change or add something - suddenly you find the web page broken. Okay, so there's a bug somewhere. Clic…

I hear you. I have extensions to your points and disagree here or there but, in general, all your points come down to the same thing: the developer toolchain for JS really frickin' sucks . Web development is a pain. Web developers have to deal with at least five separate technologies to get anything non-trivial to show up on the page. HTML, CSS, JS, server-side language, persistent store. Each one brings its own conf…

It isn't necessary for everyone to switch to something new at once. If one big browser accommodates a different language, someone will use it. If it is popular, it will be adopted more broadly.

Re: Mean Stack

#54

Post by 10098 »

pekk wrote: post #53
drhayes9 wrote: post #48

Earlier quoted context omitted.

I hear you. I have extensions to your points and disagree here or there but, in general, all your points come down to the same thing: the developer toolchain for JS really frickin' sucks . Web development is a pain. Web developers have to deal with at least five separate technologies to get anything non-trivial to show up on the page. HTML, CSS, JS, server-side language, persistent store. Each one brings its own conf…

It isn't necessary for everyone to switch to something new at once. If one big browser accommodates a different language, someone will use it. If it is popular, it will be adopted more broadly.

Not to mention, it can be compiled to javascript at first, for backward complatibility. Actually, Google's Dart comes to mind, but I haven't really used it to make an informed judgement about it...

Re: Mean Stack

#55

Post by ricardobeat »

batgaijin wrote: post #37
outside1234 wrote: post #19

Love it - except for the Angular part - can we get a MEEN stack with Ember.js?

What don't you like about Angular? The template engine makes the insanity of explicit updates go away...

Some would say data-binding and logic in HTML attributes is insanity.

Re: Mean Stack

#56

Post by Volpe »

bricestacey wrote: post #43
trimbo wrote: post #36

Earlier quoted context omitted.

> very appealing option in a number of cases. What cases do you have in mind?

Mongo sucks. I've used it in production for millions of people. I would never recommend it ever again. It's convenient, about the same way a hooker is.

Maybe your app wasn't suited for what it's good as. A File system would suck as a relational database... that doesn't mean it sucks in general. I suspect you had the same problem with Mongo.

Re: Mean Stack

#57

Post by tyre »

aroman wrote: post #42
trimbo wrote: post #36

Earlier quoted context omitted.

> very appealing option in a number of cases. What cases do you have in mind?

Rapid iteration comes to mind (as a result of its lack of schemas). It's also great if your objects are JSON documents, and as such it's particularly suited for uses such as a backend to Backbone. Those are two areas in particular where I would first look to Mongo.

The first reason sounds a lot like 'hacking things out.' That is wonderful in the early stages of development, but 'production' doesn't just getting the app live quickly. With an ORM, let's take Rails as an example, migrations make schema changes extremely fast.

As for JSON, Postgres has first class support for JSON data field types.

Re: Mean Stack

#58

Post by stesch »

krmmalik wrote: post #39
outside1234 wrote: post #20

Earlier quoted context omitted.

Mongo is incredibly productive. In the "lean startup" sense it is an easy database to start with.

Exactly the discussion i had today with a colleague. Mongoose makes it incredibly easy to get started and iterate rapidly. I have yet to experience MongoDB in a large scale production environment and the common pitfalls often cited, but let's face it - If you're Start-Up has scalability issues, it's prob a nice problem to have. Based on my personal observations, i suspect the lack of adoption is because founders are…

Is MongoDB the right DB for every size of startup? What about the people who just want to try different projects on 1 (one!) single server?

What I've read about MongoDB, it wants to use all the memory it gets. So it's only usable if it is running on its own server. (And in the beginning of MongoDB it had to be 2 servers if you didn't want to lose data.)

Is this a false information again? Am I falling for anti MongoDB FUD again?

Re: Mean Stack

#59

Post by stesch »

wasd wrote: post #3

What's the deal with MongoDB and the node.js community? I don't find non relational databases that enticing and there are javascript drivers for postgres [1]. [1] https://github.com/creationix/postgres-js

MongoDB is used in almost every community. Especially for new languages.

You can easily find relatively mature MongoDB drivers from the start for new languages, but don't hold your breath for PostgreSQL. See Rust.

Re: Mean Stack

#60

Post by muriithi »

jaredsohn wrote: post #7
cuttooth wrote: post #4

Earlier quoted context omitted.

JavaScript "developers" feel the need to not use any other language than JavaScript, so they decided to shove it into as many unnecessary places as possible, even if their code more frequently ends up being an unmaintainable mess with no noticeable performance gains.

I don't feel like you addressed the parent post. It was asking why people use mongodb instead of JavaScript bindings for PostgreSQL.

I have used both. I find it easier to iterate using mongodb because you do not even need a schema to begin with.

If I want to move forward I can switch to mongoose or move over to postgres and node-pg.

Post reply on HN