Web-App visualized
-
Actually having fun with vue.js[^] (which someone recommended to Sander here in response to his frustration with Angular) - found this on their Discord-channel: Web-App visualized - Image on Discord-CDN[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
Actually having fun with vue.js[^] (which someone recommended to Sander here in response to his frustration with Angular) - found this on their Discord-channel: Web-App visualized - Image on Discord-CDN[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Cool, after converting my angular app to a react app to a knockout app I can now change it to vue. How do people get so good at spotting gaps in the market? A js model binding framework, where do they get their ideas?
-
Cool, after converting my angular app to a react app to a knockout app I can now change it to vue. How do people get so good at spotting gaps in the market? A js model binding framework, where do they get their ideas?
F-ES Sitecore wrote:
Cool, after converting my angular app to a react app to a knockout app I can now change it to vue.
:laugh: :laugh: :laugh: :laugh: You just read my mind.
Jeremy Falcon
-
Actually having fun with vue.js[^] (which someone recommended to Sander here in response to his frustration with Angular) - found this on their Discord-channel: Web-App visualized - Image on Discord-CDN[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Sascha Lefèvre wrote:
frustration with Angular
Keep in mind, I only have experience with Angular 1.x but some development principles will never change. And that is, anything gets easier the longer the you stick with it and master it. That's the problem with the web frameworks out there today... they change so much that nobody really spends time to learn one. I don't consider myself an Angular 1.x guru and I'd much more prefer React, but the more I used Angular in projects the more I figured out how to use Angular in projects. If that makes sense. I think the problem isn't so much the frameworks, it's that people don't devote the time required to actually learn one these days. We just fart around with it until it's time to move on to the next shiny one.
Jeremy Falcon
-
Actually having fun with vue.js[^] (which someone recommended to Sander here in response to his frustration with Angular) - found this on their Discord-channel: Web-App visualized - Image on Discord-CDN[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Out of curiosity, what do you like about it in comparison to React? At first glance it seems to have gotten rid of a manual
shouldComponentUpdate, which is nice. But if I'm knee-deep in React world right now, is there anything that would make me want to switch over?Jeremy Falcon
-
Out of curiosity, what do you like about it in comparison to React? At first glance it seems to have gotten rid of a manual
shouldComponentUpdate, which is nice. But if I'm knee-deep in React world right now, is there anything that would make me want to switch over?Jeremy Falcon
Sorry if I gave a false impression - I'm actually a complete JS-framework-noob :laugh: I meant to learn some framework and then gave vue.js the first go after seeing that recommendation. I dug out that thread from Sander for you in case you want to take a look: The Lounge[^] And maybe @Super-Lloyd (who gave the recommendation) can answer your question here :-D
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
Out of curiosity, what do you like about it in comparison to React? At first glance it seems to have gotten rid of a manual
shouldComponentUpdate, which is nice. But if I'm knee-deep in React world right now, is there anything that would make me want to switch over?Jeremy Falcon
What I like with VueJS it's almost the same as normal data binding in WPF! :)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Out of curiosity, what do you like about it in comparison to React? At first glance it seems to have gotten rid of a manual
shouldComponentUpdate, which is nice. But if I'm knee-deep in React world right now, is there anything that would make me want to switch over?Jeremy Falcon
Jeremy Falcon wrote:
At first glance it seems to have gotten rid of a manual
shouldComponentUpdateIf this is not exactly where you picked that up, here's a Comparison with Other Frameworks — Vue.js[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
Jeremy Falcon wrote:
At first glance it seems to have gotten rid of a manual
shouldComponentUpdateIf this is not exactly where you picked that up, here's a Comparison with Other Frameworks — Vue.js[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Yup, that's where I got that from. Gonna go check out Sander's post on it now...
Jeremy Falcon
-
What I like with VueJS it's almost the same as normal data binding in WPF! :)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
Oh snap.
Jeremy Falcon
-
Sorry if I gave a false impression - I'm actually a complete JS-framework-noob :laugh: I meant to learn some framework and then gave vue.js the first go after seeing that recommendation. I dug out that thread from Sander for you in case you want to take a look: The Lounge[^] And maybe @Super-Lloyd (who gave the recommendation) can answer your question here :-D
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Having read the thread, I totally agree what was said about Angular. It is overly complicated, but you can still make it do stuff the more you use it. Then again, I've only used 1.x so maybe it got worse. Who knows.
Jeremy Falcon
-
Sascha Lefèvre wrote:
frustration with Angular
Keep in mind, I only have experience with Angular 1.x but some development principles will never change. And that is, anything gets easier the longer the you stick with it and master it. That's the problem with the web frameworks out there today... they change so much that nobody really spends time to learn one. I don't consider myself an Angular 1.x guru and I'd much more prefer React, but the more I used Angular in projects the more I figured out how to use Angular in projects. If that makes sense. I think the problem isn't so much the frameworks, it's that people don't devote the time required to actually learn one these days. We just fart around with it until it's time to move on to the next shiny one.
Jeremy Falcon
Jeremy Falcon wrote:
I think the problem isn't so much the frameworks, it's that people don't devote the time required to actually learn one these days
Jeremy Falcon wrote:
they change so much that nobody really spends time to learn one.
There in lies the problem for me, I don't do a lot of web dev, its not something I enjoy. However, when it takes a year for the web developers to complete a website, I get asked to go "bang something out". I have looked at some of the newer frameworks, and they just seem to make it more complicated than dropping a few controls on the screen, adding in my data layer, and binding it back to the database (webforms). Not that I wouldn't mind learning something new as I am sure at some point web forms will go the way of the Windows Phone. Just don't want to spend my life in some never ending cycle of framework of the minute. :sigh:
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
-
Jeremy Falcon wrote:
I think the problem isn't so much the frameworks, it's that people don't devote the time required to actually learn one these days
Jeremy Falcon wrote:
they change so much that nobody really spends time to learn one.
There in lies the problem for me, I don't do a lot of web dev, its not something I enjoy. However, when it takes a year for the web developers to complete a website, I get asked to go "bang something out". I have looked at some of the newer frameworks, and they just seem to make it more complicated than dropping a few controls on the screen, adding in my data layer, and binding it back to the database (webforms). Not that I wouldn't mind learning something new as I am sure at some point web forms will go the way of the Windows Phone. Just don't want to spend my life in some never ending cycle of framework of the minute. :sigh:
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
Oh come on, spinning around in circles is fun man. #sarcasm I still feel the same away about Node et al since it's radically different too. The openness of the web is a double-edged sword. 'Fraid only way to deal with it is one step at a time.
Jeremy Falcon
-
Oh come on, spinning around in circles is fun man. #sarcasm I still feel the same away about Node et al since it's radically different too. The openness of the web is a double-edged sword. 'Fraid only way to deal with it is one step at a time.
Jeremy Falcon
-
Jeremy Falcon wrote:
'Fraid only way to deal with it is one step
Nothing like tip toeing through the mine field... :laugh:
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
:)
Jeremy Falcon
