Hacker Newsnew | comments | show | ask | jobs | submit | wahnfrieden's comments login

Salt has an agent-less option as well.

-----


Indeed it does. Salt-SSH: http://docs.saltstack.com/en/latest/topics/ssh/

It was recently declared production-ready, but it isn't intended to be an alternative to the standard Salt fileserver. Seems like it's more of an easy way to bootstrap machines.

-----


View as function of model isn't a concept foreign to FRP either - MVVM is a common pattern together with ReactiveCocoa.

-----


This depends greatly on local law.

-----


Try playing draft, instead.

-----


Faster dev cycles can be safe, even safer, as long as the changes are accordingly incremental. See the whole "continuous delivery" line of thought.

-----


Even PayPal was bootstrapped partly with what he made off a previous startup.

-----


I doubt Google is worried about unfairly weighting pages it indexes with Javascript that takes so long to run, hence the cutoff. It's more a question of where to place the cutoff than whether to have one at all, which is absurd.

-----


No, the question is neither of those. The question is how to define the cutoff in a portable way that enables interoperability and long-term stability. A document format where every implementation has its own secret cutoff that also probably changes all the time is just idiotic if your goal is interoperability.

-----


IANAL, but these regulations and organization requirements in my experience haven't cared about this. A common requirement is physical location of servers / the data on them which this satisfies.

-----


VPC-only sounds like a giant caveat, and it is, but this is a good opportunity to note that this is the trend now with AWS and the direction they're heading - (non-VPC) "EC2 Classic" is being gradually phased out, VPC is now the default for new accounts, and most new features are being added only to VPC. So, time for everyone to start thinking about migrating.

-----


AWS recently announced ClassicLink [1], which helps with migration: "In order to allow EC2-Classic instances to communicate with these resources, we are introducing a new feature known as ClassicLink. You can now enable this feature for any or all of your VPCs and then put your existing Classic instances in to VPC security groups."

[1] https://aws.amazon.com/blogs/aws/classiclink-private-communi...

-----


> this is the trend now with AWS and the direction they're heading - (non-VPC) "EC2 Classic" is being gradually phased out

New AWS accounts can't even use EC2 Classic, it's effectively deprecated at this point.

-----


They will hopefully introduce a new "classic" (as an abstraction over VPC) at some point, unless they want to lose many low-end customers to "easier" clouds.

Having this level of control can be nice, but most of it really needs to be optional because for most deployments it does nothing other than add an excessive amount of unneeded complexity.

Some of the APIs are outright hostile, e.g. 'delete_vpc' which makes you track down half a dozen dependencies (without providing hints about which those might be) before you're allowed to delete a VPC.

-----


They kinda do, the default vpc they set up on new accounts has everything you need to use it without ever looking at vpc setup

-----


> unless they want to lose many low-end customers to "easier" clouds.

I've never gotten the impression that AWS is interested in building a 'cloud' for those less technically inclined. Heroku and others fill that void, EC2 is where you move after Heroku doesn't fit the bill and before dedicated hardware does.

-----


Beanstalk tries to serve that Heroku-level market, I think.

-----


Any info on how to take advantage of this development?

-----


I did by buying EXAS when the new CEO came in at about $2. The previous management didn't have what it took to get it off the ground. The availability to buy the test came out this quarter so sales numbers are not in yet (but it is fully reimbursed at ~$500, where management said they would make a killing at $300). So after doing your due diligence, it may be worth waiting for the sales numbers to come out and buy on any weakness.

The other way to take advantage is to get yourself screened :)

Disclosure: I own shares

-----

More

Guidelines | FAQ | Support | API | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: