Saaster

It’s commendable to want to start a “cooperative socialist paradise”, you can pitch it and see if there’s interest with others. But it’s totally OK as well for others to not want to join that, and go the more conventional way.

It sounds like Nate is set on starting a conventional company, and that should be fine. The previous company apparently never made financial sense so it also doesn’t work to just continue that model directly and so things and people get cut. It can be both hard to communicate and to hear, doubly so when you’re emotionally invested. That’s why IMO it’s important to separate your self worth from your job at some level, for your own mental wellbeing.

We bought our .com after we became "successful" and had significant revenue, however it just redirects to our non-dot-com, because it's too much of a hassle and SEO risk to change at this point.

If I as a SaaS provider get my SSO SAML integration via a provider like Okta or Auth0, the auth provider pricing itself is also on a "call us" tier, with a per-federation pricing in the low four figures for each individual company connecting to me via SAML.

It's pretty insane, so I'll state it again: To have a company connect to my SaaS via SAML, I as the SaaS provider have to pay my auth provider $X,000 per year for the privilege. Not counting the base enterprise tier pricing for the auth solution itself. So then I have to roll my own solution if I want to provide it for free, and I get the joy of supporting the long tail of broken SAML implementations on both the service and identity provider sides. For free. In a perfect world SSO wouldn't be a shitshow and everyone could have it for free, unfortunately that is not this world.

The code running in my browser isn't a multi-tenant production server, with access to the filesystem and DBs.

Does Deno have some built in way to vendor / download the imports pre-execution? I don't want my production service to fail to launch because some random repo is offline.

Let's keep moving those goalposts 'til the other team can't even see the goal anymore!

If business travel is reduced, you can expect the cost of regular coach class tickets to increase massively as the former pays for the flight and the latter is just there to wring a bit more profit out of the trip.

Business travel right now is non-existent and many companies are finding that things still work just fine without it and will not return to previous spend levels.

Zoom works great on Linux, it's a proper native app and the quality is excellent. Screensharing is notoriously tricky on Wayland and has been a shifting target that is just now starting to settle, I'm sure it'll eventually work.

It's still the exact same potato-cam in every model, from the Air to the $$$ MacBook Pro "16.

A primary driver of SaaS sales is trust. Nobody wants to bet on a platform that is going to pivot or shut down within 12 months. It's not about price, it's about disruption to business in both adopting and offboarding from any solution more complex than a todo list. For a lot of established companies, that unfortunately means they won't even consider you until you've been around for 1-2 years. We have a lot of customers who checked us out on day 1, and now 3-4 years later are coming back saying "Cool, you guys are still in business, now we can try you out for real".

If you're building SaaS, go ahead and take that SaaStr article as gospel (and a lot of their other writing as well). Maybe you're a special unicorn where it doesn't apply, but most likely you aren't.

My biggest worry with React is that it has restless developers with idle hands.

I have (a lot of) component code that will never be converted to hooks. Can I rely on you not to flake out and pull an Angular on me?

As a user of a library, I don't really care how it works. Under the hood it can be arbitrarily complex or simple, and please feel free to change the implementation weekly for all I care. I care very deeply about my own components, when they render, what causes them to re-render, and that I can control and reason about when they re-render. Also, stability of API (in number of years) is way more important than new whiz-bang features.

I feel that with class components I have a really good understanding of what is rendering and most importantly, when. componentDidMount, shouldComponentUpdate, PureComponent, etc. With hooks, it's much more magic. And clarity of rendering is literally the one thing I want from React.

We have two projects, one using class components and one using hooks, and working on the class components one is unexciting, straightforward, sometimes repetitious, but never confusing. When writing hooks on the other hand it's constant gotchas; can't do that here, didn't memoize this, can't call that within this, etc. fuzzing until it works as Reacts expects. And then the bloody thing still renders on every frame. Back to the drawing board to figure out the right magic incantation. Probably memoize a few more layers, ugh.

At the end of each PPP application with your bank, you get the same SBA PPP form to sign as the SBA has publicized on their web page. You then have to sign and pinkie swear that the funds are necessary and going to payroll.

The banks are doing jack shit in terms of useful work except shoveling application's SBA's way, with the SBA being the ultimate approver of the loan anyway! Bank are just in middle and limiting applications to their existing customers for no good reason whatsoever.