The docs say there's a separate event for merge_group which I assume means you can configure different checks.
https://docs.github.com/en/repositories/configuring-branches...
2,026 karma · joined July 18, 2011
The docs say there's a separate event for merge_group which I assume means you can configure different checks.
https://docs.github.com/en/repositories/configuring-branches...
(I'd also add modules to your list fwiw, they were designed without taking performance into account.)
https://developer.android.com/develop/ui/views/layout/webapp...
It's the system WebView, it's just not using Custom Tabs.
It definitely doesn't make sense to expire accounts in use by desktop software where the user doesn't login to the website.
When I've seen companies do sloppy stuff like this in the past it's because some employee manually queried for accounts but their SQL query was missing a bunch of cases.
https://slate.com/business/2022/10/san-francisco-toilet-mill...
The bug doesn't seem to discuss use cases for it either. The most I could find is: https://github.com/golang/go/issues/56351#issuecomment-13326...
Which boils down to "doing what clear(slice) does cannot be implemented efficiently today" but I'm not sure how having an efficient way to do something folks don't want is useful?
There's already a memory clearing optimization in the compiler: https://github.com/golang/go/issues/19266
So yeah I'm not sure under what situations folks will use clear(slice).
I suppose it could have been x = clear(x) or clear(&x), but certainly if you understand Go semantics then seeing any function call do Foo(slice) already signals that the call can't modify the length since there's no return value.
Ex.
https://www.researchgate.net/figure/Schematic-image-of-a-wor...
https://f-e-t.com/subsea/vehicles/tether-management-systems/
There's also this one which looks like it can get to the depths of the Titanic:
https://nautiluslive.org/tech/rov-argus
So it was certainly possible to do this with a tether, but it would have been much more expensive.
Until we get all the way to nanobots I suspect the AI overlords will keep us around as workers.
In general I'm kind of skeptical of the approach these rewrite in rust/go projects are going. Maybe as wasm plugins for hot paths in existing tools, but it's not clear to me that the full rewrites are where we want to be long term as a community.
Blazor was the pioneer here.
https://github.com/vanjs-org/van/blob/3f98060971a8ff141179ef...
And a very simple system that replaces the dom from scratch each time any data changes:
https://github.com/vanjs-org/van/blob/3f98060971a8ff141179ef...
That's bad for performance (recomputing the style/layout and repainting even for minor changes), bad for accessibility, breaks focus, etc.
It's unlikely the smaller bundle size compared to preact and friends wins anything once you've abandoned all reuse of the rendering engine computations.
The interesting thing there is that the story and dialog was written for a male character and then swapped to a woman for commercial reach reasons. They'd didn't really change the dialog when they did that change though.
Had it Ripley been originally written as a woman I'm not sure her character would have been as empowered and I'm also not sure the movie would be the masterpiece that it is.