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

Makes sense. I think this is a variant of the "parse, don't validate" motto, but is more "parse, don't parse-serialize-parse" in the implementation.

The mental health version of "AI is here to stay, like it or not you have to use it" that some people keep trying to tell me in software.

[flagged]


Let's please not trivialize rape. This is hardly the same thing.

Some rape victims detest the comparison. Some make the comparison. I would agree people who have not been raped should avoid the comparison. But I would not assume someone who made the comparison had no standing.

Yeah. Investing in stupid things can absolutely destroy wealth. But it's not the correction that does the destruction; that's just when people notice it has been destroyed.

From https://www.merriam-webster.com/dictionary/censor#dictionary...

> censor (verb): to examine in order to suppress (see suppress sense 2) or delete anything considered objectionable.

> also: to suppress or delete as objectionable

Government censorship is a very notable class of censorship, but the word has a broader meaning.


In the context of the Constitution, government censorship is the only thing that the United States cares about.

If we valued banning all censorship we'd make laws banning that. We don't: we value private property and free speech instead. Taking the rights of private parties to control what they publish tramples both of those rights. It's not complicated: you have a right to own your 'press' and do whatever you want with it. You don't have a right to someone else's press.


Censorship is free speech?

No they are saying choosing what to publish or not is part of private property rights.

I suppose it makes sense that every version that came after "c++0x" should be interpreted in hex.


Like most attempts to put AI in the browser, that feels stupidly vulnerable to injection.


Definitely worth asking the devs about, they're active on HN.


Little endian does appear strange at first, but if you consider the motivation it makes a lot of sense.

Little endian's most valuable property is that an integer stored at an address has common layout no matter the width of the integer. If I store an i32 at 0x100, and then load an i16 at 0x100, that's the same as casting (with wrapping) an i32 to an i16 because the "ones digit" (more accurately the "ones byte") is stored at the same place for both integers.

Since bits aren't addressable, they don't really have an order in memory. The only way to access bits is by loading them into a register, and registers don't meaningfully have an endianness.


> Since bits aren't addressable, they don't really have an order in memory.

Bits aren't addressable in the dominant ISAs today, but they were addressable by popular ISAs in the past, such as the PDP-10 family.

The PDP-10 is one of the big reasons why network byte order is big-endian.

That said, I forget whether the PDP-10 was big-endian or little-endian wrt bits.


I'm not sure I've ever seen that actually come in to play. Little Endian is obviously the best Endian, but I don't think that argument really makes sense.

The most obvious argument is that little Endian is clearly the most natural order - the only reason to use Big Endian is to match the stupid human history of mixing LTR text with RTL numbers.

I've seen one real technical reason to prefer little endian (can't remember what it was tbh but it was fairly niche) and I've never seen any technical reasons to prefer big endian ("it's easier to read in a hex editor" doesn't count).


It depends on the application. Big Endian is pretty good for networking and sorting. If you store the address in Big Endian, you can start doing streaming prefix matching, because the most significant address byte is arriving first. When you consider how many routers and switches a packet has to cross, any buffering or Endian conversion is going to increase latency.


Which part of that sentence do you think is hyperbole?

> Forecasting models predicted that the current steep funding cuts could result in more than 14,051,750 (uncertainty interval 8,475,990-19,662,191) additional all-age deaths, including 4,537,157 (3,124,796-5,910,791) in children younger than age 5 years, by 2030.

https://www.thelancet.com/journals/lancet/article/PIIS0140-6...


MATLAB doesn't even have 1-d arrays, it really is missing the principled and composable operations that make array languages useful


I believe the ArrayCast had this debate on whether it's considered an arraylang when they had some of the MATLAB devs on.

The determination they came to was that MATLAB is an array lang but not an iversonian array lang.


guys,

symbolic algebra package and a computer language are not the same thing :) not even remotely.


The "PBS spacetime" channel exists, so they're doing something right.


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

Search: