ishitatsuyuki
Joined 10 years ago
Karma
512
Submissions
83
Member since
Dec 16
Recent submissions
Comment · 2 years ago
Comment · 2 years ago
macOS has native password autofill which opens the Keychain experience to 3rd party password managers. Unfortunately browser support is limited to Safari (even though the API itself is open), while Strongbox [1] seems to be the only option on password manager side.
Maybe this will improve with the adoption of passkeys, where browsers are actually trying to integrate with the system passkeys API (a neighbor to autofill).
[1]: https://strongboxsafe.com/updates/macos-big-sur-autofill/
Comment · 3 years ago
Unfortunately, removal of PIIs also means less data/cues for hard-to-diagnose bugs (it can even range to CPU bugs like [1]). For Firefox, potentially PII-containing memory dumps are still sent to the server, but they're only viewable by authorized personnel [2].
There are also rule-based PII removal methods as used by Sentry minidump processing and described at [3].
[1]: https://news.ycombinator.com/item?id=37063459
[2]: https://crash-stats.mozilla.org/documentation/protected_data...
[3]: https://docs.sentry.io/product/data-management-settings/scru...
Comment · 3 years ago
IMHO, perf's decision to write whole stacks directly to the disk and unwinding them as a post-process is a really bad design. It wastes disk space, and as the author pointed out, it also has a lot of IO overhead.
As an alternative approach, https://github.com/mstange/samply processes data streamed from perf and unwinds it in realtime. The unwinding overhead is surprisingly low: it only takes around 1% of (single) CPU per CPU profiled. Solving the disk waste alone has been a tremendous improvement of profiling experience. As a bonus, the unwinding and symbolization works reliably while I frequently had postprocessing not terminating when using the perf CLI directly.
Comment · 4 years ago
It is… not? It simply invokes the unwinder / exception handler, like _Unwind_RaiseException. For normal exceptions, no signals are involved. You can get an idea of what is executed at http://stffrdhrn.github.io/software/toolchain/openrisc/2020/....
Comment · 4 years ago
Serif mentioned on Twitter that the decision is partly driven by the absence of upgrading pricing options in third party app stores.
https://twitter.com/affinitybyserif/status/15903262690314649...
Comment · 4 years ago
Rellic [1] implements an algorithm that generates goto-free control flows (citation in README), which would be a significant improvement against what Ghidra/IDA generates currently.
Unfortunately it looks like the maintenance state of the pieces around Rellic isn't very good, and it's quite rocket science to get it building. It doesn't have as much UI/GUI as Ghidra either so it's a bit far from accessible right now.
Comment · 4 years ago
> poor support for style libraries like tailwind
Can't relate. Tailwind works fine with anything that supports PostCSS. I run it with Vite and there's zero issues.
> the state management ecosystem is fractured between vuex and pinia
This is also just not true. Pinia is officially replacing Vuex as the recommended store library for Vue [1]. They're also vastly similar in how they do things, so the knowledge transfer over from Vuex to Pinia. And Pinia just address most of the design goals mentioned in the article in the most simple way.
As for Vue 2 -> 3 transition, lots of the larger UI frameworks in the ecosystem is struggling to migrate, despite lots of efforts on the compat layer to smooth the transition, which is a bummer. But as long as you're not doing those sophisticated things, Vue 2 examples should work out-of-box on Vue 3 as well. There are surely less resources for the composition API, but the official introduction guide has been good enough in my experience.
Comment · 4 years ago
This should be (2013).
Comment · 4 years ago
Carbon is absolutely amazing. They are using a very flat style in pursuit of a modern corporate brand, just like a lot of other tech companies today, but the design also incorporates a lot of traditional and familiar elements. It’s a rare instance of flat UI that does not feel mobile oriented and half assed on desktop.
Carbon components are also the most accessible component set I have seen, and they go through great lengths doing automated and manual accessibility testing.
The library though, is a bit lackluster. It’s tailored for IBM’s internal need, and is still a bit far from a complete framework. So you need to be prepared to write some CSS as well as designing your own components when you need one.
Comment · 4 years ago
Funny that the subgrid example actually has a screenshot from a browser that doesn't support subgrid: https://github.com/GoogleChrome/web.dev/issues/7453
Well, that does say something about the dominance of Chrome...
Comment · 4 years ago
Author here. Your understanding is right, and I meant that old congestion control algorithms was only using the information of packet losses.
Comment · 4 years ago
Input lag has nothing to do with network ping.
Input lag is the time between you perform the action and the computer shows that on screen. It depends on your frame rate, refresh rate, and peripheral polling rate, as well as how good the game schedules things (which is what LatencyFleX tries to optimize).
Network ping on the other hand is often hidden away. Whether you are on 2ms ping or 100ms ping, the bullet always goes where you aim at: this is done through rollback netcode [1], which rewinds the server state to the time the action has been performed. I'm not saying that having low ping is pointless, it has an effect on things like peeker's advantage, but the effect of network ping is drastically different from the effect of input lag.
[1]: https://cloud.google.com/storage/pricing-announce#network