Live data from Hacker News

Dark emerges with ‘deployless’ software model

techcrunch.com

101–110 of 174 posts

Re: Dark emerges with ‘deployless’ software model

#101
post #21
post #4

Personally I’d be surprised if this startup is around in five years

Right. It sounds like a fun thing to build. But i'd love to read an honest explanation from an investor of why they funded it. Dark raised 3.5 million USD from eight funds, which is under half a million each; maybe that amount is so small that a VC will invest it just for fun?

in theory having an online code editor that makes deployments and handles the infrastructure for you sounds good and from this i can see the logical deduction that this platform would save costs and simplify processes. But they are most likely not technical and as such don’t understand that code is written the way it is due to the many variations between projects.

Re: Dark emerges with ‘deployless’ software model

#102
For the last 10 years I've been working mostly on CI and CD automation for a few projects that as part of their offering tried to automate the deployment for their clients.

In general when you try to simplify a process you increase the level of abstraction which leads to additional complexity in terms of customization and integration with third party systems and tools. Then you decide that it is a good idea to offer integration with the third party systems and tools and you increase the abstraction even more which increases the complexity even more. Also in the end you wonder if you are in the CD tools business or you are offering your core product.

It is much more productive to develop the product in mind with the tools for deployment that are already available. Unless you want to have a product and a "Services" division that configures and operates your product for the clients...

Re: Dark emerges with ‘deployless’ software model

#103

Radical approach - they flip the whole thing upside down. The biggest challange is not new language or ide per-se imho - but detachment from git, this has implications ie. it seems open-source hostile (you can't use it for open-source code, or am I wrong?); what about libraries? Technically very interesting. Practically I'm not sure it'll fly, at any complexity project development means in big part playing around loc…

detachment from git? really?

this strikes me to be odd: why is a SCM all that important? even more important than a language and the ecosystem or as a vendor login already mentioned by several posters?

Re: Dark emerges with ‘deployless’ software model

#104
post #22

I've been coding since I was a kid, for about 33 years. I actually think they are right about all of this stuff. Including the part about combining everything together into a holistic solution. It sounds like a terrific idea. Unfortunately most people seem to hate good ideas. Especially if they represent a significant change from the status quo. And programmers are afraid to touch anything that's "easy" or moves away…

While I also long for more powerful frameworks / libs that lighten the burden of infrastructure code and other boiler plate code having it all dominated by one company, specially a small startup is a grave problem for adoption.

I think representing programs as text is the simplest form of programs that can be used by humans and computers. And that's why is has stuck.

Re: Dark emerges with ‘deployless’ software model

#105
post #34

Earlier quoted context omitted.

Lambda is the antithesis of frictionless development, most of your life is invested in figuring out the Lambda way to do things, just like App Engine before it "I just need to run this function every 10 minutes" .. (3 blog posts later) .. (1 lunch break later) .. (5 Git commits across 3 repos containing a mix of CloudFormation, CloudWatch and Terraform, 3 new IAM policies and 12 S3 buckets with completely unmemorable…

I'm working on DETA – it abstracts away Lambda/S3/CF/CW/TF. Would you be interested in a quick chat?

I hate acronyms so much :'(. To anyone reading this, please write the full term at least once before using an obscure acronym. It's a pain to decipher, creates confusion, and results in miscommunication. I have no idea what DETA is for and google doesn't help at all. My best guess is "Deployment Estimate Time of Arrival", which doesn't make any sense...

Sorry for the rant.

Re: Dark emerges with ‘deployless’ software model

#106
I’ve used Dark for the backend of a mobile app (> 20k installs) during the beta, and it has been an incredible experience. Something like 30 lines of code do it all.

Dark is a game changer in my opinion for getting a prototype online as quickly as possible, or a lightweight backend - and I imagine it can and will support much more.

Re: Dark emerges with ‘deployless’ software model

#107
post #34

Earlier quoted context omitted.

Lambda is the antithesis of frictionless development, most of your life is invested in figuring out the Lambda way to do things, just like App Engine before it "I just need to run this function every 10 minutes" .. (3 blog posts later) .. (1 lunch break later) .. (5 Git commits across 3 repos containing a mix of CloudFormation, CloudWatch and Terraform, 3 new IAM policies and 12 S3 buckets with completely unmemorable…

I'm working on DETA – it abstracts away Lambda/S3/CF/CW/TF. Would you be interested in a quick chat?

Dirty Eccentric Telecom Asshats?

Re: Dark emerges with ‘deployless’ software model

#108

Earlier quoted context omitted.

I'm working on DETA – it abstracts away Lambda/S3/CF/CW/TF. Would you be interested in a quick chat?

Dirty Eccentric Telecom Asshats?

atlanta" rel="nofollow">http://www.atlantaoutcallescorts.com/">atlanta escorts

Re: Dark emerges with ‘deployless’ software model

#109

Earlier quoted context omitted.

I'm working on DETA – it abstracts away Lambda/S3/CF/CW/TF. Would you be interested in a quick chat?

Dirty Eccentric Telecom Asshats?

[url=http://www.atlantaoutcallescorts.com/] atlanta escorts[/url]

Re: Dark emerges with ‘deployless’ software model

#110
post #17

It sounds pretty cool until the point where you read something like: "Deployment is risky because you’ve only tested on your own machine, and now you need to run the same code on many different machines, to serve (millions of) users." Which makes it seem like they don't even know about the existence of Docker; making me doubt most of what they'll try to sell us.

it runs on kubernetes, so...
Post reply on HN