Im Canadian (Not Onario), so I really wanted to enjoy reading this as a peak inside what IT is like in that environment, but the LLM generated headers and patterns in the piece really put me off and I had to stop reading after a couple of minutes Im afraid.
I think this article would really benefit from being rewritten in your own words. The concept is good
Strongly agree for the same reasons. I don’t subscribe to his stuff for any particular niche, I just enjoy the “this is a thing I am going to learn lots about and make a video”.
These are very common in Canada still and anytime I see one I point at it and make the same joke “Looks it’s Vent Reznor” and my girlfriend has never once laughed. Oh well.
No, they are very tailored to that use case. They arent general languages - but they are still probably the best examples of successful visual programming languages.
It seems odd to me not to mention things like MaxMSP or PD in an article like this. Arguably Max is one of the most successful standalone visual programming languages (standalone in so far as it’s not attached to a game engine or similar - it exists only for its own existence).
I mean it is. I’m contesting it. So unless you have some quantifiable data it is in contention.
I like ICQ. I used it. But I really just don’t agree it had “more” features. It had _different_ features. And those features are just kinda wildly different because of how business and the internet had changed. I just really do not think it is a useful point to try and imply is a weakness of slack somehow.
I find myself continuously blessed to run slack on a daily basis and literally never encounter an issue with it being an electron app. My laptop must be magic or something!
You have a weird definition of rationality. If I am against Malware, a tech I don’t use, that would make me irrational? It’s completely acceptable to take an ethical stance against something you don’t use.
To be fair - if the SSO tax was just a single SKU for adding _just_ SSO to the platform and it was a reasonable like $2 - $4 a user addition, most people wouldn't care. When we refer to the SSO tax what we normally mean is that SSO is gated into the "Enterprise" category of a tool for some reason, implying that only Enterprises use SSO. The difference usually also includes other tools that the customer doesn't need (we only want SSO) and so the price difference is usually huge. It makes SSO unrealistic for non-enterprise size customers.
IMO thats generally what people refer to when they say SSO tax. It isnt discounting that providing SSO requires work, its that its never decoupled from a huge platform upsell.
I think using the term "Skip the SSO Tax.." has done a little disservice to you, and I understand why you chose that term, but this is more "Skip the SCIM tax" I think?
Regardless, I totally understand the use case and I can immediately put this to work for my team - we will likely contribute some recipes too.
Obviously, this is a totally subjective opinion without much critical thought - but for me PowerShell is just...ugly. Its ugly to write, the PowerShell Terminal in Windows is aesthetically ugly (the blue, yellow, and red). Error output is verbose (good) but awfully formatted. The whole thing just makes it feel "cheap" to me. Find it really hard to get over that bias now when I need to work in PS.