3 ms·

> Just because you're not managing a server doesn't mean it doesn't exist Wireless internet is still connected to the rest of the internet via a wire somewher

> Just because you're not managing a server doesn't mean it doesn't exist Wireless internet is still connected to the rest of the internet via a wire somewhere; the obvious point being made is that your phone or laptop doesn't need a wire. Serverless here doesn't mean that servers no longer exist, but that you are not working at the server level to accomplish what you're trying to do.

dragonwriter 11y ago
> Serverless here doesn't mean that servers no longer exist, but that you are not working at the server level to accomplish what you're trying to do. So, just like every PaaS everywhere, since long before the new buzzword.
- pmontra 11y ago
  Understood, but that means that Rails has been serverless almost forever because of Heroku. The console is simpler than the one of AWS and you deploy with git push. You didn't have to worry about the db because you only had PostgreSQL for a long time. And you could buy add on services to do almost everything. It just happened before the buzzword was born.
spriggan3 11y ago
Wireless is accurate for handsets, since you're not using a wire to exchange data, the communication is wireless. Serverless is totally inaccurate for scripts uploaded ON a server. Since they are executed on a server. The scripts are executed and its result are potentially served from A SERVER. The fact that you don't manage it yourself doesn't change that. That's an horrible example you are using to try to make your point, it just doesn't work.
stephenr 11y ago
> Wireless internet is still connected to the rest of the internet via a wire somewhere Wireless refers to a specific component of the connection - the the connection between your device and the relevant wireless base station. No one technical is claiming "wireless internet" - and if they are, they're as guilty as the server-less crowd - they're claiming a wireless local area network (wifi), or wireless wide area network (3g/4g/WiMax, etc) - they're not inherently "the internet" they're just a radio based method for transferring packets of data. Here, you have developers literally uploading the code they've written ( the javascript code that runs on AWS' 'lambda' service ), configuring 5 separate rented services and then claiming "look ma, no server".

dragonwriter 11y ago

> Serverless here doesn't mean that servers no longer exist, but that you are not working at the server level to accomplish what you're trying to do. So, just like every PaaS everywhere, since long before the new buzzword.

pmontra 11y ago
Understood, but that means that Rails has been serverless almost forever because of Heroku. The console is simpler than the one of AWS and you deploy with git push. You didn't have to worry about the db because you only had PostgreSQL for a long time. And you could buy add on services to do almost everything. It just happened before the buzzword was born.

spriggan3 11y ago

Wireless is accurate for handsets, since you're not using a wire to exchange data, the communication is wireless. Serverless is totally inaccurate for scripts uploaded ON a server. Since they are executed on a server. The scripts are executed and its result are potentially served from A SERVER. The fact that you don't manage it yourself doesn't change that. That's an horrible example you are using to try to make your point, it just doesn't work.

stephenr 11y ago

> Wireless internet is still connected to the rest of the internet via a wire somewhere Wireless refers to a specific component of the connection - the the connection between your device and the relevant wireless base station. No one technical is claiming "wireless internet" - and if they are, they're as guilty as the server-less crowd - they're claiming a wireless local area network (wifi), or wireless wide area network (3g/4g/WiMax, etc) - they're not inherently "the internet" they're just a radio based method for transferring packets of data. Here, you have developers literally uploading the code they've written ( the javascript code that runs on AWS' 'lambda' service ), configuring 5 separate rented services and then claiming "look ma, no server".