Earth, 2026. Silently shifting through the mysterious dimensional plans, Cthulhu just jumped in. Thinking it could unleash new level of despair and frights on the mere mortal souls inhabiting this world, it was anticipating it's own jubilation. Throwing a glance omnivision on it however, all sense of joy suddenly vanished from its monstrous mind and to its own surprise, despair was invading it as it was contemplating situations far more awful than what it had ever devised. All self inflicted by small almost-thoughtless meat bags. Shifting back, it tried to convince itself this never happened and in the same time, promise itself to never land again on this desolated place.
Yeah, local is clearly the future. Even beyond the cheap Chinese models you can install the apfel[1] stuff if you're on a mac and want a quick available onboard cli option. And I'm sure people will adapt the Flash-MoE[2] integration to be even better soon as well.
One thing that has been driving me bat shit as an FE for years is the lack of browser engine implemented basic UI elements as default HTML. The fact that we still need to build custom carousels[1], tooltips, and other common patterns instead of just dropping a <carousel><slide></slide><controls></controls></carousel> or <tooltip/> is baffling to me. Stop making me write so much JS to do something that we know as a community is going to be a pattern! Just gimme the damn elements and a decent API to manipulate it reasonably! Not to mention all the custom, half ass a11y implementations I see.
There are some groups out there like Open UI[2] trying to push for this stuff but it seems like the standards bodies have no interest in a decent UI ecosystem instead favoring bloated APIs that make up 5% of your application versus the 95%. I'm mad! I'm mad online!
[1] I'm familiar with the newer carousel CSS/JS stuff but it's kind of clunky. I'll take it either way but damn
> I'm familiar with the newer carousel CSS/JS stuff but it's kind of clunky
I think you've just answered yourself why.
Browsers are the most used applications on the planet. They have one chance to get an API right ("don't break the web"). They iterate on a new API for years. When they finally launch it, devs call it "clunky".
Counterpoint: the standardized surface area of a browser is already enormous, and while these components seem simple, there are a billion different options, variables or alternative implementations to consider.
At some point, functionality needs to exist in user space, even if it's common.
Yes, please!
But browsers need to make it easier for things to exist in user space.
That means reviving CSS Houdini, particularly reviving the animation and layout worklets. (It got abandoned because browser vendors (Chrome in particular) found them too difficult to implement. They would need to rearchitect a good chunk of their rendering pipeline. Instead we got a bunch of very limited but easier to implement features like scroll animation timelines)
The CSS-only Carousels have gotten really good and easy to drop in lately.
Most tooltips can be handled by ancient `title` attributes and the ones that can't should generally be popovers anyway. Firefox support for anchor positioning is out now so HTML+CSS-only/mostly popovers are in a great state today.
There's always more UI controls people think they need. The web will be forever chasing that. But so much has happened in recent years it feels good to stop a moment and appreciate all the little things like details/summary working great for JS-free expanders and accordions.
I'd really like to see some FE folks kicking around what sorts of new form elements they'd put into HTML 6. I miss WinForms, component libraries, Silverlight, WPF, that sort of thing. Browsing the sea of components somebody like Telerik or Infragistics or DevExpress give you brings so many ideas to my mind. The web has nothing to show for decades of being in the limelight. We have buttons, textboxes, checkboxes, drop down lists... the end. Oh I guess we have date pickers now, and reasonable large text areas. I mean we build apps this way so it's not impossible to live like this. I'm just jealous of folks with Blazor and a component library license.
At a previous job, we had to refactor our entire front end build system from Rollup(I believe it was) to a custom Webpack build because of this attitude. Our FE process was completely disconnected from the code on the site, existing entirely in our Azure pipeline and developer machines. The actual theoretically exploitable aspects were in third party APIs and our dotNet ecosystems which we obviously fixed. I wrote like 3 different documents and presented multiple times to their security team on how this wasn't necessary and we didn't want to take their money needlessly. $20000 or so later (with a year of support for the system baked in) we shut up Dependabot. Money well spent!
I'm curious if there is a particular technical reason you chose to make this as a separate script rather than some kind of Jellyfin plugin? I actually appreciate that you did it in this fashion (more useful for me personally), just curious if there were limitations within the Jellyfin/dotNet system.
Either way, gonna make my World Cup viewing experience this year a lot easier haha
What a neat LLM question! Most of my results were the same as what you posted except for the first time I asked it which resulted in this pretty interesting answer:
Taiwan is in the Taiwan Standard Time (TST) zone, which is UTC+8, while the Pacific Time (PT) zone is UTC-7.
Never thought to use an llm for time zone stuff. Seems like it struggles as much as a normal person, which makes some sense given what they're trained with.
Louis Rossman recently posted a video (https://www.youtube.com/watch?v=II2QF9JwtLc) where he had Gemini replace his 10+ year carefully curated content with AI slop and he instantly shot (back) up to the top of the rankings. They're very clearly favoring their own generated generic content rather than any sort of organic, well written or well informed entries. Shame.
There's AI features and tips in Youtube's Creator Studio, they are encouraging creators to use AI tools. Makes sense that they also then reward videos that make use of it. That's how these platforms nudge people into products and behavior that they want to bring to market.
I think a web ring combined with some kind of web of trust style system would be nice. Ideally they could be both centralized where an initial creator holds the keys to what's allowed and decentralized where it just sort of exists. I haven't quite been able to sketch out a reasonable way to keep sites persistent and consistent except DNS records, though. DNS of course making it hard or impossible for smaller and less tech-savvy creators while also having it's own issues regardless.
I'm a big web ring person though so I might be biased and trying to use a hammer in place of a screwdriver.
