Um, @qyloxe - GraphQL is a bit more than your (sarcastic) example, because the query also forms the return result, which REST can’t do.
I don’t get the rest of your comment and to be honest, it’s not the discussion I wanted either. Thanks any way.
Yeah. Unfortunately, no matter what backend platform you decide to take, it will cause a vendor lock-in. There are no interop standards for backends or backend APIs, unfortunately. GraphQL comes close in some ways from an API standpoint, but what is happening to your data is always going to be proprietary to the system in use.
It’s actually being added to Vue 2.0 as a plugin!!! How cool is that?
Are you talking about the
bottom-slots prop? @christian_f
Good news! The object API will currently NEVER be deprecated!!!
So, everyone can relax and concentrate on the problem at hand. Making the new API more acceptable (either through concrete suggestions or teaching).
No. You can work with Unix timestamps, you just have to reformat the timestamp to a format the component will work with. The formatting Razvan linked to is for formatting the text output of QInput (which you’d need for making your custom date/time component).
Hi users of Firebase.
I’d like to ask you a couple of questions and hope for some great feedback.
What is it you like and/ or dislike about Firebase?
Have you found an alternative, which is better/ or worse? If so, please explain what makes it better or worse.
Looking forward to your replies and thanks in advance!
Nope. If anything, a CSS/ JS obfuscation system should be an app extension, which you can surely work on… to your heart’s desire!!!
See…that’s the FUD working. Read the RFC please!. Here are some points to thwart the FUD.
To be fully honest, I am also fighting the urge to be on the detractor side of this RFC, only because as an intermediate developer, the clear “constraints” of the options object based API helped me do fairly good Vue programming and helped me jump into other people’s code and understand it fairly easily. You’ll notice in the discussions a number of people also note these reasons for taking Vue over React.
However, as I gain experience, I see that the options-object based API has limitations. You can get easily 80 to 90% of an app done with it, but if things get complicated and larger, being able to better “split up” your code means better scalability and in the end, if done right, even better code comprehension.
You see, currently Vue with its options object is predetermining where certain pieces of an SFC’s code should go. data under data, methods under methods, computed under computed, watchers under watchers, etc. This in turn means, a feature of a component may be spread out over a number of options. Let’s say for a certain feature, you need data, some methods, some computeds, and a lifecycle hook or two. If you have a couple of other features mixed in that same component, then you are looking up and down the component in the different option groups to make sense of the feature. With the new API, a feature can be encapsulated in a single function and all of the necessary other “hooks” like state/value (instead of data), methods, computeds, lifecycle hooks, can be “bundled” up in that function.
The ability to better “compose” features of SFCs into their own functions means, a feature can be easily “broken out” into its own module and viola, you have a better more extensible Vue system (replacing mixins and their disadvantages). I read this article from Sarah Drasner and at the time I thought, “Yeah, whatever”. But now. Wow, it makes total sense to me. BTW, please don’t get confused by what Sarah writes. It was a pre-alpha POC that she refers to from Evan. The new API is different (but the concepts are the same). Read the RFC!!!
Sometimes, you have to trust those who know more than you to lead you in the right direction, that even the best people get things wrong and need to do things differently to make everything better for everyone. This is a situation like that.
And, that’s my take on the new API.
Ah. Ok. Hehehe… my_own_grave. Yeah. That’s a riot.