Hacker News new | past | comments | ask | show | jobs | submit | more zonidjan's comments login

Errrrr... dosbox?



Yes, I know what dosbox is, thank you. That's ... why I mentioned it ...


What's wrong with dosbox? Please elaborate.


> Is there an equivalent like that now for game development?

dosbox is your equivalent.


Whether there's a bug in the underlying API code, or a bug in the web server, there's a risk that it "may or may not result in the standard response format you're expecting", and therefore... should be a 500 error.

Yes, using the wrong status codes is a problem, you're right, that's the entire point of the thread you're responding to.


that's flat out not true, it's a red herring.

I can't think of very many tech stacks where an error inside the API couldn't be trapped and responded with a standard json response.


That's... extremely rare, extremely ancient, and even then was usually only a problem below a certain page length.


> it's not like you can't design super lean websites anyway.

Sure, but people don't.


> I've been using the web on mobile connections ever since I got my first iPhone in 2008.

Okay, great. You had one of the most powerful phones at the time. How was the experience for people with a "feature phone" in 2008? (I'll tell you from experience, it was terrible).

How would the experience be today, with your iPhone from 2008? Terrible. Why? Is the web more powerful as a result? Can you do more things? Nah, it just looks flashier.


> because it helps drive up the current average affordable densities of RAM and storage

It does, but it also means that RAM and storage isn't available to be used for other things. Think about what you could if you had current hardware back in the XP days...


JavaScript, SPAs, animations, pages filled with "pretty" instead of content.


Site blocking the page with an empty overlay named "BorlabsCookie". No thanks.


The cookie acceptance on this site is as good as it gets IMO. Clear, detailed, privacy policies linked, with the ability to accept a reasonable, minimal subset.


There are plenty of other ways to fingerprint a user. https://amiunique.org/


That really doesn't answer the question. Munchberry claims these analytics tools have cross domain tracking and I'm asking how, precisely. In part because of professional interest, and in part because I don't actually think it's true.


Thanks for getting my username right. ;)

You specifically got one detail wrong: it's not just for analytics tools. It's the adtech industry in general using this technique, and Adobe offers its analytics as part of its marketing software suite.

From their own site: "What is Adobe Experience Cloud? It's a collection of best-in-class solutions for marketing, analytics, advertising, and commerce."


Apologies Munch bunny, gonna blame that on a need for new glasses.

fwiw, Adobe Experience Cloud is generally not the sort of adtech that attempts to sell information.


You're right, Adobe Experience Cloud doesn't sell information, so how problematic you find the product depends on where you draw the line on privacy.

Specifically, Adobe Experience Cloud definitely offers retargeting capabilities (ads following you around the internet) and the ability to get statistics on the effectiveness of that advertising. If they're at parity with competing marketing suites, then they also have attribution capabilities to track you with per-user, per-interaction granularity.

A site that serves Adobe Experience Cloud cookies in the third-party-disguised-as-first-party way is likely enabling this capability for all marketers that are going through Adobe Experience Cloud. So the interesting question would be whether you, a visitor to Fox.com, consider being watched by marketers who aren't Fox.com to be a privacy problem.


All of the above is more private than eg google analytics because of the lack of cross domain tracking... I'd consider it a big improvement vis-a-vis google's product suite.



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

Search: