If I want to upgrade the disk on my MacBook Pro, I need to buy a new MacBook Pro with a larger disk. If I want to upgrade the disk on my work laptop, I’m SOL.
> Ensuring that diffs to updated dependencies remain within a vendor folder is trivial.
It’s not obvious to me how putting the dependencies in a vendor folder solves the diff problem. Does every code host allow you to hide diffs to certain directories?
And what’s the advantageous scenario for vendored dependencies? Is it just when the mod proxy and the upstream code host go down at the same time?
Would Fintech include orgs like Yotta Bank, Robinhood, Revolut that tried to do finance things with a tech attitude, whereas banking/finance is your more traditional HSBC, Deutsche Bank, etc?
How is this not money laundering? For what is basically a single purpose vibe coded OS, there is a lot of money going to it when money is not (and never wanted to) going into ruby, gems or rails. very very odd situation.
I gave up even touching that site many years ago. It might not have bot posters, but it probably has bot voters. Even without that, it's usually the saddest or angriest subset of people, with bad incentives.
At work I can't customise much, like the browser I use, but I did ditch Google/Chrome for Bing/Edge years ago. Not what I would usually recommend, but when work only allows those two options...
This isn’t really a paradox if you just visualize the Moon as a sphere and visualize where the Sun is shining from, and I think that’s what the plots in OP demonstrate.
The “paradox” might be in the initial assertion which does not use an accurate mental model: “After sunset, the sun is below, so we would expect the illuminated portion of the moon to point down, towards where the sun is.” This assertion might be true if at sunset the Sun ducks just behind the horizon, around the same distance or closer than the Moon is to the Earth. In reality, the Sun is of course much farther from Earth than the Moon. Factoring the relative distances into the mental model will lead you to the correct conclusion.
At least the fallout will be less if you have to resolve your custom domain differently in the intranet due to something like this.
If github is "taken down" you can't just resolve the whole domain differently, you need to only resolve the packages differently. If your "Golang domain" is taken down, it should be a lot easier to hotfix until something proper is implemented (the quickest and dirtiest would be a hostfile-entry).
Just like abortions in the 70's stopped the super criminals from existing in the 90's. Not having unwanted kids goes a long way to prevent crime. Now we are in the place where people want kids, but can't afford them so they aren't.
>Cost-wise it’s maybe $500 a year, all in (unless you have the pleasure of living in California, in which case you have to add their inane $800 on top). But that’s pretty reasonable considering the optionality it gives you to just… build shit these days.
You don't need an LLC to build things and sell things. And you also get the downsides of needing to stay at an office to be able to be served or having to have your active home address be publicly viewable.
That was addressed circa C++17 IIRC, same with all of the technically UB surrounding DMA memory. You needed non-obvious incantations for some use cases but they were expressible. C++23 eliminated most of those incantations. Before all of this you had to use “blessed” incantations that were technically UB but which compilers needed to allow because the code was expressing a valid use case.
I find it crazy that popular systems languages didn’t have an explicitly valid way to deal with all of these ambiguous ownership and lifetime issues around memory until relatively recently.
At least thrice now in the past week, Gemini has tried to sit me down and tell me to go to bed (when I'm in the middle of programming... too late for it's liking, apparently) or just recently while I was asking some questions while I was driving... it told me to change the subject because I was driving and the topic was possibly too anxiety inducing for me or something!? I have no idea. I told it to fuck off.
Has this ever been necessary/useful? Genuinely curious because I’ve been using Go since 2012 and can’t recall a time when vendoring solved a problem better than “regular” modules. Like have there been times when the source went down and the module proxy went down (or didn’t have your dependency cached)?
Should be doable w/ existing AIs to generate a staged sequence of operations by taking a demonstration & deriving another sequence of operations for achieving the same outcome w/ another set of actuators. I'm not a roboticist but robotic arms have specifications & those specifications are basically generalized algebraic datatypes so Astra or even Grok should be able to generate programs for manipulating most objects.
If I want to upgrade the disk on my MacBook Pro, I need to buy a new MacBook Pro with a larger disk. If I want to upgrade the disk on my work laptop, I’m SOL.
> Ensuring that diffs to updated dependencies remain within a vendor folder is trivial.
It’s not obvious to me how putting the dependencies in a vendor folder solves the diff problem. Does every code host allow you to hide diffs to certain directories?
And what’s the advantageous scenario for vendored dependencies? Is it just when the mod proxy and the upstream code host go down at the same time?