I really like how they handled asking questions at the end. Anyone can ask a question. Questions are voted up. They are seen (and heard) by everyone. Every presentation should be done this way.
It's amazing how much our industry has changed. We spent the greater part of 14 years to influence the industry to think of good and practical design patterns so we separated css, js, html and now we're back to having everything in the same place. Yeah, let's listen to 23-year-old engineers because they're awesome. Man repeats history over and over again.
I think you and everyone else who separated css, js, and html (myself included) fully misunderstood the separation we were achieving. Separate concerns, not file types. Separate behavior.
It's been three years since you posted this comment. Did your opinion change? I think that HTML and CSS are not flexible enough to meet these days standards (of course, that depends on the project), but JS is. So I'm not surprised that we are joining HTML, CSS and JS.
I use template strings... this syntax does make sense when you want to inject a variable into a string. Far better than appending strings and variables with some +
I'm getting sick of all those workarounds around a platform which was never designed to be used in a way it's used right now. People are trying to get a whale flying and call out tons of helicopters to pull'em spending enormous amounts of processing power to get a ridiculously low perceived user experience in return. HTML and CSS are both obsolete ready for retirement. The only reason for why it didn't yet was that the DOM was everything the browsers really allowed to do so far, there was no alternative to the DOM whatsoever. The DOM worked just fine for static documents. CSS was quite fitting and did its job of styling arbitrary text document pretty well. Though times have changed, now we live in the age of the web becoming the worlds largest application platform, we're not only serving hypertext any more. Now we run all sorts of highly dynamic apps on the web-stack, both web apps (SPAs/PWAs) and hybrid apps (Cordova, PhoneGap, Ionic etc.). WebGL and WebAssembly extend the possibilities even further making the web become the "Platforma Ultima" running on all devices and browsers with a single code base. We need to get rid of the DOM and radically change the way we write GUI software for the web. There's a language called "QML" provided and maintained by the Qt Company in the context of one of the biggest C++ libraries ever created called "Qt". QML is a superset of JavaScript, it's a declarative GUI description language, highly dynamic, fully modular, easier to learn, well designed and freaking fast. We could leverage the power of WebAssembly and WebGL to create a modern DOM-alternative as both of those great technologies are already fully supported by all major browsers. And while I know there's a lot to consider like website indexing and introspection for example... fixing a 500 year old wooden cart with duct tape which barely solves our daily problems simply isn't an option in the long term.
![Lp. Сердце Вселенной #1 НАЧАЛО ПУТЕШЕСТВИЯ [Новый сезон] • Майнкрафт](http://i.ytimg.com/vi/380Q7gLWGvk/mqdefault.jpg)
I really like how they handled asking questions at the end. Anyone can ask a question. Questions are voted up. They are seen (and heard) by everyone.
Every presentation should be done this way.
A-men 🙏🏽
Smart guy, this package is pushing React development in the right direction 👏
Can't wait till it will be optimized!
It's already effective enough for production I think
Jesus Christ, I have bled my eyes out looking at this font.
It's amazing how much our industry has changed. We spent the greater part of 14 years to influence the industry to think of good and practical design patterns so we separated css, js, html and now we're back to having everything in the same place.
Yeah, let's listen to 23-year-old engineers because they're awesome.
Man repeats history over and over again.
I think you and everyone else who separated css, js, and html (myself included) fully misunderstood the separation we were achieving.
Separate concerns, not file types. Separate behavior.
The most boomer dev comment I've ever read
It's been three years since you posted this comment. Did your opinion change?
I think that HTML and CSS are not flexible enough to meet these days standards (of course, that depends on the project), but JS is. So I'm not surprised that we are joining HTML, CSS and JS.
Awesome
Once you start using it, there is no way to go back.
How to write :hover css
Can I mix styled components with react bootstrap?
IDs are bad practice -> Why use a class name once? Just use a JS ID!!
👏best logic
Think about when you have two or more Button components.
@10:00 i saw those ugly `` and ran away.... `} seriously ????
Just you I guess
Honestly if you're worried about a tag syntax you should probably just drop web development now
You're gonna be seeing that syntax all over the place soon. Look up "Javascript Template Literals"
I use template strings... this syntax does make sense when you want to inject a variable into a string. Far better than appending strings and variables with some +
why is this so disturbing then? with the babel extension for atom it even has proper syntax highlighting on the css
I use Vim and I have proper syntax highlighting. I just don't like using those annoying quotes in this context. It just doesn't feel right imo...
I'm getting sick of all those workarounds around a platform which was never designed to be used in a way it's used right now. People are trying to get a whale flying and call out tons of helicopters to pull'em spending enormous amounts of processing power to get a ridiculously low perceived user experience in return.
HTML and CSS are both obsolete ready for retirement. The only reason for why it didn't yet was that the DOM was everything the browsers really allowed to do so far, there was no alternative to the DOM whatsoever. The DOM worked just fine for static documents. CSS was quite fitting and did its job of styling arbitrary text document pretty well.
Though times have changed, now we live in the age of the web becoming the worlds largest application platform, we're not only serving hypertext any more. Now we run all sorts of highly dynamic apps on the web-stack, both web apps (SPAs/PWAs) and hybrid apps (Cordova, PhoneGap, Ionic etc.). WebGL and WebAssembly extend the possibilities even further making the web become the "Platforma Ultima" running on all devices and browsers with a single code base.
We need to get rid of the DOM and radically change the way we write GUI software for the web. There's a language called "QML" provided and maintained by the Qt Company in the context of one of the biggest C++ libraries ever created called "Qt". QML is a superset of JavaScript, it's a declarative GUI description language, highly dynamic, fully modular, easier to learn, well designed and freaking fast.
We could leverage the power of WebAssembly and WebGL to create a modern DOM-alternative as both of those great technologies are already fully supported by all major browsers. And while I know there's a lot to consider like website indexing and introspection for example... fixing a 500 year old wooden cart with duct tape which barely solves our daily problems simply isn't an option in the long term.
Really? You needed to swear?