idubrov

7 ms·

1.
by idubrov 4y ago
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 for, what receptacle are you going to use and what are you goi
2.
by idubrov 4y ago
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, hospital equipment, too?
3.
by idubrov 4y ago
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 circuits (you could wire receptacle just for this specific dryer
4.
by idubrov 4y ago
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, of course, a solved problem). 14-50R is not what I
5.
by idubrov 4y ago
(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 try install them everywhere. There are some safet
6.
by idubrov 5y ago
It's the configuration complexity clock! http://mikehadlow.blogspot.com/2012/05/configuration-complex...
7.
by idubrov 5y ago
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). I think, San Carlos / KSQL was the only one I found?
8.
by idubrov 6y ago
>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<str> 4. Arc<str>, for interned strings (thin
9.
by idubrov 6y ago
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 zero to ~500k codebase). Some of the arbitrar
10.
by idubrov 6y ago
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 based on series of heuristics and then user would manu
11.
by idubrov 7y ago
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 dynamic dispatch, and actually got it faster. Wasn't
12.
by idubrov 8y ago
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, long commute and job at a start-up sucks your soul reall
13.
by idubrov 8y ago
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. See https://play.rust-lang.org/?gis
14.
by idubrov 8y ago
FWIW, it is possible to make it a bit more ergonomic: pub struct SmartRef<'a> { container: &'a Container, widget: usize, } impl <'a> std::ops::Deref for SmartRef<'a> { type Targe
15.
by idubrov 8y ago
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, with a lifetime parameter).
16.
by idubrov 8y ago
>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 representations: 1. Typed Rust structs 2. Vector with indexes 3. Unt
17.
by idubrov 8y ago
>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 to make a choice than about tools that will help yo
18.
by idubrov 8y ago
#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 ~70k lines. I cannot even imagine what the refactoring
19.
by idubrov 8y ago
Any comments on how FoundationDB might be the same / different?
20.
by idubrov 8y ago
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.
21.
by idubrov 8y ago
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.
22.
by idubrov 8y ago
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 backpack until I finish it). The Lucifer Effect: Understanding
23.
by idubrov 9y ago
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 bits (well, contingent on SVD file quality), which is