4 ms·

I worry how companies will be able to provide similar services in the future, as more and more stuff is running as services in the cloud. It’ll most likely bec

I worry how companies will be able to provide similar services in the future, as more and more stuff is running as services in the cloud. It’ll most likely become more and more costly, as you won’t be able to buy offline version of some complement, and keep it working on your support device for 30 years. You’ll need to build all of them yourself. And that will also most likely mean it’ll be less reliable.

est31 6y ago
People will just build new airplanes every 6 weeks when a new rustc is released. Economic growth has to come from somewhere...
sandworm101 6y ago
Lol. Aircraft software running "in the cloud". Damb right it will. It will also work "in the rain" and "in the snow".
- james_s_tayler 6y ago
  Is "Snow computing" when everything freezes up?
- samus 6y ago
  The maintenance and logistics software for the F35 is supposedly implemented with a cloud architecture. Though the project is probably old enough that the cloud hasn't found its way into the flight systems yet...
HeyLaughingBoy 6y ago
Then you "just" don't use those services. It's not rocket science ...ok sometimes it literally is... but part of reliability engineering is knowing where your weak points are and preventing them from causing problems before it happens. Since the default state is building it yourself, not being able to buy an offline version of the service is no less reliable than the alternative.
- justapassenger 6y ago
  Default state is never building it yourself. When you approach new problem, you don't go "ok, let's first start a fire, then melt some silicon to build me some transistors". You always start based on something. And as more stuff is moving to be cloud based services, you'll need to build more and more of that stuff yourself. Taking it to the extreme - will CPUs in 30 years be cloud connected and require my service provider to work? Would OS be? Or scheduler? Or terminal? Or dynamic linker for libraries? Or IPC framework? How much of that stuff will companies need to build in the future themselves? It's not like software will get simpler, so they won't need it.
  - HeyLaughingBoy 6y ago
    Changing your assumption of "default state" doesn't change what I said. The point is that systems like this go through various analyses before being built. Reliance on outside services/components is one of those analyses. Let's say that a critical component is an online service. Someone will do the analysis of what happens when that service goes away. If the outcome is that you can expect to failover to something else with acceptable degradation of performance, then the service might be used. If not, then the choice is find a more reliable service, build it yourself or do without the feature. And those last two choices will themselves be subject to another analysis. One of the nice things about capitalism is that if there's a profitable gap in products/services, that gap will eventually be filled. All new CPUs need to cloud connected and require a service provider, but there's a big industry that can't deal with that? I guarantee that someone will corner that market and start building CPUs that don't need to be cloud connected and require a service provider. Either that, or sufficiently reliable cloud services, tailored to that market, will appear.
    - justapassenger 6y ago
      You seem to forget about economy of scale. Sure, void will be filled, but you'll get worse, and more expensive solutions. Economy of scale is ruthless. And this isn't only talking about software you put on the devices. Developer environment is going to degrade even more and more. It's already bad experience to develop stuff for things that need long term support, and with cloud trends, it'll only get worse, as set of tools that you could possibly use will reduce.

est31 6y ago

People will just build new airplanes every 6 weeks when a new rustc is released. Economic growth has to come from somewhere...

sandworm101 6y ago

Lol. Aircraft software running "in the cloud". Damb right it will. It will also work "in the rain" and "in the snow".

james_s_tayler 6y ago
Is "Snow computing" when everything freezes up?
samus 6y ago
The maintenance and logistics software for the F35 is supposedly implemented with a cloud architecture. Though the project is probably old enough that the cloud hasn't found its way into the flight systems yet...

HeyLaughingBoy 6y ago

Then you "just" don't use those services. It's not rocket science ...ok sometimes it literally is... but part of reliability engineering is knowing where your weak points are and preventing them from causing problems before it happens. Since the default state is building it yourself, not being able to buy an offline version of the service is no less reliable than the alternative.

justapassenger 6y ago
Default state is never building it yourself. When you approach new problem, you don't go "ok, let's first start a fire, then melt some silicon to build me some transistors". You always start based on something. And as more stuff is moving to be cloud based services, you'll need to build more and more of that stuff yourself. Taking it to the extreme - will CPUs in 30 years be cloud connected and require my service provider to work? Would OS be? Or scheduler? Or terminal? Or dynamic linker for libraries? Or IPC framework? How much of that stuff will companies need to build in the future themselves? It's not like software will get simpler, so they won't need it.
- HeyLaughingBoy 6y ago
  Changing your assumption of "default state" doesn't change what I said. The point is that systems like this go through various analyses before being built. Reliance on outside services/components is one of those analyses. Let's say that a critical component is an online service. Someone will do the analysis of what happens when that service goes away. If the outcome is that you can expect to failover to something else with acceptable degradation of performance, then the service might be used. If not, then the choice is find a more reliable service, build it yourself or do without the feature. And those last two choices will themselves be subject to another analysis. One of the nice things about capitalism is that if there's a profitable gap in products/services, that gap will eventually be filled. All new CPUs need to cloud connected and require a service provider, but there's a big industry that can't deal with that? I guarantee that someone will corner that market and start building CPUs that don't need to be cloud connected and require a service provider. Either that, or sufficiently reliable cloud services, tailored to that market, will appear.
  - justapassenger 6y ago
    You seem to forget about economy of scale. Sure, void will be filled, but you'll get worse, and more expensive solutions. Economy of scale is ruthless. And this isn't only talking about software you put on the devices. Developer environment is going to degrade even more and more. It's already bad experience to develop stuff for things that need long term support, and with cloud trends, it'll only get worse, as set of tools that you could possibly use will reduce.