raquo

Does anyone know how they identify Russian citizens?

The last paragraph also happens to perfectly describe how Russia works. All exactly the same.

Sounds like such a freeze should be the default state.

If it wasn't accessed, they would have been very clear about that. They're just mentioning "core consumer or commercial credit reporting databases", whatever those are, to dilute the horrifying message and confuse everyone.

First, that's not much of a parallel. The morality of generic murder is clearcut, the morality of interference with other countries elections is not. Not everyone subscribes to prime directive. As a Russian I personally appreciate that someone is at least trying to instill some positive change in Russia.

Morals aside, you said

> It's curious this is virtually never mentioned amidst all the accusations of Russia involving itself in US elections.

I told you why. Because whatever the US did was not effective, and it's not as newsworthy as things that are happening in the US and affecting Americans.

It's the line that Putin and Lavrov (foreign minister) have been pushing since forever: "you westerners are no better than us, stop shaming us for the shady things that we do". That's an easy way to keep your population happy – tell them that life is no better in other countries. Corruption is everywhere, police state is everywhere, etc. And most Russians believe that.

Well, both Putin and the US have good-to-them reasons to interfere in each others elections. And to interfere in Russian elections.

On a serious note, the reason you don't hear about it is because US interference in Russia, whatever that was, didn't come even close to turning Russian elections.

No one has any doubt that the planes can fly themselves in 99% cases even with todays technology, but bringing this up to a higher uptime while still being fully automated will be very hard I think.

I don't think commercial jets are an especially favourable target for complete automation, compared to cars.

- Slow iteration, each mistake that you could learn from potentially costs a hundred lives

- No graceful shutdown possible most of the time – if automation fails in a car, you just stop or pull over, you probably won't die. A plane can't just land itself if automation fails unless the comm link works

- Comm link might not always work, it can be damaged from light mid air collisions, bird strikes, drone strikes, other damage, improper maintenance, possibly bad weather, hacking, jamming, over-saturation due to mass automation failures etc.

To me it seems that it's easier to deal with road chaos than acquire an extra couple 9s of uptime in this problem.

Also Yandex (Russia)

Well yes, that's a reasonable use case. Personally I'm not convinced that all 4xx responses should be rejections, but regardless of that, you should have about as many `catch` blocks with async-await as you have with promises.

So, were the trademark nullified, could Microsoft come up with a google of their own, perhaps on google.bing.com? I mean, they probably wouldn't, but could they?

hmm were you previously using Promise.catch for flow control? It's basically as bad as using exceptions for flow control, just with with a different set of bubbling / propagation problems. Unless you're dealing with truly exceptional conditions you should not be throwing inside your promises, thus no need for try / catch when converting them to async/await.

That was a bad example indeed. If isImmortal was accepting any params though, you wouldn't be able to make it a getter.

And sure, Object.freeze exists, but almost none of the JS code I've seen uses it. And what's the point really when assignments to frozen fields don't even throw an exception, just fail silently. Same for getters. None of those tricks are gonna make JS into a good language in the eyes of people who don't for whatever reason consider it good already.

Someone here mentioned a while ago that such random character non-answers could potentially be bypassed by answering "oh it's just a bunch of random characters" when asked for the security question over the phone.

A plausible but incorrect answer is better I think, e. g. Q: What city were you born in?, A: Severodvinsk (a random town in Russia)

I found Enpass rather unfeatureful. It doesn't even have an option to use multiple vaults.

Adding a `map` method to every single object is not a backwards-compatible change. That's why those new methods are under the `Object` global.

Static types are better and cheaper at catching type related bugs than a myriad of end-to-end tests that check dynamic types.

I am not making assumptions. I'm providing my own opinion that the problems he mentions are best addressed by funding healthcare with taxes instead of having an insurance system.

Here in BC only the province is allowed to provide primary car insurance. Our current provincial government is incredibly corrupt and incompetent, including with regards to the provincial insurer specifically, but I'll still take it over private insurers I've had to deal with before.

I don't know, but I would be surprised if Scala.js does anything in that regard. It's a Scala-to-JS compiler, its job is to translate Scala code to JS code.

Scala.js lets you require any npm modules, so you can `require()` any JS polyfills you want just like you would do if writing JS code by yourself.

JavaScript is a small language because it needs browser support and backwards compatibility. A small language that can't change much over time can't afford to have opinions on how to build dynamic interfaces.

Therefore, all the complexity of building interfaces will be in the libraries and because opinions on such complex issues vary, there are many libraries to do the same thing.

Eventually the interior ones are recognized and culled. They typically are supported for quite some time after becoming uncool, it's just that no one wants to work with lame, obsolete tehnology for good reasons.

The solution I see to this are compile-to-JS languages that make it possible to use a different ecosystem of libraries than te JS one, like Scala.js. However, those tools are also still evolving, so one way or another you're dealing with a lot of library churn in frontend development right now, so learn to pick winners and stick to them until it's as weird to use them as jquery for complex UI was in 2012.

I would like to see a similar analysis for gif vs jif pronounciation. We need to settle this.

Income taxes: https://simpletax.ca/calculator

In some provinces like BC you also pay approx. $60/month for health insurance.

Sales tax is from 0% to 13% depending on province and types of goods / services.

Nothing like doubling of income tax happened, not sure why your google says that.

Your local instance of github and github.com are not redundant / interchangeable. If either of those goes down and you rely on it, the other one is not gonna help you much, so availability is not improved by using a local instance.

Well the discounts I'm mentioning, both the finance rate and the cash discount, are coming from the manufacturer, not the dealers. For example, here's a Forester at 0.5% rate OR $2K cash discount (might need to choose BC as region): https://www.subaru.ca/WebPage.aspx?WebSiteID=282&WebPageID=2...

Not every manufacturer does this, and not on every model.

The financing rate is 0% because the MSRP of the car is slightly inflated. If you pay with cash, you get a cash incentive (e.g. $2000 off), if you pay by financing, you get a similar discount but in the form of a lower nominal interest rate.

Jurisdictions with good legislation require dealers to also show the effective APR, which takes the cash discount into account and is almost always a more reasonable rate.

---

Apart from that there could be lots of special circumstances (making a quota, etc.) that could explain the discount if the offer was made to you personally as opposed to being advertised to the public.

I used 2.1, it has all the same flags, and I did turn them on because they're not enabled by default. It's completely insane without those flags, but even with them enabled I still ran into many surprises. For example, like the other poster mentioned, its handling of variance is simply appalling.

And no, Flow is MUCH more sound, I have worked with both. Flow's limitations tend to be false negatives (code that should ideally work does not compile as is) whereas Typescript's are false positives (fails to detect type errors).

In my experience with TS, its unsoundness was very frustrating. If you use it as a replacement for JSDoc where type ascriptions are more like recommendations, sure, but I like to have more confidence than that in a type system. FlowType is much better in that regard. Scala.js has been the best for me so far.

Epoch.major.minor