![]() BY DEFAULT though, I'm reaching for a solid library if at all possible, but I'm never afraid to hand-code if that makes the most sense in a given case. It comes down to the needs of the project and what makes more sense. I've used several of the big-name parallax libraries to good effect, and I've also rolled my own vanilla JS solution. but certainly the delta isn't as extreme as it once was.Īs far as what I use in the JS case, I evaluate the needs in each situation. The days of "CSS is ALWAYS smoother" are. In these cases, I won't use any sort of library, I'll write the CSS myself because it doesn't take much effort.īuti f you get into the kind of parallax where there's all sorts of trigger points and multiple layers and even multiple axis of parallax going on, then I go for JS because it winds up being much easier to write and, these days, you can get ALMOST equivalent performance to CSS, close enough that it doesn't hurt my head anyway. It's not too difficult to write then, doesn't take a ton of lines of code, and the results are excellent. If you're just talking one or two parallax layers, I tend to favor pure CSS. ![]() I think it's a question of just how complex the parallax is. You can find a list of useful sites and resources including blogs, social media sites, utilities, guides, tutorials, newsletters, tools, and more in our /r/frontend wiki. Therefore, some lenience is allowed in the type of posts that may seem more back-end oriented so long as their emphasis seems to be in the spirit of the subreddit. Nowadays, the field of front end development is evolving at such a rapid pace that sometimes it's difficult to say what is frontend and what isn't. For it to be valid and related to frontend it should be accompanied by the open source repo, and the context of the post should be around the frontend of your project, not the project idea.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |