263 karma · joined April 5, 2016
Yaml is simple. A ton of tools can parse and process it. I understand the author's gripes (long files, indentation, type confusions) but then I would even prefer JSON as an alternative.
Just use better tooling that helps you address your problems/gripes. Yaml is just fine.
Proof of work. Look at all this data I/we created.
And the article didn't talk about logs and other operational data yet
And that's the crux of it and that's also why DeepSeek was such a big deal.
No, of course not. But he is the leader, and he guided the company to a point where certain areas became "over-invested or under-performing." In other words, he didn’t do a good job. So, it should be him stepping down. Nobody ever said being a CEO would be easy.
The biggest issue back then was finding a quality client implementation for the language you were using. Not sure what the status of that is these days.
From what I have seen, these kind of frameworks facilitates the worst possible combination of factors: A solution designed, created and implemented by non-programmers, not using a programming language ending up in a production environment.
One could argue this is a success in its own but I have only seen these kind of things hit their limits almost immediately after the initial POC and evolve into terrible tech debt. Just learn to program or script already.
That being said, I do not want to disrespect the effort into building this and perhaps there is a place for these kind of solutions I yet have to experience.
Thank you devs!