This is doubly beautiful.
FIRST, because CD Projekt Red put actual #manhole #specification markings on manhole covers in the #game #Cyberpunk2077.
And SECOND, because they used the wrong specification and a German player NOTICED.
#specification
2 posts2 participants0 posts today
Your task is not to foresee the future, but to enable it.
— Antoine de Saint Exupry
The secret to building large apps is never build large apps. Break your applications into small pieces. Then, assemble those testable, bite-sized pieces into your big application.
— Justin Meyer
Replied in thread
@riley Also using visible light for FSOC avoids all the "spectrum compliance" and "licensing" issues whilst making it impossible to ban, unless one were to ban colour filters and lights!
Having access to said #specification for #IrDA is also beneficial for #RetroComputing as IrDA was a modestly successful tech and could thus be used for #bridging...
en.wikipedia.orgVisible light communication - Wikipedia
Replied in thread
@troed Yeah, #IrSimple is AFAIK basically is a 115200 baud half-duplex serial transfer.
- Problem is the #Specification has been #paywalled and the original consortium website is long gone with the domain
irdajp.infonowadays used by some #scammers / #DomainSquatters...
web.archive.orgIrDA Specifications
Walking on water and developing software from a specification are easy if both are frozen.
— Edward V. Berard
Your task is not to foresee the future, but to enable it.
— Antoine de Saint Exupry
Replied in thread
@mrchrisadams Yeah, #S3-Style #ObjectStorage is nifty in many places.
- It's kinda good that whilst #amazon is a bad company, they basically had to "#OpenSource" S3 as a #specification so anyone would even bother to implement it at all, and basically every #hoster nowadays offers that with bit & second-precise billing if wanted, as it's more convenient to #FTP and other #quota / #fixed storage...
Replied in thread
Looking for feedback on the current state of the OWTS-01 #specification (Guidelines for Open Web Technologies) as well as the certification process and tiers.
Specification: https://github.com/open-webtech/owta-publications/blob/main/specs/drafts/owts-01.md
Certification Process and Tiers: https://github.com/open-webtech/owta-publications/blob/meta/owta-certification/meta/certification.md
#Consequential:
"#Browsers provide critical #PublicInfrastructure to over five billion people. To cover the high cost of maintaining such complex feats of engineering, #browser vendors and #searchengine providers have improvised a system in which money is levied from search revenue and distributed to browsers. This #specification…formalizes a browser/search #levy that improves on the current one and addresses its shortcomings."
darobin.github.ioWeb Infrastructure Search Endowment (WISE)Standardizing browser & search public infrastructure.
#specification pattern versus eliminating conditional logic via polymorphism.
Discuss.
We have a database "rules engine" that I greatly dislike. The maintenance of it is especially troubling.
It is essentially a huge Conditional statement. Which leads me to Martin Fowler's solution: conditionals as polymorphism.
Which led me to use JSON schemas to define the polymorphed classes at runtime. But #polymorphism in #json isnt quite that simple.
I've also considered the #specification pattern. But maintaining specifications is the issue.
Still thinking.