3 ms·
I am in the same boat, I've been full stack for many years across a variety of technologies. The intro video doesn't seem like anything is being made any easie
by eternalny1 7y ago
I am in the same boat, I've been full stack for many years across a variety of technologies.
The intro video doesn't seem like anything is being made any easier, other than hiding a few of the templated bits away from the developer.
But the developer still has to understand what all this stuff MEANS. You need to understand REST, GET, PUT, REPL and any other acronyms that are involved in API development.
If you know all that, why not just use an established language you already know and build the API, with the added bonus you aren't in a closed language with a closed system that can disappear at any time?
PLUS you can do literally anything you might need to, without hoping that things like this might get around to implementing that feature in the future (which again makes their tool more advanced, opposite of what they are trying to achieve).
Programming is for programmers, and programmers understand how to build APIs ... it's quite simple.
- steve_adams_86 7y agoOne thing that crossed my mind while walking since my last comment is that this could be great when you work on a team with some junior developers. Like you say, they need to learn all the acronyms and concepts between them, but they're working in an ecosystem with guard rails and mentors who (assuming they're experienced with Dark) can easily keep them on track and help them solve common problems. Hopefully there would be less edge cases and rabbit holes to die in. At the same time, I value all those scary holes I ventured into as a junior dev, the problem solving skills it helped develop, and the independence it instilled. It's hard to say, I think this is a cool idea but I'm biased to prefer my own methods I guess. I can't imagine working in such a closed ecosystem these days.