Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
grvcoelho
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
1.
▲
Show HN: A functional version of my MIDI Keyboard with CSS and React
(grvcoelho.github.io)
4 points
by
grvcoelho
3y ago
|
0 comments
2.
▲
Show HN: Https://169254.now.sh – an API to mock AWS EC2 metadata endpoint
(github.com)
1 points
by
grvcoelho
8y ago
|
0 comments
3.
▲
Show HN: We launched our Serverless payment microservice Open Source
(github.com)
7 points
by
grvcoelho
9y ago
|
2 comments
4.
▲
Straightforward Front-End Boilerplate with Webpack2, React, Tree-Shaking and HMR
(github.com)
1 points
by
grvcoelho
10y ago
|
0 comments
5.
▲
An AWESOME set of React Components for Voice Recognition and Speech Synthesis
(github.com)
2 points
by
grvcoelho
10y ago
|
0 comments
6.
▲
Show HN: Voice Recognition with React (component)
(github.com)
6 points
by
grvcoelho
10y ago
|
0 comments
7.
▲
React components of Web Speech API, with voice recognition and speech synthesis
(github.com)
2 points
by
grvcoelho
10y ago
|
0 comments
8.
▲
A react library to seamlessly handle DOM events
(github.com)
4 points
by
grvcoelho
10y ago
|
0 comments
9.
▲
A Fish Shell plugin to discover your wifi-password on the terminal
(github.com)
4 points
by
grvcoelho
10y ago
|
0 comments
10.
▲
Babelfish is a straightforward JavaScript lib for translation :D
(github.com)
3 points
by
grvcoelho
10y ago
|
0 comments
11.
▲
The straightforward front-end boilerplate you need
(github.com)
1 points
by
grvcoelho
10y ago
|
0 comments
12.
▲
Show HN: Front-end boilerplate without overcomplication
(github.com)
10 points
by
grvcoelho
10y ago
|
1 comments
13.
▲
Show HN: I created a useful Node.js library as a tutorial on CI, ES2015 and more
(github.com)
2 points
by
grvcoelho
11y ago
|
0 comments
14.
▲
by
grvcoelho
11y ago
This is a work in progress. More snippets will be added soon. Fell free to submit your snippets! :)
15.
▲
An awesome set of JavaScript snippets for VIM with support of ES2015 and Node.js
(grvcoelho.github.io)
4 points
by
grvcoelho
11y ago
|
1 comments
16.
▲
Show HN: A complete set of awesome JavaScript snippets for VIM
(github.com)
4 points
by
grvcoelho
11y ago
|
0 comments
17.
▲
by
grvcoelho
11y ago
I think you didn't understand the idea of the project and the concept of i18n. These translations can help you not only to translate to other languages but to translate to English as well by creating patterns of messages. For instance
18.
▲
Show HN: Straightforward and easy internationalization for the server and the browser
(grvcoelho.github.io)
6 points
by
grvcoelho
11y ago
|
4 comments
19.
▲
Simple and useful JavaScript library for translations and internationalization
(github.com)
6 points
by
grvcoelho
11y ago
|
0 comments
20.
▲
by
grvcoelho
11y ago
No probs ;)
21.
▲
An awesome speech recognition API service to decode audio to text with Node.js
(github.com)
2 points
by
grvcoelho
11y ago
|
1 comments
22.
▲
by
grvcoelho
11y ago
The only case I think it's okay to use comments is for browser-specific hacks or a set of rules that is hard to understand. But I would avoid these cases if I could!
23.
▲
by
grvcoelho
11y ago
The problem is not with the ">", but with the specificity in general! The selector ".search-form .submit" has 2 levels if specificity. What I suggest is using 1 level of specificity like ".search-form__submit&quo
24.
▲
by
grvcoelho
11y ago
Yep! It's an ~opinionated~ steguide! But I do cover some other poj ts before BEM ;)
25.
▲
by
grvcoelho
11y ago
tks! the nesting topic is the most polemic, but also the most important to me :)
26.
▲
by
grvcoelho
11y ago
see above :)
27.
▲
by
grvcoelho
11y ago
http://stackoverflow.com/questions/5797014/why-do-browsers-m... tl;dr browsers read css property right-to-left. the more specificity a selector has, the more DOM lookup the browser needs to do.
28.
▲
by
grvcoelho
11y ago
In my experience using the "&" has lead to many mistakes and a difficulty to mantain things.
29.
▲
by
grvcoelho
11y ago
About comments: your CSS shouldn't need it! About preprocessors: the styleguide was created to be preprocessor-agnostic. Also, I suggest using Postcss instead.
30.
▲
by
grvcoelho
11y ago
Hello there! Awesome feedback :) Although perhaps I exaggerated the name of this thread (sorry, I'm new here), the repository DOES say it's an opinionated guide! Also, these are not rules, these are my guidelines and recommendatio
More ›