Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Flow

flow.microsoft.com

Post reply on HN
Print view View original

71–80 of 100 posts

Re: Microsoft Flow

#71

Post by toyg »

rossng wrote: post #65
toyg wrote: post #41

Earlier quoted context omitted.

Dev A: "So, what other integrations should we add?" Dev B: "What about Skype? It's one of our products." Dev A: "I don't care, I only use Slack. Screw our users, right?" Dev B: "What about Skype for Business? People actually pay for that." Dev A: "Nah, Wunderlist is much more important. Much ."

Judging by the state of the various Skype apps, I suspect that getting anything added to Skype is a kafkaesque nightmare. I bet these guys just let it drop in order to get their product released.

Last time I checked, the main problem with regular Skype was being registered and accredited by MS as a legit app. One would expect MS would trust itself...

Skype For Business / Lync is a total nightmare of enterprisey permission models, yeah.

Re: Microsoft Flow

#72

Post by crandycodes »

sheraz wrote: post #59
stonedge wrote: post #45

To me, this looks like their own implementation of the Azure Logic Apps product. ( https://azure.microsoft.com/en-us/documentation/articles/app... ). I don't believe this is intended to be a consumer level product at all. In that sense, it's not an IFTTT competitor. Given it's got implementation points to Sql Azure, Azure Blob storage, swagger, etc. this is likely meant as a product for devs to use to hook-up integra…

Exactly what I was going to say. I setup some logic apps but never really dug into this much beyond their demos. Following on the heels of this will be Azure's Functions (Serverless/Lambda) architecture, which will overlap some things here (for devs).

/* I'm a PM on Azure Functions */

Logic Apps and Flow are done by the same team, actually, so that's no surprise. Logic Apps is for "Azure" users, which is mostly IT Pros and Dev. Flow is intended to compliment Power Apps. They can both be built by users aren't necessarily pro devs, but can use a drag-n-drop interface for configuring things.

Functions are code driven by events. Logic Apps are workflow driven by events. You can actually use the two together, which makes for some cool scenarios.

Re: Microsoft Flow

#73

Post by crandycodes »

arsalanb wrote: post #28
atonse wrote: post #23

Earlier quoted context omitted.

Ok I'll feed the troll. I've excitedly watched what Apple has done in the last 10 years (and exclusively use Apple devices in my home, and have convinced many family members to switch). But as a technologist who likes to see companies with great resources move fast, to me MS has been much more exciting lately as a tech company than Apple. We are seeing the manifestation of the new Satya Nadella decree, which went fro…

Firstly, I didn't intend to "troll" Microsoft. Well, I agree with the last sentence. Satya Nadella was the much needed U-turn from the Balmer era. It's just that by the standards Microsoft has set for itself, they've under-performed over the years. I'm talking about major failed experiments like Windows Vista, Lumia (or even the entire Nokia acquisition)

And I think that's why the "Satya U-Turn" is so promising. Vista and Lumia were Ballmer-era failures. I work at Microsoft on Azure; it feels like a new era. The open source feel is real, even if we might fail at it here and there. PMs on the freaking SQL Server team were using Macs, because they want to feel the pain of SQL users on Macs. It's really good stuff.

Re: Microsoft Flow

#75

Post by arsalanb »

crandycodes wrote: post #73
arsalanb wrote: post #28

Earlier quoted context omitted.

Firstly, I didn't intend to "troll" Microsoft. Well, I agree with the last sentence. Satya Nadella was the much needed U-turn from the Balmer era. It's just that by the standards Microsoft has set for itself, they've under-performed over the years. I'm talking about major failed experiments like Windows Vista, Lumia (or even the entire Nokia acquisition)

And I think that's why the "Satya U-Turn" is so promising. Vista and Lumia were Ballmer-era failures. I work at Microsoft on Azure; it feels like a new era. The open source feel is real, even if we might fail at it here and there. PMs on the freaking SQL Server team were using Macs, because they want to feel the pain of SQL users on Macs. It's really good stuff.

Absolutely. Now by my estimation there is still some effort going into supporting those Ballmer-era failures, but such is the burden of being a company as large as Microsoft.

Microsoft without the dead-weight of having to support failed tech — Now that is a place I would like to work.

Edit: Do you think that Microsoft is actively taking steps in trying to do away with supporting things like Vista, etc?

Re: Microsoft Flow

#76

Post by intended »

justsaysmthng wrote: post #60
CamatHN wrote: post #46

Earlier quoted context omitted.

You might be right in the certain situations but this is an open tool with a wide array of possible uses for people. Such a pessimistic approach doesn't allow for any exploration when think about its potential uses.

Frankly, I don't really care. Really. It might be the greatest tool ever created.. There's too much great software and not enough head space to fit it all in. This proliferation of tools and services hasn't achieved the proverbial "work less do more" which all of them promise. They are necessary in order to deal with the increased complexity of technology (and our lives), but the catch is - once we integrate them int…

Well, I've always found what you said to be true anyway, gloomy weather or not.

Theres a lot of tech which we are none the worse off for ignoring. The more curmudgeonly of us eventually figure out what is actually going to move the needle and what isn't.

And as a simple rule - nothing will make your life less difficult, it will only give you more spare time which will then be absorbed into work - or your job is redundant.

hmm, maybe it is the weather.

Re: Microsoft Flow

#77

Post by mistermann »

skocznymroczny wrote: post #32

Good thing they picked up a unique name that won't collide with any other similar named projects.

I wish when companies picked these common names that they would also define a ~unique search team for people to use, ie: "when discussing on forums please use msflow" or something like that.

Re: Microsoft Flow

#78

Post by badmiskallc »

toyg wrote: post #42
jhwhite wrote: post #31

Why would I use Flow over IFTTT?

Because it will (or rather should) better tie into MS properties like Sharepoint, Office365, Azure and so on, which lots of people already use for work. This said, they completely ignored Skype, so...

MS is iterating on skype web versions and and apis for skype and lync (skype for business). I'm sure it will come in time.

Re: Microsoft Flow

#79

Post by smithkl42 »

crandycodes wrote: post #72
sheraz wrote: post #59

Earlier quoted context omitted.

Exactly what I was going to say. I setup some logic apps but never really dug into this much beyond their demos. Following on the heels of this will be Azure's Functions (Serverless/Lambda) architecture, which will overlap some things here (for devs).

/* I'm a PM on Azure Functions */ Logic Apps and Flow are done by the same team, actually, so that's no surprise. Logic Apps is for "Azure" users, which is mostly IT Pros and Dev. Flow is intended to compliment Power Apps. They can both be built by users aren't necessarily pro devs, but can use a drag-n-drop interface for configuring things. Functions are code driven by events. Logic Apps are workflow driven by event…

*complement

Re: Microsoft Flow

#80

Post by arcticfox »

justsaysmthng wrote: post #60
CamatHN wrote: post #46

Earlier quoted context omitted.

You might be right in the certain situations but this is an open tool with a wide array of possible uses for people. Such a pessimistic approach doesn't allow for any exploration when think about its potential uses.

Frankly, I don't really care. Really. It might be the greatest tool ever created.. There's too much great software and not enough head space to fit it all in. This proliferation of tools and services hasn't achieved the proverbial "work less do more" which all of them promise. They are necessary in order to deal with the increased complexity of technology (and our lives), but the catch is - once we integrate them int…

This is basically IFTTT. Tons of people use IFTTT, even if I have only found a need for it a few times.

'you probably don't need any js lib for your project' is true, but 'I can probably use modern JS libs to write a competitor 5x faster than your from-scratch project, assuming it's at least moderately complex' is also true.

Post reply on HN