If they dragged the customer into court, they already screwed up.
They should have paid the customer immediately and then took it up with their vendor. If they want to take their vendor to court, they can do that separately.
They're not liable for the things that come out of their employees' mouths?
Maybe my flight tickets aren't valid either because I foolishly purchased them on aircanada.com and their website is known to have bugs? Or the ticket lady punched the wrong thing into her computer? Or I should have known the plane was going to be overbooked?
Well...they lost, and now it made the news. Are they going to keep the chatbot? Is the judge going to so lenient next time, now that there's precedent of wrongdoing?
Humans won't fabricate too much but when confronted with yes/no questions and they have a 50-50 shot of being right and any blowback will likely be on someone else....they'll answer whatever to get you out of their hair.
Case in point, I asked my bank if they had any FX conversion fees or markup. Guy said no. I asked if there was any markup on the spread. Said no. Guess what? They absolutely mark up that spread. Their exchange rates are terrible. Just because there isn't a line-item with a fee listed doesn't mean there isn't a hidden fee in there. He's either incompetent or a liar.
There was a good rent vs buy calculator I found years ago, not sure which one it was, but it doesn't even make financial sense in some scenarios, particularly for shorter terms.
No, because now you have 2 pieces of state to maintain and keep in sync.
You must store `desired_column` and compute `current_column`. Otherwise you or someone will try manipulating `current_column` to try to get the desired outcome, or worse, update one and not the other.
function ajax({url,success,error}) {
fetch(url).then(success, error)
}
Boom, same syntax if that's what you prefer.
J/K, the error status handling is not the same and the auto-deserialization isn't present. Not hard to add but it's harder to argue not to use a lib instead of copy-pasting 114 lines of niceties into each project.
There's 2 types of web pages. Websites and web apps. If you're building a web app, you're going to want a framework that isn't going to fall apart the second things start getting complicated. If you're making a little marketing website, sure, sprinkle some jQuery on there and call it a day. Probably better for performance and SEO unless you want to spend 10x as long micro-optimizing your SSR. Point is, there's different use-cases.
Then you have dumb stuff like if you check a box and want some additional form fields, you have to inject a div or input into the DOM manually, and then make sure you initialize your datepicker, but maybe there will be a flash of unpickerified input if you don't do it right.
And it's not hard to get them working in Webpack...if you're like me.. maintaining the same app for 10 years and see no reason to switch to the new hotness.
I write commit messages for future-me. Sooner or later I'm going to encounter the same problem again and wonder how I solved it last time. If I have a vague inkling that I dealt with this before, all I have to do is searching through my commit history and I can find it again. I can search my author (me), I can search by date, I can search by what files I touched. It's lovely.
I didn't think low-latency high-quality voice chat would make such a difference over our current ChatGPT chat, but oh my, I think that really takes it to the next level. It's entering creepy territory, at least for me.
I got into programming because I enjoyed programming. My first "real" job was not in FAANG, just some small company with about 2 other developers. And it was great, I had a lot of fun, I got to work with great technology and try new things.
Then I got lured into FAANG for the $$$ and free food. Now it's boring. There's no room to innovate. I'm not allowed to make any big decisions or play with fun technology. What's left? I enjoy my TC and that gets me through the day. You can't blame folks for focusing on TC when there's no innovation to be had.
5) How does 2 make sense? Shouldn't be 0 + 1? Or does the pre-increment take precedence over the addition, thus the left i is 1 but not because of the post-increment?
Can you explain 3? A space is 20 IIRC, 2013 is 260. An unsigned char tops out at 255 but I guess this one is* signed so... that's 127. And then I have no idea what happens, some kind of overflow, but I don't know the wrapping rules.
I'm not familiar with modern Sass. Has it evolved much in the last decade? I'm still using Less because I installed it 10 years ago and it still works great, but there's almost 0 features that haven't been adopted into CSS now so I really don't need at all.
There is 1 I guess. I wrote a loop somewhat recently because there doesn't appear to be a variable for DPI yet. `env(dpi)` doesn't exist or I could have did what I wanted: scale a <canvas> element to be 1.0 scaling regardless of the user's screen scaling.
That one is clear to me too, also no. How would she know? No where did you specify that she even thought going to church would solve her problems. She was told to visit church, yes, but there has to be a belief component to "knowing". Did she genuinely believe going to church would solve her medical problems? Hope and desperation don't count either, it has to be a genuine belief. Also, she was told be pray to Jesus. Depending on if you're religious or not you might say that Jesus did cure her, but a pretty strong argument could be made that the church-goers were the key, so even if she did believe Jesus would cure her, if it ends up being something else, then it also doesn't count.
> Finally, you also may want to disclose derived information - such as just that I have a vaccination in the last x months, rather than the precise date or location, or just that I'm of legal age to purchase alcohol in my country, rather than my birthdate. These sorts of predicate proofs are also of interest to the group, although the algorithms and representations aren't as far along yet.
That sounds kind of crazy. I can't imagine how you'd prove derived data. Very cool though. Thanks!
We just have these stupid unpressable buttons near me. They're big with an embossed arrow on them, but if try to press it it might budge a quarter of a millimeter. I still don't understand how they work, if they're supposed to be capacitive or just have really tiny press windows. But they give zero satisfying feedback that you've successfully pressed the button. I hate them so much. And if you hit them hard they will murder your hand.
Floor 3. It goes to floor 3. At least in my building, which I think has 5 floors. So I guess it wants to wait in the middle to be equidistant to all floors, but I suspect there is a flaw in that math because ground floor probably gets more traffic.
I don't see the "speed up" problem but I get the "I have no idea if you intend to stop, or turn directly into me".
These people drive with speed right up the stop sign, don't turn their blinkers on, and then with 40% probability, turn anyway. So whenever I get to that intersection, if I see a car approaching there, even if they don't have their blinker on to indicate they might want to turn where I want to walk, I wait to make sure they come to a complete stop before I enter the intersection. Sometimes the buggers will just start turning slowly into the intersection as I'm still walking. It's extra great when they start blocking cars going the other way.