Viewing profile — idubrov

Wiring 240V is (typically) not an issue, as it is standard (in the US) to get 240V from the transformer to the house. The devil is in the details: what current would you wire it fo…

Yeah, it shows that I have zero knowledge about commercial appliances. I guess, I wouldn't be surprised if they routinely use 20A plugs / receptacles. Would make sense. Maybe, hosp…

The problem with 240V is that there are few NEMA standards used is USA (although , they look bulky and are kind of unsafe around the kids. Which is not a problem for dedicated circ…

Right, there are code compliant solutions. I was just musing over an idea of having 240V "everywhere" (including inside the house in every room, having 240V for special needs is, o…

(everything below assumes US and NEC / local electrical codes) I don't think code prohibits it, but in my (not very educated) opinion, you might get into some gray territory if you…

It's the configuration complexity clock! http://mikehadlow.blogspot.com/2012/05/configuration-complex...

Interesting. When I was doing my research on ULPower engines (which can burn 100LL, but they would prefer non-leaded), there were very few airports who offered unleaded fuel (UL94)…

>A common way to solve that problem is usually to use references instead of cloning. Right. I think, we ended up with having everything from the list: 1. String 2. &str 3. Cow 4. A…

I have some extensive (self-assesment :) ) experience building this kind of application, and my answer would be "no, but maybe" (I was one of the first engineers & architect on our…

At my previous job I've built a tool that was capable of doing that (we were merging XMLs with form definitions). The main idea was an interactive mode. Initially, tool would merge…

Well, I have this anecdote. We switched from serde to our own serialization / deserialization scheme (it still uses serde, but only for the JSON part), which is heavily based on dy…

I have a small shop. 8x12 lathe, X2 mini-mill, some amount of woodworking equipment (table saw, track saw, etc). Haven't done anything in the last year or two, though. Turns out, l…

Yes, the idea is that you only create them temporarily. Mutability is also possible to some extent with these "smart" pointers. It gets a bit trickier and less ergonomic, though. S…

FWIW, it is possible to make it a bit more ergonomic: pub struct SmartRef { container: &'a Container, widget: usize, } impl std::ops::Deref for SmartRef { type Target = Widget; // …

Cloning is not always possible (performance reasons, non-cloneable data, etc) and would not necessarily remove lifetime (for example, it could be a struct, defined somewhere else, …

>Could you explain? I might need a concrete example. You might want different trade-offs in different places. Like, in our case, the conflict is between three different representat…

>Would that satisfy your need? It's not always possible to change the data structure -- different ways of modeling data have different trade-offs. So, for me it is about not having…

#4 highly depends on a project size. On big projects, some of these decisions might become effectively one way doors. I've been struggling a bit with these issues on the project of…

Any comments on how FoundationDB might be the same / different?

They are in the same category as mobile apps in that respect, no? Both of them are "public clients" in terms of OAuth 2.0.

I wonder if the same recommendation (use Authorization Code Grant flow plus PKCE instead of Implicit Grant) should be made for SPA (single page applications), too.

1. Digital Design and Computer Architecture: ARM Edition 2. The Evolution of Cooperation: Revised Edition 3. The Ego Tunnel: The Science of the Mind and the Myth of the Self (in ba…

I don't see anything controversial here. First, you can always use unsafe and access low level registers ignoring all the synchronization. You are still getting typed access to the…