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

I don’t think this should be implemented but I would be really curious to know who the most disliked commenter on the site is

A good writer knows when to use literary techniques.

They work just fine in this post.

Yeah, it's perfectly reasonable device that I often use. I love the circle reasoning being displayed:

  "this sounds like AI"
  "professional writers use this technique"
  "they can't be a professional writer, they're using AI"

No, it’s unpleasant to read. To be clear, it’s possible a person wrote this, and that would not change it being unpleasant.

This seems like a great use of time actually

I don't think they use Virtualization for most launches now

I think you are right, I’m not sure that they actually use it for stuff that doesn’t require Rosetta (arm64 stuff)

> the sensor lives under AppleSPUHIDDevice in the iokit registry, on vendor usage page 0xFF00, usage 3. the driver is AppleSPUHIDDriver which is part of the sensor processing unit.

We know, the law requires you tell us of this if they’re for marketing purposes.

It’s actually a cookie experiment

This depends on the program.

There are intermediate firms that will get the exploits passed to the right people. They are not very difficult to find.

This would make for a neat poster.

Yes. And: Fabric.

Shirt.


> LLVM: Pretty much everyone who has created a programming language with it has complained about its design. gingerbill, Jon Blow, and Andrew Kelley have all complained about it. LLVM is a good idea, but it that idea was executed better by Ken Thompson with his C compiler for Plan 9, and then again with his Go compiler design. Ken decided to create his own "architecture agnostic" assembly, which is very similar to the IR idea with LLVM.

I suggest you ask around to see what the consensus is for which compiler is actually mature. Hint: for all its warts, nobody is writing a seriously optimized language in any of the options you listed besides LLVM.


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

Search: