skysight-inc/HackerNews huggingface dataset:
> Unreal Engine didn't deprecate ray tracing,

They literally did. They found that Lumen looked better and used less performance then hardware ray tracing. At least thats what they said in a developer interview a few month ago.

> Have you?

No, I haven't. My day job isn't even in the game industry.
I've only dabbled a little after I bought my first VR headset.

The either was because you were dissing the article author by saying they weren't a game dev, with the argument that UE is only used because it looks shiny to management, with is pure nonsense.
I don’t think this group codes, they make music videos and fundraise.
I don't think anyone can really say if the grounds for banning those books are legitimate until they've actually read them. In any case, I have had women complain to me that software conferences I've recommended they attend (because they are focused on bringing more women into programming) were too activist in nature and turned them off programming.
> it's very difficult for me to believe that "Girls Who Code" is JUST a book that aims to introduce women to software development.

But why is that even your business? Books shouldn't be banned just because they convey a narrative you don't like. I can accept that there atr reasons to ban books in some context (like there's no place for porn stuff in a school library) but it must be some decently valid reason, not “I don't like the content of this book because it goes against my beliefs ” because this is the definition of censorship (and that's how maus got banned too)
for the same reason in one job i was able to change my employment contract to include a guarantee that all code i write on that job will be released under the GPL

i thought that way i would always be able to use the code in my own FOSS projects but i would also not be able to sell out and make my work proprietary (since it would contain GPL code owned by my employer)

this may seem less beneficial than an apache license but it was aligned with the company goals as far as my work was concerned, so i essentially had them put a verbal promise into writing, and i thought it was a neat way to commit myself to FOSS
Looks like it is not the case: https://twitter.com/centralyorksd/status/1574388246569795590

It’s a shame the article doesn’t mention that.
Game Cube worked in 2x2 blocks of pixels and could also run primitive "shaders" by cycling a pixel block through the pipeline multiple times with different settings. Made for some nice bump mapping demos but I'm not sure how much it was used in practice.
I'm a huge supporter and admirer of Snowden and wish him all the best, but there's no way that he would be protected under existing whistleblower laws. Government whistleblowers dealing with classified information are expected to use very specific, narrow channels such as making reports to agency inspectors-general. When their whistleblowing involves public disclosure of classified information, it's not at all protected by whistleblower laws, even if large parts of society end up agreeing with them.

Edit: This is even true if the government ends up agreeing with them about object-level issues (e.g. if the courts agree that something they revealed was illegal or the executive or legislature agrees to change policy).
It's perfectly normal to see baby puffins thrown off cliffs in Iceland each year
> But most of all, I'm angry that whenever this discussion happens, people try to gaslight me into believing this is just bigotry, or ideological boogeyman that don't exist, or partisan politics.

> Being told this is all a figment of my imagination, I cannot.

Perhaps then you can empathize with a queer teen who is angry that people try to gaslight them into believing their feelings are just... whatever it is you think they are?

It sounds like your frustration with being told your reasons for opinions are a figment of your imagination are very similar to those being told by people like you that their gender identity is a figment of theirs.
Horrible activist outrage click bait writing.

From https://www.cysd.k12.pa.us/:

> The District was recently made aware of a national article published last evening falsely claiming that Central York School District has banned the book/series Girls Who Code.
The information published in this article is categorically false. This book series has not been banned, and they remain available in our libraries. If you have any questions, please email communications@cysd.k12.pa.us.
The index, which is linked in the article, reveals that the banned books are not How to Code books but a series of chapter novels that feature girls who are interested in coding but know nothing about it. Furthermore, they are only banned as classroom curriculum books, not banned from the library, which makes sense because the first book appears to contain no classroom merit whatsoever -- just like most chapter books aimed at kids.

I skimmed through the first book. It's cute. A bunch of girls who are excited to learn to make apps join the coding club and get tricked by their female teacher into solving a bunch of coding trivia outside the classroom in order to develop friendships. They finally learn some actual coding from the protagonist's older brother. There really is no merit to this as a classroom assigned reading book, and it would probably be a drag for boys to read. The writing style and thoughts and feelings of the main character are obviously directed heavily at girls, except for the older brother who's a cool prankster and who actually knows how to make basic utilities.

The Girls Who Code textbook by the same author, Learn to Code and Change the World, is not banned.
I think you've touched on two different ideas:

(1) That a deeper understanding of something can make it simpler/easier to remember. One way to look at this is that you remember a model of the world. That complexity of that model determines the quantity of information you need to remember. If you can find a simpler model, your mind needs to store less information to cover everything you need to know.

(2) That a concept and its name are different things. You understand the concept of an array-length-giving function, but you don't remember the name attached to it. It could go the other way: you could know there is a function with a certain name but not remember what it does. Or you could know what it does and what it's named. (This seems at least tangentially related to linguistic relativity (https://en.wikipedia.org/wiki/Linguistic_relativity), a.k.a. the Sapir-Whorf hypothesis. The question is basically to what degree our minds build ideas on words/language and to what degree we form ideas independently of language.)
I hadn't heard the term chiplet before, thank you! When I got out of school in the late 90s, system-on-chip (SoC) was a pipe dream. It has issues because memory might have different requirements than CPU, so it's hard to put all of the components on a single die.

I always thought the situation was frankly pretty silly, because I didn't want one big die anyway. I wanted a scaleable grid of chips like the 3D processor from the Terminator 2 movie.

It took over 20 years, but maybe we'll have a chance to get something like that with an open source RISC-V. Maybe an array of matchhead-size CPUs at 1 GHz costing $1 each that could be scaled to hundreds or thousands of cores with content-addressable memory for automatic caching and data locality. Then it could be treated as a single processor with access to a one large shared memory space and we could drop the (contrived) distinction between CPU/GPU/TPU/etc and get back to simple desktop computing rather than dealing with the friction of vertex buffers.

My guess is that Nvidia doesn't want any of that to happen, so works to maintain its dominance in single-die solutions.
Re: scale – we do handle billions of rows! As you can imagine, exact throughput depends on the source and destination database (as well as the width of the rows) but to give you a rough sense – on most warehouses, we can sync on the order of 5M rows per minute for each customer that you want to send data to. In practice, for a source with billions of rows, the initial backfill might take a few hours, and each incremental sync thereafter will be much faster. We can hook you up with a sandbox account if you want to run your own speed test!

Re: configuration – you would create a config file for each "source" table that you want to make available to customers, including which columns should be sent over. Then at the destination level, you can specify the subset of tables you'd like to sync. This could be a single common schema for all customers, or different schemas based on the products the customer uses.
> That's... an interesting interpretation of what I said

In a non-verbal exchange this choice of an explicit pause followed by the use of the phrase "interesting interpretation" could also be misconstrued as an underhanded compliment/sarcasm further undermining your alleged intention.
That's getting needless sticky about definitions, and harming understanding of the point, potentially leading people to think that these Amazon workers are going to get their raises, which they clearly won't.

Let me be more concrete: am employer presenting you with a plan for future compensation[1] in an existing employment relationship does not constitute a contract. They can pay you what they want to pay you.

[1] Your back wages argument doesn't apply here. These people never got paid at all.
Any rumors that any of the Zen4 chips will get a 3D cache version?
I've been pointing this out for a long time, and 100% agree with you.

Open source was originally about the freedom to use software in new and creative ways, and NOT about giving away free stuff.
Historically they said it was good to charge your lithium laptop battery's to 90% and discharge to 10%
Have you read these specific books?
> neither do you

The put options that I closed out based on my correct prediction that the market would drop literally the day after I posted this would disagree.

Additionally since the Fed meeting and the subsequent market drop that general consensus has shifted pretty rapidly towards agreeing more with me than not.

I still think the market is even more optimistic than it realizes.

It's not doomerism, its reality: we're still in an insane asset bubble that has been propped up by a decade of insanely low interest rates and cheap money. Various conditions around the world are causing rapid inflation which is forcing central banks to raise interest rates ending the era of cheap money. The market sentiment remains convinced that this will a temporary hike, not going much about 4-5% and decreasing rapidly, however there is plenty of economic analysis that indicates this does not make sense.
No, not anywhere remotely similar except that some of the terminology like display lists (that predated PS2) are still used.
> ...it's a gut feeling...dependencies: why on Earth would I want to build a product with some many dependencies?

The truth is, your code, the entire discipline of software engineering, everything humans do, and in fact the entire universe itself, is built on dependencies. It's how the world works. We stack more and more layers of abstraction, to achieve higher and higher leverage.

Your employees are dependencies. The internet is a dependency. The building you work from is a dependency. Heating and electricity are dependencies. Food is a dependency. Your fellow man's willingness to pay taxes to fund a common defense (government) is a dependency. Your health is a dependency. The earth is a dependency. Etc. Etc.

Acknowledging the fragility of existence makes us uncomfortable. However, I don't think the right approach to deal with these feelings is to do the business equivalent of running off to the wilderness and living alone in paranoid self-sufficiency.

If you're willing to spend $15,000 a month to depend on a fragile human "employee" being around, maybe paying $15/month for Figma isn't such a big risk--and is in fact worth it?
Agreed, it has been very bubbly across the board. However, I think Nvidia (AMD as well) and Ethereum are especially correlated as first and second order effects seem proportional to incentive feedback into their respective ecosystems. Ethereum has been hounded by the 'wastefulness' of mining, which is to say 'proof of stake' wasn't born in a vacuum. Likewise, Nvidia GPU's were being bought at many multiples of msrp in BULK! Call it a perfect storm, call it what you want... but Nvidia has a tough road ahead.
https://www.sesostrisshrine.org/ looks like Nebraska area? Perhaps someone at that group might have some idea who he is.

Just finding out who made the scary tie-pin might be enough to identify this person!
Makes sense. There are two broad classes of code, actual standalone projects, and handy code you don't want to rewrite at each job. The latter really fits BSD or Apache - you're trying to break down as many barriers to use as possible and you aren't concerned about receiving contributions.
So that's not new. There was an extended BASIC in the Sinclair QL that allowed you to browse units and functions in the left pane, and edit the code in the right pane.

Before that, there was a system on the Burroughs B20 series that had a similar design; browse on the left, edit on the right.

Yeah, I approve of non-linear code editors.
The weirdest bit is that leftists themselves held modern conservative stances on homosexual rejection, transsexual mental illness, and election security as recently as Bill Clinton. You can readily find unambiguous quotes for each online. Obama himself stated on the 2008 campaign trail that gay marriage should not be legal.

Now, suddenly, these stances aren't legitimate? I do certainly agree that this seems like industrial gaslighting.
A Metaverse Without Customers
Just because you’ve launched a massively successful NFT drop, with tons of investors throwing money at you, it does not mean you have found a single person who actually wants to play your game.

A Metaverse built investor-first will be a ghost town.
NYT gift link (no paywall) - https://www.nytimes.com/2022/09/26/world/europe/edward-snowd...
> ...it's very difficult for me to believe that "Girls Who Code" is JUST a book that aims to introduce women to software development

You're sure it deserved to be banned... because it got banned?

Not sure that makes sense.
Whatever it is, I think the key to the success of LaTeX is that it is source code based. Something that displaces LaTeX should not be WYSIWYG or UI based, in my opinion. Maybe some kind if multitree based DSL.
Along with different properties of the beam other comments mention, there was also a question of dot pitch, i. e. properties of the phosphor grid. Also, the circuits generating the signals in consumer hardware often did not have that much of the full bandwidth, or the most correct wave forms.
> Is the NYT comment section just braindead? It seems like they are

They are indeed.

Critical thinking isn't something that NY Times commenters are capable of. They don't stop and think to question if the author could be wrong or even deranged in what they are doing or writing about. But instead in this case, the readers blindly support anything that is 'current trend', even if it is a more totalitarian idea and witch hunting and arresting anyone under the suspicion of wrong-think.

The blind leading the blind here.
I should have perhaps left the word "qualia" out of my summary, as Searle does not use it in his paper. (There are different concepts of qualia available, some of which are complex and dubious, and those complications can be left out by avoiding the word.)

To use his terminology to summarize the point of his argument: there is a logical difference between syntax and semantics.

Importantly, contrary to popular view, he was not trying to argue that building a "thinking machine" was not possible or that an instantiation of a computer program could not think; au contraire, he explicitly said it was possible to build a "thinking machine" and that some instantiations of computer programs could think.
ML experiment tracking and data versioning in VS Code
Well, if you are concerned that this series of books might be inappropriate for the target audience you could perhaps read one? The first book is 144 pages that are 8x5.5", you could probably finish it in an afternoon and then you would know for yourself if is as bad as you have decided it must be. You can start by reading an excerpt here:

https://www.penguinrandomhouse.com/books/537720/the-friendsh...
An interesting read. Near the end I started to feel like what the author is describing is very similar to the general approach I've coalesced on, over the years.

I've always deleted the snippet(s) in question after implementing the full behavior, however - or, more accurately, absorbed them into the final implementation piece-by-piece.

More recently, my team at work has started committing a logbook into our project repo for similar reasons of recording technical musings for posterity. Also similar to what the author describes, only in our case we are effectively _starting_ from the readme files and introducing code snippets where we feel the need. We're also maintaining the log as a single file - the plan is to archive 3- or 6-month chunks at a time as separate files once they reach a certain age.

This logbook experience makes me very curious as to how the author manages their snippets in practice. I wish they had gone into more detail than

> if you're able to keep on top of things [...] it mandates discipline

The baked-in chronological component of the logbook makes it straightforward to look topcis up by roughly _when_ they were deliberated on, but it's not great at guaranteeing a valid code snippet exists that encapsulates any given deliberation.
Conversely, snippets that

> should not even be conceptually aware of another snippet's existence

and be treated

> as a fully self-sufficient standalone program

seem to force me to incur a substantial obscuring of how any given musing or deliberation builds on what came before. At the least, many snippets will start with 10-20 boilerplate setup lines and class definitions.

Perhaps I am just wishing the author had explicitly mentioned if they import existing modules, functions, classes, etc as needed to keep the snippets short. If that is indeed an implicit assumption, then overall I don't have much to critique. If not, I am very curious as to what snippet-driven development for "framework-heavy" frontend code (eg React apps) looks like.
As the article says, the timing on the Ethereum dropping proof-of-work was shorter than Nvidia's production pipeline.
IMO the strongest applications are blockchain-related, but here are some other ideas which have been suggested -

- One can selectively disclose certain aspects of their identity. E.g. given a commitment to my DNA, I can prove that it doesn't match that of a suspect. (Though the police need some way to trust the commitment, perhaps a signature from the firm that sequenced it.)

- We can build trustless games, like an implementation of battleship where cheating is cryptographically hard.

- We could have trustless computation services, like ec2, or like SETI@home, etc. Though it's difficult to make this practical given the computational overhead of ZKPs.

- ZKPs can turn any delay function (like an iterated hash) into a verifiable delay function (VDF). VDFs could enable trustless lotteries/sortition.

- Given a general-purpose ZKP, it's trivial to build a signature scheme, e.g. by proving knowledge of a hash pre-image. This can sometimes lead to very practical signature schemes, such as Picnic, one of the leading hash-based signature proposals. Ring signatures are another generally-useful application.

- I think ZKPs have also been used as a building block in some FHE and MPC systems, though I don't know much about those areas.

- One can prove the existence of an exploit before divulging the details. This might be useful for e.g. convincing everyone to disable a certain TLS primitive which was just broken.
Got it, so then Ontario has good hardware and no incentives. Everywhere else has no hardware and no incentives. Still one step better for Ontario.

If/When the Ontario grid starts to feel the pressure of EVs, it is a choice between (No Electricity + Tiered Pricing) XOR (Electricity + 10x premium Time of Use Pricing).

I have a feeling everyone will complain but understand that the only option was to keep the grid running.
I’m handy outside of work and use sohcahtoa often enough to remember it. Triangles are everywhere and sometimes you need to compute angles and lengths of sides.

Statistics is also useful and applicable to everyday life, but I didn’t learn that till college as best I can recall.

I don’t regret having spent time learning calc, or physics or chemistry or biology for that matter. If you asked me to come up with a curriculum I’d have a really hard time prioritizing. Maybe the one thing I’d like to see kids learn better is how to be self-directed learners. I’m still fairly surprised at the number of colleagues I have who seem unable to problem solve and figure something the fuck out. Even knowing when and how to ask for help.
>"This is not a club, it is a series of books."

According to their website, Girls Who Code runs a set of clubs: https://girlswhocode.com/programs/clubs-program

The books are not the club, but the two seem closely linked.
I think we forget that Silicon manufacturing is planned a lot farther out than Silicon shopping.

They were likely trying to make TSMC purchase orders in the start of the pandemic, before a crypto boom. They also tried to handicap their GPUs wrt crypto. They likely didn’t expect the absolute shit show of a chip shortage (because who predicted or understood the pandemic early).

The rest of the market was desperate, and they probably expected it to be more robust than it ended up being. The merge would have been so far away at the time that they wouldn’t predict if it would happen at all nevermind when.
Five Walled Gardens: Operating systems are holding browsers back [pdf]
A List Apart is one of those sites that just impresses me with their content. I'm not a UI guy, and from time to time have to remember how to do something I had done somewhere else usually something to do with CSS. There's a specific example on Taming Lists from them that I refer to any time I'm trying to do inline lists that makes them play/feel nice other than display:inline.

If I'm ever searching for a CSS something and receive A List Apart link, it gets clicked
Fast-stable-diffusion colabs, +25% speed increase and memory efficient
The circumstantial evidence is pretty bad for this case, I made it to part 2 of his threads and I'm no longer interested in what he has to say. When you put forward tons of weak evidence, that doesn't make you look more correct, it makes you look desperate.

Particularly bad are the visual comparisons. What the hell is he looking at? In most cases he is simply wrong and you can see it with your own eyes.

- the sketch of Zodiac has much thinner nose

- the feathered arrows do not match, the feathers are drawn distinctly differently

(Part 2)

- the ampersands don't look the same to me

- the crosshairs absolutely do not match.

It leaves me with the impressions that he has decided Doerr is the Zodiac and will take any bit of evidence and stretch it to fit that notion.

edit: the feathered arrows look more like evidence against the idea he's Zodiac. He drew arrows a different way.
The bitter variety is a bit more drought-resistant. That's actually relevant in the Gran Chaco and the Brazilian Northeast, as both regions are rather arid and prone to drought. In the Amazon though? Not really - and yet most recipes that I've seen using bitter yucca (some using the leaves, that are heavy on cyanogens) are from the Amazon.

So the cultivation of the bitter variety itself is a tradition in all three places. In one of them, the tradition already lost the meaning to exist, but it's still there.