A really nice example. I tracked the data acquisition and fit an ordinary charging curve. For anyone interested, a 25 line script w/ data is here: https://pastebin.com/R0b1XSV0
Some insights:
- The peak DC voltage seems to be around 1.15 kV.
- The time constant is around 440 s. If you were to assume a simple RC-circuit with a constant voltage source (which it probably isnt), you would end at around 100 Ohm for the resistor.
- The start of the charging curve is not at the same time as in the video indicating that some voltage was already present from experiments before the video
Also, I am pretty sure it is not inductive coupling but capacitive because of several reasons:
- It doesn't look like a coax cable but more like an ordinary thick wire.
- I am pretty sure he didn't ground the cable at the far end and thus did not create a loop necessary for induction. And if he were, inductive coupling with ground in between would result in a very large voltage drop
- If it were inductive: A single loop covering that little area would need way more turns than just one.
I believe you that the efficiency argument played a role when they decided to reduce the life expectancy of the light bulbs. The cartel doing 'cartel-things' aside, the 1000h-limit probably was a good decision even though I think that they ultimately did not do it for the consumer.
Hah, this isn't surprising: An internal leaked Google document (https://news.ycombinator.com/item?id=35813322) a couple days ago pretty much pushed the idea. Still interesting to see the action follow so short afterwards.
Three quotes from the document:
- "Owning the Ecosystem: Letting Open Source Work for Us"
- "Google should establish itself a leader in the open source community, taking the lead by cooperating with, rather than ignoring, the broader conversation."
- "Open source alternatives can and will eventually eclipse them [OpenAI] unless they change their stance. In this respect, at least, we can make the first move."
EDIT: Misread "open to use" as "open source" and figured it was behind a signup. Sorry, my fault + maybe wishful thinking.
Whenever I see that C++ added some language extension, I can't help but think about Bjarne Stroustrup's "Remember the Vasa" Paper [1] and wonder if he had meant this type of complexity he warned against...
> Boot chain is typically Firmware → shim → grub ...
Is this really true? Or just when using Red Hat systems? I don't know too much about the boot chain, but I always thought that after the ROM stage, usually GRUB would take over directly from the UEFI.
Yeah, could be. But still that does not support the argument of "feed the data to western governments".
When you say: "Look, the people from village A north are stealing apples from the city orchard. Here is a list of apple thieves and the direction (N,E,S,W) from which they came." And this list shows that it appears to be majorly the directions E,S,W (so not directly from village A). Then how is this an argument?
It just shows that everybody steals apples, making the accusation "villagers of A are to blame" superficial. That's the point it tried to make.
> But there are also other reasons your conclusion is wrong I think
I would be interested on why my conclusion is wrong. At best, one could draw nothing from the data as it does not show any relation to state actors. And if this conclusion is drawn, then why did `mike_d` blame the western state actors in the first place?
Think for a second about this: Did you think that the link `mike_d` provided supported the argument "... feed the data to western governments" with the emphasis on 'western'?
I see your point. But then how is the accusation 'west scans internet' connected to 'see this map of countries of origin'? Because I thought he would back up this claim with this source/second paragraph.
If other people (and arguably other govt's) are scanning too, then saying 'west scans internet' seems somewhat superficial. Not that I deny western state actors scanning the internet, its just that everybody does it.
It is ironic that the very link [1] you provided proves you wrong. The top 5 countries of origin doing IP scanning in the last seven days are China (120k), India (67k), US (52), Iran (44k), and Russia (27k).
I think the solely reason why JPEG XL did not go off is simple: It had no lobby. No large tech company actively promotes it and so, many people hadn't heard of it. Ironically, the deprecation of it in chrome made me aware of it in the first place.
Technically, JPEG XL may be a superior contestant. But from a 'social' point of view? Disastrous, especially considering it already has "JPEG" in it. (To be fair, its also quite young...)
I really hope JPEG XL gets more traction because it seems like a really good successor to the old namesake.
Yeah, it's quite a well written paragraph in terms of style. Really good story-telling. And it starts so innocent as well, building up something rather mundane with trivial short and repeating sentences. And then, bang, hints at an explanation of Niemanns behaviour with that of a spoilt brat.
> That leads us to the end of Hans Niemann’s foray into cycling – his dalliance with the sport that is mostly remarkable for how unremarkable it is. And that’s fine. Kids start riding, and kids stop. Kids win races and kids don’t. Kids come up with brash stories on the playground. Sometimes kids are told they’re special at something, and some of them probably internalise it and let the lines between truth and fiction blur.
I disagree: Using docker makes it incredibly easy to tinker without real consequences or hassle. Want to try out - say - Heimdall? Create a docker-compose.yml file, an nginx reverse proxy config, and spin up the container. Don't like it? Remove said files and container. Thought about using a wiki for a project? Same thing.
For me, containers are just abstractions similar to packages, or OOP objects, or even apps. And as long as a service fits into this view, I think docker provides a great way. But, sure, you can overdo it and end up with more complexity than less (e.g. Nginx Proxy Manager).
Reliability. That's what Google traded for a quick and sudden exit. I think the damage is far greater than the rather small number of people in and around Stadia.
I guess there is a message: "When a Google product does not show a reasonable growth after a certain time, it will be killed". There are many examples (See https://killedbygoogle.com/), and I think people will more and more consider this when jumping on a newly launched platform that they will later rely on.
Is this even comparable? I mean, for C you have a three-way comparison and for C++ there is only a two-way comparison.
If you run the code by yourself you end up that C (while calling the compare() less often than C++) needs more comparisons (i.e. more '<' and '==') kinda defeating the argument of costly comparisons:
Such simulations usually consist of three major systems (atmosphere, land, and ocean) that are coupled together at their geometric boundaries by a coupler that 'communicates' values like temperature from one domain to another. The coupler is needed because of different grid geometries, time step size differences and other aspects.
You initialize the system at some known state (I.e. set the temperature, pressure, etc. at all grid points to real world measurements) and then integrate a complex differential equation for the next time step and so forth. So it is not like a automaton. Finite elements analysis comes closer, but I think they use a different scheme like finite volume methods.
Some insights:
- The peak DC voltage seems to be around 1.15 kV.
- The time constant is around 440 s. If you were to assume a simple RC-circuit with a constant voltage source (which it probably isnt), you would end at around 100 Ohm for the resistor.
- The start of the charging curve is not at the same time as in the video indicating that some voltage was already present from experiments before the video
Also, I am pretty sure it is not inductive coupling but capacitive because of several reasons:
- It doesn't look like a coax cable but more like an ordinary thick wire.
- I am pretty sure he didn't ground the cable at the far end and thus did not create a loop necessary for induction. And if he were, inductive coupling with ground in between would result in a very large voltage drop - If it were inductive: A single loop covering that little area would need way more turns than just one.