gatmne

> Real life has product placement every time you go outside in civilization. I'm getting upset about you guys getting upset over something so trivial.

That's a false equivalence and a poor way to think about things.

People making those real-life product placements are not deliberately placing those products in view of others in exchange for money for the sole purpose of manipulating viewers to buy said product. I agree with the GP. At least with ads you know that you're being manipulated.

Could you give a short summary on how it works and how it avoids the pitfalls of bitcoin? I searched around in that link but couldn't find a paper describing the currency.

> now you've still got a window where something can still break everything while the filesystem is mounted read/write

I agree, but I'm also sure you would agree that a small window were things can go horribly wrong is much more preferable than than a perpetually open one (sudo and friends stand testament to this).

Please bear in mind that my comments are in no way an attack on your person or one directed at systemd. What I want is to find a workable solution or, at the very least, a compromise to prevent this type of issues from occurring. I strongly believe that protecting hardware is a core responsibility of any operating system.

Would it be reasonable for me to ask you to coordinate with all the major tool developers to gradually phasing out this behavior? As in both the filesystem and tooling continue to support both current semantics and a newer version until the older semantics can be safely disabled. This is how support tends to get phased out from the kernel for obsolete hardware.

Issues of this type have reared their heads many times already and I expect they will continue to occur if the underlying reason is not addressed. As the person who has the ability to do something about it, I urge you to reconsider.

alphaalpha101's now dead comment is reasonable: Denying justice in one out of ten cases is unacceptably high.

Couldn't the filesystem be mounted as read-only during normal operation, and only remounted temporarily as rw when necessary? Tools that write to this filesystem tend to have the necessary privileges to do so.

Leaving efi writable like this by default strikes me as a very poor and unsubstantiated design decision.

>End of discussion.

Science is not a static. Believing absolutely in a specific scientific result and refusing to accept that it may be wrong is as harmful to our advancement as those who refused to acknowledge that the earth isn't flat (they also used their limited understanding to justify their position).

To reuse your opening statement, you'd also win a Nobel Prize if you could conclusively prove that "your cell phone cannot cause cancer" and "any radio signal from a cell phone [doesn't]."

I've personally heard of two separate companies looking to transition away from Windows to Linux desktops for employees (one of whom I spoke with personally).

I think this might be an indicator of a larger trend that's at its tipping point.

Your argument sounds awfully like a "you're holding it wrong" argument. Demanding that people adapt to newer technology with more restrictions than previous iterations of the technology is a tall order that many will not entertain.

Rude people with poor manners is orthogonal to this issue.

Legality aside, whether sharing copyrighted information is amoral or not is determined by one's own values. Some people, myself included, see a person's right-to-share to be far more important to humanity than the authors ability to employ an ill-suited business model to profit off his or her work. There are many ways to generate profit other than to infringe on others' right to share. Humanity does not owe you a successful business model, and certainly not at the expense of it's right to share.

> What gives you the right to take someone else's painstakingly created artistic creation and give it away for free to thousands of people, depriving them of the exclusive right to sell their own work.

Users sharing copyrighted work does nothing to prevent authors from profiting off their work. Conflating sharing and business is what got us in this mess in the first place.

How's memory usage? I suspect many of us are anti-memory-guzzling rather than anti-Electron.

Good riddance. Shady tactics and holding web security hostage has no place in this industry. I'm amazed they lasted as long as they did.

When I read "absurdly fast", I expected to see some benchmarks against an equivalent SIMD implementation in C or at least a similar library in another language.

Please consider adding such benchmarks so that we can assess how fast this library really is when compared to other more established libraries.

How many of those deceased children would have survived the collision if no airbags were installed?

Self-driving cars preform predictably under a set of conditions. The primary problem arises when the car, for whatever reason, doesn't correctly detect that it's in an unfamiliar condition and continues moving as normal. Humans are intelligent enough to notice when something is "off".

For a machine as heavy, large, fast, and close as a car, limited intelligence is not enough.

This is interesting. Could you share more information about your setup: What operating system you use, Order of browser installation, and the name/id of the plugin would be a good start.

It would be even greater if you could upload a zip archive of the plugin.

So Google gets a free pass for collecting information the user explicitly opted not to provide because another company does it too?

I hope you realize how flawed that line of logic is.

I've encountered the same issue when I attempted to attach a "citation needed" tag to a statement that was blatantly false. The maintainer's excuse for reverting the change was that such a tag did not belong on such a highly visible entry.

These are people with whom you simply can't reason. Any argument you provide will be shot down with the absurdest of reasons.

Personally, I'm glad this happened to me. Like you, that experience cemented the unreliability of wikipedia in my mind.

That's a very good point. However, choosing to use a specific version already implies forgoing anything newer than the next release. This would include language features and crates (generally).

Thankfully, crates.io lists the dates next to crates so that users can select a version that is released before or during the release cycle of their compiler, thus guaranteeing compatibility.

They were shady bunch long before WoSign acquired them. I say good riddance to them and their practices.

I'd call it plausible deniability.

Debian packages integrate better with the system, are authenticated by gpg, and have at least one more critical pair of eyes on them.

If you're willing to stick with an older version of cargo and rustc, why not?

HTTPS also doesn't guard you against someone replacing the binaries on the server (e.g. what happened to transmission). It also doesn't protect you from misconfigured corporate or state level MITM firewalls that don't check certificate validity.

HTTPS is intended for transport security. Using it for package authentication is generally a mistake. That's why most distributions accept the additional complexity of PGP instead of only relying on HTTPS.

I'd downvote you if I could.

How would you know that the people buying groceries in your store are not criminals?

It's how a currency is used not by whom. I'd say guarding your life savings against the reckless actions of your government is a legitimate use case.

doesn't scale to all citizens of Zimbabwe :)

I imagine porn bookmarks showing up in an official screencast, presentation, or live product demo would do wonders to a company's image and reputation.

As an end user, I see it as a feature rather than a problem. Great library either way.

As an end user, I don't care what format Airborn uses internally. What matters is that I can interact with documents and files sent to me by other people, which are likely authored using Microsoft Office, Libreoffice, and Google docs.

As a developer, I would ideally recommend to look into using a custom internal representation for a document and developing converters that convert between your representation and various formats. This way you won't be hindered by limitations of a specific format.

However, if you lack the resources to develop and maintain these converters yourself, look into the feasibility of leveraging LibreOffice by using a preexisting format like WordProcessingML as an internal format. You can then use LibreOffice to handle the conversion between the various formats you want to support. The downside to this is that you'll eventually outgrow WordProcessingML if you want to support futures not supported by that specific format.

Also, consider placing print preview near the print command, or vise versa. Having two locations that contain the same type of functionality can be confusing.

Looks really slick!

You should consider adding word support. Support for office XML formats[1] are simple enough to hand-roll.

[1]:https://en.wikipedia.org/wiki/Microsoft_Office_XML_formats

This is exactly why I pirate what I bought when I want to rewatch it. Torrents are superior in every way so those box sets usually sit on the shelves gathering dust.

I don't know why media companies insist on punishing paying customers.

Because colors with components that result in the same intensity will be identical. Think a shade of red and a shade of blue that wined up the same shad of gray. The fact that both were distinct colors is lost.

By limiting the transformed colors to those a person is blind to, you limit the amount of information loss.

I think the ideal place to tackle this issue is as near to the display as possible. A screen purpose-built for the color-blind would be best, but redshift-esque software would do the job just as well.