Live data from Hacker News

Mern: Build JavaScript apps using React and Redux

mern.io

51–60 of 141 posts

Re: Mern: Build JavaScript apps using React and Redux

#54

FWIW 'isomorphic javascript' was pretty much supplanted by 'universal javascript' last year per this medium post [1]. You might consider changing the copy. Edit: At the very least Dan Abramov (Redux creator) is ok with universal [2] [1] https://medium.com/@mjackson/universal-javascript-4761051b7a... [2] https://github.com/gaearon/react-redux-universal-hot-example

Lets not get caught in 'war of words'. There is no standard to it and I don't think it matters as long as you understand what it means.

Re: Mern: Build JavaScript apps using React and Redux

#55
post #19

Why MongoDB?

I use MongoDB because I can instantly save down a JavaScript object and later retrieve it in the same state. I don't have to worry about anything else. No configuration, nothing. That's all I need but if there are better options I'm all ears.

You can do that with almost any language and any storage. JSON.

Re: Mern: Build JavaScript apps using React and Redux

#57
post #49

FRAMEWORK (shitty tragedy in one act) Dramatis Personae PROGRAMMER, programmer HIPSTER, hipster * * * ACT I Small room. There are a table with paper stacks, opened "Perrier" bottle, two huge monitors and a programmer sitting behind. Programmer reads papers, looks on first monitor, then on second and typing something. From time to time he says "damn idiots". Number of "damn idiots" is divided equally between papers, f…

[deleted]

Re: Mern: Build JavaScript apps using React and Redux

#59

Earlier quoted context omitted.

Because people hate the constraints put in place by SQL. It doesn't really matter that they'll spend dozens of hours re-implementing stuff they would've gotten for free with SQL in a RDBMS (not to mention the benefit of serious stability), what matters is that the initial effort to make a change is much lower, and thus developers feel like they're saving a lot of time/hassle. They don't seem to connect the cost on th…

With NoSQL you do have to reimplement all of the constraints in the application but this will likely be necessary even for SQL code because you'll need to provide both server and client side validations on user input. SQL can be even more of a pain because you'll need additional checks to handle the SQL server's particular blend of error handling if/when something goes wrong. In both SQL and NoSQL, any decent ORM sho…

Like ORM, NoSQL looks as a good decision at the beginning...

http://blogs.tedneward.com/post/the-vietnam-of-computer-scie...

Post reply on HN