Yeah, I’ve filled 256GB pretty easily by recording on an action camera all day, maybe for a couple of days. 4TB would be very convenient for a holiday.

Did you pull it before checkout?

Ah, sorry.

Don’t forget rustaceans for rust!

Good to know the name, I’ve seen it invoked a few times.

In fact, I had this recently at work where I questioned a decision only for them to retort with one similar characteristic which a prior suggestion of mine shared. This was also a modal fallacy as they only used that one characteristic to come to a conclusion about both.

You also see it all of the time in politics unfortunately, a lot of “yeah but you also…” where we should be hearing good justifications.

I’ve used it for the exact same purpose, great minds think alike. It’s perfect for that scenario given there’s no internet.

I just don’t use it much otherwise because apps like Signal are far easier to move my friends and family on to and they’re more than good enough. The metadata privacy Tor would provide would give me a lot of peace of mind but I know it’ll never happen.

deleted by creator

deleted by creator

I think you’re asking if it’s possible for your government to be a man-in-the-middle? Depending on which government you live under, the answer is likely no but more importantly the answer will always be; it’s not worth their effort to find out what you’re watching.

YouTube’s public key is signed by a certificate authority whose public key (root) is likely installed on your device from the factory. When you connect to YouTube, they send you a certificate chain which your browser will verify against that known root. In effect, it’s information both you and YouTube already share and can’t be tampered with over the wire.

Technically, those signatures can be forged by a well resourced adversary (i.e. a government) with access to the certificate authority through subversion, coercion, etc. At the same time, it’s probably easier to subvert or coerce you or YouTube to reveal what you watch.

DMCA takedown from Meta incoming

To be honest, I agree they should be able to be larger at times.

I had a lot of disagreements when I was on a new codebase, knew what I was doing and I was able to push a lot of code out each day.

The idea is to have them small, easily readable with a tight feedback loop. I argued that bootstrapping a project will have a lot of new code at once to lay the foundations and my communication with the team was enough feedback. If I split it up, each PR would have been an incomplete idea and would have garnered a bunch of unnecessary questions.

That said, I think it’s generally pretty easy to put out multiple PRs in a day, keeping them small and specific. As you say, half of the job is reading code and it’s nicer to give my coworkers a set of PRs broken down into bite sized pieces.

I’d be pulled up at my job for any PR exceeding a few hundred lines. I don’t even know what they’d do if I just dropped a 15000 line stinker.

Just wanted to add a bit about Proton since you mentioned it and I use it quite heavily.

Pros:

• All-in-one platform for storage, mail, VPN, password manager and calendar. Usually works out cheaper than multiple providers.
• E-mail aliases built-in to the password manager makes it a breeze to manage. (Tutanota also supports aliases.)
• Personally, I think the UI is more polished. Not important for privacy but it’s a plus for the non tech-savvy.

Cons:

• All-in-one platform. I’m acutely aware that I’m going to have a headache if Proton is enshittified.
• If you’re not looking for all of the products they offer, it’s just expensive. Tutanota is cheaper for e-mail alone.
• The Drive app needs improvement. Migrating my files was painful and I want automatic Camera uploads. You might be okay with the Windows desktop app.
• The Calendar app has issues when not connected to the internet.
• The password manager doesn’t have a desktop application and managing it through the browser extension or app isn’t great.
• No subject-line encryption support (and other PGP interoperability issues on the free version) but… unfortunately, I don’t get many PGP encrypted e-mails anyway.

Otherwise these two are largely like-for-like for e-mail. There’s no benefit to Proton being hosted in Switzerland and I didn’t move to be warrant-proof or anything silly. The idea is really just moving emails away from an advertising company and paying for a quality service.

Yeah, this is one of those things which sounds great on paper but also introduces problems. I’ve seen people get really annoyed when exception messages are translated because it makes them harder to search for online. That would need to be solved too.

I’ve had huge issues collaborating on a spreadsheet with a Spanish client. It tries to open the sheet in your locale and then can’t find the functions. Insane that Microsoft didn’t even add some metadata to allow me to work on it in Spanish.

Bottom left is when I make a kubernetes cluster to serve up a mock weather API for practice.

Exactly. I used PHP for years, I haven’t “not used it.” It was the first programming language I seriously learned. Writing good code was tedious if not impossible and that became even more obvious as I expanded to C#, Java, Python and C++; none of which tolerated any of the bad and unconventional practices I’d inevitably picked up. Keep in mind, I was actively trying to avoid bad practices and pay close attention to types but still got kicked to the curb hard when I tried other languages. I haven’t had that since.

I appreciate it’s changed since, I’m happy to see it’s not the same dumpster fire it once was, I also don’t care. I don’t actively trash it, I just think there’s usually a better option.

Ruby on rails is alive, just not as popular. ASP.NET is popular but looks nothing like it did then; probably for the best.

Yeah, plus PHP was very popular circa 2011-2016 and laravel was loved by many around that time and beyond. It’s always been a useful language.

Yep, it’s usually an existing idea with progression in a few areas. You could definitely achieve serverless with a cluster of servers hosting the same scripts in cgi-bin and I think that context helps to put it into perspective.

I think it’s a maturity thing. You eventually see so many trends come and go, peaks and troughs of hype cycles and some developers (probably including yourself at least once!) overusing certain new tech.

You eventually discover what works with current tech and then you can become healthily critical of anything new. You see it more for where it can fit and where it can’t.

If you have something small and stateless then serverless is easy and, more importantly, scalable. It was a little easier to see its role once the hype fog had lifted and I had a problem to solve with it.