Mikeal Rogers reached out last week to talk about Web Components, which surprised me, but his follow-up blog post is essential, timely reading. All of this was wrapped up in our project’s mantra: “say what you mean”.
Serving a website seems pretty simple: Send some HTML, the browser figures out what resources to load next. Then we wait patiently for the page to be ready. Little may you know, a lot is going on under the hood.
Poor tables. Where did they go wrong? After being the bread and butter of the web for most of its early history, tables were cast aside by many designers for newer, trendier layouts.
Object-oriented architects and developers have, over the years, learned many hard lessons about successfully designing systems with object-oriented programming. This has led to a plethora of ‘best practices’ that are painfully passed on from older to younger generations via books, lectures, cons
I am focusing hard on making AR for the web a reality. This repository is where i publish the code. Contact me anytime @jerome_etienne. Stuff are still moving fast, We reached a good status tho. So i wanted to publish thus people can try it and have fun with it :)