Yeah that’s mostly what I’m referring to.

Backups are pretty easy, but service availability and failovers across cloud providers is stupid difficult. Not really from a compute standpoint but mostly from a data consistency/transactional standpoint.

However, if you are using vendor specific services like AWS connect then you have to build and maintain multiple deep integrations into those services which effectively doubles your engineering efforts.

Cool 👍

Multi-cloud is a significant amount of effort to pull off.

Being on one cloud provider across multiple regions is often plenty of redundancy.

Being available across multiple cloud providers is really REALLY difficult

Honestly surprised C# isn’t on here? It’s still one of the “big 5” languages, and .Net touts it’s incredible performance on the regular.

I work remote (Going on 9 years now) and I miss a sense of community. Do I want to stop working remotely? Hell no, screw that. But two things can be true the same time, I can enjoy and encourage them at work, dnd I can also miss a sense of community.

I think it’s okay to hold this opinion because it’s individual to everyone.

This just comes across as propaganda

Being dismissive and pulling the rhetoric that this is propaganda is toxic as fuck.

Hospital near me has password requirements for their electronic medical records system as:

• 6 characters, no more, no less
• 2 characters must be a number
• 4 characters must be a letter
• case insensitive
• never changed

And for new hires and what not, they tell them to use {hospital abbreviation}{2 digit year}. Like casu24

No freaking wonder

Too bad commenters are as bad as reading articles as LLMs are at handling complex scenarios. And are equally as confident with their comments.

This is a pretty level headed, calculated, approach DARPA is taking (as expected from DARPA).

Doesn’t appear to show any charts on Chrome for mobile…

Seems to be a responsiveness issue, because it goes away in landscape mode, and the charts show.

They work great when you have many teams working alongside each other within the same product.

It helps immensely with having consistent quality, structure, shared code, review practices, CI/CD…etc

The downside is that you essentially need an entire platform engineering team just to set up and maintain the monorepo, tooling, custom scripts, custom workflows…etc that support all the additional needs a monorepo and it’s users have. Something that would never be a problem on a single repository like the list of pull requests maybe something that needs custom processes and workflows for in a monorepo due to the volume of changes.

(Ofc small mono repos don’t require you to have a full team doing maintenance and platform engineering. But often you’ll still find yourself dedicating an entire FTE worth of time towards it)

It’s similar to microservices in that monorepo is a solution to scaling an organizational problem, not a solution to scaling a technology problem. It will create new problems that you have to solve that you would not have had to solve before. And that solution requires additional work to be effective and ergonomic. If those ergonomic and consistency issues aren’t being solved then it will just devolve over time into a mess.

Because your conservative funded news outlets have a very overt goal here.

The CEO is a right wing trump worshiper.

Dig into the company’s tweet history, and find archived tweets that were deleted for PR/white-washing reasons.

Long history of this stuff.

Yeah, but that’s not what we’re talking about here.

RTF has many more features than markdown can reasonably support, even with your personal, custom, syntaxes that no one else knows :/

I use markdown for everything, as much as possible, but in the context of creating a RTF WYSIWYG editor with non-trivial layout & styling needs it’s a no go.

Yeah, and electron already has a secureStorage API that handles the OS interop for you. Which signal isn’t using, and a PR already exists to enable…

Probably not. Having actually played with making a WYSIWYG editor as a learning project markdown is too simplistic for the formatting needs of any non-trivial text editing, as a serialized storage format.

You almost always end up back with your own data structure that you serialize into something like XML for storage. Or you end up supporting HTML or non-spec compliant syntax in your markdown.

And if you care about performance, you’re not actually working with XML, HTML, or Markdown in memory. You’re working with a data structure that you have to serialize/deserialize from your storage format. This is where markdown becomes a bit more tedious since it’s not as easy to work with in this manner, and you end up with a weird parsing layer in-between the markdown and your runtime data structures.

The commenter that’s downvoted is more correct than not IMHO (Also why are we downloading discussions??). Markdown is ill suited for “most WYSIWYG needs”. It tends to get augmented with XML or custom non-spec compliant syntax. The spec poorly supports layout (columns, image & media positioning, sizing…etc) and styling (font color, size, family, backgrounds…etc)

There are markup languages for this purpose. And you store the rich text as normal text in that markup language. For the most part.

It’s typically an XML or XML-like language, or bb-codes. MS Word for example uses XML to store the markup data for the rich text.

Simpler and more limited text needs tend to use markdown these days, like Lemmy, or most text fields on GitHub.

There’s no need to include complex technology stacks into it!

Now the real hard part is the rendering engine for WYSIWYG. That’s a nightmare.

Holy shit that’s completely wrong.

It’s for sure AI generated articles. Time to block softonic.

This is a weird take given that the majority of projects relevant to this article are massive projects with hundreds or thousands of developers working on them, over time periods that can measure in decades.

Pretending those don’t exist and imagining fantasy scenarios where all large projects are made up of small modular pieces (while conveniently making no mention to all of the new problems this raises in practice).

Replace functions replace files and rewrite modules, that’s expected and healthy for any project. This article is referring to the tendency for programmers to believe that an entire project should be scrapped and rewritten from scratch. Which seems to have nothing to do with your comment…?

This thread is a great example to why despite sharing knowledge we continually fail to write software effectively.

The person you’re arguing with just doesn’t get it. They have their own reality.

I have a weird knack for reverse engineering, and reverse engineering stuff I’ve written 7-10 years ago is even easier!

I tend to be able to find w/e snippet I’m looking for fast enough that I can’t be assed to do it right yet 😆

That’s one of the selling points, yep