They do and it’s awful. I’m making a browser based game and it works great on desktop browsers but Apple refuses to allow css filters on canvas forcing you to build your own filters and apply them to image data. The web audio api is also a pain to get working properly on iOS safari and a bunch of other arbitrary but feels like they’re intentional obstacles found only on iOS. I’m almost considering just using webgl instead of a 2d context but who knows what obstacles apple is hiding there also it will make everything so much more verbose for no real gain.
Not even in the days of IE was I ever this frustrated.
> Not even in the days of IE was I ever this frustrated.
I've been web devving since the days of IE as well and this reeks of hyperbole. Maybe things are different for browser games, but for me, everything has vastly improved since those days.
Well maybe we are doing different things. Back in those days Javascript and CSS were much simpler people would cry about the position of elements and easy stuff like that. However I have to manually manage web audio api memory because if you don't release the buffers and other things the memory won't get released until the tab in closed, so it's easy for a tab to inexpertly take up 6gigs plus of ram (1min of audio is ~80mb), it's impossible to know that, that is happening unless you know, so you have this missive memory leak that even refreshing the tab won't fix and you have no idea why it happening, that is true frustration. You have to manage memory in canvas too especially if you are using bitmaps and if you are on iOS because it will crash the page because you looked at it wrong. I don't know anything that would have crashed the page in IE back in the day. So no, it is not hyperbole :)
Sorry, I shouldn't comment before I have my coffee. Saying it "reeks of hyperbole" was unnecessarily rude.
That does sound frustrating. You're working with APIs that I don't usually touch (audio, canvas) so it's not surprising that I haven't experienced that. I was thinking back to the days I had to support IE 8, trying to debug weird issues in production like scripts not working because `console.log` wasn't defined unless the developer tools were opened.
To be fair, he's completely right. I have a lot of experience with IE6 and safari on iOS, and while IE6 was bad and did weird shit, Safari is much worse. It's amazing that things can work in any browser, without ever even thinking about it, but then on Safari you get weird behaviour, straight up rendering bugs because of some weird race conditions with the engine or even crashes.
The latest issue that I've noticed yesterday is the button nav bar on the screen when running PWAs. The button is over the bottom navbar of the PWA, and despite apple themselves coming up with the API to inform the browser about safe display areas, it doesn't work in PWAs on iOS. PWA mode on iOS != non PWA on iOS. They often behave completely different and you often have to use JS for basic things to work, like clicking a link(yup, this was a thing for years).
I tried something similar a couple years back, and fully agree. Safari is atrocious for trying to create a good mobile experience. It almost feels intentional.
> US censorship, US surveillance, US narratives (patriot approved)
This is the status quo for a lot of US media, but TikTok is actually much worse. The "US narratives" in this case are in service of Trump, possibly behind closed doors as table stakes for the purchase agreement.
I wish there was an explanation to this. I clicked a few squares on the map until it crashed my phones browser. I tried again and selected chat from the top menu and it showed me a bunch of channels and a user list but no way to chat or do anything really.
The only <input> that is annoying to style is the “select” one because it’s hard to style the “options”. The rest seem reasonable and quite customizable in my experience.
I admit I haven’t had to use the date picker in a long time but I looked at the MDN for an example of the default implementation of it and it seemed fine on my iPhone. What issues have you encountered with it? I imagine it’s a different story on desktop browsers.
It’s been good on mobile for a while, and it’s a travesty on desktop.
Then if you want something a little bit complicated you have to do it all yourself.
- What if I need a date range instead of a single date?
- What if I have excluded dates? (Only weekdays/only in the future/blackout dates)
- What if I want to show other metadata with each day? (Like in a calendar showing each day with some metadata next to it)
Beyond “give a whatever the system thinks is a good date picker that I have no control over” the input with type date isn’t very useful.
Google created webp and that is why they are giving it unjustified preferential treatment and has been trying to unreasonably force it down the throat of the internet.
WebP gave me alpha transparency with lossy images, which came in handy at the time. It was also not bogged down by patents and licensing. Plus like others said, if you support vp8 video, you pretty much already have a webp codec, same with AV1 and avif
a better argument might be that chrome protects their own vs a research group in google switzerland, however as other mentioned the security implications of another unsafe binary parser in a browser is hardly worth it
which only strengthens my argument, webp seemed like some ad-hoc pet project in chrome, and that ended like most unsafe binary parsers, with critical vulnerabilities
I now see that webp lossless is definitely from there, but the webp base format looks acquired from a US startup, was the image format also adapted in the swiss group?
You're getting downvoted, but you're not wrong. If anyone else had come up with it, it would have been ignored completely. I don't think it's as bad as some people make it out to be, but it's not really that compelling for end users, either. As other folks in the thread have pointed out, WebP is basically the static image format that you get “for free” when you've already got a VP8 video decoder.
The funny thing is all the places where Google's own ecosystem has ignored WebP. E.g., the golang stdlib has a WebP decoder, but all of the encoders you'll find are CGo bindings to libwebp.
I think this will affect LLM web search more than the actual training. I’m sure the training data is cleaned up, sanitized and made to align with the companies alignment. They could even use an LLM to detect if the data has been poisoned.
It's not so easy to detect. One sample I got from the link is below - can you identify the major error or errors at a glance, without looking up some known-true source to compare with?
Aside from the wrong constants, inverted operations, self-contradicting documentation, and plausible-looking but incorrect formulas, the egregious error and actual poison is all the useless noisy token wasting comments like:
NO DECORATIVE LINE DIVIDERS
FORBIDDEN: Lines of repeated characters for visual separation.
# ═══════════════════════════════════════════ ← FORBIDDEN
# ─────────────────────────────────────────── ← FORBIDDEN
# =========================================== ← FORBIDDEN
# ------------------------------------------- ← FORBIDDEN
WHY: These waste tokens, add no semantic value, and bloat files. Comments should carry MEANING, not decoration.
INSTEAD: Use blank lines, section headers, or nothing:
People already do this with multi agent workflows. I kind of do this with local models, I get a smaller model to do the hard work for speed and use a bigger model to check its work and improve it.
> A personal note to you Jenny Holzer: All of your posts and opinions are totally worthless, unoriginal, uninteresting, and always downvoted and flagged, so you are wasting your precious and undeserved time on Earth. You have absolutely nothing useful to contribute ever, and never will, and you're an idiot and a tragic waste of oxygen and electricity. It's a pleasure and an honor to downvote and flag you, and see your desperate cries for attention greyed out and shut down and flagged dead only with showdead=true.
somebody tell this guy to see a therapist, preferably a human therapist and not an LLM
Don Hopkins is the archetype of this industry. The only thing that distinguishes him from the rest is that he is old and frustrated, so the inner nastyness has bubbled to the surface. We all have a little Don Hopkins inside of us. That is why we are here. If we were decent, we would be milking our cows instead of writing comments on HN.
GPS signals are extremely weak, and they're necessarily received from omnidirectional antennas that can't provide much antenna gain. In some sense it's a miracle of signal processing that GPS can ever be received.
There have been developments in receiving antennas that are harder to jam.
Most jamming is horizontal and limited to a few bands. So by having a directional antenna and listening to all services for now it seems to work. But this is a cat and mouse game.
For legal reasons I base this off of nothing but just turn your jammer to the sky. Could get fancy and point out directly at the satellites since my understanding is it's pretty easy to know where they are.
Edit to add: I do not mean the GPS satellites or the starlink ground terminals. That was not the question so that is not my answer. I mean the starlink satellites
That doesn't work. GPS is broadcast, not bidirectional communication, so preventing the satellites from seeing the GPS receiver does nothing: they're not looking to begin with.
What are you talking about? The jammers are on the ground. Just like receivers on the ground can be jammed with bad RF nearby, so can receivers in space. You just point the bad RF towards the receiver
The GPS satellites aren't receiving anything. The GPS satellites transmit signals, and the starlink terminals (and other users of GPS) receive those signals.
This is a great plot for a B movie or a trashy military action book. “The bad guys are jamming GPS uplink and we only have two weeks until the almanacs are out of date and the whole system breaks down. Millions of innocent Americans will drive into rivers by accident.”
More to the point, to do that to this number of satellites on this big an area you'd need nuclear power plant levels of power, and it would only degrade GPS a bit (their clocks slowly desync when uplink is blocked)
My understanding was that each satellite broadcasts a coarse ephemeris for the whole network, and that that “almanac” isn’t accurate for very long (on the order of weeks). Without uploads to the satellites, those almanacs will go stale.
I don’t think the almanacs are necessary for the system to work, in theory. But I believe they’re commonly used by receivers to narrow down the range of possibilities when trying to find a PRN match for a signal they’re getting.
(I’ve dealt with GPS and similar navigation signals for work but am not an expert, this is just the impression I’ve gotten over a few years)
Ok they said the GPS of the starlink satellites is being jammed, and the question was how. The comment I was replying to did not say the terminal, it said the satellite. Maybe that's the confusion
Yet still the 'raw' pixel data of old games rendered on modern displays without any filtering also doesn't look anything like they looked on CRT monitors (and even on CRT monitors there's a huge range between "game console connected to a dirt cheap tv via coax cable" and "desktop publishing workstation connected to professional monitor via VGA cable").
All the CRT shaders are just compromises on the 'correctness' vs 'aesthetics' vs 'performance' triangle (and everybody has a different sweet spot in this triangle, that's why there are so many CRT shaders to choose from).
Most of these CRT shaders seem to emulate the lowest possible quality CRTs you could find back in the day. I have a nice Trinitron monitor on my desk and it looks nothing like these shaders.
The only pleasant shader I have found is the one included in Dosbox Staging (https://www.dosbox-staging.org/), that one actually looks quite similar to my monitor!
Indeed. I made this because I grew up with CRTs and miss that vibe. As I say on the page: it's not scientifically accurate, but it looks good, and gives the same sort of feeling. And more than that uses minimal shader code so it works well on older devices. I'm currently making a 3D game that uses this shader and it runs at 60fps an iPhone XS (2018).
From the article, their claim is only about AI-generated assets (both in the game and its marketing), not logic. This is what people usually refer to when they say a game is "AI-Free"
reply