yoklov

10 ms·

61.
by yoklov 8y ago
For firefox sync on chrome: It’s completely possible, but the crypto is enough of a pain in the ass to deter most people. (It’s also going to be very difficult to implement a robust sync system this way, integration with the underlying stor
62.
by yoklov 8y ago
Sure, and we do warn during password reset. I’m unsure of what alternative there is that avoids that risk while still providing the current privacy benefits.
63.
by yoklov 8y ago
.... Yes >_> https://github.com/mozilla/application-services
64.
by yoklov 8y ago
Firefox Sync actually allows this! https://github.com/mozilla-services/syncserver This still uses FxA for authentication. You can self-host that up as well, but it's not nearly as straightforward, and I'm n
65.
by yoklov 8y ago
Yes, for the most part. For passwords the story is a bit more complex (they're encrypted locally on all platforms, either with your master password (Desktop, probably Android but I don't remember), or a random key stored in the OS
66.
by yoklov 8y ago
There's no risk to your data. It's not like this will delete your local data, the only risk is when doing a password reset in some (fairly rare) cases, which does attempt to make the risk of doing so clear. I don't disagree a
67.
by yoklov 8y ago
This is not true. I work on Firefox Sync full time, as do multiple other engineers. Admittedly, the current version in Desktop/iOS/Android is in a sort of 'maintenance mode' (we still fix bugs, but don't work on new
68.
by yoklov 8y ago
Yes, sort of (more about the process: https://github.com/mozilla/fxa-auth-server/wiki/onepw-protoc... ). Key difference: you don't need to sync all the data up again, since there's a separate key for
69.
by yoklov 8y ago
That sounds like it could be mechanically cool. Or at least lead to a cool setting.
70.
by yoklov 8y ago
Rust's `Clone` trait is deep by default, except for - Types with shared semantics (e.g. Rc<T>, Arc<T>), or holding onto these internally - Types holding borrowed references (these will still reference the same data). C++&#x
71.
by yoklov 8y ago
While I agree that it's not really a measure of C standing the test of time, I kind of doubt that an alternate universe where 'C interop' / 'ASCII compatibility' weren't a design consideration, we'd h
72.
by yoklov 8y ago
Worth noting that rust is hit by the additional branches worse than C++ due to the lack of move ctors/move assignment operators. No way to safely store an interior pointer to the buffer as a result. That said, as mentioned the other fe
73.
by yoklov 8y ago
Honestly its not impractical if you just replace your coffee with it. I probably average over 6 cups per day, and don’t really do it out of any health concern at all.
74.
by yoklov 8y ago
Honestly that doesn't look that bad. SQL is a lot weirder in many ways, and I say that as someone who has written a lot of SQL.
75.
by yoklov 8y ago
Reification seems pretty unrelated, as Wasm doesn't have an equivalent concept.
76.
by yoklov 8y ago
I prefer them because they make grepping for SQL code easier. Also syntax coloring inside strings is not common.
77.
by yoklov 8y ago
IIRC https://cyclone.thelanguage.org/ did this (among other things -- I think it's also where Rust lifetimes began their, err, life) and ended up having rather poor performance for pointer-manipulation heavy code. I do
78.
by yoklov 8y ago
> there's also low-latency or real-time implementations of RC/GC to consider as well These exist but tend to have poor throughput, frequently set a maximum amount of memory you're allowed to use, and typically don't p
79.
by yoklov 8y ago
Firefox has a few million lines of JS code and the coding standard prefers `==` to `===`. I don't think it's linted for though.
80.
by yoklov 8y ago
Special relativity says it's not possible. General relativity says that maybe you can get something equivalent by taking non-linear paths through space-time but those sorts of things require very radical types of matter to avoid collap
81.
by yoklov 8y ago
I don't think most ad-revenue driven companies claim that these things are done locally, which seems key.
82.
by yoklov 8y ago
This probably needs a rename, "SQLite: View Ticket" is not a terribly descriptive title. That said, it's a little surprising to see a bug of this type in SQLite which generally has such solid test coverage... Oh well, nothing
83.
by yoklov 8y ago
I haven't used Julia in quite a while, but given its focus on numerical computation it would be fairly surprising to me if it didn't have the ability to meet your precision needs.
84.
by yoklov 8y ago
Implementing unordered map/set that way looses iterator/pointer stability, which is guaranteed by the current impl, unfortunately
85.
by yoklov 8y ago
IIRC boost::unordered_map/set offered those, and I'm pretty sure the API was taken more or less verbatim from that. I suspect some desire of compatibility was to blame, but don't know. Hopefully in the future mistakes of thes
86.
by yoklov 8y ago
> I sleep very well at night knowing my software is not keeping helicopters in the air, cars on the road, etc. Hopefully at least, but you never know where those random shell scripts you put in a gist (or whatever) might end up.
87.
by yoklov 8y ago
The theory I heard that seems more likely than a rogue lawyer, is that it accidentally got left in from the license of a pre-release test version -- I can understand why they'd want to prevent benchmarks of unreleased software (not tha
88.
by yoklov 8y ago
These are great, thanks, I hadn't seen them before.
89.
by yoklov 8y ago
Eh, it’s extremely difficult to write a physics engine that behaves predictably with variable timesteps. Likely impossible at the extremes.
90.
by yoklov 8y ago
I have no real opinion on the tech stack (beyond being glad that it works for you), but this is very cool, and is something I've looked for in the past, unsuccessfully.

More ›