but which support the actual third-level domains? for example, my last name is already taken as a .name domain by verisign, what if i want my firstname.lastname.name domain?
One can't (officially) register such 3rd level domains anywhere anymore.
It's just a combination in the ambiguity of what "it discards the dot" should mean in GGP's message combined with the article already clarifying 3rd level domains are not available on .name anymore leading to a lot of confused comments.
i'm confused, why would a system simply checking its own power state be taking so much electricity as to show up on grid measurements? unless they mean that the systems are choosing to start charging the batteries, but then it's a continuous load and not a spike at the start of the minute, right?
The Frequency is actually increasing at every event which means grid load is reduced for a short while every minute. Those UPS installations basically briefly switch to Battery every Minute to test Capacity/internal resistance and so on. This so called "load dump" is visible in grid frequency since a lot of these systems work synchronous thanks to NTP
It can be that part of battery is disconnected, to estimate cells voltage. You can not measure voltage while another source is chsrging battery. Or capacitors are charging.
I think you can. RC toys do that all the time. Maybe the measurement is less precise, but you usually don't need super precise voltage, especially if you know your capacitance and measure current.
Current doesn't tell you if the battery is leaking charge, or otherwise failing to store it though. Vastly increased losses could be a sign of failure, for example. In any case it's important to be sure.
If they are checking the charging at exactly the minute, then start of charge will happen then too, which will create a spike if it's synchronized with many others doing the same thing.
hmm, I'm not seeing anything that can be described as "inertia". Not on chromium either. Both of these are on a laptop with dragging the side scrollbars and using the up/down arrows on the keyboard.
Is this something that is related to a touch screen? I'm not using a touch screen.
I'm on a non-touchscreen mac, on firefox with smooth scrolling turned off, and have LinearMouse installed. I tried both trackpad scrolling and mousewheel scrolling. The weird "smooth" scrolling of this website is very jarring to me, and makes it take significantly longer to scroll to where I want to, since the responsiveness went from ~instant to ~.5s and I keep on overshooting.
try using a mouse or trackpad, they only seem to intercept pointer input. i also don't get affected when dragging the scrollbar or using the arrow keys.
shoving all of these vastly different applications into one monorepo does not bode well for them being seriously designed, maintained, and cared-about pieces of software. such is the nature of LLM development, i suppose.
not to mention that there are only three contributors and #2 is claude, although that might be because they just committed a bunch of previously-untracked code at once, i don't care to check.
I feel like you're being snarky but, regardless, I'm curious to hear your reasoning for the first paragraph. being a monorepo helps us share code across 50 different apps without falling into a submodule/dependency hell.
What's shared between the "Property Management" and "Photo Studio"?
The UI frameworks already exist, there's 0 reason to share more things between them. That is, unless it has a slopped revolutionary(tm) UI framework #1000.
I might be missing something but inspecting a few of them the testing seems quite thin. I won’t do anything now without layers of controls for agent coding. Just for testing — near 100s for v8 coverage, property, mutation, fuzz, chaos, contract, bdd e2e, api and playwright exploratory mcp. Long term maintenance of all of this is going to need a ci/cd that puts all that through a ringer around the clock.
there are other ways to share code than a monorepo, namely independently versioned packages. you say dependency hell but if you're in control of everything you're in the best position to avoid that if you put thought into it. with a monorepo you could actually get worse results in some cases. say i change something in a graphics api for sudoku and suddenly the zoom clone doesn't work. yuck. i only buy the monorepo argument for systems of code that actually need to be deployed in sync, like server/client stuff or larger. iirc google has a massive monorepo for nearly all of their production code because basically all of it works together (server/client stuff, auth, etc)
also a monorepo like this is worse for human interaction, if you care. what if someone only wants to pull and work on sudoku? now they have to get everything else. issues and pull requests are also more annoying to varying degrees depending on use.
That argument goes the other way though? The only reason TV manufacturers would leave frame interpolation on by default is that a decent chunk of people notice, those people care, and most of the people who notice are "normal people" who aren't repulsed by it.
If only "pro consumers" noticed or cared... well, those "pro consumers" are the ones who think it looks like shit and would rather have a TV without it.
nit: 5.1MP/s to 11.2MP/s is not an increase of 220%, it's an increase of 120%. it's 2.2x faster, but percentage increase starts at 0%, not 100%. 100% faster is double, 200% faster is triple.
reply