Conscat

I remember having this issue ALL THE TIME with Gemini CLI but personally I haven't experienced that yet with agy.

I had this experience at work trying to optimize a little high level Pytorch. It can't really get better than it already was, but LLMs were quite willing to pretend they will. The real solution is I need to open a PR for one of Pytorch's tracking issues.

> Then somewhere along the way, they decided they wanted to be a real browser for some reason

I had the impression all along this was the goal. The initial message was "You CAN build a modern browser" which includes JavaScript, modern CSS, WebGL, WASM, WebGPU, etc. The initial article that Ladybird very loudly proclaimed to be antithesis to asserted these are why you can't make a web browser.

My boyfriend and I were confused because I thought humans have a body temp higher than 97dF and somehow the title made me think this was exceedingly high.

> If people find a life partner they drop off the site, and you constantly have to find new users to replace them ... As a result, some of the less-scrupulous sites purposely make it less likely that you will see people who seem like great matches

I've often heard this sentiment, but I'm very skeptical. Firstly, most users in my experience seem to prefer casual relationships even if that's not what their profile indicates. Dating apps are also one of the highest vectors for cheating today, and one man even confessed to me on our second date that he has a wife in Rajasthan.

But I think the fact that the major apps' user bases all grow over time indicates they have a naturally healthy replacement rate. People turn 18 every day and desire a partner. People break up every day, etc.

Is Jeevansathi really that different mechanically from a casual dating service? I don't think it has a literal swiping motion (many dating apps don't either) but I've heard complaints that modern matrimony apps are even too similar to dating apps before.

There exist hundreds of fly by night matchmaking apps, but most people can only name about half a dozen off hand.

I don't remember a map from the movie so I didn't know what to expect. Instantly I love this. I actually wish I could have this rather than street view in Google Maps.

Senior is the last word in use to describe myself as a developer, personally, and I think it's hard to overstate the current economical significance of this software niche. Granted that it IS a niche and nobody would recommend Mojo for, say, kernels in video games or art editors.

In the category of AI/HPC software Mojo aims to displace (which is my industry), I don't know many people who care that much about running Windows. The software I work on may only run as a Docker image or directly in a Linux/WSL. Mojo is hardly the only tool in the space (currently) lacking Windows support.

You can implement it with templates and people do things like this often. In modern C++, it's even pretty easy to make this type of trick support `constexpr`.

I thought it was a semi-transparent window until I read this. The curvature makes that clear, wow!

It's not true that Nvidia doesn't care about CUDA backwards compatibility. The invention of TileIR was motivated entirely by that problem. GPU architectures are supported by the full tool suites for at least 10 years by CUDA (that's longer than they are for graphics).

Nvidia is also a major contributor to MLIR, which they use for TileIR and ClangIR, so should a compatibility break occur it wouldn't be entirely up to Mojo to fix it.

I don't think someone mentioned yet, but the (now defunct?) company Outrun Labs built a product Revery which seems almost exactly like what Jane Street has done (to my amateur eyes). OniVim was their only end user product afaik, built on this tech.

I was able to upload hacky unpolished amateur game demos long before LLMs existed.

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.