yuchi

31 ms·

301.
by yuchi 9y ago
Interesting article but has nothing to do with «Unsafeness». (better wording: Promise implementations leak on the heap)
302.
Cloudflare Workers Tutorial/Playground(cloudflareworkers.com)
1 points by yuchi 9y ago|0 comments
303.
by yuchi 9y ago
This is… actually not bad. :shocked:
304.
by yuchi 9y ago
«pull reload» or «pull refresh» AFAIK
305.
by yuchi 9y ago
Waiting for an answer too…
306.
by yuchi 9y ago
Help me on this: Facebook has just removed the PATENTS file from GraphQL repository, and now there are issues for this? And at the same time people are arguing over removing it from React? This is madness…
307.
by yuchi 9y ago
> This article reads as "I learnt how to do CSS this way so anything new is scary and wrong" Yes. A little bit sad…
308.
by yuchi 9y ago
Citing that article: > “It suggests that Aboriginal oral traditions may have endured for up to 30,000 years, and lends further weight to the idea that some Aboriginal myths pertaining to gigantic animals may be authentic records of extin
309.
by yuchi 9y ago
This article is a little bit flawed and a little click-bait-y also. CSS-in-JS is more or less enforced-CSS-modules + some sugar + a different way to author your styles. Most of the arguments there are against CSS modules, or “isolated style
310.
by yuchi 9y ago
Honest question: why so long then?
311.
by yuchi 9y ago
I do it instinctively since I was 5 so it's hard to explain it. If you can use a big monitor it would be easier. Place very near the screen, enough to trick your left eye to see the left small eye icon, and the right eye the right icon
312.
by yuchi 9y ago
That version dropdown in the navbar will change my life: I give lessons for a framework which in the previous version still used v2.3.2, now I’m sure my students will not look at the wrong documentation.
313.
by yuchi 9y ago
Hi Paul, thank you for your response here, could you please update the article with some references to the new options available? Would be great if included info for all platforms, not only npm/yarn :)
314.
by yuchi 9y ago
Sorry but it’s just using the standard contenteditable attribute, which works terribly, see https://medium.engineering/why-contenteditable-is-terrible-1...
315.
by yuchi 9y ago
You would have no errors except when dependencies expect to be “the only one”, in “peer dependency” style.
316.
by yuchi 9y ago
That’s how semver ranges work, in fact saying `^1.3.12` means “I tested for v1.3.12 and I want all non-breaking updates that come afterwards”.
317.
by yuchi 9y ago
The “right way” to do that is to publish alpha versions of your code. Snapshotting the state of the tree into a mutable release is calling for problems. Semver also defines a (poorly supported) M.m.b-release+tstamp pattern, so you can relea
318.
by yuchi 9y ago
Yes I read it and it calls it a fallacy . Which is not, it’s a trade off. We could argue about how many developers actually know the implications (which would be a great survey to do), but I believe having this trade off by default has bee
319.
by yuchi 9y ago
Very nice point. If you look at all npm examples in the article it shows the >= M.m.b pattern which is never found in the wild. You’ll find ~M.m.b for VERY old packages and ^M.m.b for modern ones (last 4 years). Those let the minor
320.
by yuchi 9y ago
That’s not right. Ranges are powerful and important, but you need a locking mechanism too otherwise you‘ll loose control. Npm and Yarn got finally right and dependency management in the npm ecosystem is now a breeze.
321.
by yuchi 9y ago
Please note: I can speak only for the Node.js npm/Yarn ecosystem. This article is terribly outdated. Version ranges are great and the only way to manage correctly your dependencies without having tons of duplicates. Also they are a sec
322.
by yuchi 9y ago
I expected to be downvoted («the burden») but before you do please keep in mind I’m honestly trying to understand if those issues were preventable by using a different language. Just a honest curious question.
323.
by yuchi 9y ago
I’m gonna take the burden (someone would do that eventually anyway) and ask: how many of those issues would have been completely prevented by using a safer language such as Rust? How many would have been mitigated? I’m not a system programm
324.
by yuchi 9y ago
Suggestion: cancel pending requests when another one is requested.
325.
by yuchi 9y ago
Some admin should add a [spoiler] flag to it. Fantastic read. It’s sad such great content has no right to stay on Wikipedia, where this article originated. (I’m not implying the rules of Wikipedia are wrong.)
326.
by yuchi 9y ago
Very interesting. Some docs would help in evaluating it.
327.
by yuchi 9y ago
Discipline: using, creating and sharing (among the team) checklists.
328.
by yuchi 9y ago
I second this very much. As pretty everyone says, it changes how you treat code and data. Surprisingly even when they are not the same thing :)
329.
by yuchi 9y ago
This happens at compile time. Not at runtime. This happens on the developer’s computer, not the user’s.
330.
by yuchi 10y ago
The example you found on the blog post was there to show how prettier handles conflicting cases. It will print them only in those cases.

More ›