Does "VM it" work? I mean, there is PCI and USB-passthrough in qemu, so this might be an option, especially since VMs are easy to sandbox (easier than physical machines where someone might simply plug a cable in so he can watch YouTube, for example).
That is a pretty cool way to implement regenerative breaking that I honestly never thought of (even though the tram in my hometown feeds energy in the grid when driving downwards)
> This is the first time in my life I have ever heard this phrase, in all its privilege-dripping glory. The more you know, I guess. Carry on.
"Besenrein" is a pretty normal thing if you rent out something in Germany. In fact, every holiday-house-rental and every rented flat / house I ever helped moving, this was the standard.
Even when we went to Switzerland and France - so isn't this a thing at all in the US?
Fuzzing the votes like this is cheap for reddit, but makes it more expensive for the spammer.
The best spam-filter is tricked by a hand-crafted, personalized email that is well-targeted. However, the cost of these are insane compared to mailing the same thing to hundrets or thousands of users. So anything any spam-filter ever does is making spamming less lucrative for the spammer, and fuzzing does that.
"To report a bug please open the FILE menu, and click on "Send feedback". Ta-dah.
Support is still shit if they can't do that. In a software-company everyone should know the rough path to actually report a bug, or what looks like one.
> organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations
Open source has a very different communication structure than a company. While the big three (MS, Google, FB) try to work towards good inter-departmemt relations, it is usually either
- a single person
- a small group
that are the gatekeepers for a small amout of code, typically encapsulated in a "project". They do commit a lot to their project, yet rarely touch other projects in comparision.
Also, collaboration is infinitely harder, as in the office you can simply walk up to someome, call them, or chat them - in OSS a lot of communication works via Issues and PRs, which are a fundamentally different way to communicate.
This all is reflected by the structure of how a functionality is managed: Each set of gatekeepers gets their own repository, for their function.
Interestingly this even happens with bigger repositories: DefinitelyTyped is a repository for TypeScript "typings" for different JS libraries, which has hundreds of collaborators.
Yet, if you open a pull-request for an existing folder the ones that have previously made big-ish changes can approve / decline the PR, so each folder is its own little repo.
No, but I believe that not being able to figure out the runtime-complexity of easy algorithms hinders you as a programmer.
Being able to reason about these things is important for a lot of different tasks that can and will occur in most projects, and are very crucial for some.