It's a private members bill, so hopefully it won't see the light of day. With that being said, it may be a harbinger of things to come. To have a member of a G7 parliament, of a party that sits at 20% in the polls, and holds the swing vote/power in a minority Government is mind boggling.

From the article:

"It means it would be illegal for an oil or gas company or employees thereof to say that natural gas emissions are 40 per cent lower than coal and 20 per cent lower than oil (a scientific fact) and therefore we should exploit more natural gas resources.

It means that noting the enormous opportunity for economic prosperity that oil and gas offers multiple First Nations communities would be criminalized, even if it were a First Nation itself making the argument.

It means stating the fact — I emphasize not opinion, but verifiable fact — that oil and gas contribute billions of dollars to our economy and therefore are a vitally important economic engine that should be exploited could land someone in jail."

This particular customer pays entirely too much money for the software. Product insists the bug has to be fixed. Developer spends a week tearing out his hair trying to diagnose the issue.

Testing software be like:

#m=image%2Fjpeg&dim=1080x863&blurhash=%238RfkB00%7EqM%7B-%3BkCxu%25Mt7M%7Bt7t7RjWBf7t7RjWBM%7BWBWBfQxuWBWBj%5Bay%25MxuofRjj%5BofWBayWB%7EXWBIU%25MM%7BWBofRjofIUoft7WBj%5BWBt7WBj%5Bt7WURjj%5BoffQWBj%5Bt7&x=02029640f701bd032bf1be1777244ba08225610cc9f8f38b51e0b97fb57ebef3

same here, Damus is least buggy it seems

Which client are you using most often and how are you liking it? Any gripes?

#asknostr

yep, goroutines and channels being first class and the functions as values are the three features that make me addicted to go, it's a whole different way of thinking

almost no other languages have coroutines at all and none have it as a low level syntax, maybe you could do it with operator overloading in C++ but that shit is messed up

unfortunately the GC and CSP kinda go hand in hand but in actual fact you can turn off the GC and you can write code to manage memory manually, in fact many network handlers in Go are written with allocate-once freelists, and you can actually do this for a whole application

as it is, i personally avoid using the compact declaration asignment operator for things, as many people use them inside if and for blocks without thinking about whether it makes sense to allocate yet another value on the stack when there already is one with the same name, and scope shadowing can hide some bad bugs

I’ve read his opinion, and I don’t necessarily agree with it 100%. All powerful tools are the most dangerous and require careful design and approach. 🐶🐾🫡

haha, don't get me started on that silly memory copy insanity of the pure function

it's at the centre of the debate between GC, malloc and insane shit like Rust borrow checker but i think that, as Go and Java both use GCs and both are within spitting distance of C/C++ performance that the problems of GC only exist in people's imaginations and for purposes like operating system kernels and embedded systems with no memory

Well, I guess we can leave with one deficiency. Dependency free programming is the way! 🐶🐾🤣💜

🐶🐾🤣🤣🤣

C is the way! If I am a sole dev, I love C. When it’s a team, C++ is my choice 🐶🐾🫡

🐶🐾🤣🤣🤣 don’t listen to the abstract devs

We're all winning. Except Craig.

Golang is just an abstraction on top of real languages 🐶🐾🤣🫂💪🏻