Earlier quoted context omitted.
Wait wat? I’m not disputing this but I came up on MacOS (it wasn’t even named that at the time, I believe I got started on System 6) and I never saw notifications like that.
Around Mac OS 9, they changed some types of errors from modal dialogs to floating palettes in the corner of the screen.
Growl in Retirement
201–210 of 245 posts
Re: Growl in Retirement
#202> Without Growl I do not know that we would have any sort of decent notification system in OS X They are right to say this, as the current Notifications system in OS X is ripped nearly pixel-for-pixel from Growl's implementation a decade ago. Like Spaces, Quicksilver, Cover Flow and others, Growl paved the way for a lot of the usability enhancements OS X gobbled up in recent years. Apple folks: take note. These are r…
> They are right to say this, as the current Notifications system in OS X is ripped nearly pixel-for-pixel from Growl's implementation a decade ago. I _think_ when Growl came out it was an open-source implementation of a notification UX that Apple had already demoed, either as a prototype or in some first-party apps, but it's just a vague memory. Does this ring a bell for anyone?
Re: Growl in Retirement
#203Earlier quoted context omitted.
FWIW, Growl predates iOS Edit: also, IIRC Growl was originally called "Notification Center", which is the name that Apple later used for their implementation of similar features Double edit: I should've RTFA which mentions my fun fact
IIRC, Growl was created because a similar feature of Mac OS didn’t make it into the first release of Mac OS X (sorry, can’t find pictures or documentation online) If so, I think its developers can’t be completely unhappy about the end result. Also, their code is (3-clause) BSD licensed. If the product lives on in spirit, does it really matter where the code came from?
Re: Growl in Retirement
#204I can say that Growl and desktop notifications are the very first thing I disable. Not once on 20 years of computing did I ever think: “I want applications to interrupt what I’m doing and steal my limited ADHD focus because they’re lonely and need attention”.
Re: Growl in Retirement
#205Earlier quoted context omitted.
I’m not from the US, could you explain this perspective to me? You give me internet on device X. How is it up to you how I use it?
In my experience in Canada from several years ago, the business teams in wireless telcos don't see it as providing you internet on device x. The ip connection on a device is a gateway towards a service, and the telecoms want to be providers of services, and the differentiator from competitors is having better and different services. In my opinion the biggest fear of those business development teams is to be treated a…
One group was trying to monetize services which were already free. Like make a list of data provided by stock mobile runtimes (Android, iOS), such as location data, and then create a developer portal for accessing that same data thru web services.
I'm having trouble remembering the details because I didn't even understand it at the time. My buddies were contractors, loved this kind of work, the money was good, and you could never fail. They thought there were helping me, get me some cheddar too.
I was briefly on the "mobile app services" team, it took me about 3 months to figure out what we were even doing. But there were lots and lots of meetings. Convened by empire builders and corporate climbers. Expensive suits. And lots of agile, kanban, scrum masters, velocity. To build something biggly impressive for which there would never be customers or revenue.
I assume there was at least one other group trying to "accomplish" the same thing.
The carriers would print money forever if they simply fired everyone unrelated to the actual network (cables and towers) and charged everyone a flat rate. And some overhead of the basic infrastructure services like provisioning numbers and 911.
No metering, no discounts, no custom phones, no carrier add-ons. The actual effort to create additional income streams was ridiculously wasteful.
It was crazy making. The actual features that would be awesome were never part of the conversation. For instance, I'd love to hear my voice mails on my laptop. I'm sure enterprise customers would love some tools for managing fleets of phones. Etc.
Maybe the carriers got high from the SMS profiteering, didn't realize that was a one-off bonanza, and have never recovered.
Re: Growl in Retirement
#206I'm still not sure if it works on unsigned apps, but considering all apps must be notarized on macOS, it doesn't really matter anymore.
Re: Growl in Retirement
#207Earlier quoted context omitted.
I’m not from the US, could you explain this perspective to me? You give me internet on device X. How is it up to you how I use it?
Same way it is up to me how you use books you bought (kindle) or songs you bought (any streaming crap nowadays). If you're shitty enough person (good businessman) you can profit off of anything.
Re: Growl in Retirement
#208Earlier quoted context omitted.
They could license the IP to forestall copyright/patent challenges and motivate creative devs, similar to security bug bounties.
I would guess that there is some legal problem with even referencing original app as an inspiration. Paying bounty for it would be even worse. If Apple were able to copy some app and in return mention your name as a co-author of some sort/tip you - that would probably be a life changing experience for most developers out there.
Losing your income stream certainly is life-changing.
How would Apple admitting they did it change your life for the better?
When you say "tip you", are you thinking "compensate you for all future lost sales and throw in an extra million or two"?
Re: Growl in Retirement
#209Earlier quoted context omitted.
I sorely miss Adium. I’ve learned to accept that I just have half a dozen mostly feature compatible chat apps open to communicate with the people who use them... but Adium was a real gem. I had it configured to minimal everything and never thought about what protocol I was using. Just a consolidated list of people and a tiny window with active chats in tabs. I’ve seen several attempts at unifying the current chat lan…
Oh wait, I’m still using Adium. I had no idea it was no more. Admittedly, we only use it at home, over bonjour. My wife and I use it to exchange interesting links and the occasional file. It shows its age, but still works (most of the time) for this purpose.
Most people were on RocketChat, but we’d had a Jabber server up forever, and people were just in the habit. We finally turned it off.
Tangent, sort of: RocketChat is just awful. Push notifications fail, it’s slow, and it just really does not want to mark a message as read. But they insist on having a local on-premises server, so what are you going to do? It’s just so much worse at the basics of chatting than Adium.
Re: Growl in Retirement
#210Earlier quoted context omitted.
You can make an AppleScript thing and call it from bash. I think this is the sort of documentation I used at one point: https://developer.apple.com/library/archive/documentation/La...
AppleScript does work well for this. It might also be nice for somebody to write a little UNIX-y command-line app that just allows you to pop up a notification, and potentially get a response to it. Maybe I will...