Hacker Newsnew | past | comments | ask | show | jobs | submit | adamnemecek's commentslogin

> Rust is complex.

Compared with what? C++? It is not.


False equivalence.

You focused on the C++ aspect and completely failed to engage with the actual critique - what is a “simple” language that you’re evaluating Rust against as a failure?

OS is to blame. There should be a way for the OS to tell to the app "offload your state" like phones do. Paging is supposed to achieve this but does not.

But those are retina pixels right? Like what is the max resolution of that display?

Retina pixels what? Pixel is a pixel, density _of pixels_ is what you're looking for

"Retina" is Apple's marketing name for high PPI displays.

Exactly. Retina is not "pixels" though or type of pixel

I think they mean "but those pixels are very small, right?"

6016 x 3384.

Dell monitor is twice the surface area with 3/4 the pixels … or in reverse: Apple display is half the size with 30% more pixels.

(edit: corrected dell pixel %)


What is going on here? Why is everyone in this thread using 'pixels" to mean ppi? It seems unnecessarily confusing or even misleading. I mean blatantly a 6K monitor has more pixels than a 5K or 4K one, regardless of the pixel density.

Yeah, nobody’s saying a 5k monitor has more pixels than a 6k.

I think what people are trying to communicate, but struggling to, is that high pixel count on a huge display can be deceptive.

I think grandparent was trying to say “comparing a low-poi display to a high-ppi display is not a direct comparison.”


Consider adding support for Typst.

Interesting idea! Typst is compelling (Rust-based too). Not on immediate roadmap but could be a future addition. TeX is heavier but possible via external tools + pipeline feature.

Or even better, TeX. I realize capital bought out even basic typesetting but let's not encourage this

Typst is open-source.

Open source doesn't mean relinquished from capital by any means. I also don't blame the author of typst. But TeX is truly free from capital, and that should mean far more than the aesthetics of a nicer interface.

Integration with typst will be more straightforward than latex.

Yes, at the cost of dragging people into subscription software. Fuck off

How?

Markdown was cool for a while. I have switched to typst and boy is that an improvement. It’s the love child of latex and markdown. With markdown you’d still have to embed latex, while typst has its own thing that is nicer than latex.

I've been enjoying Typst. I worry that much of it is too complex for many end users. I'm musing about having end users draft stuff in markdown, then render that markdown with Typst templates.

You don’t have to use those parts, you can use it as markdown.

Good call, I've had success with:

     pandoc -f gfm -t typst -o file.typ file.md 
and as you'll know it's easy to add a Template if required.

Pandoc is cool but I hate writing my own scripts for it.

the icing on the cake would be gitlab, github, etc. rendering typst like markdown

Typst is lovely.

I started using nushell around April 2024. While it is much better than other shell languages, the lack of proper types is painful.

Shell languages make sense if you believe in the Unix philosophy. For me, the problem with the Unix philosophy is the endless serialization and deserialization as well as lack of proper error handling. So nushell for me is a good answer to an ill-posed question.

The approach I have been taking is a single binary with a billion subcommands and aliasing these. I currently have two of these in Rust, one in Swift. I tried going all Rust but integrating with certain aspects of macOS is just so much simpler in Swift.

Like the recent push to make CLI development suck less (e.g. argument parsing used to be painful but is solved now) has made developing CLI tools a lot less painful.


serialization/deserialization will always be needed unless you got all your programs working with the same ABI. it's just that in nushell's case you aren't serialize to human readable text.

endless serialization and deserialization is what makes me hate Bash and love PowerShell which solves this issue by piping full objects between commands and the ConvertTo-JSON command.

> Abstractions don’t remove complexity. They move it to the day you’re on call.

Then they are bad abstractions. I get where he is coming from, but the entire field is built on abstractions that allow you to translate say a matmul to shuffling some electrons without you doing the shuffling.


They are very different.


AI is capital intensive because autodiff kinda sucks.


> run them like their own little ramshackle empire for their personal enrichment

If you are from the US, I’m laughing my butt off, the irony is not lost on me.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: