Recent submissions

Comment · 5 years ago
I actually quite like the mobile browser, it hasn't really given me any issues yet. The fact it supports add-ons like uBlock is awesome.
Comment · 5 years ago
FF is my daily driver (since Quantum in '17) but I've found it really just isn't holding up these days:

• Profiling functions between Chrome/FF reveals that Chrome is frequently considerably faster (usually 60%+)

• During WebGL work I'll often hit blue screens around memory management (this seems to be a relatively recent development)

• Similarly, trying to profile a WebRTC application with video feeds will consistently trigger a blue screen. (I can tell this is from FF, as the browser itself flashes white a few times before the system goes down.)

• Things like the UI changing - while minor - are enough to cause inconvenience, plus the occasional random feature removal (View Image context menu option) indicates that I'm not necessarily the target audience for the browser.

I actually slightly prefer the devtools in FF than Chrome, but there are a number of quirks that have started appearing over the past year or so, ranging from actual bugs to just weird UX.

As I write this, I'm realizing I'd love a browser that's seen more as a devtool than a catch-all web navigator which happens to have a profiler built in.

Comment · 5 years ago
This honestly sounds like a great idea. At this point I'd pay money for a browser that was private, fast, and dev-friendly, simply to avoid the moral dilemma of switching from FF to a Chrome clone.
Comment · 5 years ago
I have been working with the PETAL stack and it is incredible. I love Elixir and have only picked it up over the past year or two. There has been a noticeable increase in recruiters reaching out to me about Elixir jobs lately, too.

I think Elixir should be a lot bigger than it is. I have not had an issue or encounter with unmaintained libraries.

Comment · 5 years ago
I reached for Preact on a project and was very satisfied with it. Until, that is, I hit a bug where DOM elements would be rendered out of order when I would call setState. I replaced Preact with React and everything worked fine. The logic was fairly straightforward as well - I was not doing anything fancy.

Preact is great but be prepared for anomalies like mine.

Comment · 7 years ago
While I worked there, I heard about user studies Mozilla performed comparing Chrome and FF. It turned out that with all branding stripped, users found FF to be faster - but as soon as it became 'Chrome' vs 'Firefox', users always chose Chrome. I recall they actually faked browser UI's (i.e. made FF look like Chrome and vice versa) to test if it was about branding - and it was.

The reason I bring this up is I assume a lot of folk are in that bucket. Chrome was on top for a long time, and I think people are hesitant to switch to FF, despite the effort Mozilla has put into revamping/rewriting their browser.

(Also, I find it interesting that you only have a quarrel with Google tracking you (via Chrome) if you _see_ the ads. They're still collecting data whether or not you see the end result.)

Comment · 7 years ago
Can you elaborate on what 'other spying' Mozilla does? Do you mean their telemetry?
Comment · 8 years ago
Former Longmont resident/NextLight customer here. I can't understate how fantastic the broadband service is out there.

Usually my speeds clocked in around the 700-900mbps range (both up/down), and at its slowest, maybe 300mbps. No port blocking, so I could host my own web/game servers. The one time they performed maintenance, they notified customers a week in advance and scheduled the 15-minute down time to be around 3am. Since I was a 'charter' customer, my bill was a flat $50/mo, though I'm pretty certain that new customers don't pay much more than that.

I truly believe if more people understood what _good_ internet is like, there would be a MUCH stronger push for communal broadband services.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton