To the contrary, it's pro-democratic. In a healthy democracy, people should be able to vote to create the kind of society they want. That includes being able to exclude, through their government, outsiders who don't share their values.
Next up, in a society you should make sure that people you want to exclude have to drink from certain water fountains, can’t be in the same pool and go to separate schools…
It's really not expensive anymore. There's a Black Friday deal on amazon.de for an entry-level Anker Solix system with 4x500W panels and a 2.6 kWh battery. 1200 EUR.
For those that don't have the cash, financing is available.
Their smallest solar products are small lanterns. Simply having a pollution-free source of light is already a quality of life improvement for some people. One step up is to add a USB port to charge phones.
Oh I’m sure, Pakistan has alot of trade with China also so it’s probably cheaper than in the west. But it would still be expensive for the poorer Pakistanis, and would require some investment, they simply have less ability to do that than a richer middle class Pakistani, so the poor pay the poor tax because they can’t invest capital to bring their costs down.
Low Chinese prices are making it more and more possible though. I hope the future will be really different.
Voting machines that saw more voters had a larger skew. Up to about 300 votes per machine, the results look pretty random and natural. From there on, the pattern changes drastically and shows unexpected clustering. It's unexpected because larger samples should slowly converge but still be normally distributed (law of large numbers). Instead of matching a bell curve, the distribution shows a "russian tail" (search for it on the page), a sign of vote manipulation.
All this is only for the early votes. If you compare the scatter plots and distributions of early votes vs. election day, they look completely different.
eID is a federated identity system that uses national electronic ID systems as the identity sources. That's useful especially for apps on the EU level, e.g. for customs, to submit what you're importing as a company.
In practice, I won't be able to use my phone as a replacement for my passport when traveling internationally. But I might be able to use my phone, in combination with my national ID card which has a NFC chip inside, to submit a government form in another EU country.
While I don’t have hard evidence to support the idea, I believe this is highly variable between individuals.
I’m not a heavy coffee drinker, but I do have a cup in the mornings some time between 6:30-8:00. This makes it easy to stop as needed; there are some days where I skip it out of necessity (too busy), and occasionally I’ll go a weekend without it just to keep my tolerance in check. During these periods, I never experience adverse effects.
The main benefit I glean from coffee is not feeling awake, but notably improved ability to focus. In my experience, my baseline ability is just not as good; there’s no “bounce back” after extended periods of going without, it just stays somewhere between bad and average indefinitely.
I strongly suspect this manifests more in folks that consistently intake > 100mg per day. I used to regularly intake 200mg total across ~2 beverages (mostly because I just enjoyed the flavor), and suffered mild headaches if I skipped my schedule. I know others that start their day with 200mg in a single, quad shot beverage.
3 years ago I took a summer and then autumn off of caffeine; my intent was to quit and only use caffeine in "times of need". This would be an on-brand thing for me to do as a person, and something I wanted pretty bad. But after 4 full months without touching any caffeine, my mood/energy levels never returned or even really rebounded any further than they did after the first month. I'm just a different person with caffeine, even after I'm addicted/habituated/develop tolerance. Notably I have a lot more energy, and I'm not a high energy person to start with. This energy allows me to better take care of myself, exercise, and be social, all things that I struggle with in its absence.
From experience, I can function fine without caffeine, even under an acute withdrawal scenario. In fact, some of my greatest achievements were done without caffeine for one reason or another. Not having caffeine just makes those things more miserable in the moment, at least for me.
This makes me so tempted to get one of those whole genome tests. I had issues with anxiety from age 20 to 38. I was a regular drinker of coffee between the age 20 to 38. About a month after quitting I was finally able to yawn properly like I remember I was able to when I was young. Coffee overstimulates me I figure.
Shape.getOfType(type) would also be a factory. A factory does not need to be a class, it can also just be a function.
I see two reasons for using a factory:
1. Reducing the scope of what a piece of code is responsible for (a.k.a. "Single-Responsibility-Principle").
Assume you are working on a graphics app that can draw 50 different shapes. The currently selected tool is stored in a variable, and there is a long switch statement that returns a new Shape depending on that variable. You wouldn't want the switch statement to dominate the rest of the code:
handleClick(x, y) {
selectedTool = getSelectedTool();
shape = switch (selectedTool) {
case "CIRCLE" -> new Circle();
// 49 more lines here...
}
drawShape(shape, x, y);
}
Not only would it get more difficult to read the code, but also the test for handleClick() would have to test for all 50 shapes. If the instantiation of the shape is separated out into its own function, handleClick() can be shorter. If the factory function is injectable, the tests for handleClick() can focus on the coordination work that the function does: it asks the factory for the shape and draws it in the right place.
2. Allowing to reconfigure what kind of objects are created through Dependency Injection. For instance:
class CommentRepository {
constructor(dataSource, queryFactory) { ... }
getComments(articleId) {
commentsQuery = queryFactory.getCommentsQuery(articleId);
return dataSource.query(commentsQuery).map(toResponseType);
}
}
class PostgresQueryFactory { ... }
class RedisQueryFactory { ... }
Something has to map your click events to each of the button classes, and you have to test that code anyway. So I would just put that delegation in the Button class, I don't see the point in the extra abstraction to the factory yet. But to each their own I guess :)
Also the fact that you use the repository pattern, which I would absolutely never do even though I know it's fairly common, shows that we have different ideals (no offense). :)
Maybe you can go into more detail about what kind of modules you mean, but generally Dependency Injection allows using different implementations of a thing (module?) in the same place.
The most common use case for me is test doubles (mocks). People who are serious about tests usually use some kind of Dependency Injection.
It's the basis of democracy, and a healthy democracy does not reject a visitor just because they criticized its government.