HN user

Flipflip79

95 karma
Posts0
Comments25
View on HN
No posts found.

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

What’s the problem there exactly? There’s nothing necessarily diametrically opposed in the two articles. They’re almost complimentary really

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.

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.

Thanks for sharing!

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.

Genuinely just google whatever effect you want with “pure data”. E.g. “delay patch pure data” and you’ll find lots and lots of resources. If you want something deeper look for more generalized DSP tutorials in PD

I am only on mobile right now and travelling so can’t actually test this. But boy is it exciting to see a potential OSS alternative to max4live.

I think Max and m4l are well worth the price if it’s something you do all the time, but as a more casual user something with a lower cost of entry would be highly welcomed.