exogen

10 ms·

61.
by exogen 5y ago
I wish you were right, but this is unfortunately wrong – and it's not because developers don't know CSS well enough, but rather that CSS is just plain not good enough. And ridiculous new features keep being added to it when we sti
62.
by exogen 5y ago
I've always wanted to write my own CSS guide, because (in my experience) people are rarely focused on the right thing when they're writing CSS. Developers (especially junior) think that if it looks right, that it is right, and
63.
by exogen 5y ago
AVA is great, I use it on a few projects and even developed a simple HTTP record/replay add-on for it. I'd say it's good for smaller projects. One huge benefit of Jest though is the built-in mocking, including module mocking.
64.
by exogen 6y ago
One nice thing about GraphQL though is that you have the context of the whole query available in resolvers, parsed into a tree (like an AST) for you. You're right that the most obvious/default approach would lead one down the path
65.
by exogen 6y ago
Big fan of the Cosmic Crisp, it really does live up to the hype! Although, I have a sweet tooth and I might even find it too sweet.
66.
React Server Components(addyosmani.com)
2 points by exogen 6y ago|0 comments
67.
by exogen 6y ago
As far as I know they still support all the same fields that the Echo Nest did! At least, I can't remember any additional ones that aren't here: https://developer.spotify.com/documentation/web-api/referen
68.
by exogen 6y ago
Discogs is great. In my experience doing entity matching/record linkage across all the different music APIs: - Discogs seems to have the most complete release data. - MusicBrainz has the best organized encyclopedic data. For exampl
69.
by exogen 6y ago
This alternative falls apart as soon as you want to put a border or box-shadow around the content column while still having full-bleed elements. Now you're limited to having it individually around each group of elements before/aft
70.
by exogen 6y ago
React does detect and warn you about mismatches in dev mode. It can be tricky to track down if it only happens in prod, though (due to different data – like start/end times for content coming from a CMS). React could do better in both
71.
by exogen 6y ago
Advice on the "A Broken DOM" section: it sounds exactly like a hydration mismatch. Hydration is the process of React correlating existing DOM nodes from server-rendered HTML (SSR) with the initial render of the React app on the br
72.
by exogen 6y ago
Now let's say your data (cars) changes. Due to some interaction, a car gets added to the list. What the above code will do is completely replace the HTML for the entire list of cars, when really all that needs to happen is appending on
73.
by exogen 6y ago
Here's a great example, it was actually the first result on Google Images for "newport colonial home". Scroll through the pictures and count how many pineapples you can find: https://www.curbed.com/2017/3
74.
by exogen 6y ago
I grew up in a city with a lot of Colonial buildings, and you'll often notice pineapples carved into them (above the front door, for example). My grandmother told me they symbolize hospitality, which Wikipedia confirms: In archit
75.
by exogen 6y ago
I have a model similar to this one: https://www.homedepot.com/p/Hessaire-5-300-CFM-3-Speed-Porta... It is portable, if a bit large. The thing about price is: what are you paying to cover a certain square footage? To co
76.
by exogen 6y ago
I bought one for my space in Seattle and it's a game changer. I couldn't get A/C for several reasons, and was really nervous a swamp cooler would do nothing in this climate, but it works great! Pros: - You can (and are suppos
77.
by exogen 6y ago
This is a very accurate take that leads with some context before getting to the current situation: https://nostalgebraist.tumblr.com/post/620713736158724096/he...
78.
by exogen 6y ago
Then that tooling was broken to begin with.
79.
by exogen 6y ago
The writing could be improved, but to me it's clear that the previous paragraph is providing the context for this statement: they're talking about alternatives to using frameworks that provide a higher level of abstraction. Not al
80.
by exogen 6y ago
Those are all runtime concerns. They don't affect the literal syntax that you write, as is the case with JavaScript. You can't feature-detect syntax. Instead your entire program will just fail to parse.
81.
by exogen 6y ago
I used to work for a company that developed a JS widget people could stick on their site with ease (and not just little sites either, this was on microsoft.com, nfl.com, starbucks.com...) As such I got to deal with getting our code to play
82.
by exogen 6y ago
Maybe you should let the amateur devs at Facebook and Pinterest know how easy it is? After all, they developed this entire framework in Objective-C to address UI performance, and – shocker here – they consider 60fps a selling point there, t
83.
by exogen 6y ago
The problem before was that your class component was not updating correctly and rendering stale & out of sync data. If it were updating correctly, it would have had the same infinite loop problems.
84.
by exogen 6y ago
If you think pointing out a bug due to an edge case someone didn't think of is the XY problem, I'm afraid you don't know what the XY problem is.
85.
by exogen 6y ago
For foreign-origin iframes, that's exactly what people do using `postMessage`. But for same-origin iframes there's no need since you can access the iframe's context directly. So people can (and do) write code exactly like thi
86.
by exogen 6y ago
create-react-app isn't even using is-promise directly. It's several hops in the dependency graph away.
87.
by exogen 6y ago
That won't work across window boundaries, since each window environment gets its own distinct version of Promise.
88.
by exogen 6y ago
It wouldn't work even if everything were native – see my reply above.
89.
by exogen 6y ago
Your implementation is broken even if everything uses native Promises. I don't know how many times this exact thread needs to happen on HN (as it has many times before) until people realize their "no duh" implementations of t
90.
by exogen 6y ago
A package with over 11 million weekly installs vs. a brand new implementation by a coworker, when I might not necessarily be around for the code review? Absolutely. I would blindly trust the package 100% of the time. Zero hesitation.

More ›