divyekapoor

AI slop. Skip

Pedantic note: The speed of light in glass, optical fiber and water is different from vacuum (much lower). On a certain scale, humanity also knows how to locally alter the speed of light though not to this extent.

Why do you need a cryptographic hash function for detecting duplicates? xxHash, rapidHash or anything that’s fast will do the job. There’s no need to be secure against inverses.

If the numbers are what they claim. They’re going to make it.

Not at all! All of these are real. ETag: expiry tag on HTTP(s), SAML: auth protocol, CSP: constraint sat, BGP: border gateway protocol, haproxy: load balancer, helm: k8s package manager, SOCKS5: http proxy protocol, sameSite/httpOnly: configs for HTTP security… and so on.

Never mind. The answer before me did a much better job.

What are you using to put Fable and Sol on each other?

Nettle (https://nettle.llc/) | REMOTE | Autonomous Data Processing | Compensation and Culture: Netflix rules - Top of personal market for your role and geo, stunning colleagues.

We're building an autonomous data processing system to make data engineers 10x+ more effective.

Currently open roles: ----------

Principal Product Manager https://www.linkedin.com/jobs/view/4319438984/

Staff or Senior Staff Tech Lead / Engineering Manager (Data Infrastructure) https://www.linkedin.com/jobs/view/4319530325/

Senior Marketing Executive https://www.linkedin.com/jobs/view/4317950237/

---------------- Please apply on LinkedIn if these sound interesting!

The US law is very expensive to comply with. Probably the most expensive in the world. Incorporate a subsidiary only and only if there’s a check in your hand. Then too, consider an LLC.

We do not want red and blue functions. Any language that implements async / await as coroutines instead of green threads is making a fundamental CS mistake. https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...

Concurrency's correct primitive is Hoare's Communicating Sequential Processes mapped onto green threads. Some languages that have it right are Java (since JDK17 - Java Virtual Threads), Go, Kotlin.

Broken for me as well.

"Sundar is announcing"... not "we are announcing"... speaks volumes as to the fact that this was a unilateral decision.

Demo gif & video please! You'd have more adoption if I knew what I was getting upon install.

Hate to be that guy that ruins your security researcher dreams. Your Argon2 memory hard function is useful against mass surveillance and belongs in mass market products. Let's leave it there.

Despite your protests, for an average joe who just wants to stash a secret somewhere and not have it in plaintext, this is absolutely ok.

This reply is spot on. A vague policy statement means that the FTC itself can't be and won't be held to any standard. They might define Ecommerce one way when it helps with Amazon's prosecution and define it another way to help with Facebook and Google's prosecution. I read the policy statement - it's so broad that it's meaningless. Just lobby the politicians and hope and pray they keep the FTC at bay is not the way to run a developed country.

Booking.com is a large travel aggregator, Nasdaq listed (BKNG) with a 74B market cap - 6x the size of Expedia. They’re just not as big in North America.

And the reason she experienced what she did is because of Project Roomkey and other similar initiatives - https://www.cdss.ca.gov/inforesources/cdss-programs/housing-...

These initiatives saved the hotel industry during COVID when demand fell off a cliff. These hotels still had mortgages but no clients. State intervention saved the industry.

Project Roomkey: https://www.cdss.ca.gov/inforesources/cdss-programs/housing-...

The only task queue I loved was beanstalkd -- it's beautifully written and highly performant. Starting it takes seconds and it's been running for a decade:

https://beanstalkd.github.io/

Who is Richard Li?

I've started a thread internally to double check these numbers. Please wait for an update.

Google serves up way way more than 63k queries per second (several million requests/s is common for the critical services around search). Source: I worked there.

However, your main point is valid (180 million/s seems way too high). I've started a thread internally to double check these numbers. Please wait for an update.

Fantastic writeup and a great exposition of how to do kernel debugging. Thank you!

+1 - have had a super solid amazing experience with Mercury. Highly recommended.

Because debt-to-GDP doesn't make sense as a financial measure and most people don't understand it. CA economy is $3.4T, CA debt-to-GDP is 14.9%, the US Federal Debt to GDP is 133.9%, so the total debt to GDP on the revenue dollars in California is 148.8%.

If California were a country, it would rank 5th highest in the world in debt-to-GDP ratio right behind Japan, Venezuela, Sudan, Greece and Lebanon.

That said, debt-to-tax-revenue is a more useful financial measure. The total CA tax revenue (income, sales, corporate tax) is about $173B [1]. The debt-to-total-tax-revenue is 293%. Since we don't want to shut down Schools, Medicare, SNAP, Pensions & Unemployment, the debt-to-discretionary-expenses is even more dire at 704% limiting the ability of the state to make a dent in the debt payments without increasing taxes.

In effect, CA is neck deep in debt no matter how you look at it.

[1] https://lao.ca.gov/Publications/Report/4448

Very well done.

@galaxyLogic: you're right - we don't really need private static as well except for the single nifty/dubious feature that a private static method can't affect member variables of the class (which is useful for thread safety guarantees).

The only reason the recommendation isn't as strong for private static is that the scope of the "virulent" recursive refactor is limited to the class within which this method was located. If there wasn't a public static method calling this private static one, the refactor ends there.

Personally, I recommend against both public static and private static (I think they produce needless work) however only public static meets the bar for a style guide.

Re: static factory methods - Those are called just once (so perf isn't really the point).

With respect to non-perf reasons, Factories should also be non-static. Here's why: 1. Factories that are part of a dependency injection framework (Guice, Dagger, Spring) are actually "objects" that the DI framework is moving around. These DI frameworks already enforce object creation (see: https://github.com/google/guice/wiki/GettingStarted for example -- everything is an object). 2. public static factory classes have significant disadvantages (eg. depending on another factory class is a direct, "hardcoded" brittle dependency). Avoiding this is straightforward - create factory objects (aka Modules) and register it with the DI framework (the only public static "singleton" object) - when an object is needed, ask for it and the DI framework will give it to you (implicitly through the factory).

private static is fine. Just don't use public static - it leads to virulent refactors and brittle dependencies.

Self confidence and marketing - you seem to be doing fine on execution. Focus on PMF and sales.

+1 Law is human-to-human agreement about a lot of vague soft stuff. Code APIs are computer-computer agreement.

Some exceptions to the above are: 1. Financial contracts (see ISDA derivatives). They're written with a big "human" document upfront and then there's a "notification addendum" attached to each use of that contract. 2. Master Sales Agreements (MSAs): The first MSA is a human-to-human agreement. Everything after that is order-forms. And negotiating the MSA requirements is very very human (risk, trust, effort, cost, benefit & promises). Order forms are pricing decisions that can be "automated" (especially around annual renewals if within budget without red flags).

After building embedded library codebases that have had version skew across clients (sometimes over several years worth of code), the library approach just stops evolving after a certain point - the backward compatibility mess is a drowning morass. There is no control on the upgrade cycle, old infra can't be turned down, performance is a risk, upgrades are a risk, every deploy has "foreign code" and the potential for a dependency mismatch. Services work - use them. Unless performance is of the utmost concern, say no to libraries.