Dzisiaj na sobotni początek weekendu zapraszam na coś odmóżdżającego, czyli pokaz zaspokajania potrzeb społeczności lokalnych przez rynek.
Oto TOP6 placów zabaw na nowych deweloperskich osiedlach. 🧵
The fact that so many web devs have rejected encapsulation, but then have to invent and use so many proprietary abstractions to make up for it still baffles me.
Web components devs have so many things so easy that it's actually disorienting to see how framework devs do things.
@CP_CNC @heavysaudio@Forbes I feel you. Mine appears about a week away. Having received the preparation notice on August 8th
They are coming eventually, fwiw
@rob_van_dort I must disagree on this. RDF can be great tool for transactional data processing
What is the alternative? Modeling software as we currently do and converting to graph?
That is just useless effort and constant model mismatch between.
Reduces RDF to being a data warehouse solution
“I actually do think that RDF-Star is pretty cool, and is going to make a big difference in the RDF world. I just don’t want to see it misused, as a band-aid to cover up poor modeling practice.” — Dean Allemang https://t.co/3zWKVQfTiX
The assumption that RDF is better just because it is flexible is dangerous and hoping that RDF-Star will be the solution is just naive.
Adding a new piece to an already flawed model will only makes things worse.
But that is not the problem of RDF nor RDF-Star
That is a really nice post by @WorkingOntology.
I so often say that RDF community must seek modeling inspiration in #DDD or #CQRS. The wrong graph is as bad as inadequate relational or object model
You data (and code) must represent the domain accurately...