Our Funniest Front-End Bugs (2020)
medium.com
Our Funniest Front-End Bugs (2020)
1–10 of 21 posts
Re: Our Funniest Front-End Bugs (2020)
#2Re: Our Funniest Front-End Bugs (2020)
#3Quirks mode. Unicode normalization. Scrollbar resize infinite loop. Accidental misparse. And of course another IE bug.
Each one has manifested a zillion times on as much different web sites. And yet they keep biting us.
Is there an effective way to restructure programming to make these disappear, without locking ourselves up in a turing tar pit. Linters, fault injectors, ... Or some rust safety equivalent for the front end?
Re: Our Funniest Front-End Bugs (2020)
#4All these are classics: Quirks mode. Unicode normalization. Scrollbar resize infinite loop. Accidental misparse. And of course another IE bug. Each one has manifested a zillion times on as much different web sites. And yet they keep biting us. Is there an effective way to restructure programming to make these disappear, without locking ourselves up in a turing tar pit. Linters, fault injectors, ... Or some rust safet…
What is it that makes computer games such a robust experience and why can't we have that in front ends?
I'm not talking only about web. Native toolkits are not much better either.
Re: Our Funniest Front-End Bugs (2020)
#5All these are classics: Quirks mode. Unicode normalization. Scrollbar resize infinite loop. Accidental misparse. And of course another IE bug. Each one has manifested a zillion times on as much different web sites. And yet they keep biting us. Is there an effective way to restructure programming to make these disappear, without locking ourselves up in a turing tar pit. Linters, fault injectors, ... Or some rust safet…
Anyway, scrollbar loops and other stuff are not going to be resolved by this kind of tools I think
Re: Our Funniest Front-End Bugs (2020)
#6All these are classics: Quirks mode. Unicode normalization. Scrollbar resize infinite loop. Accidental misparse. And of course another IE bug. Each one has manifested a zillion times on as much different web sites. And yet they keep biting us. Is there an effective way to restructure programming to make these disappear, without locking ourselves up in a turing tar pit. Linters, fault injectors, ... Or some rust safet…
I was playing Dota [0] the other day, and I was amazed at how robust of an experience it is, while having many many more layers of complexity. What is it that makes computer games such a robust experience and why can't we have that in front ends? I'm not talking only about web. Native toolkits are not much better either. [0] https://www.dota2.com/home
AAA game development includes dedicated teams of QA testers playing through the game each day, flagging all bugs they come across and verifying every bug which is claimed to be fixed. That's the best source of stability in my experience.
At the biggest studio I've been part of (three offices, with about a hundred people in the main one) we also had a number of automated tests (AI running through certain missions and doing events together) where failures would alert those with contributing commits.
Re: Our Funniest Front-End Bugs (2020)
#7As I'm demonstrating this pièce de résistance of sliders, I switched to the tablet to show how it adapts to touch input.
After I've gone through all the features I slip with my finger and drag the handle a little too harshly... to my confusion, the drag handle had broken free of its confines and could now be moved anywhere one the page, all I could do is laugh, I'm glad my colleague found it equally amusing.
Also, the number of times I've seen bugs like No. 3 on big, live sites. Clearly a macbook monoculture and noone bothering to test on any other platforms. Seems like people forget scroll wheels are a thing too...
Re: Our Funniest Front-End Bugs (2020)
#8All these are classics: Quirks mode. Unicode normalization. Scrollbar resize infinite loop. Accidental misparse. And of course another IE bug. Each one has manifested a zillion times on as much different web sites. And yet they keep biting us. Is there an effective way to restructure programming to make these disappear, without locking ourselves up in a turing tar pit. Linters, fault injectors, ... Or some rust safet…
I was playing Dota [0] the other day, and I was amazed at how robust of an experience it is, while having many many more layers of complexity. What is it that makes computer games such a robust experience and why can't we have that in front ends? I'm not talking only about web. Native toolkits are not much better either. [0] https://www.dota2.com/home
Low-quality early-access releases, crashes, things clipping through one another, needing a patch on release day then a dozen patches thereafter, physics glitches sending things flying, interactions getting glitched so they can't be completed, cheaters in online play - these are all just accepted as normal by gamers.
Re: Our Funniest Front-End Bugs (2020)
#9Earlier quoted context omitted.
I was playing Dota [0] the other day, and I was amazed at how robust of an experience it is, while having many many more layers of complexity. What is it that makes computer games such a robust experience and why can't we have that in front ends? I'm not talking only about web. Native toolkits are not much better either. [0] https://www.dota2.com/home
Are you kidding? The games industry has a much worse reputation for bugs than almost any other form of software development. Low-quality early-access releases, crashes, things clipping through one another, needing a patch on release day then a dozen patches thereafter, physics glitches sending things flying, interactions getting glitched so they can't be completed, cheaters in online play - these are all just accepte…
Re: Our Funniest Front-End Bugs (2020)
#10i think the worst and most frustrating type of "bug" (not really) - is the "reload - no update" issue. not sure if it has another name.
its when you make some change, reload the browser but the update is not reflected :D - usually very trivial but often times the straw that broke this camels back.