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

If it was 8086 they would have written 8086

They write both. They write x86 repeatedly in the article and title, then show an instruction matrix that doesn't include, for example, the 468 CMPXCHG instructions or the crypto extensions PCLMULHQHQDQ instruction. Best I can guess, they mean 8086, which they think is equivalent to x86

Why is the 8086 not equivalent to x86? PCLMULHQHQDQ is from the CLMUL extension, which only began appearing in CPUs in the early 2010s - are CPUs from before then not x86?

x86 is an overarching group. Each processor is backwards compatible, I believe, so a 486 can run 8086 code, but they are not equivalent. If I download an x86 version of a program, I don't expect it to be written only in 8086 instructions

When you download an x86 program you're making a lot of other assumptions too, such as what the target operating system and hardware are. Even 8086 MSDOS software won't directly work in this emulator because it's not emulating DOS nor an IBM compatible, it has it's own addresses for the I/O. It's still x86 though.

> What you're seeing above is a C program that was compiled using GCC into native 8086 machine code being executed fully within CSS.

They did write 8086 in the text, but x86 in the title.


You could also swap to an distro where apt ugprade can't brick things, and where if you manually mess up you can rollback cough cough nixos cough cough

Agreed, write raw SQL, this has never had any security impact whatsoever[1]

- Your friendly local pentester

[1] - https://en.wikipedia.org/wiki/SQL_injection


Parameterized queries have been a thing for decades, which mitigate SQL injection attacks.[1] This is true of the examples in the post too, they used this:

  query = """
            SELECT * from tasks
            WHERE id = $1
            AND state = $2
            FOR UPDATE SKIP LOCKED
        """
  rec = await self.db.fetchone(query=query, args=[task_id, TaskState.PENDING], connection=connection)

[1] https://en.wikipedia.org/wiki/SQL_injection#Parameterized_st...

Parameterized queries fail to protect from SQL injection for decades, because database engine developers fail to listen. What could work instead, if any parameter could be safely injected:

    SELECT $1, $2($3) FROM $4
    WHERE $5 $6 $7
    GROUP BY $1
    ORDER BY $8 $9
but at that point SQL loses its point and turns into MongoDB query language.

Porsager’s Postgres package does a great job of letting you feel like you’re writing raw sql, but avoids the attack vectors.

Anyway, I agree that ORMs are pretty terrible. I like writing SQL or using a lightweight builder like Kysely. Was a huge Dapper fan back in my C# days.

There are plenty of reasonable alternatives to ORMs that don’t open you to SQL injection attacks.


What?


https://media.ccc.de/v/39c3-css-clicker-training-making-game... The CSS clicker talk was really entertaining as well as just technological amazing!


Because it doesn't use cloudflare duh.?


From their response headers, it seems like the request is coming from NGINX directly. How do they defend themselves against DOS attacks?


Big server. And if it goes down it goes down? Who cares, it's hackernews.


I have a handful of sites DNS/NS through Cloudflare, with their certificates, and they are working OK.


Why does that link redirect to a fart sound hosted on Wikipedia?


  // Vidrun, born of the sea-wind through the spruce
  // Vidrun, green-tinged offshoot of my bough, joy and burden of my life
  // Vidrun, fierce and clever, may our clan’s wisdom be yours:
  //
  //     Never read Hacker News
  // - Aphyr, "Hexing the technical interview"
  if (document.referrer.startsWith("https://news.ycombinator.com")) {
      document.location = "https://upload.wikimedia.org/wikipedia/commons/d/d4/Human_fart.wav"
  }
> https://www.boringcactus.com/assets/site.js


I find it always hilarious when websites check the referer for HN and do some random shit. "Alive internet theory"


The author doesn't like HN.


This is sort of thing is why I have a “they don't want me there, and I'm fine with that” list in my PiHole config.


The Referer header strikes again. You'd think the typo in its name would be the worst thing about it, but nope.


A quick glance at the website in question suggests that its owner may not be particularly mentally mature.


You might want to read the link first.


Kagi, an absolute must for me these days.


There is lorem ipsum text when viewed on mobile.


I don’t see any myself, unless they quickly fixed it after your comment


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

Search: