The Maverick fills that space but has limitations (less towing capacity than a 90's Ranger). I've seen it used by a ton of service folks that need a pickup but not for towing (1500 payload).

Even the Maverick is GVWR 5100. The original Ranger was around 3200 GVWR, which these days almost makes it a kei truck.

Hope this does well but the subway + walking is the way to go. Uber, taxis, etc are way too slow getting around manhattan per my recent trip.

What makes compilation fast is a good goal at places with large code bases and build times. Maybe makes less sense in smaller startups with a few 100k LOC.

This describes the classic scenario of "You don't have google's problems, so maybe stop trying to hype google's toys". Protobuf feels similarly developer-hostile vs alternatives, and I remember a lot of similar sentiment around using it. It's funny that people don't seem to learn the lesson.

Palo Alto has had AT&T fiber since 2019 depending on your location (but still not 100% coverage). I was lucky enough to be in an early coverage area but the price for 1GB symmetric has risen from $75/month to $115.

Google's Total Ad Rev ($238b) is almost double Meta's Ad Revenue ($132b).

So the GP's number is too high, and Google's share is at most 64%.

Either way, the OP's conclusion doesn't change much in a duopoly.

How are you different than a debt SaaS product like Sivo? Also is there a publicly viewable API?

Sivo provides the debt, using their underwriting structure.

We don't provide debt. we provide an end-to-end credit infra that covers origination, compliance, loan management, credit reporting, etc.

one other call out is that we allow our customers' users to always stay on their platform, without being redirected to a 3rd party, so they own the full UX and user experiences.

our api docs - https://pier-dev.readme.io

Thanks - so more loan origination/servicing/management as opposed to providing balance sheet lending (ala Canopy/Peach but with your own underwriting/compliance). Since customers need to bring their own credit warehouse/lending partner do you facilitate partner matching?

Looks like a wrapper over core data - was wondering if they made it thread safe.

This is a huge annoyance with CoreData, you can’t pass objects between threads.

I remember tearing my hair out over that, i did eventually get it working reliably across the 2 threads i needed and i swore if i ever had to try again i’d try something else, it was just so easy to start with

California occupational licensing strikes again. Just like the handyman who can’t do jobs > $500 (including materials). There’s a dead spot in that market between $500-$5000 which is the minimum most GCs will do work on.

Where would we be without the government putting their fingers into every little thing.

No dead spot, just unlicensed handymen

Handymen who can be forced out of their jobs or at least given a massive financial problem at the discretion of a bureaucrat or enforcement official and are therefore dependent on the good graces of those entities for their income.

The purpose of a system is what it does.

How much of this is coming from https://www.hoover.org/?

The 2nd edition circa 1988 uses ANSI style declarations.

And has never been updated ever since. Latest standard revision is ISO C17.

Thank god. I’d hate to see the book grow to a thousand pages.

On the other side it is full with outdated information and examples that lead to unsafe C code, not much to be happy about.

Name one from the second edition? I found the book’s examples to be fairly timeless.

I hear there are PDFs floating around on the internet, not that I would know anything about this of course ;)

My copy has no examples that use gets, although it is mentioned and I would agree that any such mention without a disclaimer that the function is impossible to use safely is a defect. Error handling, however, is generally present (or left out for brevity and noted). The functions in the standard for dealing with bounds checks are a new addition to the standard and a pox on the language regardless so it's not the best example of something new that the book should cover.

For those that care about security in C, even those functions are not the way to go, rather something like https://github.com/antirez/sds.

This is something that the book fails to teach, as it also has no mentions of modern static analysers practices, naturally given the book's age.

So at the end we get yet another C newbie writing future CVEs.

Those are both modern additions to the language, the latter of which I would say is a necessary part of any formal C education (I always mention "K&R with supplements" as the go-to way to learn C). Thus, I wouldn't call it "outdated" but maybe "incomplete"; all the information in the book is fairly up-to-date-but it is missing things that modern C programmers should know.