9,140 karma · joined February 2, 2015
2. Why is it wrong to solve problems the easy way? Why should people have to follow the "difficult" path of dieting if an easier method exists? That's not being lazy, it's being smart by avoiding unnecessary effort.
3. Many diets also have side effects (e.g. hunger, fatigue). But regardless, if people would rather experience side effects from medication than go through the difficult experience of dieting, why is that wrong?
(Rybelsus is a version of semaglutide available in tablet form, but it hasn't officially been approved for obesity yet.)
That said, I'm a bit skeptical of the utility of refinement types (and dependent types in general). They greatly increase a language's complexity (by obscuring the type/value distinction and making type inference and checking more complicated). I'm not sure the benefits are worth it, particularly because of the so-called "specification problem."
It's not just data races--it's also logical races, which are near-impossible to detect or prevent without something like transactional memory.
I'm not condoning the author's actions, but I don't think any company has explicitly told me that. (I assume by "interviewers" you meant "interviewees.")
Only a small minority (3-5%) of acts of violence are attributable to mental illness: https://www.vox.com/platform/amp/2015/10/1/18000532/gun-viol...
edit: Even most mass shooters are not mentally ill: https://www.washingtonpost.com/local/most-mass-shooters-aren...
One could even imagine those "universal contracts" being open-source, if you could find a business model.
For instance, instead of using an expert system to generate a contract that says "Alice will pay Bob $2000 a month in rent, plus utilities," you could write a contract that says "The party listed on line 1 of the attached form will pay the party listed on line 2 of the form the amount listed on line 3 of the form; if the checkbox on line 4 of the form is checked, then the first party will also pay for utilities."
Then the attached form could look something like this:
1. Name of tenant: _______
2. Name of landlord: ______
3. Amount of rent: $_____
4. [ ] Check here if tenant pays for utilities
That solution would seem to be much more efficient and transparent than using an expert system; essentially, the "templating" is being done by the judges and/or lawyers reading the contract, not by an expert system writing one.
Edit: of course any such contract might contain a lot of "conditional logic" that would only apply in very specific circumstances and thus would prove irrelevant for most users. But although the contract would be long, you'd only need to write it once, and there would only be one copy to maintain.
The problem is that almost nobody actually does this, and many GraphQL libraries and tools actively discourage it.
Biking is different, of course--you're not outside for as long (at least for a given number of miles), and you can store your water bottles on the bike itself.
But then it will forget that inference when type checking "print ((!m) 23)"; there it will infer that a == int, and that the original definition of m was really "m = ref (fn (x:int) ⇒ x)".
Essentially the issue is that type inference forgets that it already solved for "a" and can't assign it to both "int" and "bool".