It is the true teacher who leaves the class knowing they have learned the most.

Tucson, AZ
Joined September 2006
Filter
Exclude
Time range
-
Near
Yes! Just a bit ago followed link in your bio :) LinkedData fascinates me and is also a specialized domain. I'm comfortable with specialists skilled enough to know what XSLT, RDF (and variants) is at all these days, much less work with LinkedData. This is very interesting, thxya!
2
My thoughts go right to security and generating code, even quality, clean, rigorous code, is in part contributing to reliance on tools over language skills. Know the code is a reasonable ethic for use at all. And a mantra since Perl/CGI server side era.
1
1
Node.js for compiling XSLT? I'm kinda startled but shouldn't be at all. Great to know about and must see this in action. Thank you Martynas!
2
2
Replying to @markgr
To not have a cohesive history as foundation for learning increases the pre-existing human loop of recreating the wheel. When professionals don't distinguish Internet from Web and vice-versa we pass on the idea they are the same thing. Sadly, loops seems a fixed human condition.
1
Replying to @markgr
I'm now 32 years in Internet tech, 35 total if we include BBSs. My first paid work with Internet Protocols was with Gopher and Veronica! Not many young'uns remember or know of Archie, Jughead etc. Well, outside the comics :)
1
Replying to @barneycarroll
They are in use, and a good person for examples is Steven Pemberton, who continues to speak on these topics and other XML/Semantic Web long-time influencers with W3C ties use them, mostly intranets. But XML's kids are alive. SVG anyone? :)
1
Replying to @mholzschlag @markgr
And thank you. It's difficult for me, and many, to take compliments, but for that book I'll take it. :)
1
Replying to @markgr
Wow, that book. Sybex Publishing. Rodnay Zaks is a hero for so many reasons. He apologized to me a year after it was written at the Waterside Conference (now gone, comp/tech book agency) as he felt it could have been marketed much better. It was one of my best.
1
Replying to @markgr
It's been an incredible journey for us all, and a feat of such collaboration across the world. I had to step out, then I was so disillusioned I sought other routes and find myself now coming back with deeper insights and awareness. I was so darned fortunate. Also, relentless ;-)
1
The reason is because we all come to Web from such diverse skills, interests, educational and professional pursuits. That we scaled to anywhere infrastructure and access to Web exists to meet needs in a global pandemic is our triumph! Early evolution always moves fast and varied.
1
8
As the Web comes closer to 30 years (a generation) as a person who wrote #HTML prior to the W3C's formation, I made all the terrible mistakes and spread some beliefs repeated so often many folks and I correlated to truths but weren't. Despair, self-blame, blame? Recently quashed.
1
1
8
Replying to @dboudreau
HA! Roll with it is what I'd do, and in a few days say "that was awesome of you" or some positive reinforcement. But my stepdaughter is a grandmother so what do I know from parenting? I did help raise my brothers. Mom was great for ethics & wisdom but not caregiving or affection.
Yes. And of course we saw CSS Frameworks emerge largely because var() - now CSS has functions. It's been a long-standing issue as it's emerging as hybrid declarative and function. Hmmm. Maybe that's a good thing? I tend toward declarative for markup and style as foundational.
1
YES. And...the @whatwg did include serialization to serve XML. They also prove that entire shifts in approach don't have to be limited to any spec/rec/standards org but independently driven. XML, XForms, XSLT remain in use. Medical documentation for example use XML ontologies.
This tweet is unavailable
1
6
Could the #DOM have scaled had we evolved XHTML served as application as XML/XHTML? Time and implementation factored into concerns, but I don't know. What do you think, in an era of APIs, functional vs. declarative approaches, componentization and #JS "first" and frameworks?
3
5
One of the difficulties in the history of #webdesign and #Webdevelopment as I seeit now has been the evolution of the document object model (#DOM), how it works, where implementations failed us and the media="all" principle at the emergence of devices we could not have predicted.
1
1
A little #Sunday fun for grunge lovers and guitar players. I'm gonna try out some of these riffs today myself. Rock on! #Music #guitar #Grunge #SundayFunday guitarworld.com/features/the…
1
Replying to @SailorJX
Is your Mom visiting you or vice versa? All my love to her and you too 😊 ❤️
1
1
Replying to @_mariov_
I do think that's true of all tools and platforms that generate markup. It's a long-standing cultural divide, as is the bang-on point you've made about HTML's lack of acceptance as a formal language, CSS too. Ironically, HTML does not 'break' code. Error handling is very loose.
1
Replying to @vingar
Indeed! I also think ableism factors in, the "tack it on" problem, no funds for user testing, reliance on audits without knowledge of why an error is an error, no edu rubric, and a technology problem with site/app complexities and more. Hence my ask :)
1