jpdb

I've been seeing this company in ~all of my searches across various tech topics.

They're absolutely dominating search results. The quality isn't terrible, but there's so much content that I can't trust them to be accurate.

Given that you literally started your response with a pleasant agreement and affirmation on my point makes feel like you are arguing this in bad faith, but if statements like, "how was your weekend" included in an ask cause you distress then you are so maladapt to society to the point that you should have close to zero expectations for others to accommodate your needs in public spaces such as a work environment. You almost exclusively have the responsibility to regulate your emotions or not expose yourself to situations where people might include a hollow inquiry into your weekend in their written communications.

Asking people not to include minor pleasantries in their written communication isn't a "reasonable" request for anything larger than a small group of people.

> If x finds preamble unpleasant, but you use unnecessary preamble when communicating with x, that won't help you be perceived as pleasant to work with.

Absolutely! But OP isn't suggesting preamble is unpleasant, they are saying there is little or even no value and to remove it altogether.

Even if OP did in fact mean to suggest this when speaking to them directly, it is unbelievably selfish to ask (let alone _beg_) someone to eschew their voice just so you don't have to read a few more words and "waste calories" to gather the information they believe is important.

The pleasantries and preambles and hollow words _are_ important. People might be adding them without having deep thoughts on them to the point where they explicitly include them, but they want to signal to you that they consider your humanity. That signal isn't noise, it's a very minute sign of camaraderie. If OP doesn't value that signal, that's fine, but pretending it's noise is antisocial.

Asking (begging?) people to communicate with you in a certain way because you think it is depriving you of your attention(time?) is _much_ more selfish because you are depriving people of the opportunity to control how they are perceived.

How and what people think of me is extremely important to me. I want to be perceived as someone who is effective _and_ pleasant to work with. Changing my voice to suit your inability to summarize and interpret the ideas being communicated is selfish and antisocial behavior.

You are not a being of pure logic. The way I say something to you _will_ effect your perception of me AND the topic at hand.

> Politeness has a place, but I beg you put clarity first.

Having conversations with little-to-no noise as possible has a place, but I beg you to consider that the person conversing with you has a baseline level of empathy and ego and is not a p-zombie.

Wanting to be seen a certain way is just as (if not more) important than the extremely minor distress you feel by having to read some extra words.

Love this! Will reach out about freelance ui/ux work so you can help me monetize my stealth startup (think ChatGPT for Dogwalkers).

> If LLMs really multiply productivity, why would you fire people and handicap the boost?

Presumably, because some of these areas are cost centers versus profit generating.

That particular benefit has no value if you still need to support v4.

It's almost a self-inflicted tragedy of the commons or reverse network-effect.

Adopting IPv6 doesn't alleviate the pain of IPv4 exhaustion if you still need to support dual-stack.

> A sharp knife is SAFER than a dull one.

I do a lot of cooking and own quite a few kitchen knives, most of which have bitten me at some point. I understand the idea around sharp knives being safer...but I don't agree.

If a razor sharp 210mm Japanese carbon steel knife touches your finger, it's split open and might need stitches or glue. A less-sharp knife would need more weight behind it to cut effectively which can lead to you completely severing a finger, but simple slices are a much more likely scenario than your finger being completely under the knife to the point where it's effectively a digit-guillotine.

You can also use passkeys so you aren't tied to a centralized SSO provider.

But if you make something that's as smart as a sloppy intern and costs even a small amount less, you're making an unbelievable amount of money off it.

You could just disable cdn/caching.

Tailscale funnels do work, but it's public only. No auth.

I generally prefer tailscale and trust them more than cloudflare to not rug-pull me on pricing, but the two features that push me towards cloudflared is the custom domains and client-less access. I could probably set it up with caddy and some plugins, but then I still need to expose the service and port forward.

I have the same z13 gen one, but my m1 is a Pro.

I do absolutely love the z13 and prefer it most of the time...but I definitely would not call the battery life "all day" or even "almost all day"

Web performance is probably/mostly valued as efficiently as it needs to be.

The numbers mentioned in the article are...quite egregious.

> Oh, Just 2.4 Megabytes. Out of a chonky 4 MB payload. Assuming they could rebuild the site to hit Alex Russell's target of 450 KB, that's conservatively $435,000,000 per year. Not too bad. And this is likely a profound underestimation of the real gain

This is not a "profound underestimation." Not by several orders of magnitude. Kroger is not going save anywhere even remotely close to $435 million dollars by reducing their js bundle size.

Kroger had $3.6-$3.8 billion in allocated capex in the year of 2024. There is no shot javascript bundle size is ~9% of their *total* allocated capex.

I work with a number of companies of similar size and their entire cloud spend isn't $435,000,000 -- and bandwidth (or even networking all up) isn't in their time 10 line items.

A leak showed that Walmart spent $580m a year on Azure: https://www.datacenterdynamics.com/en/news/walmart-spent-580...

These numbers are so insanely inflated, I think the author needs to rethink their entire premise.

You should be able to get this done with OBS.

Set OBS up so your streaming a window of this application.

Go into OBS settings and go to "Stream" and set it to custom.

For server use "srt://127.0.0.1:7777?mode=listener&timeout=50000&transtype=live"

Then in VLC, open a network stream for srt://127.0.0.1:7777.

This article seems to focus on the shortcomings of LLMs being wrong, but fails to consider the value LLMs provide and just how large of an opportunity that value presents.

If you look at any company on earth, especially large ones, they all share the same line item as their biggest expense: labor. Any technology that can reduce that cost represents an overwhelmingly huge opportunity.

America was under a fascist ruler, but not under a fascist system of government.

Trump tested American democracy by consolidating power and was not successful, so we avoided being under a fascist rule

The fear is that we might get to test democracy again, and most of America doesn't seem to mind that. Maybe it's due to lack of understanding, not caring, or genuinely wanting fascism, I don't know.

Would love to see this!

Are you able to handle branching as well?

Neon seems really great to me, but I wish I could easily run it locally via Kubernetes. I know there are some projects out there[0] but they are all supported by 3rd parties and things like branching and other features don't appear to be supported.

I'd love to be able to just use a helm chart to have Neon in my homelab.

[0] https://github.com/itsbalamurali/neon-operator

And if you're pairing your infra-as-code with a gitops model then you can help prevent these kinds of issues with PRs.

You can also use your git history to restore the infrastructure itself. You may lose some data, but it's also possible to have destroyed resources retain their data or backup before destroy.

> Probably even better is to ship a controller and a CRD for the config.

But how do you package the controller + CRD? The two leading choices are `kubectl apply -f` on a url or Helm and as soon as you need any customization to the controller itself you end up needing a tool like helm.

> You don’t need to use NAT. Which means you have to set up a firewall on the router correctly. Default-deny, while still allowing ALL ICMP traffic through, as ICMP is kinda vital for IPv6 because it’s used to communicate error conditions.

I do think using NAT in the form of NPTv6 is awesome for home use because it allows you to have a consistent address regardless of your ISP prefix assignment.

Think of NPTv6 as a kind of "stateless NAT" where the prefix is mapped 1:1 to your internal prefix. This means if your ISP changes your address, you only need to your external DNS versus all of your devices.

I really wish oxide had a Homelab/consumer centric offering!

Spec wise, some low power systems like an Intel NUC, LattePanda Sigma, or Zimaboard. You could fit 3/4 of them in a single 1u with a shared power supply. They could even offer a full 1u with desktop grade chips on the same sleds.

I have thought about building one myself, but it's a large investment of time that I can't seem to find lately.

I agree with you, but I think the idea is that the underlying storage engine affords you functionality that you can't mimic yourself / elsewhere and therefore your capabilities to leave are limited.

You're always "locked in" to some degree and it's an almost worthless thing to invest into if you never actually need to actually migrate off.

I really wish there was a device like this that could be used as a type of "blade server" that could be inserted into a standard 1u/2u short-depth rack mounted chassis. That would let me re-use my existing 8u wallmounted rack instead of a shelf with zip-ties.

Docker in Mac runs via a VM, so you wouldn't be running it a process under your Mac, necessarily.

Bazel now has a module system that you can use.

https://bazel.build/external/module

This means your packages are just Git repos + BUILD files.

A simple explanation is that you borrow a certain number of stocks, sell it, and re-buy at some point in the future (at a lower price hopefully) to return the number of stocks you borrowed.

Imagine you think widgets that are worth $1 today are going to be worth $0.50 tomorrow. You say to me, "Hey jpdb, can I borrow 100 widgets and give them back to you tomorrow?" I say sure and you turn around and sell those widgets. Tomorrow, we meet up and you take your $100 and buy 100 widgets for the new price of $0.50 each. You return the 100 widgets you borrowed and you now have $50 in your pocket. In this example you have "shorted" widgets.

> One of my colleagues keeps repeating “reliability is our number one feature”.

I think reliability is the #1 feature at any stage because if you're unavailable, you're at best useless and more than likely you are actively harmful because your users have an expectation.

However, if you're unavailable outside of times customers don't expect you to be there then you're not actually unavailable. This is more likely for an early stage start-up, but you don't typically choose or know when you're expected to be available nor do you always get to choose when you're unavailable.