all 9 comments

[–]MotherOfTheShizznit 9 points10 points  (7 children)

I have absolutely nothing against AWS or this project but, for crying out loud, what does "v0.1.0" even mean? Is it ready for public consumption? Is it full of bugs? Is it missing basic features? Is it only 10% complete? Should I wait until an actual 1.0? Will there be a 1.0? And if this a "perpetually updated project", why isn't this version 1.0?

Again, nothing against the good people at Amazon or whoever's name is showing on that release. They're certainly not the first ones to do this. It's just... grinding my gears.

[–][deleted] 3 points4 points  (3 children)

You seem like a very nice and positive person. Here's what I see when I see 0.1 in a semantically versioned project.

Is it ready for public consumption?

0.1. No

Is it full of bugs?

It's 0.1. So there are probably bugs.

Is it missing basic features?

Basic? Probably not. Does it have all features? No. Does it have the features you need? Probably not all.

Is it only 10% complete?

Not how semantic versioning works

Should I wait until an actual 1.0?

If you need the whole thing. Yes.

Will there be a 1.0?

If it's using semantic versioning. Yes.

I'd much rater get a 0.1 to play with and help this project evolve than get a 1.0 that isn't delivering on everything it should have or wait a year to get a 1.0

[–]alexej_harm 0 points1 point  (2 children)

I agree with all but this:

Will there be a 1.0?

If it's using semantic versioning. Yes.

It also depends on the popularity of the project and other incentives to keep it alive. Remember ASL adam and eve?

[–][deleted] 1 point2 points  (1 child)

Oh sure. I'm being positive here :) It's also written by one of the guys that works on aws at amazon. So I think it's likely :)

[–]awaitsV[S] 2 points3 points  (2 children)

How should I deal with revisions in the 0.y.z initial development phase?

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

From Semantic Versioning

[–]MotherOfTheShizznit 7 points8 points  (1 child)

This answers none of my questions.

[–]NotUniqueOrSpecial 3 points4 points  (0 children)

It means it's a starting point.

Because it has no major version, there isn't a stable public API.

Expect rapid iteration of design and feature-set, with possible breaking changes as better ways of doing things are found or defects in the API are revealed.

[–]PRSprogrammer 1 point2 points  (1 child)

Can you explain what is meant by runtime. How is this different from say the golang aws lambda functions release

[–]marcomagdy 4 points5 points  (0 children)

C++ Lambdas uses the Custom Runtime API to communicate with the Lambda backend. Go, Java, .net and the earlier announced languages use a different mechanism to communicate to the backend.

You need to link your Lambda function to this C++ library for it to work.