Let’s see how long it takes for people to go “Please come back”
Yo whatup
Let’s see how long it takes for people to go “Please come back”
Go around and ask people their thoughts on nuclear. The vast majority of people bought the anti nuclear propaganda and believe it to be extremely dangerous and expensive
How do we stop a President when all the checks and balances are in favor of what he wants?
Your freedom to cough like a toddler ends at my face. Sorry but that’s just how the world works if you can’t understand that go back to pre-school
I mean he was right about some things. Course extremely few people are wrong about those things but every now and then simple arithmetic trips people up
Aww that’s so sad. It’s a shame nobody has the economic wealth and power to absolutely dominate the market if they put a equal amount of money into EVs. I guess we’ll just have to keep spending our money on the military
Surprisingly little. I can only conclude they didn’t work out as well as he’d hoped
And yet I know people who think they are friends with the Discord chat bot Clyde. They are adults, older than me.
So again. Profit is the excess revenue (this time in bold and italicized) that isn’t needed to run the business. Believe it or not stock buy backs aren’t required to run a business. Weird huh?
No. That’s not what that means. Profit by definition is the excess revenue that isn’t required to run the business.
Nah standard libraries are great but C++ has a lot of… cruft. Maybe don’t plonk a lot of Rust in there despite all the positives
Gonna need to start calling it C++++ at this point. So much extra shit in the standard library
Eh? How’s that work. I’m not going to sit here and say there isn’t too many factories in Java but as a concept it’s extremely useful. You hand off a “factory” to something which actually creates the object. This is really useful in for example serialization. How so? You could register factories (mapped to some sort of ID) which get passed the serialized data and return some sort of created object. Now the core serialization code doesn’t know nor care how exactly any particular type gets serialized. Pretty nifty huh?
Some languages have better ways to encapsulate this functionality but that’s what the factory concept is
No python is statically typed. You have type hints, which makes the language tolerable but like their name implies it’s a hint at the type. You can perfectly legally pass in something completely different that doesn’t conform whatsoever.
The primary thing static languages provide is static typing, that being the ability to determine before runtime that all the types are valid. A good example of this is how C++ programs will refuse to compile if you try to invoke a method that doesn’t exist on the type. That’s because it’s statically typed. At compile time you know that the code is wrong. Dynamic languages fundamentally don’t work like that. You cannot know until runtime if the method you called or the field you are trying to touch exists or not. Again type hints help a lot with this but that doesn’t change how the language actually operates.
They specified statically typed languages. Python would be dynamically typed
Yes it’s real
So the big important part of git is that it’s a collection of commits. A branch is just a labeled commit and each commit is a list of what changed from the parent. Rebasing (the most confusing one for people) is when you fiddle with a commit from underneath yourself. Or in even more simple terms editing a parent commit. Rebasing is extremely powerful but most useful for when you notice a bug you wrote a couple commits ago. Fixing such issues via rebase (or !fixup commits you auto squash at the end) keeps your history clean. It’s as though you never wrote the bug. The other thing you do a lot with rebasing is moving your branch up in the history cause somebody updated the remote.
Elon pretended to lean left. He was and never has been left leaning. He’s been the same old guy this entire time it’s just continuing to be more and more difficult to pretend otherwise.
Yup, libraries should usually let the consumer chose what to do with an error, not crash the program without a choice in the matter. The only real exception is performance critical low level code such as the core of a graphics or audio driver. Though in those cases crashing also often isn’t an option, you just power through and hope things aren’t too screwed up.
Like 3 years iirc. Though they started getting quite within a couple months and by a year in few people were defending it already.