Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chriskrycho
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
chriskrycho
4y ago
I think one of the possibly-good moves Zig makes, similarly, is using `comptime` for generic types. I don’t have a good sense of how that interacts with parametricity and ability to constrain those (and I suspect that’s an important quest
92.
▲
by
chriskrycho
4y ago
That’s a good goal! A 100% correct program which cannot guarantee a lack of memory safety bugs is not a 100% correct program, though, right?
93.
▲
A new protocol (IndieWeb adjacent): “Spring '83”
(robinsloan.com)
5 points
by
chriskrycho
4y ago
|
0 comments
94.
▲
The Specificity Gradient
(doriantaylor.com)
12 points
by
chriskrycho
4y ago
|
2 comments
95.
▲
The Specificity Gradient
(doriantaylor.com)
1 points
by
chriskrycho
4y ago
|
0 comments
96.
▲
by
chriskrycho
4y ago
Besides the (correct!) sibling comment: the idea here is to provide underlying primitives which can then be used to express UI in a variety of contexts, first of all native UIs but (as the post notes at the end) also including the DOM. Fo
97.
▲
by
chriskrycho
4y ago
Poor animation design has exactly the problem you describe. Animation in general is a very useful affordance, though: it allows you to convey the relationships between the various nodes and modes in your UI. That ranges from being able to d
98.
▲
by
chriskrycho
4y ago
CSS transitions are fairly restricted, but animation in CSS is substantially more capable than transitions if you’re using the animations API instead: https://developer.mozilla.org/en-US/docs/Web/CSS/CS
99.
▲
by
chriskrycho
4y ago
Thanks for the clarification!
100.
▲
by
chriskrycho
4y ago
> it’s just unnecessary mutation Yes! The article says as much in both the introduction and the caveats at the end! The only reason to reach for this is: cases where for some reason you cannot change the existing API. As for the `ext
101.
▲
Misusing TypeScript assertion functions for fun and profit
(v5.chriskrycho.com)
38 points
by
chriskrycho
4y ago
|
6 comments
102.
▲
by
chriskrycho
4y ago
I’ve used TypeScript’s handling extensively as well as Rust’s, and I would say that there are actually significant tradeoffs, rather than it being an easy win for either. In particular, the fact that `| null | undefined` is just another uni
103.
▲
by
chriskrycho
4y ago
I do this for a bunch of pages for the same reason—series pages, for example, but also tag pages. I like how it subtly undercuts the recency bias of the reverse chronological “stream” that is the default.
104.
▲
Misusing TypeScript assertion functions for fun and profit
(v5.chriskrycho.com)
1 points
by
chriskrycho
4y ago
|
0 comments
105.
▲
Four Eras of JavaScript Frameworks
(pzuraq.com)
3 points
by
chriskrycho
4y ago
|
0 comments
106.
▲
by
chriskrycho
4y ago
In principle, yes, absolutely! You can cover the 90% case with simple rules of thumb, and so just following the top-level recommendations from the spec do indeed cover a lot of it: have tests which cover your type API fully (not just your
107.
▲
SemVer for TS in Practice – real world example of avoiding breaking changes
(v5.chriskrycho.com)
14 points
by
chriskrycho
4y ago
|
2 comments
108.
▲
Ember.js' Road to TypeScript
(youtube.com)
4 points
by
chriskrycho
4y ago
|
0 comments
109.
▲
SemVer for TypeScript Types (v1.0.0-beta.1)
(semver-ts.org)
4 points
by
chriskrycho
5y ago
|
0 comments
110.
▲
Small, Non-Trivial Projects: where you can try things and those things matter
(v5.chriskrycho.com)
2 points
by
chriskrycho
5y ago
|
0 comments
111.
▲
by
chriskrycho
5y ago
Those are some very large qualifications, though, right? I think a better way of saying this is something like “you actually have to work quite hard to write native code that outperforms an equivalent Java/Kotlin/Scala implement
112.
▲
by
chriskrycho
5y ago
This is a key insight. One of the things which has most endeared Dorico to me is that it’s the only program in the space which even seems to have had the right approach for this to be possible. They’ve taken the view, from the very outset,
113.
▲
by
chriskrycho
5y ago
You might try Obsidian. I think it checks all of those boxes except “web view”: it’s an Electron app, but like VS Code it shows that web tech doesn’t have to be slow (it just nearly always is). They just shipped the native client and it
114.
▲
by
chriskrycho
5y ago
Ah, no, sorry: I took your meaning; I was just talking on a related bunch of things your comment brought to mind! That’s a very interesting approach, though: doing it via script rather than hand-editing in a DAW.
115.
▲
by
chriskrycho
5y ago
Yep, and it totally gets the job done. (Hey, Steve!) I’m just perpetually surprised that 6 years past 1.0 we don’t have a Rust native implementation of the equivalent. What I’ve slowly concluded is: we as an industry more broadly just don’
116.
▲
by
chriskrycho
5y ago
Honestly it’s astounding just how good the representations from top notch virtual instrument libraries can be given the very real limitations of MIDI. The combination of key-switched articulations with velocity-driven patch variation plus c
117.
▲
by
chriskrycho
5y ago
The worst part about it is: same schema/ontology, but different (legitimate!) choices within it ! Cue sobbing emoji.
118.
▲
by
chriskrycho
5y ago
MusicXML is indeed widely used, and it is basically the standard interchange format for music notation apps. Every major app I can think of supports it—certainly the “big four” of Dorico, Sibelius, Finale, and MuseScore, as well as other
119.
▲
Keep It Local, or: (part of) what “reasoning about your code” means
(v5.chriskrycho.com)
3 points
by
chriskrycho
6y ago
|
0 comments
120.
▲
RFC: Semantic Versioning for TypeScript Types (For Ember.js and Anyone Else)
(github.com)
2 points
by
chriskrycho
6y ago
|
0 comments
More ›