A couple of companies I have worked for are Windows 100%. Everything is very much locked down (can't even run an executable that somebody has not approved).

WSL gives me back a little usability and productivity. I can install linux and start coding (in whatever language), performing data analysis and generally using computers the way they should be used.

Some fuckwit computer 'experts', who only know Windows, just don't understand people being productive.

Are these people smart enough to use an anagram?

To be fair, it wasn't just the US. All countries experienced shortages. Each country producing their own goods doesn't really make a lot of sense, as well as being horrible for the environment.

It needs a different solution. One that is resilient to extreme events. Perhaps robotics can play a role here, but it is still too early for that. The orange man isn't helping here at all so I doubt the solution will come from the US. Even if it is a good solution, global trust in the US is gone now.

BTW Don't ask me what that solution is. I don't know. But it is global, not isolationist.

Ok, now imagine what nonsense is finding its way into code bases by people who swear by the AI assistants.

The top answer in a google search, even prior to the recently worse returns, is not always the correct way to do something. It is good, and it looks like a good answer, but given the circumstances, not hard for there to be a more appropriate answer.

Or am I just an old fuddy duddy?

Somebody does't write computationally heavy code.

I'm on the fence. I used to use tabs on the left but now use spaces. I'll adopt whatever standard the existing code uses.

I doubt it would work the first time. For just as you describe.

However, the new group of 80% of the population will get to see what happens when the person/team they voted for trashes the office, lies to them, treats them as garbage, etc. The new voters can no longer sit on the fence, as they have always done so, and bitch and complain about politicians and politics. Because now, it is their fault. They voted for them.

So next time, more of them will pay attention to the details that affect them. Hopefully, eventually, they start to think beyond themselves.

Infinite Window manager 'eh? You should have a look at Eagle View.

Works exactly as it does in the video. I think it needs a little 'lock-to' as it can be a little sensitive (that could be my mouse though).

I've been using OpenShot heavily lately. I like it.

It has some bugs but it gets the job done. Surprisingly well. The other big thing going for it is that it is incredibly simple to use.

I started to use Blender but I had to abandon it. It was going to require a significant investment of time to be able to do similar stuff. I just don't have the time at the moment.

It kinda is.

I attribute my total nerdiness to being raised "free range". I was mixing farm chemicals, putting together mechanical graders for fruit classification, architect and building water piping to get water from A to B (trenches go deep when dug by hand), etc. Parents were not around for large periods on time.

Mind you, this was a thousand kilometres from the nearest capital city in Australia. Right out in the bush. Shit was pretty wild there.

I'm a mathematician now. Well, with a good helping of computer science. Did ten years of supercomputing before starting my own tech company.

Yeah, lock those parents up for neglect.

No. It is a big fucking problem of Amazon that IAM S3 keys can be used outside S3. A BIG FUCKING problem! A major security incident.

They, Amazon, need to sort their shit out. If I have IAM keys that are S3 read only on a certain bucket, then I EXPECT that it is read only on that bucket. If somebody has those keys, then all I want them to do is to read from that bucket. Not start EC2 instances, or change my Route53 records, or anything else.

This is Amazon's fault. No two way about it.

If somebody got the keys via github, then all they should have been able to do was what they were permitted to by those keys. PERIOD!

Exploited routers, pry the handshake where you know keys are being exchanged, collection and brute force. An organisation with the budget, people, knowledge and will can make magic happen.

Article even talks about placing stooges in security and standards groups to subterfuge weaker methods (by weaker, i mean in the first three of the NSA's five level rating).

Article talks about VPN being no problem ... surveil 20,000 vpn connections per hour in 2011.

Hi,

    I'm Australian. So as far as you possibly can get from technology and innovation.

    I can understand the need for a specific language from a technology giant. When you build the hardware platform as complex as these guys probably have, with the type, and volume (in space and time), of data they have from customers hitting various services, it makes sense to have an internal language that understands how the data is stored and when wanting to run queries you want them to be run in an efficient manner. And I'm not talking about efficient as in fast. I'm also talking about the thousands of other people who also want to run queries. I'd want a language that natively understands queuing, scheduling and load balancing so not to disrupt the normal operations. If you don't, you can bring hardware to its knees very quickly.

    I get it. I'd do the same thing. The wrong type of generic programming could potentially be very bad for a company whose job it is to deliver consistent service.

Could also be because this Remembrance Day marks 100 years of the start of World War I.

But sure, two soldiers killed is also significant.

Forgot to mention.

Anzac day is a big deal as well as Remembrance Day. But that is more that we acknowledge how our commonwealth masters dictated us to our mass slaughter on a foreign soil whom we didn't have a particular argument with. My great grandfather got a VC there but plenty other relatives died. We're all still in awe, anger and sad about it.

For what it is worth, I'm still for the Monarchy. Mainly because I don't trust an Australian in the position.