Ex-PagerDuty here. Without weighing in on the criticisms of pricing and innovation with the product, I will say that the value of PagerDuty is its reliability in notifying you when it receives a signal from a system. Rebuilding the product isn't just asking an LLM to spit out a web app to do scheduling, it's in the notification pipeline (SMS, email, push notifications, Slack), maintaining all that and mobile apps too.
Just like Uber itself, this is one of those "I could replace this in a weekend" things that doesn't actually pan out that way.
For the time when OS 9 was relevant that would have been a RAM hog. My iBook (first generation) had 32 MB RAM on board (plus an upgrade slot, how refreshing).
Sure, that wasn't top of the line, but it would definitely restrict your ability to multi task with other programs at the same time. My memory is that many programs used far less than that, allowing you to easily have 5-7 programs open (I had a RAM upgrade for a total of 64 MB).
Maybe because those programs were not doing anything as graphically intensive as this. Or perhaps this programs caches more. When OS 9 was relevant were there any programs with comparable capabilities? Such statements are meaningless unless you have insight into how much memory this task should take (and even that is highly variable depending on how one wants to trade-off CPU vs memory usage). Only then can you determine the difference between a “RAM hog” and your computer being too small.
Wow. As a comparison, I just opened a new Google Maps tab in Chrome.
According to the Chrome Task Manager, the tab alone uses 433mb RAM and 34mb GPU memory footprint after first load.
Florb (an FLTK based map viewer similar to Dillo in specs) would use almost the same RAM as native Mac OS 9 software. And yet people say "JS software it's far better". Even a TCL/TK based viewer with TCCLib/TKLib it's far lighter.
JS is easier to develop, easier to deploy cross-platform, and, more importantly from a business perspective, easier to hire for. So it makes complete sense to use JS in the commercial world.
Cursor Remote Agents are important to our AI orchestration layer. It's possible that Claude can do this directly but Cursor Remote Agents made this laughably easy.
I just got a Docusign and it didn't work in Firefox, I had to use Chrome. That's a huge blow right there. (I sent negative feedback about this to Docusign.)
>There'll probably be a startup tomorrow that digests user input and boils out the noise to provide a robust enough signal to guide some monitoring agent, and it'll help some cases, and train us to be even worse at others.
Not even Fairphone can repair your phone if it's out of parts.
reply