4,271 karma · joined September 4, 2007
[ my public key: https://keybase.io/ketralnis; my proof: https://keybase.io/ketralnis/sigs/-b8hg9xv4sLOgAEnBoAfmQjftzv790I-mM2YelSrYfI ]
If you call a function that calls a function that has side effects, or that closes the file descriptor you're using, or could panic, or that needs global shared state, or spins up a thread, or allocates, we don't have a good way to deal with that. There are some partial and underutilised solutions like monadic IO and linear/affine types and, uh, not having panics. I have some (bad) ideas but I think this is a space that's worth playing in.
> All credits to FX. I do not own any rights.
Appropriate
B: yeah we're hurting you but if we didn't, A & C would
C: yeah we're hurting you but if we didn't, A & B would
I guess it’s nobody’s fault then
You're not disagreeing with the GP
Why? Well, stall speed isn't a real thing. There isn't a speed at which you stall, that's not how it works. It's a convenient short-hand that we use for the more complicated reality. The physical reality is that stalls happen at a particular angle of attack (AOA) into the apparent wind. That is, the angle of your wings relative to the airflow. Up to the critical angle a higher AOA means more lift to counteract gravity. As you slow down you generate less lift because there's less airflow over the wings. So as you slow down, in order to generate a similar amount of lift you have to increase your AOA. If you keep slowing down and adjusting your AOA to compensate, you'll reach a speed that's low enough and therefore AOA high enough that adding more AOA no longer adds more lift (the air no longer flows smoothly over the wing). That's the stall speed, the speed at which more AOA no longer generates more lift. But it's the AOA that's the problem, not the airspeed.
In addition to lower speeds needing more AOA, you also need a higher AOA if you weigh more. A wrong but illustrative way to think about it might be that you need the engine's thrust pointed more towards the ground the more you weigh. That means that as you burn fuel (lose weight) the AOA that will stall you doesn't change, but the excess AOA available due to your weight-change does so in effect the air speed at which you would be near the critical AOA to stay airborn does change.
Stall speed is still a useful concept especially while landing but it's misleading outside of landing and when anything else is remotely unusual like weight or modifications to the plane. For this reason the FAA has been trying to get AOA indicators installed in planes and to train pilots to look at those instead of thinking about stall speeds https://www.faa.gov/sites/faa.gov/files/2022-01/Angle%20of%2...
So? It's not about LLMs?
In fact, time perceived as volumetric rather than as a length is the specific example he uses and includes the actual research. There are extremely specific cases like this where it does in fact hold up but the effect is extremely minute, to the point that it's difficult to even measure properly. In most cases it doesn't hold up at all. But these very tiny barely measurable cases are often used as evidence for frankly nonsense claims so it's important not to extrapolate this to "Japanese blue and green are the same word so Japanese people must be colourblind", which is where people often take this.
In many contexts yes but as a blanket statement no. Calca allows whitespace in names and it is a delight to write as a result
That said, how are people using this to generate any income at all? Printing out and selling mazes? How big can that market be?
Ignoring their pervasive station reliability problems, their app is pretty bad and only barely functions.
* I've had to skip a perfectly functioning station because the app thought I was still charging from the previous time and wouldn't change its mind about it.
* Their Carplay app has literally never worked for me, not once (usually it shows me still charging from a session >1wk ago even when the regular app doesn't, sometimes it doesn't boot, sometimes it shows me as not logged in. The main screen has never once rendered.).
* One of their level 2 stations (which tend even less reliable) existed in the app on about 50% of refreshes.
* The app requires a pretty solid signal to work at all since it seems to consult their API to query for stations near where you are and then you guess at which one it is ("is this the target one or the mall one? it's the target that's in the mall?") which is pretty silly when you're parked at the station so it's in range of your hands and eyes.
* I eventually figured out that I can add the EA plan to my Apple Wallet and tap the phone instead of ever opening the app, but that seems to randomly select between the "free" plan (rather, included in the purchase price of my car) and the $10 balance that they make me maintain for god-knows-why when at California electricity prices no charge has ever been below $10.
* The stations have credit card readers which I've never tried to use but almost always when I see somebody having trouble at a station it's because they're fighting with that thing. I assume EA's response would be "just use the app, it's so much better"
That's all just one app, not a slew of them for every charging network in my area (which also includes at least evgo & chargepoint just to cover the big ones). The sooner this app bullshit can die the better.