221–230 of 261 posts
Well, this is the problem with designing backend, knowing what to do. Not actually writing the implementation. The way I see it, no problems are circumvented.
Cool development-environment nevertheless, it'll be really good for beginners.
- Have multiple projectional views of the system, triggered on keypress, e.g. caller context, database context, handler context. So if I'm editing a function I should be able to see the handlers that are affected, also the call stacks up and down, even show function calls inlined, current live errors overlaid, etc.
- Easy example based testing. Can I just click on a function, type input values at the top, then dark shows my intermediate values and output, and then I mark a 'check' on this trace to stamp it as a test case? Then every related change (or a special button) runs affected tests and I can see what's failing. I didn't see any testing in the demo.
- History of each function, each handler, each table - absolutely need this, with 'blame'.
- Immediately live is nice but really you want to roll out some related changes together, and a 'diff' of a snapshot against another one is great. I should be able to see the db diff, the function diff and handler diff in one integrated view. Should be able to 'label current version', in addition to auto-save.
- Annotations - these should be allowed everywhere. I assume functions, AST nodes, tables, columns etc are already reified, so I should be able to link to them in free form annotation comments that I may put in the code or just floating around by themselves. Documentation needs to be integrated as well. At the very least I should be able to link to a function or table via an external hyperlink.
- A standard CRUD UI for DBs should be available.
Earlier quoted context omitted.
https://github.com/parse-community/parse-server (joke)
Hijacking the joke comment to plug Dark a little bit. Data migrations and schema changes are hard (especially when you want to test on a subset of users), and Parse only avoided a lot of this pain because it was typically used for relatively simple-schema'd projects. Dark seems to have done the hard work of making an entire language and environment to avoid footguns and provide more-or-less seamless data migrations,…
Schema migrations are easy if there's no complexity to the schema.
Earlier quoted context omitted.
So this "non-engineer" learned a new programming language, understands Heroku and Flask, and created a REST API integration for Slack? Can anyone let me know what an engineer is again?
Many people who are "self-taught coders" don't perceive themselves as "engineers", often because many other forms of engineering have certifications. They expect that "engineer" requires a certain level of knowledge that they do not have; it's an unknown unknown kind of thing. I know someone who, through using a lot of Goole Sheets, managed to re-invent SQL joins. She'd never identify as an engineer, but she did mana…
Earlier quoted context omitted.
How is this different than running on certain cloud providers? For instance, a team can become deeply integrated with AWS services and then have trouble moving off if AWS starts raising prices.
AWS has competition, there is only one darklang. While it certainly would be difficult for most to move away from their cloud providers, it can be done. Almost all cloud providers are just packaging together open technologies with their established internal conventions. There is a world of difference between "this is a pain in the butt and we should have planned better" and "you have to start over completely from scr…
Is there an open source version of the language? ...bc I'm not touching a programming language with a ten foot pole if it hasn't got at least two implementations, and at least one open source :| Sure, keep the IDEs and deployless infrastructure and all proprietary, but a core programming language in 2019 can only be open-source. Heck, even Microsoft gets it now.
https://github.com/parse-community/parse-server (joke)
Earlier quoted context omitted.
No, it does not. The word is not used anywhere on the page. There is a mention about privacy, PII, GDPR, Audit logs etc. and how that's not implemented yet. If that's what you meant, fair enough. Still a bit scared for your initial beta users running their business on this as mentioned elsewhere.
Oh, so it doesn't! Sorry, I meant to check before pressing send but got ahead of myself. We do quite a lot of security work - it's probably the one area we don't cut scope on. Someone reported a security bug today and we fixed it immediately.
NO FUCKING THANK YOU.