191–200 of 322 posts
The only good offering here is available as part of the $10/month "Supporter" plan, a "direct feedback channel to the MDN team." The video describes that as "regular chats with MDN engineers." Shockingly, this isn't even listed as a featured bullet on the plan list. https://developer.mozilla.org/en-US/plus#subscribe The only bulleted advantages of paying $10/month are, "Early access to new features" and "Pride and jo…
There's something in the water at Mozilla that negatively effects all product decisions. Notifications and collections are features, not a product. A viable and attractive MDN product would be a subscription to all the layers above the existing docs and guides, combined with a major initiative to connect with experts to create course material and sell it as a part of the platform. MDN: what got you here won't get you…
Earlier quoted context omitted.
It looks like Mozilla's average SDE salary is about $120k, so yes. The national median software developer salary is something like $110k. The middle 50% range is like $85-150k, so if you're making above 150k TC you're already in the top 1/4 of developers, who are already very high up in general. I say this because people on HN love to pretend that "industry-standard" means $250k+ for new grads and $400k for experienc…
That definitely feels a bit low. Is this considering only US or worldwide?
Earlier quoted context omitted.
Does Mozilla pay their software developers an industry-standard TC?
It looks like Mozilla's average SDE salary is about $120k, so yes. The national median software developer salary is something like $110k. The middle 50% range is like $85-150k, so if you're making above 150k TC you're already in the top 1/4 of developers, who are already very high up in general. I say this because people on HN love to pretend that "industry-standard" means $250k+ for new grads and $400k for experienc…
I'm not sure where you're getting that number, but it's much too low.
The figures at https://www.levels.fyi/company/Mozilla/salaries/Software-Eng... better match what I saw when I worked at Mozilla.
You can compare compensation at equivalent levels for Mozilla and peer companies at https://www.levels.fyi/?compare=Mozilla,Microsoft,Apple,Goog... . You'll see that Mozilla pays well, but significantly less than them.
In general, Big Tech companies should pay more into open source, and especially into the standards committees they manipulate to their own ends. Perhaps there should be some kind of NATO-like membership fee based on percent of global revenue. It would be amusing to see w3c tax these corporations more efficiently than any government has been able to.
I'm curious how often people are needing offline access to documentation for web development.
Probably not very often. Next time you're flying across the pond, try coding (without bothering to subscribe to onboard wifi). Also, it can be useful in places where steady internet is sketchy, which is a lot of places. The folks at 100 rabbits [1] would be happy. [1] https://100r.co/site/working_offgrid_efficiently.html
And regardless, it seems like offline web API documentation would make more sense as a one-time purchase? It's not like the web is rapidly evolving at all times, with major updates being released annually. It's a good chunk of years before enough browsers are updated to support new APIs, so if you grabbed the current docs you'd probably be able to work with that for a while.
Fundamentally, maintaining MDN is costly because of the rate of instability in rapidly changing browser APIs. Those APIs change quickly and inconsistently because they’re managed by a centralized cabal of a few corporations with a combined multiple trillions of dollars in market cap. And yet, somehow it’s Mozilla, the browser vendor with the least money, that ends up saddling the cost for MDN. Why is this? In general…
The other day I wanted to learn Svelte. Even though the tutorials on the Svelte homepage are great, I found the MDN Svelte tutorial to be better: it explains the conceptual differences wrt other frontend frameworks well, it explains in detail how to enable Typescript and migrate your projects, and it has a dedicated section that describes different deployment options. While of - of course - all of these infos can be…
(unrelated to the main topic) > The other day I wanted to learn Svelte... Any highlight(s) regarding positive/negative experiences that you had with Svelte so far? Asking because it's on my to-do list for my future frontend (bought 2 books about it, but pending to be read as I'm currently first trying to assimilate "Rust" to program the backends) and I ended up selecting Svelte as potential best candidate after havin…
Sveltekit was a bit of a pain to get running, but using svelte itself has been insanely nice. I got an entire internal website up and running with a bunch of cool functionality in ~3 days. The state management with Redux alone would have taken that long if I was using React.
Being able to just use regular HTML is also nice.
There are some gotchas, how it handles CSS is kinda weird, and docs beyond the basics are rough in places.