← Back to context Comment by ohhhwell 9 years ago Oh fun, didn't expect to see my side-project here :)A few of my personal favorites:https://www.dwitter.net/d/90https://www.dwitter.net/d/406https://www.dwitter.net/d/433https://www.dwitter.net/d/617 9 comments ohhhwell Reply lionleaf 9 years ago Didn't mean to post with that account. Oh well. lauriswtf 9 years ago Awesome project, love the idea!It's fun to optimize the code under 140 bytes. https://www.dwitter.net/d/832 NKCSS 9 years ago I love https://www.dwitter.net/d/739 zamalek 9 years ago A little feedback, the tab got helluva laggy after scrolling down a few pages. I assume that's because you aren't unloading dwitters when they scroll past the top of the viewport - which you probably should.Chrome 56, Windows 10. lionleaf 9 years ago The dweets are stopped but not unloaded as you scroll away. You're entirely right though, needs some proper unloading.Edit: Link to the issue https://github.com/lionleaf/dwitter/issues/66 dorianm 9 years ago Infinite loops (accidental in my case) should probably be catched in some way. brian_cloutier 9 years ago Yeah, the halting problem has been around since 1936. You'd think someone would have solved it already! azeirah 9 years ago if (time_elapsed > some_arbitrary_threshold) { interrupt_sandboxed_code(); } jlebrech 9 years ago maybe give the scripts a quota of cycles then can consume.maybe the script tag should support that one day
lauriswtf 9 years ago Awesome project, love the idea!It's fun to optimize the code under 140 bytes. https://www.dwitter.net/d/832
zamalek 9 years ago A little feedback, the tab got helluva laggy after scrolling down a few pages. I assume that's because you aren't unloading dwitters when they scroll past the top of the viewport - which you probably should.Chrome 56, Windows 10. lionleaf 9 years ago The dweets are stopped but not unloaded as you scroll away. You're entirely right though, needs some proper unloading.Edit: Link to the issue https://github.com/lionleaf/dwitter/issues/66
lionleaf 9 years ago The dweets are stopped but not unloaded as you scroll away. You're entirely right though, needs some proper unloading.Edit: Link to the issue https://github.com/lionleaf/dwitter/issues/66
dorianm 9 years ago Infinite loops (accidental in my case) should probably be catched in some way. brian_cloutier 9 years ago Yeah, the halting problem has been around since 1936. You'd think someone would have solved it already! azeirah 9 years ago if (time_elapsed > some_arbitrary_threshold) { interrupt_sandboxed_code(); } jlebrech 9 years ago maybe give the scripts a quota of cycles then can consume.maybe the script tag should support that one day
brian_cloutier 9 years ago Yeah, the halting problem has been around since 1936. You'd think someone would have solved it already! azeirah 9 years ago if (time_elapsed > some_arbitrary_threshold) { interrupt_sandboxed_code(); }
jlebrech 9 years ago maybe give the scripts a quota of cycles then can consume.maybe the script tag should support that one day
Didn't mean to post with that account. Oh well.
Awesome project, love the idea!
It's fun to optimize the code under 140 bytes. https://www.dwitter.net/d/832
I love https://www.dwitter.net/d/739
A little feedback, the tab got helluva laggy after scrolling down a few pages. I assume that's because you aren't unloading dwitters when they scroll past the top of the viewport - which you probably should.
Chrome 56, Windows 10.
The dweets are stopped but not unloaded as you scroll away. You're entirely right though, needs some proper unloading.
Edit: Link to the issue https://github.com/lionleaf/dwitter/issues/66
Infinite loops (accidental in my case) should probably be catched in some way.
Yeah, the halting problem has been around since 1936. You'd think someone would have solved it already!
if (time_elapsed > some_arbitrary_threshold) { interrupt_sandboxed_code(); }
maybe give the scripts a quota of cycles then can consume.
maybe the script tag should support that one day