161–170 of 297 posts
Earlier quoted context omitted.
Nor do they like it when they do support all platforms from day one via an Electron app...
People on HN don't like anything.
Earlier quoted context omitted.
You can't talk about Chrome's market share without mentioning that it was (maybe still is? I don't know) prominently advertised on the google.com homepage. Everyone who went to search Google saw the ad. It said something like "Try a faster browser" The fact that Chrome was advertised on the most popular page in the world, and especially that it was the only ad on that page, definitely made a difference in adoption. T…
Source? I don't remember such an ad. Speaking as a dev, the dev tools had a ton to do with it.
Disclaimer: I am the creator of the video
Earlier quoted context omitted.
I’m talking about numerous issues that I had with linux kernel (and alikes) on desktops and workstations for decades. My story is freebsd 4.x-7.0, then debian (codenames I forgot), then OSX 10.5-10.9, then unbuntu/mint since ~ 2014-2016 maybe (when gpu and os updates broke it again). I also supervised an entire office of debian/ubuntu + printers & scanners for few years. I’m not what you would call a regular linux ha…
Linux these days, if you just want a working desktop experience, requires no configuration. You pop in an ubuntu usb drive and install, done. It will often run better than the version of windows that the machine actually shipped with. Myself, personally, I stopped running anything but linux more than a decade ago. All I remember from windows is how often it broke in ways that were completely unfixable.
I want to switch but every time I kick the tires I'm baffled at how quickly it blows up.
If this works well, it could eventually be a very big boon for Firefox in the business world. Q&A can now send reproducible bug demos to development. Technical clients can do the same. I wouldn't be surprised if someone built tooling to map these recordings into automated tests either: expect the given recorded workflow to not throw errors. I can't quite remember when I had a bug where a tool like this would've been…
Earlier quoted context omitted.
Why not? A huge portion of developers uses Macs and windows support is coming at some point. Better to get an actual feedback from the developers.
How about linux users?
If this works well, it could eventually be a very big boon for Firefox in the business world. Q&A can now send reproducible bug demos to development. Technical clients can do the same. I wouldn't be surprised if someone built tooling to map these recordings into automated tests either: expect the given recorded workflow to not throw errors. I can't quite remember when I had a bug where a tool like this would've been…
Oh yeah, wow. Having bug reports come with a replayable & inspectable recording of the user's session would be an absolute game changer. We approximate this now with telemetry tools that allow you to see what the user was doing (sort of), but this would be 100x better.
Why "Download Firefox Nightly for macOS"? Is it not supported on Linux and Windows? Why?
This blew me away a bit. Is MacOS this popular in the Web frontend crowd? I always felt that the price/quality ratio was way off with MacOS, compared to a good regular laptop. By good I mean top 10% ranked by price/quality. Even if it wasn't, Apple's general hostility towards consumers is infuriating. Right-to-repair is a banal example.
Once you're price-insensitive, the quality looks good for macs, keyboard issues notwithstanding.
Very cool, but I'd much prefer they spend their time bringing Firefox's dev tools up to par with Chrome's first. I've tried several times to switch to FF completely, but every time I end up switching back on my work computer because of the dev tools.
I recently switched back to FF after many years on chrome and find the dev tools to be as good of not better this time around. Curious which tools in particular you find worse? When was the last time you tried?
Partly it's little usability things:
- There was one time when an HTTP request was failing and I couldn't figure out why, and in the Network tab Firefox wouldn't show any information about it, even the request that went out (other than the URL), whereas Chrome not only showed the headers, it surfaced that it was a 404.
- There's no way to view all source files. You have to go to "Style Editor" for stylesheets and "Debugger" for JS files. I'm not sure how to view the other files that were loaded, outside of the Network tab.
- I do enjoy how Chrome's inspector puts the box layout directly above the computed styles, instead of in a separate tab.
Those all feel like nitpicks, though. It could just have more to do with me not being used to it. Maybe I haven't given it enough of a chance and should give it another try.