Falell

We should know shortly, the PR to fix this will presumably be paired a crater run, a build of the entire public crates universe.

This was my first question too, I don't see anything addressing e.g. the cyclical arc example from the original 'spawn' conversation.

It seems like you have to auto-propagate !Forget, and then make 'anything that be used to logically implement forget', probably most importantly things like Rc take a Forget bound and do it at an edition boundary? But the link mentions none of that...

Maybe a typo for To Be Quite Honest?

The kind of people GP is referring to refuse to actually learn from this. I've had several coworkers over the last 15 years that absolutely refuse to 'learn to fish'.

I think it shows exactly the opposite of the second. Even with the availability of checklists, and instructions to use them, people won't and don't actually use them consistently.

'With enough eyes, all bugs are shallow' and AI is an automatable eye that looks at things we can tell nobody has seriously looked at before. It's not a panacea, there will be lots of false positives, but there's value there that we clearly aren't getting by 'just telling humans to use the tools available'.

See also: modern practices and sanitizers and tools and test frameworks to avoid writing memory errors in C, and the reality that we keep writing memory errors in C.

Fun. 2.2 loads a blank screen for me, all previous levels were fine and 2.3 loads. Windows, Firefox 149.

Edit: Confirmed fixed.

This doesn't follow at all. The game received _excellent_ reviews prior to release. It's currently the second best reviewed PC game of the year on metacritic [1] (an aggregator with some problems but I don't think this is controversial).

Exactly contrary to your point, both Clair Obscur and Blue Prince (#1) got excellent reviews in the days leading up to release leading to people on e.g. Reddit saying "this game came out of nowhere and it has amazing reviews, I'm excited".

https://www.metacritic.com/browse/game/pc/all/all-time/metas...

There isn't one, there are hundreds. Given that you end up on a small fandom wiki, you have no idea where 'the better community' is. You go to your search engine of choice and start clicking random wikis hoping at least one other one has decent info (most are useless).

As a concrete example, Path of Exile moved to https://www.poewiki.net/ (which is a single MediaWiki instance not associated with a larger network). The content is quite good but it took probably 18 months for it to start reliably appearing in google search results.

> What you need is volatile read/write or load/store intrinsics. When you have those, you can express what's actually possible on a hardware platform, and not inadvertently enable people to write nonsense in your language...

Linus recently said something similar in a memory model discussion on LKML (long thread, only Linus's posts are really relevant here) https://lore.kernel.org/lkml/CAHk-=whmmeU_r_o+sPMcr7tPr-EU+H...

Firefox has all of this except the date. `about:config` lists all config values, values in bold do not match their default or do not exist by default, values can be reverted with one click, and there's a checkbox to filter out unmodified items.

"worse is better", the fact that a great ecosystem has grown does not necessarily mean the language and its tools are great.

Personally, I find the lack of static types makes maintenance a nightmare, and think the build and deployment situation is miserable.

Credit cards have by far the best in-person UX of the options that I am presented, tap my card or phone and leave and they're accepted everywhere in practice (my debit card is not).

The 'cardholder can always reverse any charge' behavior is also nice once every few years.

Not a direct compiler optimization, but consider memcpy() vs memmove() as an example. If you know two regions of memory do not overlap you can call memcpy() for a direct optimized copy, but if they overlap you must call memmove() and introduce an intermediate copy.

From the PR body...

> The cowardly handling of the recent RustConf keynote fiasko...

The article shows that federation delivers data to Meta even if you personally don't use Threads, but I agree with your point.

If you want to control distribution of your data, don't join a federation designed to distribute data. Trying to blacklist nodes in a graph that you don't control is not a solution.

Information wants to be free, if you post something to a social graph assume everyone in the graph can see it forever.

This is discussed at ~12:10.

This is such an obviously good solution to covering API costs that it becomes clear that the actual goal is not to cover API costs, but something else - probably to kill third party apps.

I happily paid for Premium for years, I've gotten a lot of value out of Reddit and I wanted to make sure that they got money even though I blocked all their ads. I cancelled when they announced these API changes since it's the only leverage I have.

A paid ad-free version of their site isn't really good enough though. To keep me happy I need to be able to keep using third party apps on mobile, maybe something like 'exempt requests from Premium accounts from API billing'.

A relevant example from yesterday: https://lore.kernel.org/lkml/CAHk-=wjifBVf3ub0WWBXYg7JAao6V8...

Relocating them will actually break things in many cases, especially when native code is involved.

Non-managers, they aren't responsible for anyone but themselves. I know nothing of Meta's specific titles but I'd expect that e.g. the first level of full time engineering manager would convert to a full time senior or staff engineer.

Bloomberg's comdb2 does something similar, using the SQL grammar and query planner but swapping out the storage layer. To quote from their paper:

"In SQLite a query plan is compiled into a bytecode program that is executed by a virtual machine, named Virtual DataBase En-gine (VDBE)... In the original SQLite implementation the VDBE operates on the real B-trees of the database... In contrast the Comdb2 VDBE operates on the cdb2 abstraction of a table during the OCC phase of transaction execution..."

http://www.vldb.org/pvldb/vol9/p1377-scotti.pdf

This has been discussed in comments of Wayland threads on HN for years. People who want to keep using X complain that they still use it, someone replies "All the X maintainers have moved onto Wayland because they think it's the path forward, if you want X to be maintained step up and do it" and it's not clear if anyone ever did.

Brazil is apparently a suburb of RPG.

Science has a large cluster in North Programming, and a cluster in Eastern Finance. The search is pretty good.

Tokens and very basic walls with flawless click drag seems like all you need to make useful tool eventually, but...

Windows, Firefox 99.0.1. Click drag on tokens is inconsistent and broken, and the edit token popup shows up on mouse-down, I'd expect it on click (down + up on same token) and not show at all if I drag.

My understanding is that the problem with high bandwidth/resolution setups over displayport (which may not be your use case) is in your mac, not in your hub. Older comment thread here https://news.ycombinator.com/item?id=29214726

Nobuo Uematsu's music sounds great when arranged for piano! The Piano Collections are fantastic, if you can play them.

Uematsu was a big part of my childhood and it was a bummer when he stepped back from composing so much, but Masayoshi Soken has done amazing work on FFXIV, he's a worthy successor. I really like this piano arrangement of the Endwalker soundtrack https://www.youtube.com/watch?v=wRmXuN53ggw

You can use the latest goodies in environments that you control. Server side node, client side node, etc.

This is a common thing when working on library-like-things outside the web too. Widely used C++ libraries generally aren't taking hard dependencies on C++20 features right now without continuing to support e.g. C++11/14/17.

My job uses https://oracle.github.io/opengrok/ and I'm generally happy with it. It has some problems with special character searches at times but generally does what I want. It's certainly better than code search in our on-prem github instance.