Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
exogen
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
121.
▲
by
exogen
8y ago
I'm aware and agree, and it also – even if less so than other solutions like Styled Components – counts as CSS-in-JS. So welcome to enjoying CSS-in-JS :)
122.
▲
by
exogen
8y ago
Good software is reusable. I can import functions from 1,000,000 different npm modules all into my project and they don't fuck with each other, right? Let's say you wanted to pull in a button from Bootstrap for one part of your pa
123.
▲
by
exogen
8y ago
While different from Styled Components, many people still consider CSS Modules to be squarely in the realm of CSS-in-JS. It literally generates a JavaScript module that you must import into another JavaScript module in order to actually use
124.
▲
by
exogen
8y ago
People often confuse the two, but CSS-in-JS is a distinct concept from "inline styles" (which can make pseudo selectors more challenging). Almost all CSS-in-JS solutions (including styled-components mentioned in the article) still
125.
▲
by
exogen
8y ago
What about non-basic front end code?
126.
▲
by
exogen
8y ago
Does not classifying it as a programming language help this situation at all?
127.
▲
by
exogen
8y ago
It's a language either way, whether you consider it "programming" is not really important. So, good luck with that. I live in the real world where it's used almost exclusively by programmers.
128.
▲
by
exogen
8y ago
Nobody thinks it's hard to delete a file. It's hard to know when you can delete a rule . Are you positive that all the rules in your component's CSS file only affect that component? Then great, delete the whole file. What
129.
▲
by
exogen
8y ago
Imagine a programming language that only had global variables. You have to carefully name your variables using complicated conventions in order to avoid any conflicts or unexpected behavior. Even your functions don't have local variabl
130.
▲
by
exogen
8y ago
Unfortunately npm is probably the biggest source of my daily development frustrations, even on the latest version. I still come across bugs (that are definitely in npm itself) that have been around absolutely forever, like: > npm ERR! cb
131.
▲
by
exogen
8y ago
Yeah I don't recommend `postinstall`, but `prepare` (and all the potential build-type scripts it could run) is actually useful (esp. for allowing people to install from unpublished versions via git), and would need special consideratio
132.
▲
by
exogen
8y ago
Even the latest version of npm 6 can get dependency resolution wrong. Like, the basic core feature.
133.
▲
by
exogen
8y ago
I'm assuming that lifecycle scripts (and scripts called by lifecycle scripts) in particular will still need to use common Windows-supported syntax? Even if the devs of the package are guaranteed to be using Yarn, people installing th
134.
▲
by
exogen
8y ago
Since I'm working in git repos the majority of the time, I type these hundreds of times per day: alias s="git status" alias d="git diff" I prefer looking at this stuff in a terminal rather than an IDE.
135.
▲
by
exogen
8y ago
All the conditionals in your rendering are at the very top level..?
136.
▲
by
exogen
8y ago
Likewise, I feel the same way about template DSLs (why add yet another language's control flow/scoping/etc. into the mix?). I think if JSX had been around first, many more developers would find templates off-putting, seeing a
137.
▲
by
exogen
8y ago
In this case, you gain the Apollo helpers around entity management, caching, etc. and the components they've already created for sending queries & mutations – so the ecosystem basically. Also if you're planning in the future t
138.
▲
by
exogen
8y ago
It's less about the approach being popular and more about dealing with the hand you've been dealt. The use case for something like apollo-link-rest is "I'm in control of the frontend only, and am being provided with a RE
139.
▲
by
exogen
8y ago
Seeing as the article under discussion is all about GraphQL, maybe the top-level comment was off-topic? Another thing to consider though, and something I've done in the past, is that you can actually embed the GraphQL resolver runtime
140.
▲
by
exogen
8y ago
Indeed! I wasn't talking about REST vs. GraphQL at all, but rather the benefit that fancy clients get you (notice I said "systems like what's described in the article", not GraphQL in general). I think that's what
141.
▲
by
exogen
8y ago
For (1), how does the parent know whether those components will actually be rendered? Keep in mind one of the requirements was "only fetch if they're actually rendered." Presumably some other components along the way could be
142.
▲
by
exogen
8y ago
Here's what just sending a request looks like with React + Apollo: https://codesandbox.io/s/q71px7njrw Which boilerplate do you take issue with? There are a couple imports you might find ugly, I suppose. Most like
143.
▲
by
exogen
8y ago
If even in Ember-land it's an entirely separate package, then why make the comparison to React at all..? (Ember + Ember Data) is more like (React + Apollo) then, no? But you're just comparing it to React without anything else.
144.
▲
by
exogen
8y ago
Why would a UI framework know anything about records? Keep in mind that it's explicitly not React's goal to know anything about requests, routing, records, data, or anything like that. That's why you hear React people talking
145.
▲
by
exogen
8y ago
It's certainly easier to start out that way. But there are also a lot of pitfalls, that systems like what's described in the article are designed to solve. For example: let's say when component A or component B get rendered,
146.
▲
by
exogen
8y ago
I write React every day and don't know what you're referring to – you can just call fetch() in a lifecycle hook and be done with it, just like in any other framework. But mostly I'm curious how your point relates to this blog
147.
▲
by
exogen
8y ago
Interesting, having used them both a lot I feel exactly the opposite way – I think grid's capabilities apply to more situations and suspect it will be the go-to layout/alignment tool once it catches on more. Grid is the more power
148.
▲
by
exogen
8y ago
This is honestly the most ridiculous thing I've ever heard. You think it's acceptable to never admit that you don't know something? You're advising people to pretend to know everything? I would immediately try to get you
149.
▲
by
exogen
8y ago
It's been a while since I've used IRC daily, but I think I remember the basics... Doesn't IRC file sharing involve directly connecting to individual users to transfer the file, instead of those users choosing to download it a
150.
▲
by
exogen
8y ago
In my experience doing stuff like this for artist/song record linkage, the key is really to take a "query expansion" approach rather than a "normalization" approach, because choosing a single normalized form is impo
More ›