It solves the problem of scientists that have done experiments, but have no way to share and have their experiments and have them validated using the same procedures and programs. At least that's the way I understand it.
This is pre-alpha. They just finally opened the repo to the public for contributions. I don't believe they are replacing any of that, just not implemented yet.
I think the goal is feature parity. It is going from 2-3 so I would expect some backwards incompatibility. I know they plan on shipping a separate compiler just for IE11 if you need support for that browser. The new reactivity model is driving that decision.
> Yes. However, one thing you fail to see is that it directly compiles to function calls.
I understand how JSX works, stop patronizing me. The only thing I fail at is seeing how any of your examples are complicated or have magic so deep that you need to continue to burn Vue at the stake for. In fact, I find your Vue template examples completely intuitive and easy understand with minimal time invested in learning how Vue templates work. It's my preference to spend a little bit of effort up front learning how Vue templates work in order to have clearer separation between business logic and templates.
> Look, it's exactly what React without JSX is [3]. Only in React you don't need to invent a custom scripting language and binding rules.
JSX is a custom extension to JavaScript. It's not part of JavaScript or intended to be part of the spec or implemented in browsers. In fact, you have to use some sort of transpiler in order to use it. So, it's not just JavaScript.
There's really nothing that complicated in here, if you're familiar with Vue. In fact, it's really easy for me to see what's going on at a glance in one place, which is my personal preference. From my own experience, that's rarely the case when working with React the way JSX tends to get broken up because it doesn't have something as simple as a standard if conditional statement within JSX itself.
I've never claimed you do not need to learn anything when working with Vue templates, you need to understand how the system works, but it took me all of a few hours to understand. The features and benefits that I prefer over React/JSX make that worth it to me.
I've read this before. Vue is a framework. It also has a templating system that is not JavaScript, it's valid HTML with attributes that tell Vue how to bind to it. It's really not that difficult.
> Vue's templates are not HTML-compliant. They are just that: templates. That get compiled to JS anyway.
Sorry, but you're wrong here. They are valid HTML.
"Vue.js uses an HTML-based template syntax that allows you to declaratively bind the rendered DOM to the underlying Vue instance’s data. All Vue.js templates are valid HTML that can be parsed by spec-compliant browsers and HTML parsers."
IMHO only the simplest of components featuring JSX that don't read like a spaghetti PHP coding nightmare to me. For the small number of times you actually need the full power of JavaScript you could also use JSX in Vue with a render function if necessary. I personally prefer to keep my templates and logic separate when possible.
> It's not a webpack add-on. It's a part of Vue's templating engine that is essentially CSS-in-JS, they just give you a template to work in.
No, it's not part of the template engine, it's part of vue-loader which is used by Webpack to create single file components.
> and has a very wierd concept of how objects work in JS.
What is so weird about it? I personally find Vue vastly more approachable than React is, especially once you have to start writing all the plumbing to get all the libraries you need to go along with it to write a real world app.
> ] It's a templating system with its own rules and mini-DSLs that ends up being compiled into JS.
Vue has the option to use Webpack to compile html compliant templates to JS functions just like JSX (which BTW is not JavaScript and not HTML compliant and is also a separate concept that needs to be learned as well.)
CSS is just another add-on through Webpack when using Single File Components. Nothing really ground breaking here except for the fact that it creates a nice separation of concerns. This is especially true on teams with junior devs or designers. Or with a team that works on a site with mixed MPA and SPA features.
You can just use DOM templates with Vue.js. Basically write your HTML the way you normally would and add the Vue.js attributes that tells Vue what to bind with. If JavaScript is disabled you just have plain HTML. It does scale up to doing a full SPA with single file components and compiled templates with Webpack.
It's too bad SawStop saws are incredibly expensive (and going up in price Feb 1st.) They are definitely worth it compared to the cost of an injury, however many people are priced right out of owning one.
I'm skeptical that this book will ever be finished. The last time I bought an unreleased book authored by John Resig it took two and a half years before it was published. If I remember correctly another author had to take over in order to complete it. I'm super interested in GraphQL, but I wouldn't consider purchasing this ebook until it is 100% complete.
Vue can be used to enhance web pages, but it works equally well if you want to build a large application. This was one of the design goals. Something that you can start small and scale up with that works equally well for both. If you use the Vue CLI you can have a setup with a router and build tools and setup something very similar to create react app.
I wouldn't mind a slightly smaller cheese grater truth be had. It's a heavy beast of a machine and takes up a fair bit of space. Although it doesn't really move much and I don't notice it too much sitting next to me. Top specs and upgradability are my top feature requests.
Great. Now they need to reintroduce a MBP with top of the line specs and without the stupid touchbar.
Snark aside, I have a mid 2010 mac pro at home that is still going strong (due to upgrades, SSD, more RAM.) However, I would like to get a new GPU for the machine, but I'm not about to spend $500 on a better, but ancient GPU that's compatible with a 7 year old machine. I've been wondering what my upgrade path would be. No way in hell I'm buying a trashcan mac without any upgradability. And I'm certainly not going to buy a MBP with the touchbar (I need a real escape key) and under powered specs.
I'm really hoping this is true, otherwise in the next year or two I'm going to be seriously considering building a PC like I used to and deal with Windows 10. The rest of my family uses apple and it makes support for their devices easier being on the same platform, but I need better performance for photo editing and audio production.
Yes I do and the escape key. I use the escape key all the time to cancel out of modal windows. I also use the function keys quite frequently when using Intellij/Jetbrains products as they have quite a few shortcuts bound to them in the default config.
You can even have a notebook run in a cluster.
http://ipython.org/ipython-doc/dev/parallel/