arek_nawo

Are you looking specifically for Markdown or e.g. a WYSIWYG with Markdown shortcuts support?

I’m building something in this space and I’m curious what’s the appeal of the former vs the latter?

Why is it a "huge asterisk"?

I'm also working on a WYSIWYG editor and using TipTap. It's great, but on its own, it's not a ready editor, but a great framework.

There's a lot you can do with TipTap (and ProseMirror) to make your editor stand out and fit your use case better than others.

I want to think of marketing as a way of providing valuable content and explaining why your product might be just what the consumer needs (potentially helping them with their problems).

What's described above really doesn't fit into this view, but is definitely how I've seen people "play the game". ChatGPT-generated fluff, copied content, and the same tips & tricks, inspirational stories, etc. you see repurposed all the time on different platforms - especially LinkedIn.

I hope marketing can be good and value-adding but, the way it's going right now, we're due for a change.

Happy to see the SIM card go away. eSIM provides just so much better experience.

This also enables easier installation and setup for basically any carrier. Just download the app, configure eSIM and you're good. Maybe the easier switching is why adoption is kind-of slow on the carrier side? Easier to keep you locked-in with more obstacles in place.

Seen some comments mention potential issues with it vs physical SIM, but I hope these get resolved with time or standard solutions are developed. Personally I had no issues with it, using it for over 2 years now.

I've seen quite a few Postman alternatives pop up recently (quite curious what's the reasoning behind that?). Currently I'm mostly using Hoppscotch - also open-source with pretty sweet UI, and Thunder Client in VS Code.

That said, I'd consider switching for type-safety (or more specifically auto-completion) if there was an ability to e.g. import existing OpenAPI schema and automatically pick up the types.

Love it! Good looking, polished UI. I'm probably most impressed by the easy integration and React API. Congrats.

Pretty cool.

I haven't really explored WASM hands-on (I'll give this guide a try) but, given that it's already been a few years, I think it's been hugely beneficial for web development.

Not the "JavaScript killer" some where hoping for, though it was never meant to be one. Instead it integrates pretty nicely within the existing ecosystem, optimizing existing use-cases and allowing new ones when heavy computations are required. Net benefit for all web devs - faster libraries, impressive dev tools and more portable node binaries.

Also fair points :)

I think it all depends on the project’s scale, type (is it part of your infrastructure like a database or all-in-one solution like a CMS, etc.), goals and other factors.

It’s difficult to make the right choice at the very start, as something that might have worked then might not work when you’re at a scale of competing with AWS.

Thanks for clarifying. I should indeed explain better what I had in mind.

You are correct that under AGPL-3.0 people still can provide the software as a service, but they’ll have to disclose any changes to the source code they’ve made.

This, in my mind, effectively discourages doing so as, if all you do is change the branding, people will eventually know and, depending on their ethics and the provided offering, they might choose not to use the “official” service.

In theory people still could distribute the product as-is or just be fine with the open-sourcing and actually add something of value to their fork. However, as I’ve seen in practice, this doesn’t seem to happen at a meaningful scale and people usually prefer to contribute directly to the original project.

Like you’ve said, there are other licenses that aren’t really open-source, prohibiting this from happening at all.

Most interesting options from these, for me, were SSPL (which puts the open-sourcing requirement on other elements of your stack, like hosting provider, making it a non-starter), or ELv2 (which just prohibits SaaS use entirely).

But again, not being recognized as official open-source licenses, using these puts the project more in the camp of source-available software rather than open-source.