4 ms·
>A lot of our software's more complex interfaces are Chrome-first since its faster to develop - yesterday was the first time I made a serious consideration to c
by theon144 8y ago
>A lot of our software's more complex interfaces are Chrome-first since its faster to develop - yesterday was the first time I made a serious consideration to change that approach.
Heh, I wonder if the next privacy blunder from Google will make you further reconsider your "voluntary vendor lock-in" approach :)
- statictype 8y agoI said Chrome-first. Not Chrome-only.
- reitanqild 8y agoI'd still ask to consider a Firefox first policy. I've been using Firefox as my main dev browser for years and it has a huge, practical advantage: - Usually it Just Works in every mainstream browser (had one single case in the last year where it broke in another browser). My colleagues who use Chrome has to fix QA bugs more often than me it seems ;-) Bonus: Support a good cause (cross browser compability)
- wiz21c 8y agoyeah like in "this is just temporary code we put in production, we'll clean it later" :-) :-) </joking-with-a-touch-of-cynism>