I mean I guess. Salesforce did it with Apex and Wolfram did it with Wolframlang or whatever Steve is calling it these days. But I feel like this is a solution in search of a problem. The issue isn’t complexity or even accidental complexity. It’s that businesses usually have many competing and often conflicting needs. I can already hear the angry snort when I go to the head DBA and ask if I can use some new hosted product to replace our on prem data warehouse. It’ll never happen. And it’s not even an “old school” thing. We just have a variety of reasons why it’s a bad solution. So now we talk about setting up small web apps hosted in Dark’s cloud. How is it any better than what we have hosted in Amazon, Google, and Azure where we also have the ability to at any minute tap in to a huge market of developers? I guess then we look at this for new projects that aren’t interfacing with production stuff? In that case I guess it’s an interesting experiment. But the reality is that most corporate things (from my experience anyway) have an if it ain’t broke don’t fix it mentality and with good (often painfully learned) reasons. I’m not debating the values of this (it’s hard to since their entire site is marketing buzzwords) but I’m saying it doesn’t seem on the face of it to be a realistic problem solver. I’m very likely wrong but that’s how it feels to me.
Dark emerges with ‘deployless’ software model
171–174 of 174 posts
Re: Dark emerges with ‘deployless’ software model
#172One question/unsolicited advice: the articles frequently mention “feature flags,” but these will cause simultaneous rollout in prod without any real testing or canary. It seems like an experiment framework (eg whitelisted customers or IP addresses for alpha testing and percent rollouts) is a min bar for any reasonable implementation in Dark.
I think that what you're calling an experiment framework is what we call feature flags.
It’s good your feature flags have the necessary...features. The same word is often used for global bools; I wish there was a better word (eg “experiment” or “experiment flags”) or documentation to brag that you’re doing more than simple flags.
I’m also curious what kind of infrastructure you use to affinitize the rollout to particular customers. I’m used to that being coupled to user or device IDs, which I don’t see as a coupled feature of your stack.
Re: Dark emerges with ‘deployless’ software model
#173Re: Dark emerges with ‘deployless’ software model
#174Earlier quoted context omitted.
Ok, so how do I just look up the langue, tools and play around with it? The website shows no examples of what the language actually is, what tooling actually exists etc. I got accepted to the private alpha but I can't tell why I should actually use this.
We'll be showing it off in September (come to the launch: https://darklang.com/launch ), and the only way before that is to get onboarded into the alpha. But if you don't know why you need it, it's probably not a good fit for you just yet.
>But if you don't know why you need it, it's probably not a good fit for you just yet
Right, it's def not a failed marketing push as to why your website talks about a programming language, with no actual examples of said programming language.
SMH, get some self awareness buddy.