746 karma · joined September 5, 2017
1. Lots of external references to the GitHub repository would need to be updated. (I probably should have used a vanity URL for the Go module name, but it's a bit late for that now.) 2. They haven't started charging for open source projects yet. (Not that other behaviors of GitHub make me happy.) 3. Some of my usage involves projects where I'm a maintainer but not the project owner.
Wealth moves in lots of ways. Yes, as has been pointed out, we over value stock assets. When you own a significant percentage of a company, you can't just sell that ownership at the last trading price (the stock price would quickly crash). Wealth is also moved between national borders, allowing the wealthy to shop for the lowest tax location to stash their funds. Property can't be moved, but it can be financed with debt, making it taxed at effectively 0%. And the other side of that debt may just be an overseas shell company. There will be entire industries formed around avoiding a wealth tax, funded by the wealthy.
But probably the most capital efficient way to avoid the wealth tax is to buy politicians, influence the elections, and invest in lobbyist, which the wealthy do in the US to avoid taxes. Until money is removed from politics, I'm not holding out any hope that we'll find a way to tax the wealthy.
My best guess is that it will be integrated in the center tube. Buoyancy ensures the center of the ball is usually above water, and one end of the tube would always be above water.
I think the JS developers could take a lesson from the Go proverb. I often write something from scratch to avoid a dependency because of the overhead of maintaining dependencies (or dealing with dependencies that cease to be maintained). If I only need a half dozen lines of code, I'm not going to import a dependency with a couple hundred lines of code, including lots of features I don't need.
The "rule of three" helps avoid premature abstractions. Put the code directly in your project instead of in a library the first time. The second time, copy what you need. And the third time, figure out what's common between all the uses, and then build the abstraction that fits all the projects. The avoids over-optimizing on a single use case and refactoring/deprecating APIs that are already in use.
[1]: https://go-proverbs.github.io/ [2]: https://en.wikipedia.org/wiki/Rule_of_three_(computer_progra...
If the project is even slightly useful, but with a restrictive license, someone else will create an alternative with a free license. The community will quickly move, and the time spent trying to push a political opinion will be wasted.
In the long term, a free software license is always going to win. Even when it's unsustainable for one maintainer, the software remains free, and if it's useful enough, others will take on the maintainer role.
For sustainability, that's going to be a mix of lobbying your government, and companies realizing they need to hire developers because the open source maintainers aren't able to do everything for free. Just realize that governments are slow with conflicting goals. And companies will minimize their costs, leaving the average open source maintainer at the edge of being sustainable.
It's not that the goal is to write low quality code, it's that big businesses understand the sales cycle and how to maximize profits. If they over spend on employees, that cuts into their profits or causes the product to be too expensive. And if they spend the time to write quality code rather than developing features, they lose sales. Customers don't buy quality, they buy features at a price, and quality issues (like bugs) get thrown over the wall to downstream support staff.
As much as I dislike this, knowing how unstable it makes the overall software ecosystem, companies aren't wrong for making these decisions. The companies that choose differently don't become big businesses, they either stay small, get acquired, or go out of business.
This could have been a standard bar chart, allowing all the text to be easily read. And the colors could have indicated something like the average income to make it easier to see the outliers.
I've only worked a couple elections in a single US county, so I don't claim to be an expert. But the projects described by the company align with each of the devices we use in elections today. Using their software would be the equivalent of moving from MS Office to LibreOffice for operating the government. It won't solve everything, could have bugs, but there are some significant long term advantages, like not depending on a company that could go out of business for security patches.
The first device voters encounter is people working the electronic poll books. We still have a paper backup available, but prefer the electronic versions. First, they can scan the barcode on the drivers license for a quick check-in (usually). When person shows up at the wrong location, we immediately know without spending a couple minutes looking through the paper list. We can even tell them where their voting location is rather than "you're not on the list, we don't know why". When someone needs to vote from their car, we can take a poll book with us and check them in curbside, no extra back and forth. And anyone can check-in at any poll book, rather than splitting the list up by last name. If there is ever a hack of the poll book, changing the list of voters, that could have also been done with the paper backup, and that's why there's a provisional voting process.
After that, over 99% of voters get a paper ballot. They mark their oval with a pen, and take it over to the scanner. This is where the security happens. There's a paper audit of the vote, and the vote is anonymous, your name is not on the ballot.
Less than 1% of the voters ask to use a ballot marking device. They are there for ADA requirements, allowing people that have difficulty marking a ballot by hand to vote. They have headphones to read the choices if needed for the blind. When finished, their choices are printed on their paper ballot, human readable and verifiable, and taken to the same scanner used by other voters. Most people don't even realize ballot marking devices exist, I didn't before I started working the election, and I've yet to see anyone request to use it.
The next step is where people get suspicious. The paper ballots are run through a scanner at the precinct, by the voter. These are monitored by an election worker to ensure the voter scans their ballot, but we stand so we can't see the ballot choices for voter privacy/secret ballots. These machines output a tally in multiple forms at the end of the election, including multiple paper copies and USB drives. The various copies get split up and separately delivered, each by a team of workers, for both redundancy and to ensure no one person is ever alone with the results.
A very important process happening throughout the day is counting the votes. The number of voters that register in the poll books is compared with the number of ballots given out (when ballots are unwrapped, they are counted, and what remains at the end of the day is counted again), and also the number that went through the scanner. Things get complicated (I assume reports are made after an extensive search is done) if we are ever off by one ballot in those counts.
The common fear that someone could stuff the ballot box, even by an insider, doesn't match my experience. In addition to the counts above, multiple workers, from multiple parties, are assigned to each precinct. We don't leave the ballots at any stage unattended at any time.
At the end of the day, the tallied ballots are sealed in a box. All equipment is locked back up. And lots of items (tallies, USB disks, sealed ballot boxes, provisional ballots, etc) are returned by a team of people that night to the county government building. From there, initial counts are released and then the election needs to get certified. That's where my personal experience ends.
The certification process includes deciding which provisional ballots to accept, and then counting them. But it also includes audits of the equipment. And those audits are supposed to take some boxes of ballots from select precincts and run them through a different a scanner to verify the tally is the same. The precinct scanners are also audited before we receive them, which is visible because a permanent count is tracked on the machine that's never zero for us, even when it's a new machine that's never been used in a previous year's election. In addition to all those electronic counts on different equipment, some percentage of ballots is likely hand counted. This certification process all happens over the course of days, if not weeks, but the initial count is usually out in a few hours when a first team of workers brings back one of the two USB disks (along with other items).
There are ways to hack an election, but these electronic machines are at the bottom of my list. Someone would have to alter the counts from the scanners without adding or removing votes, in a way that doesn't get caught in an electronic or hand audit in the future on independent equipment, and doesn't get detected in an audit of the machine before it is placed in service. And the whole process is constantly watched by workers from more than one party affiliation.
Instead, if you wanted to hack the election, you'd first become a billionaire, and buy all the media companies to ensure the population only sees one opinion. Then you'd gerrymander the election districts so most elections aren't really contested. And in locations where it might be close, you fill it with ads and social media misinformation so that voters don't know what to believe and they follow the loudest voices that repeated the most. Not only is that a lot more likely to work, but there's no chance of any consequences if you get caught since it's not illegal.
Time has disappeared as people attempt to do everything themselves (work, cooking, cleaning, managing finances, etc) that may have been shared or outsourced in the past. But time has also disappeared into intentionally addictive apps on our phones. Every commercial game and social media site is designed to maximize your eyes.
Money seems to be ignored by the article, but every generation is worse off than their parents, as wages stagnate, housing skyrockets, student loan and medical debt keep going up, leaving less and less disposable income. With finances so tight, people cut back on group gatherings that have an associated expense (bars, concerts, etc). And raising children becomes unaffordable.
Personally, I blame billionaires, including their influence on tax policies, suppression of wages, and the creation of monopolies that push up prices. The elimination of sex is just one of many side effects of a much bigger issue affecting the working population around the world.
I blame smart phones, but blame is a strong word. We no communicate with texting, social networking, and many other means than in-person conversations. Teenagers are electing to get a drivers license later in life because they don't need a car to be connected to their friends. Less in-person interaction results in less opportunity for intimate interaction.
I blame the womens movement, and that's a good thing. More women are placing their careers first, and getting around to having a family later and later in their lives.
I also blame the economy. The recession ended technically, meaning we stopped getting worse. But our economy isn't seeing the wage growth that would indicate a prosperous environment that encourages recreational activities, and procreation.
User namespacing in docker is enabled at the daemon level, not per container, so all containers share the same offset. This would ensure that a root user in the container would escape to a different uid on the host, but doesn't prevent someone from moving sideways through the containers on the same host.
Note that enabling this will break the developer workflow of mounting files from the host into the container. I believe files will show up with the wrong ownership inside the container.
When you're a guest, you follow their rules. And their rules are fairly simple:
- Stay on topic
- Don't duplicate existing questions (look before you ask)
- Ask a specific question ("how do I fix it?" is not a specific question)
- Be polite (no one is getting paid to answer your question)
- Don't be a spammer (and avoid looking like a spammer)
With coding questions, it really helps to:
- Reduce the problem to a specific detail and be concise, if I haven't finished reading the question and have an idea of the answer in 30 seconds, I move on.
- Provide enough detail that someone else could reproduce your issue. So many people assume I have remote access to their laptop, not to mention what they are thinking inside their head.
- Write it in English, with punctuation, and capitalization. If there's a 10 line block of text without a single capital letter or period, I move on. Same goes for anyone with their capslock key stuck in the on position. I try my best to understand non-native English speakers, because I sure can't talk in their language, but sadly when there's a language barrier, I move on fairly quickly.
Employee: Does what the boss says, and works when the boss wants them to work.
Contractor: Does what the client asks them to do, but has the flexibility to do it on their own schedule and according to their own way. In the US, the IRS may want to reclassify you as an employee if you dictate too much of how the work is done.
Consultant: They review what the client is doing and recommends what they should be doing, often performing that work too. The key difference to me is the client accepts they may not be the most knowledgeable in what change they want to make.
To give examples for programmers:
Employee: works on a app in the office from 9-5 adding the features requested.
Contractor: adds requested features to the app.
Consultant: reviews the app and proposes some features to add.
That said, VM's have their place, and docker has the option to switch out backends. It's entirely possible to replace runc with some other tool that starts VM's instead of containers. (That's already happening today with Windows containers.)