Viewing profile — djrenren
djrenren
HN member- Joined
- Thu, Apr 09, 2015, 8:02 AM UTC
- HN karma
- 195
- Public activity
- 37 items
- HN profile
- View on Hacker News ↗
About djrenren
No profile information was provided.
Recent public activity
-
comment
Comment #47283088
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.
-
comment
Comment #47282959
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…
-
comment
Comment #44827468
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` Attestatio…
-
comment
Comment #44733536
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
-
comment
Comment #38439593
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…
-
comment
Comment #38439558
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 …
-
comment
Comment #38437371
You can absolutely follow a discipline like this which recreates this separation in a framework that lacks it
-
comment
Comment #38436960
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. Ex…
-
comment
Comment #38436713
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 - En…
-
comment
Comment #38436489
> 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…
-
comment
Comment #38435758
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 …
-
comment
Comment #38435358
> 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 (m…
-
comment
Comment #38435197
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 …
-
comment
Comment #38435091
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…
-
comment
Comment #38382442
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.
-
comment
Comment #38381051
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 prov…
-
comment
Comment #34997635
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 equiv…
-
comment
Comment #33310330
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 …
-
comment
Comment #33310150
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-t…
-
comment
Comment #33310121
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 ensurin…
-
comment
Comment #26638724
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 l…
-
comment
Comment #24575859
I dont think Rust traps on overflow in release builds
-
comment
Comment #22958570
This seems like an odd choice... do you know the rationale? (or have a link to an issue/RFC I could go read)
- comment
-
comment
Comment #19764332
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!