Amazon Web Services

OH. MY. GOD. Apple just launched their revolutionary "Liquid Glass" effect and developers are absolutely LOSING THEIR MINDS after discovering it's literally just backdrop-filter: blur(2px); — a CSS one-liner that's been around since the STONE AGE of web development! 💀 The AUDACITY to present basic CSS as groundbreaking technology while charging $1999 for devices to run it! I'm SCREAMING! Next they'll announce they've invented the revolutionary concept of... wait for it... MARGINS! *faints dramatically*

Content 1048 M Tweet Meghan Duffy duffyma Two factor authentication but for reply all. 3:50 PM 10 Feb 20 Twitter Web App 2,189 Retweets 11.6K Likes 17

Content Ijust wanted to add to this discussion that I am just compiling on VS and GCC, and used to use include guards. I have now switched to pragma once, and the only reason for me is not 199 performance or portability or standard as I don't really care what is standard as long as VS and GCC support it, and that is that: pragma once reduces possibilities for bugs. It is all too easy to copy and paste a header file to another header file, modify it to suit ones needs, and forget to change the name of the include guard. Once both are included, it takes you a while to track down the error, as the error messages arent necessarily clear. Share Follow edited Nov 30, 2014 at 9:57 answered Jul 22, 2011 at 16:55 Cookie 11.7k 13 52 81 5 This is the correct reason. Forget performance--we should use pragma once because it's less error prone. It occurs to me that if compilers are already tracking include guards, they're already doing most of the work necessary to issue warnings when they see different files using the same macro name. - rieux Jun 13, 2019 at 6:36 Add a comment pragma once has unfixable bugs. It should never be used. 169 If your include search path is sufficiently complicated, the compiler may be unable to tell the difference between two headers with the same basename (e.g. afoo.h and bfoo.h), so a pragma once in one of them will suppress both. It may also be unable to tell that two different relative includes (e.g. include "foo.h" and include "..afoo.h" refer to the same file, so pragma once will fail to suppress a redundant include when it should have. lanc arca attocic tho commorc amia

Content 2 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Machine, Pls make website, all responsive like, w BIG pictures 000, use my fav fonts, also fancy menus with whoosh on, load fast pls Thanks, Human PS no bugs :)

Content The code base in your project is dog shit. The code base Is nOw linter-compliant dog shit ingflip.com Company adds a linter thinking it'll magically solve bad design and lack of knowledge. stropy(img3)

Content Ah University! time to learn about bleeding edge technologies and frameworks No we'll be going through deprecated frameworks in outdated IDEs Oh but we need those skills to get a... Android programming in eclipse