Wow, the UX kind of sucks. I just wanted to browse the devices - no way to do that, only option is an 'ai' search. Ok, I type in "Show All Devices" and it canoodles for about 30 seconds (great use of compute resources) only to apparently come up with the phrase "Browse all devices available in the directory without specific project-based filters." that it then seems to feed into the actual search tool... which then shows no results.
Two thoughts - (1) is your device list some state secret that you have to hide behind a search functionality? Because it would be nice to be able to browse through it without needing to engage in some sort of 'search'. (2) can you provide another option besides an ai search that is so intelligent that it has superseded the ability to do wildcard searches?
Edit: same feedback, but for the projects section as well.
- by default, we are displaying all the devices so you can just scroll through the list
- if you want to get all the devices for a specific use-case, you can setup filters
>> You think kids aren't running across the street at night out in the country? Chasing a soccer ball?
>Only in well light areas, usually with a low speed limit too.
Not something I've commonly seen when driving, but certainly as a kid out in the country I ran around in the dark near the road.
>> People, deer, fallen branches, large roadkill, garbage cans blown into the road by the wind, the list goes on and on.
>Of those only people are at all common, and not on large roads. I have never even seen roadkill large enough to be unsafe to drive over.
>I have only once come close to hitting any of these on country roads in the UK. I have been dangerously dazzled by oncoming bright headlights all the time.
I've seen all of these multiple times (tbf the trash cans were in the city, not the country) out in upstate NY and rural Indiana and Kentucky. Maybe trees don't drop branches over in the UK, but over in the US that is certainly a hazard to be expected during and after severe weather.
To be clear, I agree that excessively bright running lights and people who can't seem to properly transition between hibeams and lowbeams are problem. I just don't agree with the sentiment from the gp that "[o]ut in the country, you still don't really need brighter headlights."
I've lived in Montana for 25 years, a place where there are deer (and moose and bears) rampaging all over the place. People hit them all the time. But the only place I ever hit a deer with my car was North Yorkshire.
> If someone is interested in draw over a period, e.g. over one hour, you'd say it used 5Wh in that period.
Wh per hr? Let's just cut through the confusion and say it draws (J/s)Hr / Hr. :P
More seriously, if you are interested in energy the "correct" SI unit is J although in electrical applications [k/Mega/Giga]Whr is common. If you are interested in energy draw over a period, aka power, the "correct" and common unit is W. While 5 Wh per hour might seem simpler, it is equivalent to say this thing draws as much energy per hour as a device that that draws 5W would draw over one hour - needlessly redundant.
In the offgrid world we look constantly at batteries and they often express themselves in Wh. So it is a habit to measure anything else that way to avoid confusions.
If you aren't fussed about galvanic isolation there are many SMPS topologies that don't use transformers. Cheapest step down converter would be a simple buck regulator - no transformer needed!
This actually is useful, because it allows the symbols to visual indicators when reading currency figures and can be used in a programmatic way. $ becomes a start marker for the beginning of a currency figure where the most significant digit is immediately after the marker and anything remaining after flows from that, and the same is true for cents where the symbol acts as an end marker and infers a lower bound. They can almost be thought of as start and end markers in regex, although they are not used together so not exactly that way.
It makes a sort of rational sense, at least to me.
The rationale I've always heard for having the $ at the beginning of the number was so that a handwritten value on, say, a check couldn't be modified by sticking a number at the beginning. 1.00$ could be forged into 91.00$, but not so with $1.00.
A great many people when they see a open straight road with little obstacles or pedestrians will go 45-50 MPH. A great many people when they see a 15 MPH sign will go 20 MPH. Pair that low speed limit with a "fast" road and you will end with many people going 45 MPH and many people going 20 MPH. This variance in speed, with some people going much slower than others can be more dangerous than if most went the same speed - e.g. if the limit were 45 MPH.
You are correct that people driving too fast make the road dangerous, but so does people driving too slow. Generally, from a safety point of view, you want the slowest speed at which almost everyone will actually drive at, as large variance in speed between drivers is dangerous. I think this is what the parent post was getting at: a speed limit too fast OR too slow will increase the number of accidents, keeping in mind that there will always be at least some drivers speeding.
> You are correct that people driving too fast make the road dangerous, but so does people driving too slow.
It's accurate to say that people driving too fast are extra dangerous when there are slower vehicles in the road. The danger is still caused by the people driving too fast, not by those driving slowly, though. Speed kills.
Two thoughts - (1) is your device list some state secret that you have to hide behind a search functionality? Because it would be nice to be able to browse through it without needing to engage in some sort of 'search'. (2) can you provide another option besides an ai search that is so intelligent that it has superseded the ability to do wildcard searches?
Edit: same feedback, but for the projects section as well.
reply