numbsafari

Yeah, especially if you deploy it on Azure...

... no mention of golang and minimal version selection?

https://go.dev/ref/mod#minimal-version-selection https://research.swtch.com/vgo-mvs

Instead of a "lock" file, go includes a "sum" file, which basically tells you the checksums of the versions of the modules that were used during a build happened to be, so that you can download them from a central place later and ensure you are working from the same thing (so that any surreptitious changes are identified).

> seems like a really confusing question

Agreed. ‘sendOnce’ implies something very specific in most async settings and, in this interview question, is being used to mean something rather different.

How does it compare to a wet rag with tongs?

I work with batch oriented store and forward systems and they definitely push data in batches.

As in urns for ashes, not Universal Resource Names.

I am imagining putting this in my toddlers bedroom and how much delight he would derive from and how much chaos would ensue.

Ah, my precious…

Hiring a bunch of recent college grads to build your startup is fun. They're great drinking buddies and they make you feel young again. They'll inefficiently work around the clock, sleep at the office, and treat it like their mom's house, and make you think you're a big, important boss.

Coming in as a gray hair to fix their disaster definitely pays the bills.

With the referral to the US attorney’s office, he actually might.

Consider how painful that is going to be for Apple, and Roman, with how the current administration is abusing the DOJ.

The repercussions of this could be huge.

... and that industry led consortium will have a board all paid princely sums, and an executive leadership team that is conflicted to the hilt and paid kingly sums, and they will charge exorbitant rents in order to keep the lighthouse lit.

There's flaws with every approach, but I much prefer the approach where this sort of thing is treated as a public good, rather than as yet another soon-to-be walled garden.

I have completely soured on Dockerfiles. I view them as anathema.

The supposed "caching" of layers really doesn't work in practice unless you add a bunch of other infrastructure and third-party tooling to your build process. Getting truly incremental and reproducible layers into your build process is non-trivial, and the Dockerfile approach fails to take advantage of that work once you've done it.

This is what I've done for years: doing app development using the .test TLD, and .internal for, well, internal services that are more like "production IT".

I've had nothing but trouble with .local and .localhost. Specifically, .local is intended for other purposes (multicast DNS) and .localhost has a nasty habit of turning into just "localhost" and in some cases, resolvers don't like to allow that to point to anything other than 127.0.0.1.

More recently, I've stuck to following the advice of RFC 6762 and use an actual registered TLD for internal use, and then sub-domain from there. I don't use my "production" TLD, but some other, unrelated TLD. For example, if my company is named FOO and our corporate homepage is at foo.com, I'll have a separate TLD like bar.com that I'll use for app development (and sub-domain as dev.bar.com, qa.bar.com, and maybe otherqa.bar.com as needed for different environments). That helps avoid any weirdness around .localhost, works well in larger dev/qa environments that aren't running on 127.0.0.1, and allows me to do things like have an internal CA for TLS instead of using self-signed certs with all of their UX warts.

For "local network" stuff, I stick to ".internal" because that's now what IANA recommends. But I would distinguish between how I use ".internal" to mean "things on my local network" from "this is where my team deploys our QA environment", because we likely aren't on the same network as where that QA environment is located and my ".internal" might overlap with your ".internal", but the QA environment is shared.

Mentions Buck, but no mention of Pants or Please.

I think "certified unix" is meaningless to most people who use "a unix".

I stopped treating Mac OS as a Unix and I started sleeping at night. It’s a great platform for running a Unix in a VM.

Besides Tesla?

Many years ago a roommate and I had an HPUX machine running IE on HPUX just so we could forward X session to our FreeBSD and Linux desktops and not have to use our Windows machine for anything other than PC games.

From the ass of Secret Dreams, comes Imaginary Friends.

I grew up with six siblings on a cul-de-sac filled with other families with 3+ children (enough kids for two complete baseball teams) and had imaginary friends.

You answered your own question.

No evidence, but the fact that the "IngressNightmare" PR piece was announced before there were even PRs created to fix this smells like the team at Wiz leaked this before it was really ready.

Whether the scores are legit or not, the fact that this was such a botched disclosure process is not a good look for the Kubernetes project, of which this is a part.

Edit: According to [1], the team at Wiz show a responsible disclosure timeline. Seems like the Kubernetes project's process didn't work so well. If Wiz is accurately reporting what happened in their blog, these fixes (or the plan for them) was available a month ago, despite seemingly not having working PRs until today, after the security announcement?

Again, I really appreciate the work of the team to ship this, but this isn't a good look for the Kubernetes project itself.

[1] https://www.wiz.io/blog/ingress-nginx-kubernetes-vulnerabili...

> Putting too much trust on Eddy Cue

I've never understood the love for Eddy Cue. Apple pundits all seem to love him. Personally, I am really unimpressed by everything he's done. My understanding is he's been really good at negotiating big contracts.

I just don't think his execution or vision are exciting and, as you are hinting at, I don't think his moral compass points in the right direction. That said, despite some early pushback, my understanding is that Schiller was ultimately on-board with holding to the 30% cut.

This is not true, as evidenced by the slave taking exhibited by nomadic peoples in North America. It was a pretty routine practice, well documented in history. Losers in battles would often be assimilated by the winner as slaves.

This has nothing to do with supply/demand, and everything to do with geopolitics.

I can assure you that "Jack The Horse Lake" in Northern MN absolutely reflects whatever you think that name implies.

https://www.google.com/maps/place/Jack+the+Horse+Lake/@47.61...

> This by default almost assumes a hostility towards the former group because their interests will of course be at odds with the interests of the latter group.

I would generally agree that that's the "default".

However, there are cases where two sides of a market need an intermediary with which they can both independently transact, and a net benefit of that interaction is felt on both sides. The key is to construct the solution such that the intermediary depends on the goodwill of both sides of the market.

I think Kagi is somewhat flipping the script. By "taking" data from publishers for free, they are then selling it to readers at a cost. However, there is a trade off. Kagi needs to make sure publishers continue to make their content available so that it can be searchable, or used in their Assistant product. In order to do that, they need to do the opposite of what Google is doing by trying to sequester traffic on Google.com: Kagi's best interest is to make sure that they provide good value to both sides.

Indeed, using the Assistant product, the way it is structured, I very often find myself clicking through to the referenced original sources and not just consuming the summarized content.

How this evolves over time, from a product design standpoint, will be interesting to watch.

> making it so hardware providers must maintain their drivers is a good start

How do you propose that happens?

NOBUS is a disaster. Knowingly leaving citizens unprotected is an absolute failure of government. Having a robust policy of identifying a resolving cybersecurity faults, and holding organizations accountable for patching and remediation is necessary if we are going to survive a real cyber “war”. We are absolutely unprepared.

These are the same people that insist we arm elementary school teachers and expect those teachers to someday pull the trigger on a child instead of having proper gun laws.

There is no irony.