I know that the plural of "anecdote" isn't "data", but ... I ended up with a Polestar because I got a fantastic lease deal but my wife literally wouldn't countenance buying a Tesla because of Musk.
What are the CEO of Hyundai's personal beliefs? Do you even know?
Unlike Musk, the CEO of Hyundai doesn't go out of their way to make sure I'm aware of their opinions. I don't even know the name of Hyundai's CEO, and we bought an Ioniq 5 last year. One might argue such a dichotomy is one of the reasons we didn't buy a Tesla (well, that and the crap build quality).
Same in Slovakia. Max is 11kwt. Its because of taxes. Anything above 11 is not considered residential any more, and you have to pay taxes on electricity you make and sell to the grid.
You do realize that Ukraine was shelling their Russian-speaking citizens in the east for several years for before Russia invaded, killing over 10,000 civilians?
As much as I disgusted by Western propaganda and hypocrisy, I must say that most of them died in 2014 and 2015. Following Zelensky's election about a dozen or two civilians died on both sides per year in the Eastern Ukraine and mostly because of old mines. Killing thousand times more people is hardly a solution.
It was the Ukraine who was trying to regain control of DNR and LNR.
14000 is the total number of Ukrainian citizens, both civilians and fighters, who died on both sides, not counting Russians who overtly or covertly helped rebels.
In 90s and yearly 2000s Russia was invading Russia and tens of thousands of military and civilians died.
> 14000 is the total number of Ukrainian citizens, both civilians and fighter, who died on both sides, not counting Russians who overtly or covertly helped rebels.
The local population was more than happy to set up their own autonomous zone after the central government began discriminating against Russian-speaking citizens, even passing laws against the use of the Russian language. Putin actually asked them not to hold referendums on multiple occasions— it was only until he realized late last year that Zelensky is totally controlled by the right sector and would happily sacrifice his people for US geopolitical goals that Putin acknowledged that area could never be safe for Russian-speaking people with Kiev in charge.
I share same account with my brother for several years.
I would have no issue paying for my own if Netflix at least offered some kind of profile export or migration.
If your whole file is semantically the default export, then why not?
There are advantages with default exports, e.g. you can name it at usage site the way you want without the `:` syntax. Also some things like `React.lazy` only works with default exports.
Not OP but I avoid default exports unless I need to do a lazy import. For me, there's a few reasons: consistent naming, easier importing, encourages importing what you need, avoids weird situation where you do both a default and named import.
Consistent naming: since I named the exported thing, that's what the consumers will call it as well unless they go out of their way to do `import { X as Y } from '...'`. This is useful because it helps ensure all consuming code looks similar at least in it's usage of modules. More familiar code is easier to read and reason about. It's also useful for looking up usages of something. I know I can run $IDE's version of "Find Usage" but sometimes it's easier to just Ctrl+Shift+F > X.
Easier importing: If I have something exported as X then I go to a module that isn't using it and I type X, my editor will suggest I import it from the appropriate module. This _can_ work on default exports but only if you use the same name as was used internally at the point of definition. That kind of defeats the benefit of default imports where you can use whatever name you want without hassle and it's your responsibility to make sure you match the names correctly.
Encourages importing what you need: when you default to named exports, you default to pulling in the bare minimum to do the job. Consider the opposite case. Someone imports some monolithic chunk of code as a single object then does `library.thingIWant` with a bunch of different things. Now you've got a larger possible space to look at when trying to load all of the context of a file in to your head. This is also useful for tree shaking. Assuming you've written your code in a well-defined manner and are using a smart build system, it can more easily eliminate dead code because it knows you never import certain pieces of a module. This applies to both your code and code from third-parties.
Both default and named imports: This is common when working with React. You'll see `import React, { useState } from 'react'` or similar. I don't have a rational answer for this but it rubs me the wrong way.
