That's a situation where the person in charge decided they were just not going to do their job and give orders, while everyone else thought it was OK to sit around and wait for orders.
1,700 karma · joined January 9, 2021
That's a situation where the person in charge decided they were just not going to do their job and give orders, while everyone else thought it was OK to sit around and wait for orders.
I've never been told cash, but if I was, I would be happy to pay in cash.
Jetbrains solved this is in an even better and consumer-friendly way:
- You buy the software on a recurring subscription and always get the latest version
- If you stop your subscription, you can continue using a year-old version of the software forever
This aligns everyone's incentives! Jetbrains is incentivized to invest in R&D, because they don't want customers to decide the older version is fine and not continue their subscription. The customers know that regardless of what happens, they will always have access to the software they need.
you got it completely backwards, unless you have a very fancy and expensive ECM motor.
Increasing resistance decreases power draw, as the fan needs to do less work. You can test this by hooking up a vaccum cleaner to a killawatt and blocking the intake.
There may be concerns about cooling the motor, but it really doesn't take that much air movement to dissipate heat.
I'll continue to follow up here, but it seems like an actual human has read the message this time.
Of course, their config is the best according to the benchmark (and ohmyzsh is the slowest option), but DIY configs are also covered, particularly possible performance optimizations.
> Gaming was associated with poorer self-reported hearing. Use of hearing protection is uncommon (<5%) among gamers.
The study quoted by the featured study is very reasonable in finding this given its context, but I think it's a little ridiculous the featured study suggested that gamers might use hearing protection as opposed to turning the sound down.
In any case, this is interesting to see. I never turn my volume up past about 20% because it becomes physically painful at that point, but I thought maybe some people might have insensitive hardware that needs higher power to create reasonable audio? Are folks just leaving their volume on the default 50% or 100% or whatever it is?
Many consumers prefer durbin-exempt cards since they have more favorable terms. Average fee on durbin-exempt cards is 1.41%, and they are 38% of transactions.
Average fee on covered cards is 0.45%, and they are 62% of transactions.
Seems reasonable to me that Wise wants to make a profit on every single transaction. Probably would have issues with abuse from 1% debit cashback cards otherwise.
It's interesting how quickly we forget about how things used to be. My grandparents were subsistence farmers in my lifetime, and they did not use horses to get around town. I don't think they ever owned a horse.
For regular everyday travel, they walked.
They'd sometimes need to go work out in a field. On those days, they'd hitch up the cows to the wagon and spend the day working there. This is a slow process, so they'd need to have enough work to spend the whole day there.
Horses were never a transportation method, except for the extremely rich. They were agricultural tools. Looking at France, because data is easy to get there, the population of France was about 40 million in 1900[2]. Around that time, France also had about 3 million horses, or about a horse for every 13 people. Of these 3 million horses, 2.5 million were "draft horses" used for pulling plows.
[1]: https://www.researchgate.net/figure/Evolution-of-the-horse-p... [2]: https://en.wikipedia.org/wiki/Demographics_of_France#Histori...
If you're looking to optimize a few hundred instructions, then focus on reading and understanding the code manually at the instruction level. A profiler will never help you there, CPUs are too complex:
1. I don't trust that the profiler has equal probability of pausing on any specific instruction
2. CPUs do no execute instructions in sequence, but in parallel. So you will need to understand data dependencies & maybe pipeline structures for your target processor. If you're getting really serious, you'll want something like https://uops.info/table.html
I thought that maybe aluminum foil would work here. I found this paper: https://www.acsu.buffalo.edu/~ddlchung/Materials%20for%20ele...
> electrical conductivity is not the scientific criterion for sheilding ... Metals ... function mainly by reflection.
> A secondary mechanism of EMI sheidling is usually absoprotion.
> The absorption loss is a function of the product σrμr, whereas the reflection loss is a function of the ratio σr/μr, where σr, is the electrical conductivity relative to copper and μr is the relative magnetic permeability.
> The reflection loss decreases with increasing frequency, whereas the absorption loss increases with increasing frequency.
So it turns out aluminum foil wouldn't actually be much good, with σrμr=.61 and σr/μr=.61. The commercial material listed says it uses copper & nickel: nickel's σrμr=20, copper's σr/μr=1.
So my thought here is completely wrong. Who would have figured the commercial product has gone through more thought than my random guesses!
>user: turn my living room lights off
>llm: {action: "lights.turn_off", entity: "living room"}
Search available actions and entities using the parameters
> user: available actions: [...], available entities: [...]. Which action and target?
> llm: {service: "light.turn_off", entity: "light.living_ceiling"}
I've never used a local LLM, so I don't know what the fixed startup latency is, but this would dramatically reduce the number of tokens required.
If you don't want the LLM to unlock your doors then just don't allow the LLM to call the `lock.unlock` service.
There's no need to declare anything in that case. Might need to declare the preservation chemicals, but nothing about the actual dead animal.
I try to avoid this in two ways:
1. I use the history in my terminal to search for previous invocations of the command, which tends to give me a good set of examples of how it should be used.
2. For anything but the quickest and dirtiest CLI tools, I like to use a declarative parameter parser like docopt or argparse. This forces me to spend a couple extra minutes writing some docs and makes the --help useful.
> The following factors are applied to all shipments of mailable live or dead animals:
> … Protection of the mail and the environment against the following: … Obnoxious odors and noise.
> ...protection of animal specimens against spoilage
https://pe.usps.com/text/pub52/pub52c5_003.htm
There's some other restrictions on mailing dead wild animals, but mailing livestock carcasses is not restricted from what I can see outside of those broad guidelines.
Of course, I got a new message from them yesterday because they've added a dozen different lists since then and automatically opted everyone into them.
I appreciate there's more technical detail in this blog post than the forum post, but it is generally polite to cite your sources even if there is no legal or cultural requirement.
$ hyperfine --shell=none "node -e ''" "python -c pass" "perl -e ''" "php -r ''" "bash -c ''" "echo"
Benchmark 1: node -e ''
Time (mean ± σ): 87.3 ms ± 8.0 ms [User: 69.8 ms, System: 18.4 ms]
Range (min … max): 77.9 ms … 111.1 ms 31 runs
Benchmark 2: python -c pass
Time (mean ± σ): 24.4 ms ± 5.6 ms [User: 17.5 ms, System: 6.7 ms]
Range (min … max): 15.8 ms … 31.3 ms 97 runs
Benchmark 3: perl -e ''
Time (mean ± σ): 2.8 ms ± 0.6 ms [User: 0.9 ms, System: 1.8 ms]
Range (min … max): 1.7 ms … 3.9 ms 863 runs
Benchmark 4: php -r ''
Time (mean ± σ): 19.3 ms ± 4.2 ms [User: 8.9 ms, System: 10.0 ms]
Range (min … max): 12.1 ms … 24.8 ms 241 runs
Benchmark 5: bash -c ''
Time (mean ± σ): 4.9 ms ± 0.8 ms [User: 2.8 ms, System: 1.8 ms]
Range (min … max): 2.6 ms … 6.4 ms 552 runs
Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.
Benchmark 6: echo
Time (mean ± σ): 1.2 ms ± 0.3 ms [User: 0.7 ms, System: 0.3 ms]
Range (min … max): 0.8 ms … 2.1 ms 2237 runs
Summary
echo ran
2.41 ± 0.89 times faster than perl -e ''
4.17 ± 1.39 times faster than bash -c ''
16.37 ± 5.91 times faster than php -r ''
20.74 ± 7.64 times faster than python -c pass
74.21 ± 22.49 times faster than node -e ''
(tested with node 21.5.0, python 3.11.6, perl 5.38.1, php 8.2.14, and bash 5.2.21 on Ryzen 2700X)There's no legal blessing for this, but there's already an industry standard (in the vein of the ESRB ratings): https://www.rtalabel.org/index.html?content=howto Most porn sites have already voluntarily applied this label.
> What am I missing?
My best explanation is that moral panic always plays well to voters.
And because any sign of depression or mental illness is career-ending from a pilot, the FAA and airlines' policy turned something that might have been treatable into something much worse.
This situation reads to me like a last ditch effort to fix the depression before attempting suicide. The tragedy here is that this will only lead to stricter regulations, rather than the mental health reform this industry needs.