pedrocr

Canada isn't small, it produces almost 10x the electrical energy that Minnesota does. But I wasn't even giving it as an example of total capacity just of a neighbor that has a bunch of hydro that can be useful in some moments. And it works both ways too. When Minnesota has excess wind Canada can benefit. The same exercise needs to be modelled with all demand and capacity within viable transmission range. And with the advancements in HVDC that range keeps increasing.

Why would you model Minnesota specifically when that state is part of a larger region that can tradeoff power over time? Canada's hydro is much more "here" than the hypothetical new nuclear plants Minnesota would have to build.

Splitting up the world in areas and then claiming you need to solve a different problem in each is throwing away probably the most cost effective way to get cheaper energy, more grid interconnection and more price mechanisms to shape supply and demand.

"The best LLMs of the last 6 months spend their time fixing people's grammar"

Doesn't have quite the same ring as a lament

I learned of these in-band commands at Stanford and created a very short print file to be able to change the status message of any printer on campus. I couldn't push it centrally but I just queued the file into the global print queue and was able to change any printer by walking to it and asking for my print. To not be too disruptive and given the character limits I only ever put in something like "READY FOR CAL" in reference to the Bay area school rivalry. I don't think anyone was ever annoyed by it, or maybe even noticed it beyond the few people I showed it to, but hopefully the statute of limitations has also passed.

You elided the most famous quote from that diatribe. The lawnmower comparison is the expansion on:

"Do not fall into the trap of anthropomorphizing Larry Ellison"

The web is the only platform where people routinely chide other people for wanting to use their favorite programming languages. For some reason not liking Javascript and wanting to use something else is offensive to a lot of people. In all the other platforms some language may dominate but others are still used and don't cause these reactions.

This is a case of both in-band error codes and overloaded meanings of inputs colliding. Modern languages make both things much better but even in C the kill(2) interface seems much too clever. It seems it could have easily been a couple of different functions.

I get a week of battery time out of my Fitbit Charge 5 with really good sleep tracking as well as reasonable tracking of exercise including swimming and GPS tracked runs. The screen is really nice but not always on e-paper and I can't really program it, so I guess there's some space to improve but was the pebble really that much better?

That's weird. The fitbit bands that Google still sells do have that. They seem to be having a really hard time making the fitbit acquisition work in many ways so I guess that's not surprising.

This is not the passenger vehicle. That's the second stage, this is the first stage booster. They've also landed the second stage but that did a water landing from orbit which in many ways is even more impressive.

From a quick search:

"Please be aware that if your spoken words include personal or other sensitive information, that information will be among the data captured and transmitted to a third party through your use of Voice Recognition," Samsung posted in its SmartTV privacy policy.

https://money.cnn.com/2015/02/09/technology/security/samsung...

There's nothing to hide, it's part of the way the TVs work and explicitly stated by the manufacturers.

They died only 6 years before Dropbox was founded and had a plan to have cloud storage and an app store. It seems possible they could have executed well on those fronts and have nautilus "just" be a high-end frontend to the services. It probably required a very different mix of engineering focus though.

The Teams web app works very well in Chrome. I only miss being able to set a custom background to my video and popping out presentations into their own window. It seems much lighter on resources too, maybe because Chrome does more of the video encoding or decoding using hardware.

My understanding is that pipewire finally unifies JACK and Pulseaudio. You no longer have to decide if you want a general audio setup or a low-latency one, there's a single audio server now that does everything well.

So from that list the unification is now:

- JACK and Pulseaudio are both replaced by pipewire

- OSS is long gone, ALSA is now the only low-level interface

- ESD, NAS, ClanLib, xine, portaudio, allegro and Phonon are not present in the Ubuntu install I just checked

Basically we're down to a unified stack that has BlueZ and ALSA to access actual hardware and pipewire as the single audio (and video) daemon. Everything else is either shims so apps don't need to change interface or cross platform APIs like SDL and OpenAL. We are much better than what this diagram shows.

That's about maximum mess historically but thankfully most stuff on that diagram is no longer present in a modern install. And that's before pipewire which has further unified the stack.

Mb is unambiguously megabits but it's a lost battle at this point. This thread includes so far MiB, MB, Mb, mb all to mean megabyte.

It's often easy to find what's meant from context but sometimes we're discussing network stuff and it becomes hard to figure out what people mean by "gb" or "mb" or other frankenunits because the context refers both to data in transit and at rest. It's almost certainly not gram bit and milli bit which helps narrow it down...

> The current landscape bears a striking resemblance to the early days of cloud computing. Fifteen years ago, it was commonplace for individuals and businesses to pay less than $10 a month for shared hosting or a VPS. This pricing model seemed set in stone, with costs expected to continue declining.

A Digital Ocean VPS starts at $4 a month. It's not so much that we've lost the cheap part of the cloud, it's that the big cloud providers figured out how to do enterprise sales and capture the part of the market that was already overpriced and wasn't sophisticated enough to optimize itself.

There's a known buffering issue with YouTube on Firefox. Apparently it's been fixed and will ship in the next point release:

https://bugzilla.mozilla.org/show_bug.cgi?id=1878510#c114

https://www.reddit.com/r/firefox/comments/1djkdql/for_people...

According to the reddit comments it's a broken implementation by Google that doesn't trip up Chrome.

I mentioned that. There were others but nothing at the scale of what VW did.

This is commonly believed and seems to massively let VW off the hook. Almost everyone was overfitting their optimization to the test and thus not delivering real world lower emissions. That's not illegal, just unethical, particularly since they also lobbied to not make the test more realistic. But VW actually detected it was in the test loop and changed the settings. That's a defeat device and completely illegal. There were a few much smaller cases of similar things found in other manufacturers but nothing even close to the scale VW did it.

> You need very tiny wires through very tiny holes in locations very precisely aligned on both sides. Aligning things on the scale of nanometers is very, very hard.

Do you need to align that precisely? Can't the power side have very large landing pads for the wires from the signal side to make it much easier?

Wayland has gotten it right in the latest protocols but up to very recently it still did only integer scaling and scaled down for fractional. Scaling the buffer in fake coordinates is also needlessly complex. Just start with the 150x90 buffer to begin with and the scaling is just a UI hint. All of that would work fine with X11 exactly because there's no need for fake coordinates. All scaling is the client's job based on a DPI or scale hint.

> But nowadays we have this thing called HiDPI, where 1 pixel can mean 1.5 real pixels on one screen (150% scaling), 2 real pixels on the second (200% scaling), and 1 real pixel on the third (100% scaling).

This is the wrong way to do scaling and even Wayland got it wrong and has been very slowly fixing things. What you actually want to do is just use real pixels everywhere and just tell the client "here's your NxM window size and it will be displayed in a X scale" and let the client do the intelligent thing. If it's a browser, a 3D game, or a PDF reader it will render directly at target resolution and scale with no fuzziness and those are most use cases people care about. GUI toolkits were stuck at integer scaling for a long time and thus the strange solutions to render at higher resolution and then scale down happened. All of this can work in X11, just always use native resolution for everything but Wayland is much better anyway and works great these days.

I still don't get why after all this investment in AI Spotify can't just give me a seamless never ending stream of music. I need to keep selecting from playlists they generate which often repeat some songs extremely often. All I want from a Spotify interface is play/pause/skip/like/dislike. Then use those to continuously adapt the selection of the next song. If you want to be fancy add a warmup mode where you ask me some questions or show me some songs to like/dislike for that particular moment so that the initial selections start warmer. If I had that I could explore a lot more music. Because I don't I end up just listening to the greatest hits of things I remember and then that further pollutes the dataset to the point where my musical tastes must stagnate.

Sometimes these videos have worse audio than what was actually heard by the pilots and ATC because they're recorded from somewhere else with worse reception. But it's not only that.

It's amazing how much we've stretched this way of communicating into a very safe industry by the numbers. Maybe the remaining failure modes are now showing up. There's an almost accident where the plane reached only a few feet of altitude on approach to Paris well before the airport because the controller gave bad information and the read backs were not enough of a check. There's another almost accident where the controller didn't receive the communication that a plane had aborted takeoff because another plane talked on the same frequency at the same time. Maybe there is now value in having a more standardized digital messaging setup for key moments that augments the normal audio conversation. There is so much that is tipified that it seems that could actually reduce the workload if done with good UX.

Since in AM5 all CPUs have a basic iGPU, for a home server all the normal CPUs already work fine. The advantage of the APUs is they're on a monolithic die so should have quite a bit lower idle power usage which is important if you have a NAS or other homelab server running 24/7.

They've measured that too. Here's the video:

https://www.youtube.com/watch?v=tuJlgzcQWAg

It's an hour long and very informative. The research seems well backed up.

It can be done with push in cages to trap the queen inside the hive. Because there's still a queen they won't start new cells. Because she's limited to a very small area the brood break is almost complete. I think a two week break is enough. The national honey show had a great video explaining this method. Apparently commercial beekeepers are going that route now that varroa treatments are becoming less effective.

There are some options, particularly if you want just DisplayPort. If you want to have power as well for example pretty much all the cheap adapters are HDMI only. With HDMI there are many more options and of more reputable brands usually.

On a somewhat related note, it's very surprising how hard it is to get DisplayPort out of a USB-C connection. Although DP is natively there all the cheap adapters tend to be HDMI even though that requires extra hardware to create the complex HDMI signalling out of the DP native output. So although monitors tend to have DP inputs and now everything has DP outputs in the form of USB-C it's actually hard to connect the two.