SS uses it internally already :> see
It's a learning curve for sure, and it can be daunting. But generally I find it's not too bad. Would you like help with something?
@Terry Apodaca what ails you?
I think he’s at the I’m too old for this shit wagon at the moment 😄
I feel that can be a common sentiment. Sometimes I feel like that too. I notice tweets from old colleagues along the same lines :P
Yesterday I logged into twitter since quite a while, discovered there's a new Raspberry Pi out. Nice. More RAM, more processing power. YAY.
So I think to myself
>Oh, so maybe, just maybe, it might have enough power to run a single modern day website?
I don’t know how to use React, and get the sentiment completely as well. But also understand why it exists. I’ve worked with Vue though, pretty cool
yes, I am still old school with a lot of things. You all should remember how long it took me to accept Composer, and then how long it took me to learn SASS and other "tooling" things.
I checked a pretty base install of SS yesterday. Granted it was a dev install (so contained a lot of JS
src folders), but I excluded all
Webpack is my current demon I need to face and conquer
I totally get it @Terry Apodaca - I resisted the scss sass less whatever train for a long time too. But I just have to accept it, this is where we are.
Who moved my cheese, etc.
Who Moved My Cheese? An Amazing Way to Deal with Change in Your Work and in Your Life, published on September 8, 1998, is a motivational business fable. The text describes change in one's work and life, and four typical reactions to those changes by two mice and two "little people", during their hunt for cheese. A New York Times business bestseller upon release, Who Moved My Cheese? remained on the list for almost five years and spent over 200 weeks on Publishers Weekly's hardcover nonfiction list. It has sold more than 26 million copies worldwide in 37 languages and remains one of the best-selling business books.Hide attachment content
I still don't fully agree with the modern tooling, but I get it.
Yes, Webpack, Gulp, etc, etc...once they are initially set up, they are great!!! But I have had trouble getting these tooling things set up properly so I have had to lean on some of you "experts"
as @Ramon Lapenta said.
webpack I get actually, oddly. I couldn't configure it from scratch, but I can follow the SS default file, it makes sense.
it's just a build system. All it does is find files and link them together.
i need to understand it to use it. Gulp I really like, and have made my own build system using it
Webpack Im still in the process of understanding it 😄
@Ramon Lapenta I mean, they're all build systems. It basically comes down to one of two things:
Right, but I am and old schooler...I still "prefer" to hand code all my CSS (even browser extensions), don't care for the "compact" versions of my
css files, nor do I care for how these tooling mechanisms have so much control on the final product when my hand coded versions are perfectly fine.
Me too, actually Terry.
But as I said, sometimes it's not all about me ;) I accept that these tools are things I'm required to know in order to
Also, why have to learn (even though I did) SCSS or SASS syntax? I know whey they came out in the beginning, they added value because you could start setting variables, etc...but just like with any language/technology...pure CSS these days have caught up
yup. And you find as time goes on people start mixing the two, making scss mostly irrelevant... "but that's what we do". The impact it has is with a few features, and mostly compilation into bundles.
And now...React. Don't get me started...building an entire website in all JS?
yeah Terry, but usually you and me build websites, content and documents
I get it. In order to show some text in a file, we load that file, then load the JS to load the text... but we do it last so we can show you more ads first.
the peuple who created React and those are building apps
very different use 😉
I'm in a semi unique situation in that I build apps, and that most of this modern setup magic has been done before me.
I've built two React sites...the tutorial one "Hello World" and then a very small template based React that was just a proof-of-concept for my old employer who just wanted to see what React was
One could say the same thing about SS. Once upon a time a web server would load files. Now it loads a path still, but the file is generated dynamically and doesn't even actually exist.
Agreed on all parts
We use react to create parts of a page, not all of it at once.
I’ve had to build things that are more app-like, and felt the pain of doing it in jQuery, much have preferred to have had Vue to do it 😞
i.e. it's not an all or nothing scenario.
I still usually only build Websites, when i have a project that's an actual App, i am required to use .NET
make the parts that need to have high interactivity in this newfangled JS noise, and do the rest in static joy.
It's all about how you apply the knowledge you've obtained over the years :)
There is no "right" way ;)
So don't stress it too much. And don't be afraid to ask questions. People are generally willing to help.
@nightjarnz for sure! and the next time I get a project that requires or is already using React...that's when I'll actually "Learn" it 😄
Anyway, composer has finally finished updating ( ) so I must get back to it :)
Have a great evening you two 👋🏼
@Terry Apodaca I'm the same. Knowledge doesn't stick unless I'm doing it. I get the concepts, but the application of it eludes me until I've "done" it.
One last thing :> This is what we've been working on lately. It uses the React ( not intended). But I think it's important and cool. Please feel free to check it out and provide feedback :)
typo in the heading
the route will be pre-defined
so basically: by luck.
however that presumes that most scripts have been included with an identifier defined (which they haven't).
@Kong Jin Jie there's a second parameter to
Requirements calls that acts as a "after" definition.