The tone is very poor. "This is bad: closed" is not a friendly way to communicate and attract contributors. There are obviously better ways of encouraging contributions to match quality requirements/project style.
I don't think OC is a fair baseline to qualitatively distinguish between CPU classes (at least low/mid vs high-end). OC is surely a large factor in purchasing decisions for a subset of high-end users, but not all.
Also: Safari crashes with force touch click-through fairly often. Lots of notifications seem to flick around faster than I can see them or react. Weird bias towards closing app over switching apps in the app switcher.
It does seem a particularly messy release, perhaps akin to iOS 7. But many things also seem snappier and more useful. Like another commentator, I put it down to teething problems.
If you worked at Netflix and everyone around you made a million whilst you made half a million, you might give such an answer on a survey, and it probably wouldn't change with the absolute amounts.
What kind of parts of the US are you talking about? Amsterdam is reasonably dense (not compared to say, NYC, but that isn't "much of the US"). People often commute 30-60 minutes by bike there.
I'm using JustWatch (https://www.justwatch.com/) for manual searches (there seem to be Python packages offering an API but not sure how legitimate they are).
I do too. However, the new one is significantly upgraded from its first version if memory serves - I recall new settings being added all over the place which didn't exist previously.
The mature thing to do is leave, or discuss your needs honestly. If the enjoyment comes from the risk then you're getting your kicks at someone else's expense. That's really selfish.
When I have reported black cab drivers misleading passengers, lying about pricing and regulations or bus drivers driving dangerously and being rude to everyone, TfL are totally uninterested. They give the impression that they know the scams operate and don't care. It's an interesting comparison with my Uber experience, which has been almost flawless and issues are usually fixed by Uber themselves promptly.
I was just thinking about Opa the other day - it looked nice but I never used it. People were worried about debugging through the layers of abstraction. Is it still "alive"? You write in the past tense...
Surely it should also be emphasised that any competing products that happen to violate those patents would be off limits? The emphasis in most of these discussions is that you have to get off React, but it's likely you couldn't move to a direct competitor either.
There are two (very closely related) languages. In principle implementations are compatible, whereas language version are explicitly incompatible by intention. I think that was clear from the parent.
Maintainers often have a perspective that rates backward compatibility higher priority than an individual user would. Even if they have learned from previous mistakes in policy or implementation.
I don't find it to be better or worse than any other Northern European countries. And I can't find good tomatoes at any price - the more expensive on-the-vine ones smell good initially but only taste slightly better.
I think the important thing is that it's a form of deceit. It's not about the value to the public vs the value of the person's wishes: if you don't intend to go through with the wishes or believe there is a good chance that you will not be able to, then you should recuse yourself at the point of the request (or as soon as you realise). Deciding to stay involved and make your own choice is simply duplicitious - it completely defeats the point of having the legal power. It wouldn't surprise me if someone could sue the executor, since they are clearly acting against the best interests of the person.
I'm getting the impression that a lot of extension developers are not just complaining about these changes but also making the decision to shut down their development. Feels like it could be pretty bad news for Firefox.
They neither call it unbeatable nor mention hardcoding anything. The "unbeatable" is a quote from a professional tester, and they discuss the losses, acknowledging the need for further improvements for more general play.
As I understand it, the research is not completely conclusive but the claim is that there is significant habituation effect. I've also heard that restlessness/insomnia are just as likely to be caused by withdrawal effects in the evening as they are by high consumption. Withdrawal effects have similarities to high usage, and anecdotally if I'm drinking a lot of coffee but stop early in the day I often have problems sleeping.
I rarely hear people complain about genuine use-cases but this would seem to be one. However, aren't most/all of the dataframe operations done in C extensions in these cases?
Yes, I feel that the "Bonus" section (with no explanation even) is rather encouraging beginners to mis-use regular expressions in general, and - more specifically - contains errors.
Couldn't agree more. Little-mentioned relative to the others because it wasn't connected with the narrative of the financial crisis, but most of the others seems like repetition of ideas from FbR.
Soap is mostly for helping to remove dirt by helping both scrubbing and the mixture of oils in water. I think it has some side-effect as an antibacterial due to pH or something, but it's not inherently a bug killer (of course, you can get anti-bacterial soap these days. Arguably a bad thing globally).