dochtman

33 ms·

331.
by dochtman 7y ago
Seems to me that one-stop shop is very different from one-stop tool. GitLab is aiming for the latter, whereas Atlassian (at least when I was using those tools) seems much less integrated. Jira may be the most comprehensive issue tracker (wh
332.
AMD releases Optimizing C/C++ Compiler (based on LLVM/clang)(developer.amd.com)
4 points by dochtman 7y ago|0 comments
333.
by dochtman 7y ago
In my experience the built-in tracking protection (now enabled by default) does a pretty good job.
334.
by dochtman 7y ago
That's a pretty unintuitive use, since "sigil" is more commonly used (in programming languages) as a single symbol , as in a non-alphanumeric character that's used as some kind of syntax. https://en.wikipedia
335.
Google Discloses Security Bug in Bluetooth Titan Security Keys(techcrunch.com)
2 points by dochtman 7y ago|0 comments
336.
by dochtman 7y ago
Don't they get encrypted on iOS? The last few times I tried to extract stuff from my Android phones, it turned out the SQLite databases were encrypted (AES-something IIRC) and getting them decrypted was a pain in the ass (trying to cob
337.
by dochtman 7y ago
It's unfortunate that the official Docker images haven't been updated yet (on DockerHub).
338.
by dochtman 7y ago
Good throughput with GC seems to come with significant extra memory use: "We compare explicit memory management to both copying and non-copying garbage collectors across a range of benchmarks using the oracular memory manager, and pres
339.
by dochtman 8y ago
I got the Tom Bihn Smart Alec after reading this: http://randsinrepose.com/archives/a-bag-of-holding/ Would always recommend diving into Wirecutter articles to figure out what's best for your specific needs.
340.
by dochtman 8y ago
It's interesting that this seems to mirror our experience with Cloudflare's Rust implementation of QUIC: https://news.ycombinator.com/item?id=19019150
341.
by dochtman 8y ago
The important part of QUIC is that lost packets will not block delivery of all other data being delivered over the same connection, but only the data from any affected streams (for example, a single HTTP request/response will usually b
342.
by dochtman 8y ago
QUIC is developed by an IETF working group where anyone can participate, and there are definitely some productive participants who don't work for Google (or any of the other big companies).
343.
by dochtman 8y ago
If your client or server has support for key log files, Wireshark can deal with TLS quite well. In fact, this is usually how I debug my QUIC implementation.
344.
by dochtman 8y ago
Discussion here: https://www.reddit.com/r/rust/comments/amat47/cargos_next_fe... https://internals.rust-lang.org/t/cargos-next-few-years/9321...
345.
by dochtman 8y ago
Thank you for openly discussing this. Ralith has mostly responded in terms of the API our quinn-proto offers; it seems like you and/or ghedo may have missed that? I just also wanted to respond to this: > nor would they likely be abl
346.
by dochtman 8y ago
Definitely not! I'm merely stating that there would be advantages from pooling efforts, and that I haven't seen a compelling reason not to do so.
347.
by dochtman 8y ago
I still don't quite understand why Cloudflare is going their own way rather than joining our Rust implementation ( https://github.com/djc/quinn ). So far the primary maintainer told me "I quite like how quiche
348.
by dochtman 8y ago
The original version of QUIC was contributed to the IETF by Google, but at this point many people from outside of Google have contributed. Saying it is Google-developed is inaccurate at best if you're talking about recent drafts of the
349.
by dochtman 8y ago
ninn is a fork of a much older, much less functional version of Quinn. I have a plan for making the security protocol fully pluggable in Quinn, so that we can easily support things like Noise.
350.
by dochtman 8y ago
I really like the new GitHub dashboard (have been using it for a while now), but the thing that's really annoying me is how on mobile browsers it has much less comment (missing the activity feed). Then, when you go to the desktop versi
351.
by dochtman 8y ago
I understand what you're saying, but I'm not sure I fully agree. If you quit a position where you get paid full time to work on Rust because of reasons having to do with your working relationship, maybe MoCo doesn't control t
352.
Microsoft patents a magnetic USB-C port(neowin.net)
2 points by dochtman 8y ago|0 comments
353.
by dochtman 8y ago
Firefox bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1226042
354.
by dochtman 8y ago
Some experiments with Noise as the QUIC encryption mechanism have recently been published: https://dl.acm.org/citation.cfm?id=3284854 Pluggable encryption has been scoped out of QUIC v1, but will likely make a return soon a
355.
How to Become a Rust Super-Developer(hashnode.com)
3 points by dochtman 8y ago|0 comments
356.
by dochtman 8y ago
I think it works on stable these days.
357.
by dochtman 8y ago
If I were writing a small blog today, I would probably still go with Rust, just for the robustness. Catching bugs at compile time is so much nicer no matter how good your unit test coverage is (and especially when coverage is not great). Pe
358.
by dochtman 8y ago
In that case, the HTTP part would probably just be working against you. Fortunately, people are working on DNS over QUIC: https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic...
359.
by dochtman 8y ago
Cloudflare is also already testing draft QUIC support.
360.
by dochtman 8y ago
I wrote a little script a few years ago to make a nice map out of my location history: https://dirkjan.ochtman.nl/writing/2012/11/28/tracing-a-path...

More ›