bhalp1

This is true— But also, we will support the journey towards being 100% cloud agnostic— It just wasn't worth holding up this release to get it all perfect.

Nothing is deeply cloud-specific in the core stack— Opportunities to go cloud agnostic are there, we just might have to do it via contribution, as we have a few important projects on the go with conflict with the time this would take. But it's open source, and it will happen :)

Yes, Forem is extracted from dev.to— which was built to reach millions— With crowdsourced moderation, feed algorithms, rich editors, etc, and we're working backwards from there. So yeah, it's a little complicated at this layer of the stack, and getting simpler over time as we work to extract from the core.

Background processes, on-the-fly image optimization/caching— It's more shopify for independent social networking than it is classical forum software.

Great post

I'm not sure which ones they are, but I'm sure some of the most impactful things ever published had this moment of hesitation involved.

Blog post: "I'm creating an entire web OS as my personal website for 2021"

https://dev.to/nicolalc/i-m-creating-an-entire-web-os-as-my-...

A lot of good things here. I think I'll try to address a lot of this in an upcoming blog post or two. I'd get into it now but I'm a bit tired from an exhausting day of making this announcement.

You can follow me at https://dev.to/ben to get notice when I get a chance to flesh some of this out publicly.

Honestly, that sums it up well enough. But the devil is in the details.

Branding has been the bane of our existence, we're gradually figuring it out.

Luckily our longterm plans revolve around helping other people use our software under _their_ name.

We have some private alpha users, but mostly the re-usable software isn't quite there yet.

We've been mostly focused on phase 1 which is our own use of the software, but have a roadmap to get more folks on the underlying platform in 2020.

Yes, Medium pulled a bait and switch which lead to a lot of rightfully unhappy customers.

It was this behavior which led to publications like Hackernoon and FreeCodeCamp to begin leaving.

Ultimately the reasons for wanting to leave make a lot of sense. Doing it _in this way_ is the troubling part.

Yes, you can post it wherever you wish. A third party publication on Medium, however, cannot do so without your consent.

Great research, great read.

Yes. And actually, this is a mistake in our processing configuration. We don’t want separate body tags, but it hasn’t been a problem so we haven’t gotten around to fixing it.

PRs welcome. :)

It's a bit of column A, a bit of column B. Mouse context is not always available. Tuning + preloading.

Merged.

Google says "If you're building a Progressive Web App, consider using a service worker so that your app can work offline."

What does "consider" mean here?

And I'm pretty sure SPA is also not a criteria for PWAs, it's just a suggestion.

And also, the install banner is not really yours, it's the browser's functionality.

Per Google:

> Chrome uses a set of criteria and visit frequency heuristics to determine when to show the banner.

That's the rub

AFAIK the US also has significant tariffs on certain kinds of imported vehicles, namely pickup trucks.

I see this sort of thing becoming a bigger part of journalism in the future.

We have a very OSS-friendly community at https://dev.to

I find it useful to go out of our way to schedule free time in the form of video chats. Where we just talk about stuff and catch up until something that needs to be covered comes up naturally. That is an ordinary thing that happens face-to-face. Less-so remote, so you have to go out of your way.

"How Node.js Powers the Many User Interfaces of Netflix" https://thenewstack.io/netflix-uses-node-js-power-user-inter...

Well at this point the expectations are a little lower. "Anything but going all the way to zero" seems like the current tone.

Reminds me of this post: https://dev.to/aunyks/lets-build-the-tiniest-blockchain

At https://dev.to we have a similar product to Medium in a lot of ways. One thing we try to do is offer the benefits of Medium in terms of distribution, but also encourage users to easily make their own site the canonical source, because we don't want to force vendor lock in when you get to this point.

I'd like to think we also do a good job dealing with a lot of the UX issues that the author outlines :)

Our form said Zip Number/Postal Code and State/Province and neither were required fields.

Founder here. Here are a couple comics that describe why it might have been the right choice to not try and software develop our way out of this one in the first place. https://xkcd.com/974/ https://xkcd.com/1319/

Duly noted. I'm pretty proud of our team in general though. At the time there were two devs working on the whole app and I think we got a lot of good work done.

Founder here. https://dev.to a platform for the software dev community to talk about what they're hacking on and teach one another. It's a lot clearer on the home page. This post is just a story about stickers. :)

As the creator of https://dev.to and the co-author of this article, I concur mightily.