The article isn't about solving those problems, it's about taking a few days longer to do the actual travel to save a bunch of money, since there's already massive delays on either end.
We recreated this experiment in one of my university physics classes. It was a lot of work, and our results weren't nearly as good, but it was instructive and interesting. The equipment requirements were completely reasonable for an undergrad physics lab. I highly recommend giving it a try if you can.
> Usually not. You can ask your provider for a new number in a different city and they will issue it. Most Canadian providers are country-wide so you don't need to switch provide if you don't want to.
There's a way around this that I've done a few times. You port the number to VOIP (I use voip.ms) and then you set up that number to forward to whatever the new number you get given. Dialing out you still get your new number, but people dialing you can use the old number.
This was super handy when I had to move my mom from a retirement home in one city to another city a province away.
Spine is fantastic for artists, and it's integrations with various engines is really good. My biggest complaint about it is that it's very CPU heavy. A spine runtime that has less features but uses GPU skinning would be excellent, especially if it runs on the web. Ages ago I had to write a JS shim to the C runtime compiled to WASM and it worked well, but I still wish it used a lot more GPU and less CPU.
What if we stopped adding layers of abstraction? The idea of renderer-agnostic shaders is cool, but in general you want to write your shaders for a specific renderer for best performance.
I'm kind of surprised that washing machines don't have that sort of filter already. I recently cleaned out two of the filters in my own washing machine and it did a pretty decent job catching a lot of things. I guess because it's so fine it would have to be cleaned out more?
I'm disappointed that the names aren't released already, but I'm glad that something's being done. Greenwashing is wildly annoying and always takes ages to investigate properly.
I daily drive the Keyboardio Model 100. I like it a lot, but I really would like to remap a few of the special characters. It works fantastically well for just arbitrary documents, but writing C++ is frustrating. The custom shape of all the keycaps makes it basically impossible to remap without just using clear keycaps.
I remember learning an amazing randomized algorithm for max cut. If you pick edges at random 50/50 to be cut, you get a 2-approximation to the optimal solution. That is it's no more than twice as bad.
There's also an IBM-built emulator that has at some point shipped with Eclipse. I used to work on it. The 3270 was fine, just took a bit of getting used to. JCL was the real horror show.
I see that the assembly instructions are different, but what's the performance difference? Personally, I don't care about the number of instructions used, as long as it's faster. With things like store forwarding and register files, a lot of those movs might be treated as noops.
I disagree. It's good to understand what the GPU is doing at scale before jumping in too deep. It's obviously not how you do your day-to-day work, but it helps you understand what's going on at a deeper level.
In Canada, I grew up getting up at 6/7am on Sundays to watch the races. North/South American races were definitely easier to watch, but we just got up early every 2 weeks. It was a ritual.
My OnePlus6T just hit 5 years old and the battery is plenty usable. I just slow charge it at night every night. Is it as good as it was when new? No. Is it still perfectly usable? Absolutely.
A car autonomously drove across the US in 1996. Self-driving cars aren't a new technology. Check out Drive: The Race to Create the Autonomous Car by Alex Davies for some good background.