dahauns
Joined 13 years ago
Joined 13 years ago
I know I'm a rather late here and essentially just ranting a bit while waiting for github to finally do as it is told, sorry :)
But that's exactly the (frustrating) issue - as I've laid out in another post - no, they don't work as well. It's not about others being better in every aspect (yeah, they usually aren't), but about expected baseline features that are simply missing.
(And to be honest, I've become a bit jaded regarding the resulting discussions :) No, that thing doesn't just suck in general. No, it's not impossible. It's Apple's implementation. External Display Support flashbacks incoming ;) )
I do not have to that even with my ~30€ JBL buds.
This statement only has any merit if your usage pattern is 100% limited to Apple devices, otherwise it falls apart.
It would be fine if they fell back to "at least as good as the competition" in a mixed use case, but in the mixed case they are worse than what even low-budget BT buds often offer (no BT Multipoint, no ear recognition, etc., hell, not even a battery level over BT...and even pairing/reconnect is often a crapshoot reminiscent of the state of BT Audio 10-15 years ago). It was honestly a really disappointing realization.
The "office building" setting meant resticted areas, sure, but it features TONS of reflections - especially transparent reflections (which are practically impossible to decently approximate with screen space techniques).
Oh, and: The Northlight Engine already did more than most other engines at the time to get "90% there" with a ton of hybrid techniques, not least being one of the pioneers regarding realtime software GI.
It's about having a high degree of systematization and standardization and detailed guidelines around command structure and behaviour. The same with parameter naming and handling. About actually being able to work with typed data at input/output/pipes instead of only raw bytes, with all the benefits that entails (and a "standard library" of cmdlets/modules liberally making use of that). And so on. Having the whole .NET runtime available as a first-class citizen if needed is a nice bonus as well.
Don't mistake lack of familiarity for obtuseness.
$file = Get-ChildItem "C:\some path\having spaces.txt"
Write-Output $file.DirectoryName
Write-Output $file.Name
Write-Output $file.BaseName
Or if that's still to verbose: $file = gci "C:\some path\having spaces.txt"
echo $file.DirectoryName
echo $file.Name
echo $file.BaseName
People should really get over their aversion against powershell.Just because it's the mess we are all intimately familiar with, doesn't make it less of a mess.
Weeell...here's the thing. Erm. You didn't push through to the end. You just got the "bad" ending.
The game does very much have a proper ending, and reaching it is surprisingly straightforward.
You just have to beat it twice.
https://github.com/eu-digital-identity-wallet
Everything's very much WIP, but it aims to provide a detailed Archictecture and Reference Framework/Technical Specifications and a reference implementation as a guideline for national implementations:
https://github.com/eu-digital-identity-wallet/eudi-doc-archi...
https://github.com/eu-digital-identity-wallet/eudi-wallet-re...
https://github.com/eu-digital-identity-wallet/eudi-doc-stand...
You'll find several (still evolving) Technical Specifications regarding ZKPs (including a discussion area) in the latter.
...erm.
To adress the elephant in the room: Who exactly is supposed to be verifiable to never have looked at the original source? You or the LLM?
Works just fine here (1920x1200 125%, 4K 150%, 1080p 100%).
It really pains me to be that cynical, because I do find their products incredibly fascinating and inventive. But for anything but their lowest-end toy products the design aspirations - and boutique price tag - clash hard with the reality of their quality track record.