152 karma · joined March 23, 2019
At higher scanning rates the achievable angle of deflection with commercially available MEMS scanners (the type of scanner used in the 720p pico projectors) is too small to be useful.
The other class of laser scanner potentially relevant to practical high resolution projection are the solid state laser scanning systems, which suffer from limited angle of deflection AND a limited number of resolvable angles.
60fps 8k is achievable with a mechanical system using a turbine-driven polygonal mirror. Unfortunately, the precision machining, several tens of kilowatts input power and requisite hearing protection present some obstacles to commercialization.
As a general rule, if a raster laser projector claims to achieve much over 720p they are either lying, mistaken, or out of your price range. It requires an order of magnitude increase in scanning rate to scale from 720p to 8k. The next incremental milestone for this sector is "actually achieving 1080p instead of just lying about it".
I appreciate that you are not making that claim and I'm glad that we agree. However, that "WireGuard is faster than IPsec" is exactly what the authors are claiming without qualification, and supporting with controversial data, on the official website. As such I believe examination of the claim is justified.
> Unfortunately we live in the real world where this assumption doesn't hold true.
Yet we are in a rational discussion of the merits of the two protocols, in which outliers that introduce additional variables should be first discovered, then examined individually, rather than dismissing the first order effects out of hand on the supposition that outliers influenced by additional variables may exist.
It's actually quite simple under the hood and frankly can't be made much simpler while still achieving the security objectives. The often wildly overcomplicated configuration syntax together with subtle differences in implementation defaults, cipher and parameter naming are what I see creating challenges for vendor interoperability.
It is also possible to recognize without trying WireGuard that it has more protocol overhead, access to fewer ciphers than IPsec, and access to no ciphers that IPsec does not support. This means that IPsec encryption will be as fast or faster in all cases and IPsec framing will be more efficient in all cases, all else being equal.
It is not, for example, faster than the literally dozens of ASIC implementations of bump in the wire IPsec that scale to line rate n * 100Gbps. It's not even faster than kernel IPsec on architectures which support AES with dedicated instructions. Incidentally, this is the default configuration for Strongswan on supporting hardware.
In fact, the benchmarks published prominently on the WireGuard website (https://www.wireguard.com/performance/) are completely nonsensical and compare the clients under circumstances where neither should be bottlenecked and where it is known the underlying algorithm with AES-NI is considerably faster than chacha20-poly1305. Yet, they find that WireGuard achieves higher throughput (magically exceeding line rate, in fact!) in spite of more header overhead and a slower algorithm. They find WireGuard is lower latency by something like an order of magnitude more than the actual single packet latency for an IPsec compression with AES-NI. When I find the official hard data about a product to be complete bullshit, it raises a lot of red flags for me. Either the authors of this marketing fluff are completely ignorant or completely dishonest, but in neither case does the material motivate interest in the product.
It's extremely debatable that it's more secure than common IPsec implementations. The core IPsec implementation is a very simple state machine which has been under review by virtually everyone with an interest in secure comms for decades. It's very wishful to suggest that some hipster shitware that got puked out a few years ago because Strongswan was too hard is "more secure".
If you're in the position of designing a secure interconnect for something more consequential than a friend accessing your home media server and do not have the luxury of abdicating responsibility for the outcome, the fact that the client is easy to use is perhaps the single lowest bullet point on your list of priorities. Interoperability with existing software and hardware, flexibility to adapt to different customer environments and requirements, maturity and proven performance all rate much more highly. IPsec is and has been the go-to for that, while WireGuard is drenched in hype and bullshit and completely unproven.
If the option to resist the imposition is not presented, the question of consent has not been called.
The act occurs without consent but also without dissent.
When likely future intent is made known by past actions, the question of consent has been called and may be answered.
You raise an interesting challenge and it is a scenario I haven't considered before. I am happy to discuss it and any other issues you find with my morality, but I would prefer if we could please agree that language is an approximation of meaning, attempt to seek clarity before semantic assertions, and that I be allowed to speak for myself.
I find the post you're responding to be an amusingly phrased and more reasonable interpretation of democracy than most, and will with the remainder of my post attempt a proportionate defense from the imposition of will you intend in representing your self-interest as moral truth.
> can you see how that is not the same thing at all?
I believe this phrasing is unnecessarily dismissive of the viewpoint you are responding to. A micro-imposition, if you will.
> [Democracy] also opened up the field for consent on all sides
Democracy does not transform or create consent, consent existed in the same form prior to democracy. If you do not resist an imposition of will, you consent. There is one point of the original post I will disagree with: the vote does not impose on the governed in democracy, the people with "swords/bullets" who find that vote to be an agreeable imposition and resistance to be a disagreeable imposition do. Voting may often be an adequate proxy for the use of violence to coerce, but it is nothing other than a statement of one's willingness to use violence or see violence be used for coercion towards a specific end.
> Democracies with minority protections (aka one of the ways we differentiate democracy from mob rule) make true win-wins possible
I disagree. Democracy enables aspects of reality to be classified by criteria which do not convey moral meaning, and for those classifications to become parameters in the function that allocates violence for the purpose of coercion. The closest approximation of a "true win-win" within the constraints dictated by reality is when all parties minimize their imposition. Voting in regards to which arbitrary classification of reality shall be imposed on in the interest of some other arbitrary classification is a statement of violent intent which is so far detached from moral meaning it amounts to a random walk in that metric space.
> There is not way to wage a war in such a way that all sides win, a way to fight in a way where noone gets hurt.
It is not possible to exist in such a way that all things which do exist or could possibly exist win. Physical reality is inherently adversarial: conservation of energy suggests that a quanta of energy released by one process can only and will only be consumed by exactly one process. One may strive to maximize the entropy of reality, to allow the largest number of contending states to be occupied, and this is moral. Democracy, again, moves with no discernible direction in relation to moral meaning.
> The first sentence describes the removal of democracy. The second claims that this is evidence for democracy not always being good for the people. Compared to ruling by force, yes, democracy is inherently good for the people
Democracy is exactly ruling by force. Resist the imposition of the will of the majority, or something which is fraudulently misrepresented as the will of the majority unopposed, and you will be coerced by violence. The only thing that is inherently good for the people is for every individual person to minimize their imposition to that which is necessary to survive and seek truth, and only then if that does not require a greater imposition than they would resist. Anything more is an immoral act of self-service.
However when a person's point of view is objectively fallacious (Evangelical Christians, national socialists) and advocates doing harm or passing fallacious moral judgement of a class of people (Heathens, hedonists, homosexuals, jews) and that class of people includes you I do not believe you should ever be expected to tolerate or abstain from challenging that point of view.
If an individual is advocating harm to others and can't withstand scrutiny of their agenda then that's their problem. I don't see this any differently than suggesting you should avoid challenging sexual harassment or physical abuse in the place of work in order to minimize friction. Certain "points of view" should encounter friction at all times and from all sides, because they are reprehensible.
If you are able to build up a significant velocity in horizontal direction, you might in the final moments before landing be able to shift posture to an aerodynamic form which converts your horizontal motion to a force in the positive vertical direction with a drag force in the negative horizontal direction, reducing both your horizontal and vertical velocity for a brief period.
The notion reminds me of how helicopters land in the event of an engine failure, a regime of flight called autorotation. After engine failure the main rotor begins to be driven by the airflow. It is set to maximize drag, impart a horizontal velocity (I think? I am not a helicopter pilot, this is not helicopter landing advice), and primarily maintain rotational inertia -- more like a glider with a spinning wing than a rock falling from the sky as one might assume. In the moments before landing the rotor angle of attack is increased, and the rotational inertia is converted to brief surge of lift allowing the helicopter to touch down practically as normal.
The question becomes, what posture should one assume to maximize lift to drag ratio? It seems like something edge on, with the body in a flying wing formation essentially, could come pretty close to offering enough lift to make survival feasible if you could somehow manage to transition to that orientation through what appear to be aerodynamically unstable configurations which would oppose that. And the side-on orientation does not seem like a good posture for the actual impact, so you'd need to quickly shift back to the "shock absorption" posture and if the flying wing orientation had the intended effect you would not have much airflow to maneuver with so it would presumably have to be something more like a zero-g change of attitude (https://youtu.be/960CsCgI6Jg?t=105).
I'll be sure to give it a try if I ever end up falling out of an airplane and let everyone know how it goes, though.
The standard distribution of Golang has been historically non-receptive to the notion of providing intrinsics, the capability for inlining assembly function calls (note: not inlining assembly source), and in general proposals to trivially extend the language or standard library to address performance concerns whose need would not be considered controversial in any other context (I'm not talking about generics, here). In quite a few cases it has been communicated that certain features will never be made available because fuck you that's why, although in recent releases there has been a trend of backtracking on these "promises" under the onslaught of justifiable need.
These conscious "trade-offs" severely impact the specific cases where dedicated hardware instructions exist that are capable of providing sometimes orders of magnitude improvement but are not yet encapsulated by builtins or blessed with snowflake exceptions in the standard library.
Your options for implementing the kinds of compute-bound tight loops which benefit from specialized instructions in Golang are: 1) Write the whole thing in Golang assembly so you only pay the price of a function call once on entry (Let's call this 0.4ns for a 2.5GHz CPU using a single cycle latency instruction per operation) 2) Use hilarious bit twiddling hacks that the compiler can inline which perform the equivalent operation with 10-20 cycle latency (4-8ns) 3) Use a Golang assembly library which presents a single invocation of the hardware instruction as a Golang function and have all of the gains absorbed by the function call overhead (~10ns) 4) Use the primitives available via the standard library to implement the function (as a general rule not worth wasting the time to optimize and comparatively benchmark for this class of function) 5) Fork golang, implement what you need, offer it as a pull request, and have upstream tell you to just go back to C or assembly if you care about performance (Literally.) 6) Target gccgo/(llgo?) (much better for this specific class of function but less performant in other areas, a different set of trade-offs).
In short: optimization trade-offs.