Ok but if you’re at a bus stop, and the bus is just coming round the corner into sight, you can say “this bus” even though it’s not parked up yet.
Same thing with this Friday. If it’s close enough to be in mind, you can use this.
Yes, it makes it much worse. It is absolutely a serious plan and you should worry about it.
https://www.influencewatch.org/non-profit/heritage-foundation/
They’ve created substantial policy for Regan, Clinton, and Trump. You should also pay attention to the shear amount of money they have. They spend 80 million plus in a year on lobbying.
He’s the president of the fucking Heritage Foundation. That makes him the head of one of the most influential political organisations in the country.
That’s much more important than what his PhD was on.
It’s very true on a Mac. Almost every time you click the green button, it jumps to full screen and then you can’t drag another window on top of it.
It’s a pain in the arse because my workflow is to have a reading screen with documents and emails on, and a work screen with whatever I’m actually doing. But if outlook is full screen, you can’t drag any other windows on top of it.
Don’t know why the first guy was saying this is a Windows thing though. I only run onto it on macs.
It would just encourage people to create sock puppet moderators.
Same problems as without those rules, just harder to spot.
Well this is it. What really enforces the policy is rejecting commits that break user space.
Now if you’ve got a large enough group of devs, rejecting commits is fine, but if you’ve only got a small group you need everyone to be working productively, and you can see why Linus ended up giving angry feedback about commits that were wasting everyone’s time.
It’s half this, and half an explicit policy “we do not break user space”. Together it meant that if you did anything that screwed up the user space you got told about it at length.
Now Linux culture is established enough that it only really needs the policy, and not the cussing people out to enforce it.
Famous email about it here: https://linuxreviews.org/WE_DO_NOT_BREAK_USERSPACE
Lots of the cheap Chinese watches Xiaomi, amazfit etc do a rectangular face. Rectangular lets you use standard screens and is cheaper and easier to get.
Same. I would take it now, so I could go back to being 20, but this time I would not fuck up all my joints because I know I’m not actually invulnerable.
Dev jobs and data scientists often get a lot of leeway.
Very big tech companies tend to be more open to it. When I was at AWS their threat model was basically to treat every end user device as untrusted, which then meant that they didn’t rely on keeping laptops locked down for security.
Eternity is fine. You just need to log out and back in. I’m using it now.
Details here: https://codeberg.org/Bazsalanszky/Eternity/releases/tag/v0.1.2
Yeah, I think the reason threads is attaching itself to the fediverse is precisely because meta don’t see it as a threat.
It’s an easy way to appear open to the regulators without actually helping any competitors.
Characteristic sleep-EEG changes in patients with depression include disinhibition of rapid eye movement (REM) sleep, changes of sleep continuity, and impaired non-REM sleep.
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6386825/
Yeah, I think we have multiple types of sleep because we need them, and if you’re getting too much rem sleep at the expense of other types it’s going to cause problems.
I was listening to a sleep scientist the other day and they were saying that one thing we know is that depressed people have more rem sleep on average, and SSRIs decrease the amount of rem sleep.
If it is something sleep based that goes some way to explaining why it takes time to have an effect. Building up or wiping out a sleep debt can’t happen instantaneously.
It’s difficult. Perjury requires intent. If a badly trained employee in a hurry makes a mistake that’s not perjury.
This means it’s legal, under the current law, to badly train your employees and to set them quotas for the amount of DMCA takedowns they have to serve.
They’re not intentionally making false statements.
To stop this, you need to create new explicit penalties for bad takedown requests.
Yeah I thought you’d ask this. Basically they’ll never do this, just because their attitude is “fuck you I’m a bank”.
Beyond this, there’s a big difference between source code and having a working system.
For very long running systems their state depends very heavily on how they were maintained, little bits of informal design decisions that get components working together, and the order stuff was loaded in, and what other services were up and running when you booted up.
None of this magic is captured by source code, and it can make even setting up a replacement server, even as part of the same infrastructure really hard.
Of course banks are moving to more modern dev methods that encourages turnkey deployment, but the fact that they still rely on a bunch of COBOL code tells you there’s a lot of very old system running in “do not touch” mode
It wouldn’t matter much.
Most of what a bank does isn’t on your phone, but server side.
In fact most bank apps could be replaced with an internal web browser that is pointing at their website, and a password manager, with no loss in functionality or change in security.
And if you’d like to review the client side code the bank is using you can just open dev mode in your browser, right now.
It’s super hard to get involved as a UI person. If you’re a developer, you can just rock up to a project and fix bugs, and if you follow the coding style they’ll probably get accepted.
If you want to successfully contribute as a UI person you have to convince a bunch of developers that you know what they should be doing better than they do. It basically never happens.