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

https://x.com/Monodraw suggests there have indeed been updates


To be fair, the last tweet is from 2 years ago.

However, I’ve made pretty good use of it, and it’s really a “complete” product. Not much more to update than the occasional mandatory platform upgrade.


Excellent (and shocking) research!

Rather a shame that page with the abstract has excessively large & linespaced body text which makes it hard to actually read on mobile... that the chat feature assumes you must be a student not anyone else... and the Contact Us is buried many levels deep in the nav... hence me giving up and telling you about the above here.


Kind of, using it became known as "AJAX" and it took many many years (and the addition of promises to JS) before the more sophisticated "Fetch API" became available.

Even then usage of AJAX declined rather slowly as it was so established, and indeed even now it's still used by many websites!


I assume you mean the decline in the use of the term AJAX as it was now just the standard and you don’t need to use that to describe your site or tool as being capable of being highly interactive and dynamic vs just static.

Before the invention of the xmlhttprequest there was so little you could do with JS most dynamic content was some version of shifty tricks with iframes or img tags or anything that could trigger the browser to make a server request to a url that you could generate dynamically.

Fetch was the formalization of the xmlhttprequest (hence the use of xhr as the name of the request type ). Jquery wrapped it really nicely and essentially popularized (they may have invented async js leveraging callbacks and the like), the creation of promises was basically the formalization and standardization of this.

So AJAX itself is in fact used almost in the entire totality of the web, the term has become irrelevant given the absolute domination of the technology.


You're mostly spot on but your last sentence is flawed, as it's chloramines that are the problem with pools, not chlorine, and urine is all-too-often the root cause

https://www.chemicalsafetyfacts.org/health-and-safety/how-ch...


From the article, reasons why chloramines get created:

> perspiration, oils and urine that enter pools from swimmers’ bodies.

I choose to be an optimist and will believe that list starts with most common source and ends with the least common.


According to the article, chloramines come from the reaction of pool chlorine with human urine, sweat, and body oils.

It seems like that would still be happening in the absence of urine?


Presumably you meant to say "insanely inefficient"?


No, that's kind of the trick of it. To be able to do this, the thing you create has to be, on a base level, insanely efficient compared to what came before. You're frontloading years of optimizations in one big leap.

On top of that solid basis, you can introduce artificial inefficiencies, and then gradually remove them.

But you can't do the trick at all, if your rewrite doesn't start off being an orders-of-magnitude efficiency improvement.


yes :)


Does it lie? Or just get things wrong sometimes?

Lying requires knowledge that what you are saying is not the truth, and usually there's a motive for doing so.

I don't think ChatGPT is there yet... or is it?


Technically, what ChatGPT is doing is bullshitting because it doesn't have any knowledge of or concern for truthfulness.

https://en.m.wikipedia.org/wiki/On_Bullshit


Sure, it's not lying, you're right, there's no will there, I'm anthropomorphism. It is producing entirely wrong facts / pseudo-opinions (as it can't actually have an opinion).


I was about to suggest "pathologically dishonest", but then I looked up the term and that seems to require being biased in favour of the speaker and knowing that you're saying falsehoods.

"Confabulate" however, appears to be a good description. Confabulation is, I'm told, associated with Alzheimer's, and GPT's output does sometimes remind me of a few things my mum said while she was ill.


And USB-C sockets are much more robust than USB-A sockets


I genuinely cannot tell if that's sarcasm or not; if a serious claim, I'd love to see some comparisons, on both the socket and on the cable side (i.e. with Micro and Mini USB, it was not typically the socket that gave way, but the flimsy connector on the cable, which is generally my fear with USB-C cables as well. USB-A, I never ever ever had an issue or fear with either cable or socket).


LOL, I remember hearing this lie too. They are slightly more robust than micro-USB, but so are spaghetti noodles.


The 3com card with the minimal pop out Ethernet socket [1] was super cool but it was rather fragile, especially if someone tripped over the cable!

[1] https://cdn.shopify.com/s/files/1/0597/9131/1011/products/3C...


I had a PCMCIA card as a 33.6Kbps modem.


It already exists, see http://www.quakejs.com/

I don't have an Apple Watch but it would be interesting to know what happens when you fire it up on one.


I have two Chromecast Audio devices which similarly provide both analogue and optical digital outputs, but they seem to be much more expensive second hand than the Airplay alternative.


I'm not sure if Chromecast Audios support lossless, if that matters.


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

Search: