turndown

I thought that this was a GCC extension(you need to use #define n 10 instead of int n = 10). Is this not the case anymore?

On box mods(the big vapes you might recall starting to see 10-15 years ago) there is a chamber up top you have to manually fill with nicotine. This can be a bit annoying to do but the real problem is remembering to bring liquid to refill with.

That’s really the only negative to the large box mods, other than having to recharge 18650 batteries all the time. But disposables are usually much smaller(easier to hide if you’re in school), use nicotine salts(which are much more potent) and they usually last a long time - sometimes 20k hits. So these aren’t “bad” products, they have a lot of selling points.

This is all well and good, but just because something came from before doesn’t mean it was a good idea then, or especially now. You’re basically citing survivorship bias. Of course something still used from the 80s is well made, otherwise it would have been replaced 30 years ago.

> 1998 - 2009 was a tough time to be a Windows user

Is that true? I was too young to really have an opinion but to me most people cite XP and especially Windows 7(ignoring Vista which was bad) as the height of Windows. Of course outside of Windows, like mobile, it really was bad but if we’re just talking Windows then I can’t help but disagree.

Just because we are natives of this universe does not mean its behavior or characteristics will be naturally sensible to us. There is no “real” reason it should be something “simple” or reasonable to us. The universe simply is; us as well.

I really cannot until this business model FAANG has come up with in the past 20 years where they are somehow owed money by developers for creating services and products for a platform is completely repudiated. I owe you money because a user clicked a link in my app and then bought something? I am so glad I have never written a line of code for an Apple product.

I imagine you got that code snippet(or a similar example) from somewhere but to me the fairly obvious problem is the chafing between the C and C++ world. %s is for C style strings and I have to imagine that printf function is in the C world. The String(“Hello world…”) is an object in C++ world so expect weird behavior when you try to combine them. As you say in your edit, SSO will make this even weirder.

And that’s just for your first recursive descent compiler. One thing to remember is that you will also one day want extended functionality in your language and either implement C FFI in your language(straightforward or even freely done for you depending on language) and call some C library for the purpose or you have to implement the functionality somehow. So you end up writing a lot of stuff you wouldn’t otherwise.

IMO compilers make you a lot more mature in recursive algorithms and trees, and then after that much more conscious about what exactly the code you write resolves to in terms of that languages semantics. Learning how closures work(variable capture and having to traverse the scope stack to find bound variables) is also a positive.

Intel is coming out with an improved x86 instruction set that removes a lot of the cruft, called ‘APX’ for advanced performance extensions.

I’m wrong. Fourth paragraph from the bottom, last sentence they say “normal resource limits.” I thought that meant “the limit of something called normal resources” not the normal amount of the resource’s limit. Probably because I was trying to find out the exact same question as OP and thought that was it when I read it. I wish articles explained names more specifically sometimes…

Programs are tightly coupled to textual representations because a compiler is a textual representation transformer. If you deviate from the accepted textual form then the compiler is generally clueless to do anything - that is, it can’t read your intent.

Is option 3 exactly what you’re supposed to do? Freezing your dependency graph and/or explicitly denoting what version of the dependency you want are your best bets for avoiding problems like this

Seems to be “normal resources”, where normal probably meant file descriptor based.