Відео

Time passed. How popular is your automated versioning?

beautiful

You came up with a really nice toolset, but I'm not convinced of your arguments to use version numbers exclusively to machines for the sole purpose of reliably detecting "breaking changes". You are implying, this would make updating dependencies easier or even automatic. A version change of 5 major versions would then imply 5 breaking changes, the actual impact on your specific usage still may or may not be as big as a change of 5 minor versions. And I argue the idea to adopt release names for us humans is even worse, because they don't have an ordering! e.g. just try to put the following Ubuntu releases in the correct order from old to new: Precise Pangolin, Lucid Lynx, Saucy Salamander, Buster, Quantal Quetzal, Raring Ringtail But that's exactly what needs to be done to upgrade. It even gets worse the more releases you're currently behind.

Great I am really excited to comment on this

Not only a great hack but also sweet slides and animations

This is on a different level! Things like Yin/Yang and samsara come to mind..we are getting there

the lady asking questions looks bored like whatever.. she doesnt have any idea what threejs is all about.

3:03 I saw this on 3js site glad to see its owner

Ofc there are no questions, the presentation was perfect.

this is so idealistic beautiful, but can we be productive doing all these

a talk years ahead of it's time. well done!

Thx Matthew, reading and testing it...

:grin: :heart_eyes: :relieved:

Oh, something good (a commit message standard) actually came out of Angular! jk guys

great insight

OH ME AGAIN DO BETTERRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR

This far was the best on Functional UIs and Unidirectional Dataflow

Epic

Andre KILLING IT. Thanks CycleJS!

Those fruit skewers had a lot of vegetables on them... Poor separation of concerns IMO!

Thank you for sharing this!

Holy cow that was fantastic!!!

Is the audio off for anyone else??

So glad I checked this out

slide speakerdeck.com/aemkei/jsconf-budapest-invisible-code

retina screens density?? they have the worst ppi in 2016 :D

Un genio...

I like how ANDRE actually shows us how we interact with computer in simple diagram, great JOB.

developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/observe

Interesting.

I didn't know Budapest only ran at 15fps, neat!

awesome talk!

Both this video and your tutorial series on egghead.io were incredibly informative. Thank you very much!

I loved that template string thing, but its not working for me. Did you use any extension library to jquery or did you use an specific version of it?

lol who's the girl?

Deterministic isn't exactly what described, instead: given an input, the output is always the same. A system can be deterministic and time variant, such that time is also an input variable. But for time invariant systems you don't have to go back in time to repeat the experiment (since time is irrelevant for the output).

really nice and illustrative talk, such a champ

best

Very nice watch thanks.

Brilliant!

Is shader toy the same thing as three js? or is it another API?

Modules should NOT start at 1.0.0. Yes, the 0.X.Z epidemic has gotten out of hand, but that doesn't mean the solution is to start at 1.Y.Z. The relationship of X.Y (in regards to semver matching) is different in >= 1.Y scenarios than in < 1.Y scenarios, and for good reason. The public api might need to change in such a way that deprecated or added api methods alter the usage of methods that didn't change during the last update. This is common in pre-release scenarios prior to v1, whereas changes of that nature after v1 is release would require a new major version. The minor version increments in 1.0+ scenarios are assumed to NOT be breaking api changes, whereas prior to version 1.0, it's assumed that minor version increments ARE breaking changes. By starting your packages at 1.0, you lose the flexibility granted by this feature of the semver specification.

Mind blowing! Amazing! Fantastic!

The answer to the question regarding the future with, for example, Web components was so dodgy. The issue is not whether Web components will be the next big thing or not, but whether some future technology managing its own state will prevail, and how the "one state"-approach will deal with such an issue. Okay, so Mikael Brevik just won’t deal with it.

great talk! thanks

TL;DR: fruit sticks

This is one of the best talks I've listened to in a while. It's hard to find totally different perspectives than the ones we're used to, and this is one of them.