mmastrac

44 ms·

751.
Repairing an Apple Silicon Developer Transition Kit [video](youtube.com)
1 points by mmastrac 2y ago|0 comments
752.
by mmastrac 2y ago
In pop culture, there's a very common mixup between tracheotomy (the actual incision or cut made into the trachea) and tracheostomy (the overall procedure involving the creation of the hole, aka stoma).
753.
by mmastrac 2y ago
This is an impressive amount of public AI work coming out of Google. The competition we're seeing here is really pushing things forward.
754.
by mmastrac 2y ago
The NOAA forecast suggests it'll be nearly as powerful as the March 13th storm in '89 that took out the Quebec grid: https://www.swpc.noaa.gov/communities/aurora-dashboard-exper...
755.
by mmastrac 2y ago
I tried to understand from this page, but what is a Membership Card? Is there some context to this post? EDIT: aha, 14 years ago there's some context http://www.bramblyhill.com/post/2010/10/27/Member
756.
Homelab Cable Television Setup [video](youtube.com)
11 points by mmastrac 2y ago|1 comments
757.
by mmastrac 2y ago
Fun fact: countries are obligated to return the debris from objects launched into space that has returned to earth to the original country. "A State Party to the Treaty on whose registry an object launched into outer space is carried s
758.
by mmastrac 2y ago
Why did you omit this part? "at the authorization holder's request"
759.
by mmastrac 2y ago
I think we're talking about the same thing -- the original post in the thread used "no impl Drop" as "trivially destructable", not "no functional difference between drop and forgetting".
760.
by mmastrac 2y ago
A type that is not Copy may have associated memory allocations, however. You cannot simply forget a range of !Copy structs without the risk of memory leaks.
761.
by mmastrac 2y ago
Trivially copyable and destructible means that they are plain-old data, with no allocations, associated resources or any other side-effects.
762.
by mmastrac 2y ago
The size, the sockets, the heat distribution, etc, etc, etc.
763.
by mmastrac 2y ago
Ugh, finally. And it's not just a repurposed desktop memory standard either! The overall space requirements look to be similar to the BGA that you'd normally solder on (perhaps 2-3x as thick?). I'm sure they can reduce that o
764.
by mmastrac 2y ago
It sounds like the magnetic field is somehow interacting with the photon/nucleus/electron absorbtion/re-emission. The photons don't feel the magnetic field, but the combined system appears as if they do? It's like h
765.
by mmastrac 3y ago
Given this was published in 2010, and https://en.wikipedia.org/wiki/Word2vec was published in 2013, perhaps this was an early precursor? From the article linked from this blog post: "Enabling computers to underst
766.
by mmastrac 3y ago
I wrote https://github.com/mmastrac/keepcalm as a way to help with this, especially for writing webserver-like code. For most cases this type of code can take a small perf hit in exchange for drastically simplifying th
767.
by mmastrac 3y ago
It's not nonsense. It's really not difficult to structure code for 100% coverage of unsafe code if you're thinking about it from the start. You're also perfectly fine to write code that is free of `unsafe`, freeing you f
768.
by mmastrac 3y ago
I forgot about this. I actually had to ignore a test in Miri because of this exact issue. https://github.com/denoland/deno_core/blob/98b09fa4f77db1131... Anxiously waiting on https://github.com&#x2
769.
by mmastrac 3y ago
This is cool, but hitting break on the single timeout example in Firefox suggests that this code is actually filling the stack up pretty quickly, once per iteration through the loop. The concept is neat, though: it's basically handing
770.
by mmastrac 3y ago
It's my bare metal, so ... yes?
771.
by mmastrac 3y ago
This is trivially solved by putting code coverage and Miri into the same project, however.
772.
by mmastrac 3y ago
I'm not aware of any UB that can 1) be caused by unique pointer violations from Box and 2) are undetectable by Miri (assuming good code coverage), but I might be wrong about this.
773.
by mmastrac 3y ago
I strongly disagree with this article. Perhaps in the days before Miri it might have made sense, but it's pretty trivial right now to discover UB in unsafe code with a simple `cargo +nightly miri test` run. It feels like the Rust team
774.
by mmastrac 3y ago
Sure, why not?
775.
by mmastrac 3y ago
Apple doesn't even give you the option to program against the bare metal kernel and a GPU surface so that's a pretty unfair leading question.
776.
by mmastrac 3y ago
The EU doesn't seem to be a fan of their "maximally self beneficial letter of the law" approach to compliance. I'm impressed with what they've gotten out of Apple so far -- it's just a shame we don't have
777.
A blue mineral that grows on buried bodies and confuses archaeologists (2016)(atlasobscura.com)
121 points by mmastrac 3y ago|74 comments
778.
Recollections of Early Chip Development at Intel (2001) [pdf](deramp.com)
1 points by mmastrac 3y ago|0 comments
779.
by mmastrac 3y ago
These are pretty basic to advanced brain puzzles, but there's a few gems in there. Magnets is a lot of fun. Net, Signposts and Tracks are clever puzzles. There was one other one in there I used to enjoy but I can't recall which on
780.
by mmastrac 3y ago
If someone gets their hands on one and wants to build Deno with `cargo build --release`, I'd love to get myself release-optimized executables without waiting ten minutes for my M2 to fully compile and link the project..... Seriously. H

More ›