Damn straight! Mactards are still using a vulernable bash. Unlike us lunix geniuses that have patched bash 3 times in the past week and are still using a vulnerable bash!
I agree that python doesn't cut it. But node.js is a better bash than bash. We replaced all our shell scripts, perl scripts, etc with node.js a couple months ago. Since it's javascript, all our front-end developers are comfortable writing system admin utilities. And since it uses non-blocking, it's faster than bash or C. There are npm modules to do most things you need to do already.
What I find interesting is the ability to create new operators. Not just overloading existing ones, but creating new ones that affect parsing -- prefix, postfix, or infix with custom precedence and associativity.
Custom operators can begin with one of the ASCII characters [list of punctuation dice considers junk characters], or one of the Unicode characters defined in the grammar below. After the first character, combining Unicode characters are also allowed. You can also define custom operators as a sequence of two or more dots (for example,....). Although you can define custom operators that contain a question mark character (?), they canÃ(TM)t consist of a single question mark character only.
If nothing else, the javascript nee ruby nee php hipsters will give some great examples of why this is a bad idea!
Looking forward to some great fart apps written in ascii art...
The 1.0 syntax was just barely frozen. There are a couple open source swift implementations (check github... you won't find them on source forge!) that are making progress. Not sure how useful it would be without a Cocoa/OpenStep library, though.
It's worse than that. The original iphone was 320 x 480. They went retina by doubling it - 640 x 960. No problem, you provide 2x images, everything works great. Then the elongated it to 640 x 1136. still pretty straightforward, though, 2x images with a bit more height. You may need to adjust your layout a bit but no major problems. But now the iphone 6 is 750 x 1334 and 1080 x 1920.
It's like they somehow decided android's fragmentation was a competitive advantage! Oh, and now you provide 3x images and they get downsampled. It will not look as good. Full stop.
Listen Apple, you didn't build a phone that people wanted, you built a phone that the press wanted. Not because they wanted it as a phone, but because they need to write stories about something. These are the same idiots that spent 20 years calling you beleaguered and taking bets on when you would go bankrupt. A larger phone won't do shit except change the narrative from "they need to release a larger phone" to "out of ideas and copying samsung"
There are people who have food, clothing, and shelter covered. They're not the people who are contributing. (ok, maybe a few basement dwellers and college students are!)
Do you need a metric to determine that pizza tastes better than dog shit? Take a look at the GCC codebase and take a look at the llvm/clang codebase. I don't know how anyone could dispute it. (Even if you hate C++, GCC code emulated C++ and has finally started using C++ directly). GCC intentionally fucked up their code for political reasons (to keep people from bypassing the GPL spirit). llvm/clang also have the advantage of being a newer codebase. Some of GCC's code dates back to the 80s and they assume you may be using a 1986-era SunOS k&r compiler to bootstrap it. Remember how OpenSSL has pages of #ifdefs to support Windows 2.0 or big-endian x86 (no joke)? GCC is just as bad.
the point is, they're built-in functions. Not a library or package, but part of the core language. What other language has a function (let alone two functions) to tell you when easter is?
Slashdot Mirror
Damn straight! Mactards are still using a vulernable bash. Unlike us lunix geniuses that have patched bash 3 times in the past week and are still using a vulnerable bash!
I agree that python doesn't cut it. But node.js is a better bash than bash. We replaced all our shell scripts, perl scripts, etc with node.js a couple months ago. Since it's javascript, all our front-end developers are comfortable writing system admin utilities. And since it uses non-blocking, it's faster than bash or C. There are npm modules to do most things you need to do already.
The hipsters got a case of HPV - Haskell, Postgres, and Varnish. The only cure is more buttsechs.
Emma Watson's opportunities are better than yours.
What I find interesting is the ability to create new operators. Not just overloading existing ones, but creating new ones that affect parsing -- prefix, postfix, or infix with custom precedence and associativity.
Custom operators can begin with one of the ASCII characters [list of punctuation dice considers junk characters], or one of the Unicode characters defined in the grammar below. After the first character, combining Unicode characters are also allowed. You can also define custom operators as a sequence of two or more dots (for example, ....). Although you can define custom operators that contain a question mark character (?), they canÃ(TM)t consist of a single question mark character only.
If nothing else, the javascript nee ruby nee php hipsters will give some great examples of why this is a bad idea!
Looking forward to some great fart apps written in ascii art...
And hosted on source forge. Which makes it the first new source forge project in 6 months.
The 1.0 syntax was just barely frozen. There are a couple open source swift implementations (check github... you won't find them on source forge!) that are making progress. Not sure how useful it would be without a Cocoa/OpenStep library, though.
How's that hyperloop working out for you? Big on talk, even bigger on fine print.
Did you go to public school in Texas?
Well, he shoved the pen up his asshole. And his phone is a blackberry.
I assume these are all hardcore porn or snuff flicks or something else worth digitizing. And not shit 80s movies or your daughter's dance recital.
Is this the same specialized Microsoft department that valued skype?
It's worse than that. The original iphone was 320 x 480. They went retina by doubling it - 640 x 960. No problem, you provide 2x images, everything works great. Then the elongated it to 640 x 1136. still pretty straightforward, though, 2x images with a bit more height. You may need to adjust your layout a bit but no major problems. But now the iphone 6 is 750 x 1334 and 1080 x 1920.
It's like they somehow decided android's fragmentation was a competitive advantage! Oh, and now you provide 3x images and they get downsampled. It will not look as good. Full stop.
Listen Apple, you didn't build a phone that people wanted, you built a phone that the press wanted. Not because they wanted it as a phone, but because they need to write stories about something. These are the same idiots that spent 20 years calling you beleaguered and taking bets on when you would go bankrupt. A larger phone won't do shit except change the narrative from "they need to release a larger phone" to "out of ideas and copying samsung"
Yep.
The iWatch detects skin color.
Unless your cock is thicker than your wrist, you can strap your watch to your pecker.
There are people who have food, clothing, and shelter covered. They're not the people who are contributing. (ok, maybe a few basement dwellers and college students are!)
Do you need a metric to determine that pizza tastes better than dog shit? Take a look at the GCC codebase and take a look at the llvm/clang codebase. I don't know how anyone could dispute it. (Even if you hate C++, GCC code emulated C++ and has finally started using C++ directly). GCC intentionally fucked up their code for political reasons (to keep people from bypassing the GPL spirit). llvm/clang also have the advantage of being a newer codebase. Some of GCC's code dates back to the 80s and they assume you may be using a 1986-era SunOS k&r compiler to bootstrap it. Remember how OpenSSL has pages of #ifdefs to support Windows 2.0 or big-endian x86 (no joke)? GCC is just as bad.
I prefer Intercourse's COMEIN feature.
It's just javascript! Plus the worst parts of python and ruby....
pretending synchronous code is magically asynchronous when you add a 10-story callback pyramid.
tweaky, as in toothless meth addict.
the point is, they're built-in functions. Not a library or package, but part of the core language. What other language has a function (let alone two functions) to tell you when easter is?
holy shit, I thought you were joking.
Hide The Salami.