Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: small readme typos/rephrasings #330

Merged
merged 3 commits into from
Aug 18, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ This isn't another wrapper around [Express](http://expressjs.com/) or a framewor

##### Minimal API surface area

Lux utilizes JavaScript's standard library rather than creating a ton of functions you'll have to learn and remember.
Lux uses JavaScript's standard library rather than creating a ton of functions you'll have to learn and remember.

After your learn how to use it, you'll rarely need to look at the docs.

Expand All @@ -62,7 +62,7 @@ It's fast, it allows the developer to get low level with a relatively simple API

##### Not so fast (metaphorically speaking).

The last bit there "It's just JavaScript" has actually been somewhat of a double edge sword. This has positioned Node as a "great prototyping tool" or "only used for micro services".
The last bit there "It's just JavaScript" has actually been somewhat of a double-edged sword. This has positioned Node as a "great prototyping tool" or "only used for micro services."

I can somewhat see why people would think that when returning a list of the first 10 records from a SQL database table looks like this:

Expand All @@ -78,11 +78,11 @@ app.get('/posts', (req, res) => {
});
```

Could you imagine how ugly that would be if you have implement pagination, filtering, sorting, or better yet formatting the response for JSON API?
Could you imagine how ugly that gets when you have to implement pagination, filtering, sorting, orbetter yetformatting the response for JSON API?

Also, where does that code live? What file in what folder would I be able to find that? What pattern do you use for organizing this code?
Also, where does that code live? In what file and folder would I find it? What pattern do you use for organizing this code?

😲Ok ok give me back Rails I'll worry about performance and scaling later. After all premature optimization is the root of all evil.
😲Ok ok give me back Rails I'll worry about performance and scaling later. After all, premature optimization is the root of all evil.

##### Problem.resolve();

Expand Down