estebank

38 ms·

481.
by estebank 2y ago
Congratulations on reinventing sixels. :)
482.
by estebank 2y ago
Telegram started 11 years ago. I know the term has been diluted for ages, but it still rubs me the wrong way to use the word startup for decade old businesses.
483.
by estebank 2y ago
We have said that already: https://www.icrc.org/en/document/weapons
484.
by estebank 2y ago
If you don't mind the presentation style, https://www.youtube.com/watch?v=XusyNT_k-1c is great presents an even direr situation: because water rights are "use it or lose it", we are actively encouraging wat
485.
by estebank 2y ago
You need to compare not against what you currently have, but rather what you'd have if there was political will and budgets comparable to what was spent on the existing car infrastructure. Otherwise is saying that no-one wants a bridge
486.
by estebank 2y ago
> German police authorities are authorised to stop vehicles throughout the territory of Germany at any time, although the police have the general authority to scrutinise a vehicle only in order to inspect the technical condition of the v
487.
by estebank 2y ago
There's a "trick" that works somewhat well for some compound emoji like "family": replace ZWJs with whitespace. Emoji width is not standardized because it depends on platform, fonts available, shell and terminal emu
488.
by estebank 2y ago
Anyone complaining about British food has never eaten Dutch "cuisine". After having lived in both countries I'll always defend the Brits when it comes to food.
489.
by estebank 2y ago
> I'm not aware of camera manufacturers publishing details on the wavelengths their sensors respond best to It is relatively easy to experimentally find this out https://nikongear.net/revival/index.php?topic=106
490.
by estebank 2y ago
Picture a company with its own on-prem bare metal servers. Over the years they have had space to expand but projections show that soon either a new data center will be needed, either in addition or to move to. Doing so would require a huge
491.
by estebank 2y ago
> Indexing into an array adds bounds checks which takes non-zero time. * When done in such a way that the compiler cannot know the access is in-bounds. The same code in C would also need to perform bounds checks on access. If you do the
492.
by estebank 2y ago
I don't have the time to check in detail what's going on, but given that rustc didn't have a platform tool chain for M1 Macs then, I would assume that winit didn't support it correctly back then either. I pulled the repo
493.
by estebank 2y ago
There's of course also cargo semver, but I don't think it would have helped here.
494.
by estebank 2y ago
To expand on some of the things already said: This issue was caught during a crater run. An earlier version of time had (accidentally) an "identity" conversion (<T as Into>::into(T)), which was caught by a blanket trait impl
495.
by estebank 2y ago
I think the closest to what you're asking for is to build with a contemporary rustc version (have a rust-toolchain.toml in your repo). This isn't a satisfactory answer, but it is an available option nonetheless.
496.
by estebank 2y ago
> That documented use of safe Rust can easily lead to UB The only thing that comes to mind that this could be referring to are the open bugs at https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Ais...
497.
by estebank 2y ago
I would add that the paperwork is easier in countries other than the US, but the cultural aspects of immigration are hard everywhere. Small things like the food, the sense of humor, the cultural expectations, having friends and family far a
498.
by estebank 2y ago
The issue I have with Default is that the verbosity jump from derive(Default) to impl Default for Type is high, evej if you just want to specify a single field. The other reason I want this is because it makes defining builders almost trivi
499.
by estebank 2y ago
Last time I had this conversation[1] the main sticking point were around semantics of private fields, but I am convinced that the maximally restrictive version can be done (only pub fields can be optional) and maybe relaxed later after we g
500.
by estebank 2y ago
Adding support for struct default field values would allow for - leaving some mandatory fields - reduce the need for the builder pattern - enable the above to be written as f(S { hours: 2, seconds: 53, .. }) If that feature ever lands, coup
501.
by estebank 2y ago
Funnily enough, because the borrow checker is so strict I feel more confident writing complex borrowing logic that I wouldn't dare attempting in C or C++ because even if I were to get everything right (a big if), there's no assura
502.
by estebank 2y ago
The information density of the "human syntax" Rust syntax both remain linear in size, but with a significant different N. function max with a lifetime a, a lifetime b, and type parameter T wit
503.
by estebank 2y ago
For what is worth, the turbo fish falls from the decision to use <> for generics (for familiarity for C++ and Java developers) and a desire to make the syntax non-ambiguous (side stepping the C++ problem of having to delay determinin
504.
by estebank 2y ago
function max with type parameter T with arguments a of type T and b of type T and returns a value of type T where T implements trait PartialEq Vs fn max<T>(a: T, b: T) -> T where T: PartialEq
505.
by estebank 2y ago
Unicode is that better encoding. The "small and efficient per locale encoding" that you proposed was the status quo, and was an endless source of mojibake. There is a reason we moved away from that.
506.
by estebank 2y ago
And people in other locales want to be able to use their own name without software mangling it.
507.
by estebank 2y ago
A DSLR has the added benefit of not needing a screen to be on for it to work (this is why they still have better battery life than mirror less as well). Then again, SLRs have even better battery life (it's only used for the light meter
508.
by estebank 2y ago
The niche between those two market segments is currently catered to by the used market of older pro gear.
509.
by estebank 2y ago
> For the FAM, your example looks like it requires a compile-time constant size. That's the same as hardcoding an array size in the struct, defeating the whole point. Short names will waste space, and long ones will get truncated. Y
510.
by estebank 2y ago
> it would be more difficult to make raw syscalls in Rust Would you like to expand on this? Is it because of type conversions that you'd have to do? > I use[1] flexible array members to minimize allocations I was under the impres

More ›