tankenmate

And `/dev/shm/` (which postgres uses by default on most Unix platforms)

Sure, but what if that "known good customer" proxied access to someone else?

"means your benchmark is inaccurate by my book.", and like The Dude says "Yeah? Well, you know, that's just like uh, your opinion, man."

Create your own benchmark, and you can say it is a subset of "U.S. large-cap equities" and "best single gauge of U.S. large-cap equities" and let the market decide who does a better job.

Sure, but then it comes down to your opinion vs the S&P board's opinion. I suspect (given that there's only been a few days of this getting into the public eye) that more people support the S&P's position vs their critics. But the trade flows will show if people get out of SPX (or SPY/VOO) in the coming days.

"The inclusion criteria prioritizes companies that extract their cashflow into profit", in almost all cases, yes. But if you want to buy into these newer stocks there are various high growth indices you can buy, no one is stopping you. If you want to buy into only one or two of those stocks then you can. It's a free market for stocks and it's a free market for indices. There's no regulation that says the S&P has to include certain stocks.

"The S&P rules exist so the index can accurately reflect the market", the rules exist to reflect a subset of the market, and the committee chooses that subset. It's their subset so they get to set the rules, you don't have to use it if you don't want to. If you don't like that subset then create your own index. Then you just need to convince others to use it.

"Because the index needs accuracy.", and I would argue that include price accuracy not just inclusion accuracy. The S&P is a benchmark that is designed to reflect a subset of the market, and giving only some companies early access to the benchmark changes the benchmark. So if you want a benchmark that's designed to include all the big stocks regardless of age, profitability, etc then go make a new benchmark. The only thing you need to do is convince others to use your benchmark.

Brings back memories of desk checking

From my perspective it is a synthesis of "It is difficult to get a man to understand something, when his salary depends upon his not understanding it." and "but npm is the source of all the shiny shiny!".

TENEX and TOPS-20 would be nice

"Vibe coding a slop website drastically increases your bounce rate and reduces trust in your project."; but only for a subset of the potential audience.

This is something I learnt early in my start up career, "You are not your customer"; what you value and what your customers value may not be the same.

They will just fine them into oblivion; they are known to fine companies AUD10M to AUD50M for this sort of thing, and from 1st April this year they can now fine up to AUD100M.

Will this mean that Bambu will withdraw from the Australian market? Possibly maybe probably, but the ACCC takes a very hard stance against bait and switch.

The rumour mill says that parts of Canonical's infrastructure are being DDoSed. That being said Canonical did maintenance on their PPA infrastructure 2 days ago according to their Mastodon page[0]. If it is an attack maybe this is an attempt to stop people being able to cleanly upgrade to avoid the Copy Fail / algif_aead issue?

[0] https://ubuntu.social/@launchpadstatus

This sounds more like a belief, based on little more than "correlation is causation", than analysis that controls for macro-trends backed by evidence.

As long as this tool doesn't break "fast forward merge" and proper linear history and allows you do delete PRs unlike its GitHub progenitor then I'm happy.

I have found that a number of times GitHub's idea of "convenient" comes either from 1) not understanding git fundamentals such that it closes off possible workflows, or 2) pushing a philosophy on users, i.e. I know better than you, so I'm going to block you.

I'm so surprised that so few people have heard of Portmaster, it's been around for years and runs on Linux (and Windows if you must). And if you don't need traffic history it's free.

I use Portmaster (on Linux) and I have never seen ads (either in the app or apps that get their DNS from Portmaster) on it. About the only thing I saw different between the free version and the base level paid for version was traffic history and weekly reports (and badges on Discord if that's your kind of thing).

it's great, i really like it! i've been working on something similar for CPUs but not getting into the EE weeds (like i don't get into DRAM at all, no voltages, no slew rates, etc, etc).

it was all reasonably easy to get until you get to the sense amplifier which has an almost complete lack of explanation of why you need the required outputs, it is "clear if already known". i.e. if you've never done any electrical engineering it makes zero sense and is not the sort of thing a software developer could ever figure out with the minimal explanation.

actually i just checked, yeah, ubuntu would have to add none back to the kernel and `CONFIG_PREEMPT_NONE=y` the config so that it can be selected at boot.

Not necessarily;

``` $ grep PREEMPT_DYNAMIC /boot/config-$(uname -r) CONFIG_PREEMPT_DYNAMIC=y CONFIG_HAVE_PREEMPT_DYNAMIC=y CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y ```

if your kernel has CONFIG_PREEMPT_DYNAMIC then you can go back to the pre 7.0 default by adding preempt=none to your grub config. I haven't seen any plans by Ubuntu to drop CONFIG_PREEMPT_DYNAMIC from the default kernel config.

LLMs can't be held legally liable, only the people who use them.

Firefox uses randomised IDs for installed extensions, so the method highlighted won't work on Firefox. That's not to say they aren't trying other methods on Firefox.

Given their AI "hiring / onboarding" process all I can say is; couldn't have happened to a nicer company.

It already exists; cloudsmith

Jira is Australian.

It's almost like Churchill's quip "He has all the virtues I dislike and none of the vices I admire". In other words, in some ways the JS ecosystem rushes to all the tech debt inducing "shiny shiny" and avoids all the tech debt reducing "hard work of refactoring and wisdom". It's almost like a large chunks of the JS ecosystem thrives on "the dopamine hit". Santayana's wisdom whispers behind every import.

Again looking back at the history of Unix, it used a 56 bit variant of DES encryption that used the user's password as the key. So only the first 8 characters of the password were used and the rest was silently unused, for example "password" and "password123" would have been the same password on early Unix. And although most BSDs and Linuxes moved in the mid 90s to PAM (and hence md5, etc) most SVR4s didn't move until late in the 90s. And at the other end, DES crypt() made its way into Unix in some v6s (~1977) and became widely available in the release of v7 Unix. So 8 character passwords were a thing for about 20 years.

This decision long predates Linux. It's been a staple back to the earliest days of Unix; and it isn't a weird decision if you take into consideration of multi user systems in office environments that have non trivial security considerations (for example telecoms companies), which is exactly where Unix came from.

Indeed a whole class of issues become moot if you just don't use javascript anywhere. In the browser world this is obviously difficult/impossible; I look forward to the day when WASM can run natively in a browser and doesn't need javascript at all, DOM, network, etc, etc. On the server side? Just steer clear of the javascript ecosystem altogether.

And not just token usage, expensive token usage; when it comes to tokens/joule not all tokens are equal. Efficient use of MoE architectures does have an impact on tokens/joule and tokens/sec.