Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Inxentas, also le yuck on that filthy stuff. Just don't. You're doing something very wrong if you have to do that... Also 'var'?! Seriously?
-
@100110111 I sure feels wrong, yet the internet seemed convinced it's no big deal. Why exactly is it wrong? Should I store the reference in the "data" block?
A few ugly references is probably not why my canvas goes spastic though. And yeah, I'm on my third day tinkering with VUE so I probably don't have the proper mindset yet.
So I have been migrating my website from AngularJS to Vue as an experiment. I'm late to the party.
It has a navicon that opens a dock, a bar that drops down when you scroll, and some insane particle effect that is first drawn to a canvas and then pushed into a div's background image in real time. Seems nesting Vue instances isn't an option, so I made it into a component.
After two days I finally got it working... and it spazzes the hell out. It's literally the exact same code, but now the canvas starts to flicker like crazy the moment you scroll the page.
Not only have I been doing really filthy stuff like 'var self = this', I have no idea where even to begin debugging this nonsense.
rant