schadara

From the second image, it appears he set the cornerRadius too high and the buttons became almonds. If that’s what he was going for, then perhaps it IS skeuomorphic? /s

Porn helps me sleep. Boom. Done.

Also, a motivator because I sleep dreaming of having a nice gf one day :)

Well, then you’ll be a leet neovim ninja, and you can hack text like no other. Don’t be so hard on yourself. :)

Wow, damn awesome post. I’m on my phone and can’t type a lot, but I would write a lot if I could about how your post resonated with me.

I’m productive but I’m fighting inner demons constantly. Your post is a good warning. Try to fix the small things before they become big things, like the “no broken windows policy”

From the link posted above parent: https://dontkillmyapp.com

> Unfortunately, vendors (e.g. Xiaomi, Huawei, OnePlus or even Samsung…) did not seem to catch that ball and they all have their own battery savers, usually very poorly written, saving battery only superficially, with side effects.

I did Ruby since 2011, and tried Elixir in December 2019. I really hated the verbose syntax compared to Ruby, which has a comparatively simple syntax. The next thing I hated in Elixir was the boiler plate for GenServers and having to deal with pids and named processes. However, this weekend, I rewrote about 2k lines of sloppy elixir that I hastily copy pasted, and condensed it down to around 700-800 lines in a few hours with barely any effort. It was easy because it's just functions calling functions. I guess I'm kind of a believer now. Besides that, Phoenix channels are very performant, which makes me think I might switch from Ruby to Phoenix permanently.

Try sticking through it.

You seem pretty certain about their intent. The truth is Apple added battery throttling in iPhone 6 and up not in their older phones even though their older devices were capable of CPU throttling as well. For example, the iPhone 5S would throttle if it got hot enough to protect itself, yet it didn't receive the same throttling feature for the battery.

https://arstechnica.com/gadgets/2013/10/ipad-airs-a7-chip-is...

Yes, this was a feature. This feature was so great that they kept it a secret and were subject to lawsuits and forced to pay millions in fines.

Not sure how neglecting to inform users of throttling is some kind of improvement.

They have an article about hardware microphone disconnects, prolonging battery life, etc. yet they neglected to write an article about hardware throttling.

It's almost as if they had a hardware problem and instead of issuing a recall, they quietly pushed a software fix. No, that can't be it.

It's curious that this problem was introduced in the iPhone 6, but not in their earlier phones, wouldn't you say?

Supposedly, Apple didn't "implement" battery throttling on the iPhone 5S - Apple's discount battery replacement program only applied to the iPhone 6 and up. This suggests that Apple switched to a flawed battery technology in hardware starting in the iPhone 6 that wasn't realized until years later. And, instead of issuing a recall or repair program, they pushed a silent cover up in the software. Whatever the motive, they should have been more open about it.

I had an iPhone 5S that ran ok until I upgraded to iOS 13, IIRC. After that, the frames started skipping and it became frustrating to use.

Apple didn't inform users that battery replacements would make their sluggish phones fast again.

To that end, I agree with you there.

3blue1brown's latest video on YouTube demonstrates that we can also buy time by using a combination of mitigation techniques short of a full lockdown. It's a video of a computer simulation created by a mathematician fwiw, but it shows some of our options, and that brute force may not be required.

Sometimes I want to advocate for a full global lockdown, but I think about the random emergency appendectomy, and other weird edge cases that would be complicated by a lockdown of any magnitude.

Ok, let's say we lockdown for 2-3 months. What do you think will happen again after we open back up?

During walks, I believe the recommended 6-10 feet of separation is not enough. An infected person's perspiration / saliva / phlegm lie on the path, and, within 3 days, any subsequent passerby traversing that path could potentially pick up the virus along the bottom of their shoes. And, upon entering their homes, they will have brought the virus, this creating a whole new branch of infections.

I agree that every life must be saved, but every month is a battle, and there will be a war.

China locked down and won a battle, but you will likely see another outbreak in a few weeks, and if they lockdown again, there will be another outbreak when they open up again. The daily cases chart will look like a dribbling ball.

Notice that US officials are focusing flattening the curve, instead of a strict quarantine to prevent all infections. It's not only because they're worried about the economy or the logistics. It's because a strict quarantine only works if everyone is doing it - I mean EVERYONE in the world. If we do a Nationwide lockdown, we will need to do another one when an asymptomatic visitor/citizen enters/returns to the US.

I see two outcomes: 1) Eventually, most everyone will either be infected or immunized for this pandemic to stop. 2) We do a global lockdown for 5 weeks.

I would understand if you were trying to do a cost benefit analysis between saving lives versus saving the economy but it sounds like you're trying to frame this to focus on semantic differences between closing roads vs closing the economy temporarily. Baq's point is that mortality rates from the covid 19 grow at exponential rate compared to car fatalities which are flat YOY. If you let covid 19 continue to spread, about everyone will be infected, of which 1% will die - young and old - because we will have overwhelmed our healthcare system. This is why the road analogy is flawed.