I feel like if you treat temporary variables as documentation they feel less icky. All these examples with the pipeline operator cause way more mental overhead than reading temporary variable names.
I think it really depends on what operations you are applying. Having one succinct named variable like $slug with a few simple pipeline calls like in the example is "self-documenting" and easy to read. However, some lambdas and non-standard function are definitely a place for nicely named temporary variables in my opinion.
This looks like some visual artist was given a task to design the UI. Visually interesting but completely disregards UI research and usability standards.
Doesn't it mean you're now dependent on the US (and our particular politics) as well as the middle eastern oil monarchies? Or is the idea to try to source all of the EU energy needs independently?
The concern with having the grids connected to Russia rather than the EU is that Russia might exploit this in the future (inducing instability on the grid for instance) so switching to the EU removes that risk
As for the US and ME monarchies, this applies more in general to the EU as a whole which depends quite a lot on imports for fossil fuels, but not all dependencies are made equal and at least for now Saudis and Americans haven't been invading countries in our neighborhood so I'd still take them over the Russians
The ideal scenario would be reducing as much as possible that dependency which is why there's a bunch of interest in renewables, energy efficiency and nuclear across the continent
As can be seen in the link, both Sweden and Finland currently exports power to Baltics.
Both Sweden and recently Finland are European power-houses when it comes to electricity.
Sweden always was (despite what everyone complains about here in Sweden). With a healthy mix of hydro, nuclear and recently wind power. And Finland just recently finished a large new nuclear reactor.
Also, in many places of the world (e.g. Scandinavia), electricity does not equal Oil.
Middle eastern monarchies are currently better than Russian "democracy". If you had asked me 30 years ago I would have said differently. If you ask again in 30 years I have no idea what I will say. The US likewise has good and bad points and exactly how they come to play changes over time. There is a lot to dislike about the EU as well which anyone living there should be concerned about more than the US (though since I live in the US I worry more about the US - I have a chance to change it maybe)
Even if you don't care about privacy, every single page using bare HTTP can have HTML or JS injected into it by a third-party.
Certain ISPs, hotels and airlines do it to their clients, and the script kiddies messing around the poorly firewalled subnet of their college's AP do it too.
It would prevent one’s ISP from injecting advertisements in the HTML as has happened commonly in the past with US ISPs. I presume that has mostly fallen out of practice but one could well blame that on the near-ubiquity of HTTPS.
3. So when that dependency gets removed by npm uninstall how should that comment be handled? You know that in business we just would end up with a bunch of dead comments in the package.json - is that really a better alternative than just using Ctrl+f to find where the dependency is used?
Has it stopped crashing yet? Honest question, I try it every few months and it always spontaneously combusts in between playbacks (browsing media, when finishing playing, etc.)
I do not remember the time it has ever crashed - and I am quite sensitive to software not working well. I can complain about the strange UI choices but not about the stability. Running this on latest Apple TV 4K
reply