Skip to content

Instantly share code, notes, and snippets.

@dhindurthy
Last active March 20, 2019 15:53
Show Gist options
  • Save dhindurthy/5551053cbf071ca9bb4447f09299183c to your computer and use it in GitHub Desktop.
Save dhindurthy/5551053cbf071ca9bb4447f09299183c to your computer and use it in GitHub Desktop.
day 2 conf
import Ember from 'ember';
export default Ember.Controller.extend({
appName: 'Ember Twiddle'
});
<h1>Welcome to {{appName}}</h1>
<br>
<br>
{{outlet}}
<p>
The first conference day has started with many expectations on what the founders have to say about the existing state of the tech and its future. There were many familiar people, sometimes people you just know by their GitHub handle or as authors of blog posts or articles or of the various addons and so on. The keynote has started with an applause as the two founders have walked on to the stage covered in tomsters. Tom dale and Yehuda Katz announce the age of Ember to be 8 years old and a note on its evolution from its beginning. We were all asked to be welcoming to everyone and not make anyone uncomfotable and also make someone comfortable if you find anyone being aloof, I networked with a lot of people using that excuse later in the day. There was a lot of talk on how they try to maintain the values of the tech while adding and shipping features. Values have always and will always be in the context while adding any single feature. Not just following the trends but still maintain values and things like providing codemods and 6-week release cycle and so on. The stability versus progress has always been a constant thing across the entire evolution of the tech. While the release of 2.0, stability and coherence have been considered the most important rules as they did not want to sidetrack from their values. When you care so much about coherence, there could be pitfalls. Incremental changes could be a cause for this. There is a rescue for this and you all heard it already, it’s called Edition. In this situation, Octane Edition for the rescue. A lot was talked about the octane edition like its features and state of the art items being added as part of it and so on. The ergonomics and readability and the clarity that is being brought to the templates was highlighted. It might look like just syntax changes but the size of the application is being brought down drastically. The tracked properties were again praised this time like in yesterday’s training. The fact that the HTML-Template-DOM all the three will now look same has been highlighted since that has been a very unique thing for ember components all this time. There was some talk on future of ember from here on like the new file layout, embroider. Embroider is something for faster builds and optimizing assets, similar to what webpack and rollup do right now. The aim is to generate a final app.js and app.css irrespective of what the developers choose to have as part of their environments. I managed to say hello to most of the core team members I have spoken and associated with so far and also conveyed the greeting on behalf of the HoneyComb team to Dan Gebhardt, he asked me to reciprocate it to everyone. Of course you all migh have guessed, I was with Melnaie Sumner the entire time looking around into her slides and getting introduced to various Ember community members. Jen Weber, one of the the main people on Ember Learning Team and I got a chance to talk.I mentioned my concerns to her about how some parts of the documentation could be very tricky to understand and as the person who wrote it assumes a lot of pre-required knowledge about stuff, the one thing she said was - 'go ahead and send your additions to the documentation and reason it, we will add it in'. I am mentioning this because, again, I was encouraged and told to encourage others to contribute to the ember community. The source code itslef or addons or documentation or blog posts, anything is highly appreciated.
There were the talks from here on by various speakers and I will give a very brief intro on each of them.
Building a UI style guide in Ember by Frederic Soumare:
There was this idea of setting up a new landing page for centralizing all info about Ember at one place, I believe HoneyComb has beaten them to it with our own landing page. There was talking about having a strict set of style guide rules for any related websites and web pages as part of any ember piece.
Your desktop, the studio by Kate Ruggeri:
This talk consisted of how everyone should be helping each other and look for others to help for their coding practices and learning. There was a lot of art referral examples and this person was a very beginner level Ember developer and shared her thoughts on how to collaborate with the existing developers when you are new.
Comparing pattern in React Ember by and Preston Sego
This was a talk that was comparing React ways of doing with the new Ember octane and surprisingly it was not that too different. This was mostly code comparisons and seeing the lines of code.
Typed Ember: Strong Types for better Apps by James Davis
This was similar to the Typescript training yesterday, all about the types available as part of TypeScript. Like how we should not try inserting a square into a circle, assign a number value to a string and so on. It was a well detailed talk into Typescript and its conventions.
Crafting Web comics with Ember by Jessica Jordan: this talk has some interesting insights and ideas of doing comics with Ember and importance of color contrasting while creating interfaces. There is not much to communicate here unless you are into that part of development.
Anatomy of and addon ecosystem by Lisa Backer highlighted the addons out there and how they have been evolving and new ones being created every day.
Don’t break the Web by Melanie Sumner:
This has the important topic, accessibility. How we are our own enemies and should stop giving excuses as to why you are not having accessibility as a default when you create something in the web. How there are so many preventable errors being made in the web and many of them are common while using a website based on a framework. An example of how when you go to a bakery and order a cookie, the baker has sugar in cookie even though you didn’t ask for it. Similarly, you have accessibility in a website even though nobody asked for it specifically.
</p>
<br>
<br>
{
"version": "0.15.1",
"EmberENV": {
"FEATURES": {}
},
"options": {
"use_pods": false,
"enable-testing": false
},
"dependencies": {
"jquery": "https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.js",
"ember": "3.4.3",
"ember-template-compiler": "3.4.3",
"ember-testing": "3.4.3"
},
"addons": {
"ember-data": "3.4.2"
}
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment