djrenren

6 ms·

1.
by djrenren 7mo ago
If it’s a simple change, they might accept a PR. If it isn’t, well that’s your answer. Not worth allocating engineers for it.
2.
by djrenren 7mo ago
The typescript language server (along with the rest of the compiler) is being rewritten in go for Typescript 7. This work has been going on in parallel with the work on 6.0. The go port has most features of 6.0 already and you can follow it
3.
by djrenren 1y ago
All non-enterprise big tech uses of passkeys (Google, Apple & Microsoft Accounts), do not require an attestation statement (or in spec-parlance, use the `None` or `Self` Attestation Types). The presence of other attestation types in the
4.
by djrenren 1y ago
CBOR isn't a hobby spec. It's integral to the WebAuthn API spec. Every time someone uses a passkey, CBOR is used to exchange messages with the authenticator
5.
by djrenren 3y ago
This is a great approach for components that want to inherit all styling from their context. In cases where you want to introduce just a little styling, the CSS Parts API is really cool: https://developer.mozilla.org/en-US&#
6.
by djrenren 3y ago
Well, this is only sort of true. When you’re writing HTML you’re restricted to attributes but custom elements are JavaScript objects and are free to respond to property updates on the object. Relying solely on strings is a limitation of you
7.
by djrenren 3y ago
You can absolutely follow a discipline like this which recreates this separation in a framework that lacks it
8.
by djrenren 3y ago
Please remember that Web Components are much more akin to an ABI for web projects and not a full-featured framework. Any web component easily plugs into React, svelte, lit, etc. Existing components written in those frameworks can pretty eas
9.
by djrenren 3y ago
Web Components are really just the minimal APIs required to allow the implementation of new HTML elements. This includes things like: - Responding to being attached to the DOM - Encapsulating DOM nodes (the Shadow DOM) - Scoped styling (Sha
10.
by djrenren 3y ago
> They are not even in the same arena as React. This is 100% correct. I think a lot of the disappointment about web components comes from a mismatch in expectation between the spec writers and what people when they think "components
11.
by djrenren 3y ago
As someone who just had to answer this for my startup, the value of React is that it's robust and immensely hire-able. If you're looking for frontend developers, the one thing you can always expect is at least passable React knowl
12.
by djrenren 3y ago
> You don't need those in React either. I mean... sometimes you do, that's why they exist. But yeah, most of the time you don't. > Whatever you do in Web Components can probably (most likely) be done in React. Of course
13.
by djrenren 3y ago
Forgot to mention, the knock-on effect of this thought process is that if you want to adopt web components, you still need a templating approach. And you'll find that most of your code is templates, and only a few are really components
14.
by djrenren 3y ago
I've found webcomponents to be really good at encapsulating anything that doesn't directly query application state. Specifically there are two type of components that really thrive as web components (as opposed to react): 1. Highl
15.
by djrenren 3y ago
Really cool to see these issues are on the roadmap. I remain skeptical on timeline for these but if the plans speed up dev time work out, then this is great news.
16.
by djrenren 3y ago
After using Rocket in production for a year now. I'd really recommend Actix Web. Don't get me wrong, Rocket has some really nice features and good UI, but a couple things have proved to be real pain points: - Middleware ("fai
17.
by djrenren 4y ago
Dependencies in package.json are essentially just links to the npm CDN. (admittedly with a constraint solver in front that determines the exact link to use). `npm install` is equivalent to ` https://deno.land/manual@v1.31.1&#
18.
by djrenren 4y ago
One of the authors of FaCT here. This is a great question, because at first blush it feels like it might. movfuscator creates a branch-less program. But my guess is that we’ll run into two key problems: 1. Leakage via cache. If our memory a
19.
by djrenren 4y ago
Hey, one of the paper authors here, this has been a serious problem in the past (and present), but is definitely improving. For example, intel’s docs state that cmove is constant-time on recent hardware. ARM’s DIT (data-independent timing)
20.
by djrenren 4y ago
Hey, one of the paper authors here. If the compiler stopped here, yes this would be an error, but subsequent transformations (described in section 4.2) eliminate the branch ensuring that timing is equivalent regardless of the value of notRe
21.
by djrenren 5y ago
Hey just a heads up, on the web (or at least in CSS) px is resolution independent. It represents 1/96th of an inch [1]. The web has physical, font-relative, and viewport-relative lengths which all serve slightly different purposes. Lik
22.
by djrenren 6y ago
I dont think Rust traps on overflow in release builds
23.
by djrenren 6y ago
This seems like an odd choice... do you know the rationale? (or have a link to an issue/RFC I could go read)
24.
by djrenren 7y ago
Don't forget that if it works over http(s), it's a lot easier to build a web interface for, and that's a big win for ease of use!
25.
by djrenren 7y ago
Looks like the current code doesn't support it. https://github.com/wasmerio/python-ext-wasm/blob/master/src/... but in theory it shouldn't be too hard™
26.
by djrenren 8y ago
Hey one of the authors here! Crazy that someone else posted this, I'm happy to answer any questions. I also just gave a talk about this at POPL2019 in Lisbon. Slides are here: https://docs.google.com/presentation/
27.
Proposal for Custom Test Frameworks in Rust(blog.jrenner.net)
11 points by djrenren 8y ago|0 comments
28.
by djrenren 8y ago
I don't believe this would work with the rustc compiler because, although it uses Cargo to build, it has a special process that bootstraps the compiler by building itself.
29.
by djrenren 8y ago
Yeah, doc tests are part of rustdoc and they essentially strip out the comments and generate test functions using libtest. I'm not very familiar with the internals, but they're here: https://github.com/rust-lang&#x
30.
by djrenren 8y ago
You can do the same on rustc by just doing --keep-stage 0. This doesn't work with with codegen-like stuff but for a lot of changes it works.

More ›