I know you can play the game at chrome://dino, but it doesn't evoke the same nostalgic feeling of a 10yr old me turning on aeroplane mode and spamming space bar to try and beat my brother's high score. Good memories.
this post was submitted on 21 Jul 2023
838 points (93.2% liked)
Memes
45586 readers
1307 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not sure why there's so much love for FF here. It sucks for web development - or rather there are some very important features that Firefox doesn't have that Chrome does have.
As someone that uses FF regularly AND does web development, I'm curious, specifically, what important features are you talking about?
So when you're writing JavaScript, as I'm sure you know, it's bad form to add prototypes to primitives.
So let's say you have an Object, and it holds data about a person: hair color, eyes, weight, height, etc.
But if you want to make that object do something, like calculate the bmi, what do you do?
You could just go ahead and add ".calculateBmi" to Object, but that's bad form, right?
So you create a Person object, and it has weight, height and all the other stuff, then you can also assign it methods, like .calculateBmi, and that's great.
Well, in Chrome when you console.log the Person object, it's says "Person" and it lets you open it right up and look around to see what the height and weight are, and it's great.
However, In FF, it just says "Object." And you have to open it, then open a few other things underneath it to find out what type of object it is, and it's members and methods.
And its takes way longer to debug. And there's a few other, little things like that, that I can't think of. I'd love to use FF, but it's just not there yet.