6 ms·

I'm wondering what makes swift ready for the enterprise ecosystem. It barely seems to meet the requirements of the "enthusiastic consumer" outside of Apple OS.

barkingcat 10y ago
To be ready for the enterprise ecosystem basically means that you can sue someone if things go wrong, and you can buy support packages for enormous sums of money. IBM is saying that you can 1) buy bluemix swift from them, and 2) sue them if anything goes wrong - but since they have a great legal team, they probably got ironclad agreements ready to go.
- madeofpalk 10y ago
  > sue them if anything goes wrong Cool! https://www.theguardian.com/australia-news/2016/sep/23/australian-bureau-of-statistics-lays-blame-for-census-bungle-on-ibm https://www.theguardian.com/australia-news/2016/sep/23/austr...
- themihai 10y ago
  I thought stability of the ecosystem (i.e. stable standard library) was also a "must" for adoption by the enterprise. Never thought that a language in flux with "hosting" support from IBM is enough. But now it seems the enterprise world is eager to try the coolest thing and rewrite/refactor it after the next release as long as someone will host/run it. Now that you enlightened me I can see the stock markets, hospitals, banks and all enterprise consumers embracing Swift and eager to upgrade once Swift 4 is released.
  - pjmlp 10y ago
    Java and Smalltalk both benefited from IBM support. However, Smalltalk later suffered when Visual Age for Smalltalk became Eclipse and IBM switched focus to just Java.
  - iheartmemcache 10y ago
    IBM's BlueBix et al was a direct result of the purchase of Rackspace, which was strategic buy to hedge against the growth market of Amazon and it's bazillion EC2-esque offerings. (Likely in response to seeing Amazon's success, almost strategically similar to why Azure and Google's App Service or whatever exist.) They're still making money hand over fist in maintenance keeping the mainframes up (your state's DMV won't move off MVS/zOS as long as support for their old JCL/REXX stuff is still available, especially those 'cheap' z13s which come in at under 100k) but that's an entirely different tier of customer.
    - themihai 10y ago
      Maybe you mean softlayer. As far as I know Rackspace was recently bought out by someone else. I understand IBM wants to be cool but it doesn't make sense to promote an immature technology as enterprise ready...
- erikpukinskis 10y ago
  It's not about having someone to sue it's about attracting blame. Blame assignment isn't really about who made good decisions, or who worked hard, or any of that, it's a combination of how bad it went and who made uncommon choices: common choice + failure = external blame (who could have seen it coming?) uncommon choice + failure = it's your fault for doing it weird common choice + success = great job! uncommon choice + success = I don't trust you, but you might be a genius Since hierarchical relationships function using blame ("responsibility"), making predictable decisions becomes more important than making good decisions at some depth of hierarchy.
  - iheartmemcache 10y ago
    This is probably the most important comment in this thread. Being able to delegate blame out to $common-choice on project failures is the difference between that CIO being able to say "hey, not my fault, I bought the Oracle platinum integration package!" to satisfy the board rather than "sorry guys, I really thought my node.js idea would work, it's all the rage with the kids! Haven't you ever heard of Slack?!" (If this sounds strange to you, just replace "node.js" with "Rails 2" and you'll see why ASP.NET and Java's still king in any company with a market cap > 100MM && age > 20 years. It's about continuity of support, and Windows 2016 servers can still run ASP Classic and .NET 2 WebForms apps just fine.) "Responsibility" == risk mitigation for that purchasing authority.
    - l1ambda 10y ago
      Slack is PHP and Jquery, no nodejs AFAIK.
  - nandhp 10y ago
    > common choice + failure = external blame (who could have seen it coming?) "Nobody ever got fired for buying IBM"

barkingcat 10y ago

To be ready for the enterprise ecosystem basically means that you can sue someone if things go wrong, and you can buy support packages for enormous sums of money. IBM is saying that you can 1) buy bluemix swift from them, and 2) sue them if anything goes wrong - but since they have a great legal team, they probably got ironclad agreements ready to go.

madeofpalk 10y ago
> sue them if anything goes wrong Cool! https://www.theguardian.com/australia-news/2016/sep/23/australian-bureau-of-statistics-lays-blame-for-census-bungle-on-ibm https://www.theguardian.com/australia-news/2016/sep/23/austr...
themihai 10y ago
I thought stability of the ecosystem (i.e. stable standard library) was also a "must" for adoption by the enterprise. Never thought that a language in flux with "hosting" support from IBM is enough. But now it seems the enterprise world is eager to try the coolest thing and rewrite/refactor it after the next release as long as someone will host/run it. Now that you enlightened me I can see the stock markets, hospitals, banks and all enterprise consumers embracing Swift and eager to upgrade once Swift 4 is released.
- pjmlp 10y ago
  Java and Smalltalk both benefited from IBM support. However, Smalltalk later suffered when Visual Age for Smalltalk became Eclipse and IBM switched focus to just Java.
- iheartmemcache 10y ago
  IBM's BlueBix et al was a direct result of the purchase of Rackspace, which was strategic buy to hedge against the growth market of Amazon and it's bazillion EC2-esque offerings. (Likely in response to seeing Amazon's success, almost strategically similar to why Azure and Google's App Service or whatever exist.) They're still making money hand over fist in maintenance keeping the mainframes up (your state's DMV won't move off MVS/zOS as long as support for their old JCL/REXX stuff is still available, especially those 'cheap' z13s which come in at under 100k) but that's an entirely different tier of customer.
  - themihai 10y ago
    Maybe you mean softlayer. As far as I know Rackspace was recently bought out by someone else. I understand IBM wants to be cool but it doesn't make sense to promote an immature technology as enterprise ready...
erikpukinskis 10y ago
It's not about having someone to sue it's about attracting blame. Blame assignment isn't really about who made good decisions, or who worked hard, or any of that, it's a combination of how bad it went and who made uncommon choices: common choice + failure = external blame (who could have seen it coming?) uncommon choice + failure = it's your fault for doing it weird common choice + success = great job! uncommon choice + success = I don't trust you, but you might be a genius Since hierarchical relationships function using blame ("responsibility"), making predictable decisions becomes more important than making good decisions at some depth of hierarchy.
- iheartmemcache 10y ago
  This is probably the most important comment in this thread. Being able to delegate blame out to $common-choice on project failures is the difference between that CIO being able to say "hey, not my fault, I bought the Oracle platinum integration package!" to satisfy the board rather than "sorry guys, I really thought my node.js idea would work, it's all the rage with the kids! Haven't you ever heard of Slack?!" (If this sounds strange to you, just replace "node.js" with "Rails 2" and you'll see why ASP.NET and Java's still king in any company with a market cap > 100MM && age > 20 years. It's about continuity of support, and Windows 2016 servers can still run ASP Classic and .NET 2 WebForms apps just fine.) "Responsibility" == risk mitigation for that purchasing authority.
  - l1ambda 10y ago
    Slack is PHP and Jquery, no nodejs AFAIK.
- nandhp 10y ago
  > common choice + failure = external blame (who could have seen it coming?) "Nobody ever got fired for buying IBM"