mitchitized

This is precisely why I ended up on Joplin several years ago... Being able to sync for free (I just pay for S3 costs) means I got cross-device/platform support and know I will never lose my notes.

I'm trying to understand the use case where it would be worth it to switch to Obsidian and pay monthly for the sync and no longer host the data myself, which doesn't sound like an improvement to me.

The way Obsidian organizes notes sounds intriguing though, I can see how some might find that worth the additional cost (or loss of sync ability).

I see this as "Joplin, just not nearly as free (speech or beer)." Why would I pay monthly for sync and have no control, when I can already sync to my own s3 buckets and only pay for AWS storage and transfer?

Is there a compelling reason to switch from Joplin to Obsidian? Honest question.

Amen, but forget about external influence - if you work in a business that is profitable, you're certain to bump into coworkers outside of technologies that live in a pure deadline-driven world. That's business, and it is not negotiable.

There will always be major events that are locked to fixed dates, like conferences, launches and many things that are impacted by launches (like hiring new teams to be using the new systems that we were supposed to be building). This does not mean this company sucks, or working at this company sucks, it usually means this company is profitable.

"Waterfall" is starting to get twisted into some sort of virtue signaling for folks that like to complain about deadlines.

Managing this tension is what we all need to be good at - there's definitely no silver bullet or perfect methodology to manage this, because it is always evolving.

"Ooh, lookit that funny car over there!" - points phone almost at your face, takes picture - uploads picture to Facebook

You'd literally have to have the kind of Momma that would dig a hole and hide you in it at birth to really be "off the grid" at this point.

I once let my then 13yo borrow my laptop to do some research as he wanted to start experimenting with modded minecraft. I sat next to him while he researched minecraft plugins - no opportunity for him to hit some cough other websites, it was totally legit browsing session. Let's just say the advertising bubbles that Google rammed me into literally forced me to install adblockers just to make my web browsing experiences SFW again (also saw a huge spike in hostile ads with malware, and suspect it was too drastic and immediate a change to be mere coincidence).

Saying "crap ad tech" is giving way, way too much credit to ad tech. I'd argue current ad tech IS crap, because the overall methodology and approach is fundamentally crap.

I remember the GOOD OLD DAYS(TM) where I had to pay to upgrade Mac OSX, iOS, and paid monthly for MobileMe. You know what? That just worked.

Now it is all free and 99% Jankytown. Apple, take my damned money and give me my productivity and happiness back!

I despise the "legal risk/threat" aspects of this process, which is most likely the reason nobody can actually tell you something useful. In many large companies you can't even provide critical feedback to your own employees, and if you end up letting them go as a result, you are unable to tell them what really went wrong.

I understand an aversion to legal risk, but IMHO this is going to an extreme that hurts all of us.

How tiring. We can litter the internet with posts like this, but it would be a lot more useful to post reasoned, factual and detailed posts when discussing the merits or pitfalls of a given technology.

I've launched very high traffic websites using MongoDB, where it was the least of my worries. I've also launched very high traffic websites using MySQL, where it was my primary source of pain.

Shall I now run around screaming loudly about how badly MySQL sucks? On the surface you might assume so, but with reasonable effort to consider all the facts, it becomes clear that there's more to this than just "this database is better than that one because I hate it."

This post is more of an angry payback rant from someone who got banned from IRC for being abusive to newcomers and greenies. On top of that, it is factually incorrect in some spots, and misleading in others. Not impressed.

That said, NoSQL databases are evolving extremely quickly, and have reached a point of maturity that they can excel in the right scenario. Just like relational databases, they can provide big benefits, given that the user takes the time to learn how to use them, as well as making sure they have a use case that merits the strengths of their chosen tech.

I really enjoy working with MongoDB and Redis, and have been a community cheerleader of sorts for PostgreSQL for years. It is possible to have multiple tools in your toolbox, and use them when appropriate. No tool is perfect, and no tool is perfect for every job.

Complaining bitterly that your shiny new piano makes a lousy boat, on the other hand, simply adds to the noise.