I watched this video a few days ago after it was randomly recommended by YouTube. Definitely found it very interesting and he has a load of other videos about learning Old English, so I'll be checking out more of them soon.
When this was first presented, I was watching this in a large dark hall with this on the projector and the sound level set to extremely loud. Like a fool, I sat through this to the end wondering whether it was going to ever end rather than recognising it as a glorious troll.
Well, arguably if it's immutable, then it's not a variable so "var" doesn't make sense. The corollary is if it's a variable it should be mutable so "var mut" is a tautology.
I think "const x = something();" would be logical but they've used const already for compile-time constants. There's probably a sensible way of overloading that use though, depending if the expression would be constant at compile-time or not, but I've not considered it enough to think about edge cases (as it basically reduces to the halting problem unless any functions called are also explicitly marked up as compile time or not).
Trying to pick a good name for the keyword is valid but it's bikeshedding. Either way the keywords should be consistent and a config option is more trouble than it's worth.
And "variables" in math are almost always immutable within a single invocation. It's not a particularly bad word to use. But there's plenty of options. const/var. let/var. let/mut. var/mut I guess. let/set from a sibling comment.
Unfortunately, the one thing this article needs to get right is broken: the examples.
On my screen (Chrome on Windows on 1080p screen), it's in a scrollable box filling the middle half of the width of the screen. Some of the screens are set to display so many rows in the viewport, I have to scroll down several screenfuls to get to the horizontal scrollbar to view the right hand half, and then I can't see all the important stuff at the top right.
Secondly, mixing in emojis makes the font non-proportional so most of the screens don't line up properly. This isn't ASCII driven development, it's not even iso8859-1 driven development.
This seems daft to me as it would be trivial to identify on a network. Real SMTP will have significant data flow in one direction towards the destination, will close the connection fairly quickly once it's transferred (so no pauses) and has very little traffic being returned. It's hard to think of a worst protocol to try to hide a proxy in.
Having received a counter offer more than once, and accepting it once, I'd say that it's better at that point to just leave.
If you're already at the point of having decided to resign, you've already done a lot of soul searching (well, unless it was an easy design to leave) and weighed everything up and decided to leave. Even if the financials were an important factor in making that decision to leave, by the time you've convinced yourself it's the right choice, you'll have looked into all the other areas of the job that really annoy you. Even if you take the extra money, those things will eat away at you, and you'll probably always second guess yourself about how much better life might have been at the place you had lined up and then turned down for the payoff.
In other words, once you've made the decision to resign, there's part of you that has already mentally checked out of the job, and that will never be satisfied staying in the job, even with more money.
The counter offer I accepted was fairly early on in my career, adding about 25% to my pitifully low salary at the time. In relative terms it was massive, and most importantly allowed me to get a mortgage (at the time mortgage companies in the UK were very strict about not lending more than 4x your annual salary). However, the discontentment I had with the job remained and within 6 months I decided I still had to leave because I was still unhappy there even despite the extra money. Sure enough, the next job was much more fun because I was working on something new.
I've not been on the other side, but just from my own experiences, I don't think it'd ever be worth making a counter offer unless you knew they were chronically underpaid compared to the cost of hiring someone new AND you new that even when they were unhappy at work they'd still bring enough revenue to more than justify the extra spending knowing that it's likely to just be a short term fix.
TLDR: Once you've decided to leave a job, just do it. If an employee wants to leave a job, just and wish them well and let them leave.
Ditto. From all the places that I’ve quit, the only counter offer I’d accept would be “we’ll implement this structure/process change that is slowly killing your will to work here”.
Also, one thing I forgot to mention that I think is really important...
If the company is prepared to offer you a big enough raise to tempt you to stay, and able to organise that raise at short notice, why didn't they value you enough to give you that raise before then?
> The legal question is posed: Who is liable under Roman law?
My question is why does anybody have to be liable at all? Most normal people would consider this just to be a freak accident.
Sure, there's learning points that can be taken from it to prevent similar incidents - e.g. erecting a fetch around the field (why didn't you suggest that the field owner be liable) as it can be reasonably foreseen the situation of a ball escaping and being a nuisance to someone else (maybe it just startles someone on the road, maybe it causes a car crash, whatever), or legislating bars or plastic film on the barber's window, etc.
But here nobody seemed to act in any way negligently, nor was there any law or guidance that they failed to follow. It was just the result of lots of normal things happening that normally have no negative consequences and it's so unlikely to happen again that there's nothing useful to be gained by trying to put the blame on someone. It was just an accident.
> My question is why does anybody have to be liable at all?
This question mistakes what civil law is doing. A more accurate framing would be, “why does anybody have to bear the loss?”. But of course, somebody must. So the task of civil law here is to determine who. Certain policy choices will align better or worse with a sense of fairness, better or worse with incentives that could reduce future losses, etc.
"The loss" is already performing an abstraction to create something generic that can/must be assigned. The person who died is dead regardless of the creation of that assignable loss.
If there are too many instances of people dying in such situations, then the fundamental way to solve that is to prevent such situations from existing. A specter of civil financial liability is but one way of trying to do this, and having judges create common law theories is but one way of assigning that liability. Relying on those methods to the exclusion of others is not a neutral policy choice.
The whole point is that there's a legal system that allows a plaintiff to make an argument that there was negligence at play, and OP outlined a logical list of examples of how it could be argued up to the government itself being negligent for zoning. It's the job of the legal system to remove the ambiguity of "seemed", particularly in the context of tort and compensation.
This example just happens to be less obvious than a construction company building a house or bridge that collapses and kills people, and most cases in front of a court are equally ambiguous.
That's such a strange interpretation that disagrees with my intuition.
If the Yankees hit a practice ball out of their stadium and into my house, causing bodily harm to a loved one, I wouldn't be satisfied with any of the reasoning in your comment.
More generally, people are allowed to take on risk as per their own appetite, but legal liability allows risk-hungry individuals to be incentive-aligned with everyone else.
I don't actually find it a particularly strange interpretation.
Here's another lens:
I install cabinets in your kitchen. Your loved one trips, hits the cabinets, breaks their neck and dies.
Should I be liable in this case as well? I did a thing that was involved in harming your loved one... if the cabinet hadn't been there, they might not have died.
---
In both cases, it's pretty clear that there's no intent to harm your loved one. At best you're arguing that it was "foreseeable" that hitting a baseball might harm someone, and that it wasn't "foreseeable" that installing cabinets would harm someone.
But clearly that's ALSO wrong, because we know people have been hurt hitting cabinets before.
So clarify how you'd assign blame in this case, and why it's different from the baseball case?
Basically - your stance is that risk is always a decision someone has made, but I find disagrees with my intuition. Risk is an inherent part of life.
reply