Conscat

Clang pointer authentication makes any type of vtable attack impossible in C++.

According to Apple, are there any tech companies in the galaxy who haven't stolen their trade secrets?

It would only be effective if the significance of this work is clear. They certainly felt this message needed to reach people, and that it did work makes it self evident they were probably right.

Personally I hated Publix when I lived in Florida and it made me homesick. I've never had so much food come with mold in the packaging than from Publix.

As much as I loved growing up with HEB, my fondest memories are of eating Central Market squid salad and brie in its playground/music venue backyard.

This seems like the "obvious" solution. Why was the rejected?

EDIT: It appears to be an objection to GPU programming entirely.

I have been a ClearFlow user for over a year now. Generally I like it, but there absolutely are still common words that are hard to input consistently. The THEA cluster has given me no shortage of problems. Still a fan though.

A Pascal string has a leading length byte. Because that is one byte, the text can't exceed 255 characters.

Clang and GCC both let you use Pascal strings in C if you would like (with `\p`). But Pascal strings aren't that useful today because the maximum length is too short.

I feel like I've never gotten a compelling explanation for why Nastaliq is hard/unavailable. I'm not an expert on abjads, but it doesn't look harder to render then Naskh (and it self-evidently is possible since the fonts exist). Does anyone here know why they make it difficult? Urdu is much less obscure than, say, Sharada or other languages with Unicode support. I think Punjabi is also often written in Nastaliq when it's not in Gurmukhi or Roman.

Isn't it customary for the author of a post shared on HN to leave a comment on the thread?

I find it very funny to imagine Keralam and Tamil Nadu part of Sri Lanka.

I've got really comfy `just` scripts for generating Clang "intermediaries" in my CMake project. I can generate `.ii` files which get formatted and edited in a manner making them directly recompilable, along with `.ll`, `.bc`, and `.s` files. All the above are per-translation unit or post-LTO and I can constrain the output to specific functions or files, and the LLVM bitcode can take optimization passes or optimization levels to very easily introspect how my work in this codebase optimizes.

I've also got a clang-repl wrapper for this codebase that is very easy to use and makes interactive programming much easier for me.

Obviously 5 year olds deserve access to safe abortions whether they are trans or cis. It's not safe to carry a pregnancy so young.

The point here is that these examples need to be updated because @cImport, the syntactic feature of Zig, is being deprecated and removed. That there exists an alternative isn't relevant.

These demos honestly look pretty good to me. But it is objectively true that this and similar technologies are used at huge scale by every leading autonomous vehicle manufacturer, so we can inductively reason that it _is_ good enough for that use-case. I don't work on Cosmos, but I am currently working on a superficially similar non-open technology at Nvidia used by many of these leaders which, in my opinion, produces similar quality. Some of the open research for it is here:

https://github.com/nv-tlabs/3dgrut/

https://github.com/NVIDIA/harmonizer

https://github.com/NVIDIA/instant-nurec

https://github.com/nvidia/ncore

Nvidia also is integrating Gsplat into at least what I work on and contributing upstream.

https://github.com/nerfstudio-project/gsplat

Does anyone else miss KWrite? I had it configured as a very slightly more advanced Notepad.exe clone. I really enjoyed opening it for quickly writing out thoughts that crowd my ADHD brain, and I feel like the full Kate takes much longer to open up and looks much much heavier and emotionally oppressive for what I want to do.

These are some very extreme examples of this that push the feature's limits:

https://news.ycombinator.com/item?id=47256810

https://news.ycombinator.com/item?id=26495059

Fwiw, nobody has ever suggested to me that I employ token compression in my daily workflow. I don't pay full attention in all the AI workflow demos I'm supposed to attend, but I don't recall that even being discussed. Is this an Nvidia blog or tweet you're referencing? I'm actually interested to see what they have to say.

I'm not, I work higher level products. I've talked to a few people who do but I don't recall if they have different standards.

At Nvidia, we have no limit for Anthropic or Open AI models (for now) and are heavily encouraged to use them as much as possible.

I learned to read Devanagari by putting generic Google images cards on my phone's wall paper.

I had never heard of low background steel. That's a fascinating problem it solves (and I love the analogy).

In the bay area, I've met relatively few NRIs who don't know Hindi well, even if it's not their first language. Most of them that I've met are not even Kannadiga, Mallu, Telugu, or especially not Tamil. Sample size of at least several dozen.

Studying Hindi has felt very rewarding to me, and it impresses people disproportionately to my actual skill, but I don't feel it has affected my ability to communicate with coworkers whatsoever.

Any media company which deliberately rids itself of everyone willing to speak vaguely positively of transsexual people may not be attracting the most free thinking writers.

That feels reductive. It's actionable to get OCI, renounce US citizenship, and become Indian after a decade. It's just not very practical for most people. I know many people who don't work their dream job, but switching to a favorable company isn't currently practical for them.

My understanding from speaking with a few Tile IR devs on dates is that its primary motivation was providing better portability for programming tensor cores than PTX offers. Nobody ever told me they saw it as a response to anything other than customer feedback.

Every reasonable language has a Python interop story. All it takes is C FFI. But what Mojo promised early on was the eventuality of compiling a large amount of Python code if not entire wheels as Mojo.

At least it doesn't go down as often, I guess. I think most users do want a centralized forge that gives them discoverability and star graphs.