The YouTube thing is Google's choice, not Apple's, as those are "premium" features. Install Vinegar (https://apps.apple.com/us/app/vinegar-tube-cleaner/id1591303...) to get a standard HTML5 player in YouTube, which will let you make it full screen, PiP it, background it, whatever.
> The YouTube thing is Google's choice, not Apple's, as those are "premium" features. Install Vinegar (https://apps.apple.com/us/app/vinegar-tube-cleaner/id1591303...) to get a standard HTML5 player in YouTube, which will let you make it full screen, PiP it, background it, whatever.
But it IS Apple's choice. The problem is they have a mixed up conflict of interest, and it's even worse when Apple themselves is trying to sell you their own services.
IMHO the company making the hardware, the company making the software, and the company selling the cloud services shouldn't be allowed to all be the same company. There's too much conflict of interest.
Google sells PiP, background playing etc. as part of YouTube Premium (not Apple!). Google serves browser clients a player that can't do those things, because they want you to pay for them. Vinegar is a browser extension that replaces Google's player with Apple's plain HTML5 player. Apple's plain HTML5 player does all that stuff for free.
I love Django, and the new `tasks` framework to replace `celery` (/whatever processor you prefer) looks great.
I've only recently come back to it, and I do hope they continue to add more batteries to their "batteries included" framework over time. I was surprised just how much stuff I had to add to my little project that will require updating _outside_ the main framework, eg.:
* django-components for little template partials (I'm not sure the new partials feature is robust enough to replace this)
* django-(configurator,split-settings,pick-your-poison-here) for more robust settings management
* structlog for much better logging (feels like this should get baked into Python's stdlib...)
* debug-toolbar
* dj-database-url for parsing database URLs (should be baked in!)
* django-money
There's plenty of other deps that are less annoying/surprising (eg. Sentry, granian, Tailwind), but the set above feel like more or less like they should be baked in, and (to my mind) don't represent an inordinate amount of work to adopt.
Other than that, it's been a real pleasure coming back to it, and I'm excited for its continuation.
EDIT -- oh, and built-in static types, stubs and stubs-ext were a bit of a nightmare to get working well.
I just recently found it and it has been amazing. It logs all your requests and responses by default (but is quite configurable) as well as your SQL queries (and how many/how long they take), in an easily searchable database. It can even profile functions for you.
Makes it very to see at a glance what pages are slow for people, and why, so they can be optimized accordingly.
Absolutely! Just wish half the filters weren't broken... if I try to show only "POST" requests or only things from X seconds ago, it just always shows nothing... several other fields aren't working either.
It’s likely a future left-wing government will reintroduce these funds. The problem is the ratcheting effect: it takes no time at all to destroy something like this. Society reacts; people leave, people retrain, we lose the ability to do the thing we used to do. Then, a new government arrives and we rehire into these positions: it takes a lot more money to find people, attract them back to the country, get their programs established… and then the next government arrives and says “wow this is inefficient” and cans it again.
NZ in general is starting to suffer from the swings in partisan politics, despite our MMP system. Similar problems happen with bread and butter infrastructure projects.
True. The current government has taken a torch to everything the prior government did whether it made sense to torch, or not (replacement Cook Strait ferries for example). And they've enacted a bunch of extreme ideologically driven policies that no government left wing nor center could bear to keep.
We're in for dizzying swings in direction
This government arrived on a promise of “fixing” our financial problems. A lot of these shortfalls have been artificially created; as an example, our healthcare sector went from breaking even to being “hundreds of millions” in deficit after the budget was massaged. That created the “crisis” that let them fire the board in charge and appoint a commissioner who has been aggressively slashing public services in order to meet the new budget. The reduction in service is driving growth in the private insurance sector.
Science is in a similar position. The shortfalls they’re talking about now are shortfalls they created last year and left to rot so they could have a crisis now.
> A lot of these shortfalls have been artificially created
Can you point to a link showing this?
Officially:
Our revised budget for 2024/25 is a $1.1 billion deficit. This is significantly lower than the $1.76 billion deficit we were heading towards without our cost reduction programme,” Ms Apa says
I’m on my phone right now and getting search engines to limit their time frame in a mobile UI is tiresome, so I’ll do that when I’m back at a computer :) (but the core thing to do is compare projected budget under the previous govt and actual budget under this govt). Both of those numbers above are post-new budget. The budgeted “increase” in healthcare was less than the increases in population and inflation. It gets worse when we add in the fact that NZ has an aging population with requisite cost increases.
This govt gave us tax cuts and restored billions of dollars in tax rebate for landlords which decreased the spending pool available for things like healthcare.
Sure, but the framework cares about that for me. I don’t use rails personally but that’s the whole point — someone upstream of me is paying attention and making everything work together.
In contrast, I have work apps made in React that need regular piecemeal updating — routers, form libraries, query managers, CSS — because we’ve chosen to cobble that together ourselves. That’s fine, that’s the path we chose knowingly when we picked the tech we picked, but the point isn’t that frameworks don’t have dependencies — it’s that they take on more of the burden of managing them for you.
Well, Next is kinda like that then. It takes care of the sub-dependencies for you and when you upgrade, you just upgrade to the next major Next version (which isn't necessarily easy, but more so than upgrading 100 individual packages). They provide codemods for some stuff too.
I suspect that most rails, or next, projects add additional dependencies than just the framework. Generally the framework isn't the issue in my experience.
Sure, but it's not an either/or situation. Every big project adds dependencies, but using Next means you have some basic, common functionality included out of the box by default/by convention (like TypeScript, linting, testing, routing, caching, SSR, static builds, serverless definitions, etc.) all done in a predefined way. Maybe your project has 200 deps, but Next would replace like 50 of the big ones that you'd otherwise have to separately install and maintain. Just having a basic page/app router and minimal state system (via contexts and RSC and props and such) reduces a lot of the headaches of the bad old React Router days.
It replaces "React soup of the day" with a more standard "recipe" shared by most Next projects – like "Grandma Vercel's secret React minestrone", I guess. But yes, projects would typically still add their own "spices" on top of those basics.
For things like a missing person alert, it provides an instant feedback mechanism and the ability to share things with people you might know in the affected area.
Otherwise, there’s absolutely utility to interacting over social media. We’re doing it right now!
This is fantastic news. Between the Svelte 5 RC and Deno 2, I’ve been really enjoying working with the JS/TS ecosystem for the first time in a long time — it’s just been vaguely difficult keeping up with the (minor) tweaks in the RCs along the way. Congratulations to the team :).
I followed this avidly through the early access period. It’s really nice. I hope the announcement of the new HoMM drives more people to try Songs of Conquest, because for me, it does a fantastic job of revising and modernising the old formula.
Some game developers do test under Proton. Saying that because I'm in the discord server(s) for a few, and they mention stuff they're working on/support/etc over time.
Likewise, some do write GNU/Linux games, yet that wasn't in a number relevant enough to keep the original SteamOS going as businesses, until translation of Windows APIs was added.
Nintendo Online is something like $33/year where I live; Xbox Games Pass (the version with actual games) is $263.40 (the version with a much more limited subset of games is $155.40).
I assume the price difference is similar in the USA; the two products -- at least to me -- seem quite clearly different.
I dislike the new Safari layout in iOS 26 too. https://support.apple.com/en-nz/guide/iphone/ipha9ffea1a3/io... -- change it from "compact" to "bottom". I assume this choice will disappear in the future, but for now, you can make it more familiar.
Unfortunately, I don't have any advice for the Clock/Alarm; I don't typically schedule one-off future alarms. That would be a useful feature.
reply