That's irrelevant to that claim being true or not. The fact that M series win in power efficiency is already addressed.
2,504 karma · joined December 20, 2023
You must sign in to view this post.
This account has requested that users sign in to view their profile.
If there was something controversial in a post that motivates public interest warranting "leaking" then sure, but this is not that.
He did share a public version of this on Mastodon, which I think would have been a much better submission.
https://hachyderm.io/@robpike/115782101216369455
IMO the current dramabait title "Rob Pike Goes Nuclear over GenAI" is not appropriate for either.
BTW I think it's preferred to link directly to the content instead of a screenshot on imgur.
> I’m sure you’re fine if your email is real (in my experience they all resolve to Onvoy LLC instead of a real cell provider),
Email is expected to be resolving to "a real cell provider"? Wut?
I'm on the other side where I've been buying Thinkpads partly because of the display. Thinkpads have for a long time been one of the few laptop options on the market where you could get a decent matte non-glare display. I value that, battery life and performance above moar pixels. Sure I want just one step above FHD so I can remote 1080p VMs and view vids in less than fullscreen at native resolution but 4K on a 14" is absolute overkill.
I think most legit motivations for wanting very high-res screens (e.g. photo and video editing, publishing, graphics design) also come with wanting or needing better quality and colors etc too, which makes very-highly-scaled mid-range monitors a pretty niche market.
> I got too spoiled by retina screens, and I can’t comfortably use anything with lower DPI.
Did you make a serious effort while having an extended break from retina screens? I'd think you would get used to it pretty quickly if you allow yourself to readjust. Many people do multi-DPI setups without issues - a 720p and a 4k side-by-side for example. It just takes acclimatizing.
Nodding along with the rest but isn't this backwards? Are M series actually outperforming an Intel i9 P-core or Ryzen 9X in raw single-threaded performance?
I don't think it's at all as rare as I see other commenters say. I don't know earth sciences specifically but I'd be surprised if there is a STEM field where a strong SWE expertise isn't an asset you can put to regular use in research.
If you look in the DOM tree / source like I proposed, you see that the list is already a table, so you can use that exact approach you already mentioned.
table tr:nth-child(odd) td.rank{
color: red;
}
table tr:nth-child(even) td.rank{
color: green;
}
To figure out where styles come from, open Developer Tools in your browser and Inspect Element. You shoud see the HTML DOM element highlighted and its styles and where they come from on the right.
In this case the alternating font colors aren't from CSS at all.
Police is a protected title but anyone can be a thought police. One can be a spin doctor without any academic acumen. Notice how when qualified, the words take on a broader and sometimes illustrative meaning than when used in isolation. Context matters.
There are caveats here too of course - forking every single thing and excessive NIH syndrome comes with their own costs and risks.
I believe I did:
> This can all be verified at any point in the lifecycle without running any of the code, provided a network connection and/or the module cache.
It does not require a JS runtime[0] - you fetch a tarball and check its integrity. You can extract it and validate the integrity of a module cache or (non-minified) distribution.
> Another matter is that most software I know of doesn't even use lock files.
I don't believe the goal should be to lower the bar until "most software I know" pass. And you don't need all the libraries you depend on to ship lockfiles/SBOMs themselves as long as you take ownership of it wrap it up in your own builds and installations, right? Besides, lockfiles are definitely the norm in js/npm land these days from what I see...
[0]: If you have a dependency with a lifecycle script which at runtime say downloads, builds and installs new components into the module tree then all bets are off. If you are doing SBOMs for anything more than theatrical checkbox compliance, such (usage of) dependencies should already have been yeeted before you got here and if not, well, I guess you have work to do. If you get to this point I'd say the process is serving its purpose in forcing you to face these.
After all, hindsight is 20/20 and at the end of the day a major part of our work is making (appropriate) abstractions. Picking good terminology is sometimes hard. I guess to point out that the message shouldn't be read as "all abstractions bad (stop trying)" but to be more conscious about them and to restrain from piling new "magic" on top of a tower of old apocrypha.
Then it would be great of the population follows.
But it is certainly not the role of government to decide what foreign communications services their citizens can access.
Autoritarian censorship is not a democratic tool even if other apparently democratic countries are doing it.
The promise is to simplify and unify things but as noted, such efforts often have the opposite effects.
"Teams are struggling with properly adopting FooTech - our FooBarTool wraps it in a beautiful package and magically solves everything with a single command and one config file"
"We should template all this yaml"
Systemic issues make poor clickbait.
Basically you can get much better read performance if you can read everything sequentially and you want to avoid random access at all costs. So you can basically "hydrate" the loading patterns for each state, storing the bytes in order as they're loaded from the game. The only point it makes things slower is once, on download/install.
Of course the whole excercise is pointless if the game is installed to an HDD only because of its bigger size and would otherwise be on an nvme ssd... And with still affordable 2TB nvme drives it doesn't make as much sense anymore.
Food for thought: Rather than nitpick on people who apparently use the word in earnest in its actual meaning and thereby conceding that those policies are actually "taking your privacy seriously", rendering the word void of meaning, we educate and take it back?
Saying "Make sure that it's impossible for my online actions to be traced to my identity, and then I don't need privacy" is in a way giving up on privacy alltogether.
They contain for each dependency name, version, (derivable) URL and integrity checksum, plus of course the intra-dependency relationships.
This can all be verified at any point in the lifecycle without running any of the code, provided a network connection and/or the module cache. What's missing?
> With authenticode, the "catalog" can be signed
You could trivially sign any lockfile, though I've never seen it. I think it could be neat and it might have a chance to catch on if there was more support in tooling for it. The NPM registry does support ECDSA package sigs but I guess signatures for this use should be distributed on other channels given how much of an antipattern uploading lockfiles to registry is considered in the npm community and that's an uphill. In the context of SBOMs I guess there's already a slot for it?