Oh, I didn't realise (I don't use it). Thanks for the info.
dan
Ideally use a VPN with port forwarding (like AirVPN ~~or Mullvad~~) so you can properly seed :)
then complain about them later.
I don't see where they're complaining? They don't seem to be asking anything of the C devs other than help with API definitions.
Sounds like the equivalent of Alt+SysRq+B.
In this case, the issue is really the C kernel devs, not the Rust devs. Some are not open to new ideas at all. Take a look at the conference video he linked to for example: https://youtu.be/WiPp9YEBV0Q?t=1529. He clearly states that he's not trying to make the C devs learn Rust.
I took down the home page of one of the top 5 websites for around 5 minutes.
There were two existing functions that were written by a different team: An encode
method that took a name of something (only used internally, never shown to the user) and returned a numeric identifier for it, and a decode
method that did the opposite.
Some existing code already used encode
, but I had to use decode
in my new code. Added the code, rolled it out to 80% of employees, and it seemed to work fine. Next day, I rolled it out to 5% public and it still seemed okay.
Once I rolled it out to everyone, it all broke.
Turns out that while the encode
function used a static map built at build-time (and was thus just an O(1) lookup at runtime), decode
connected to a database that was only ever designed for internal use. The DB only had ten replicas, which was nowhere near enough to handle hundreds of thousands of concurrent users.
Luckily, it's commonplace to use feature flags changes, which is how I could roll it out just to employees initially. The devops team were able to find stack traces of the error from the prod logs, find my code, find the commit that added it, find the name of the killswitch, and disable my code, before I even noticed that there was a problem. No code rollback needed.
That was probably 7 years ago now. Thankfully I haven't made any mistakes as large as that one again!
Always use feature flags for major changes, especially if they're risky!
This has been the case for a long time, unfortunately. Australia is even worse than Las Vegas in terms of gambling losses. 20% of the world's slot machines are in Australia (and they're widespread in a lot of venues, not just casinos), a huge percentage of Aussies say they're regular gamblers, and per-capita gambling losses in Australia are far higher than any other country.
I still don't think that I've ever seen a 4k image or video
Have you not watched a recent movie? Modern midrange to high-end TVs have been 4K for a while (eg my 2019 LG OLED is 4K) and it's pretty common for movies to be released on 4K Blu-ray.
Good 4K looks great. Not the low-bitrate streams from services like Netflix, but the 60Mbps+ streams from Blu-ray remuxes (for example, via Real Debrid or downloaded via usenet) or from Blu-ray disks themselves.
You've definitely seen a 4K image. It's equivalent to 8.3 megapixels, and good cameras have supported at least that resolution for a long time. Even the nearly 15-year-old Samsung Galaxy S2 had an 8MP camera.
It's using the YouTube API, so that makes sense. The developer likely wants to keep the app focused and reduce the amount of feature creep, hence reusing YouTube's standard subscription and list systems rather than building their own. That's also what the majority of users expect - if someone subscribes to a YouTube channel on one device, they'd expect to be subscribed to it on all devices.
On KDE, there's also Kate. They used to be totally different apps, but these days, KWrite is a simplified version of Kate. They both use the same text editor component, but Kate adds more IDE-like features.
Using X forwarding would require you to install big chunks of GNOME or KDE on the server. A better approach is to mount the remote server over SFTP then use KWrite, gedit, whatever, directly on your desktop.
And make sure it's a VPN that supports port forwarding. Sharing is caring.
or just use Usenet.