Swift is now the defacto development language for iOS so yes the changes impact a lot of code, first from 2.2 to 3 and from 3 to 4. The difference is Apple & the open source stewards basically said "here's a migration tool, use it or stay put". They aren't vacillating and dithering about their choice.
But like I said, every language and platform goes through this. The language evolves, gets standards, changes, deprecates stuff, introduces new APIs, removes old ones. Python made a bad choice to string out 2.x so long because it entrenched itself even deeper.
You really live in a naive world if you think intelligence agencies give a rat's ass about your sad little life. Or that you think they operate by the rules that govern society. They do dirty, sneaky, underhanded shit because adversaries do dirty, sneaky, underhanded shit. If that means planting a trojan on some target's machine to see who they're in contact with they'll do it. If that means tapping an underwater cable to read messages they'll do it. All so that when terrorist tries to blow up a plane, or an adversary is about to supply weapons to some rebel group they'll know about it. But thanks to Snowden, they might not. He is a traitor and you are an idiot if you think he is some glorious freedom fighter.
Look at the history of Cobol, Fortran, C, Java, Ruby etc. They all contain breaking changes in the language specification or the APIs from one version to the next. Some are substantial, some are not. People deal with the changes and move on.
The differences between Python 2 and 3 are relatively minor at a language level so there is no real excuse for prolonging 2x for ANOTHER decade and the inordinate amount of effort required to do so. Also 2to3 meant most code could be ported with relative ease. Ah but all the Python impls like PyPy, Jython etc. chose to hedge their bets and implement around 2.x and now it's a millstone. In the context of this article where it asks if Python will become the dominant programming language, the answer is perhaps it might have been if it didn't have its head up its ass for 10 years. All of this was avoidable.
Swift would be one recent example and provides a migration tool. But all languages have breaking changes at one point or another.
And besides, someone using Python 2.x is not compelled to move to 3.x but it can be made clear there are no new versions of 2.x and 3.x is where all development lies. It really isn't rocket science.
No it would not have killed both versions. Other projects have managed breaking transitions far more quickly and without wasting nearly a decade supporting two code bases with the subsequent confusion and stagnation that goes with it.
Braces won over other forms enclosure like begin / end because they're terse and easy to parse. Other languages contemporaneous with C would been far more verbose. From a convenience standpoint it's easy to see why braces won. That said, C really screwed up by making them optional for single statement blocks.
Python uses indentation for blocks which in theory is is even more terse than putting braces around blocks. On the flipside it imposes a coding style and line continuation over multiple lines is a really ugly hack.
The clusterfuck was not that some stuff broke in version 3 but that the community wasted an inordinate amount of effort and time supporting version 2 and version 3 in parallel, backporting some things, writing shims, maintaining & building two code bases.
Version 3 should have come out and the community told that in 18 months version 2 was going to be mothballed. A clear timeline that would have focused minds and moved the language forwards.
Not necessarily. A couple of years ago Ireland was in the same place. The government called an election, the leader (Enda Kenny) made some serious gaffs and they failed to get a majority. Instead of resigning he stayed on, they formed a coalition / minority government and it's still operating.
Kenny has only recently resigned as party leader and Taoseach (PM), so it might only be a temporary stay of execution. But May could dig in, form a coalition, or a memorandum of understanding and still lead at least for a while.
I expect for the most part Conservatives will have sufficient majority to push whatever they want. The DUP tends to vote the same way anyway whether they were in coalition or not. So for most things they have an effective majority. The biggest issue is obviously Brexit. The DUP wants a soft Brexit (i.e. customs union, common travel area etc.) with soft borders with the republic of Ireland. The other parties would be in favour of that too. I expect many Conservatives would too. So the prospect of a hard Brexit has definitely diminished.
When you see contemporaneous videos of Guilliani giggling like a girl about an "October surprise", it becomes more clear why Comey slipped an announcement of reopening the investigation. He clearly knew that someone was messing with his investigation and leaking to Guilliani so he took in his opinion the least worst of two options.
Guilliani is currently under investigation as part of the Russia probe.
He committed treason against a country. The United States to be precise. He is no hero or patriot. It is no wonder he is skulking in Russia right now, little more than a mouthpiece and proxy for Putin.
Comey wrote an unclassified memo precisely for this eventuality.
What's less easy to understand is why Slashdot is shilling articles for a traitor sitting in Russia at this very moment for stealing classified material.
I listened to the hearings and the explanation given was entirely reasonable. To wit, if you're recording a communication between two foreign suspects and they mention someone else's name(s), then how do you know if that person is an American citizen or not? It might be simple to check or it might require time consuming and highly intrusive checks to find out. Is the John Smith they mentioned a US citizen? How many John Smith's personal records are you going to trawl through to find a guy who isn't even central to your investigation. What about suspect's schoolfriend Abu who is mentioned to be married now? Are you going to bust into some Pakistani school to find out if any Abu's have emigrated to America and subsequently married? Even though again it's not relevant to the investigation.
If you can't know in the majority of cases if a person is a US citizen without a disproportionate and arguably even more intrusive investigation, and in some cases never know, then what's the purpose of the question again?
It would be better to ask how many names are immediately identifiable as US citizens or whose name have accidentally been exposed contrary to the rules governing FISA.
As long as the default was off to filter them then I'm okay about that. The quality / relevance of search results suffers when high ranked results end up at paywall dead ends. It's no good for users and no good for Google.
Printing out a document on an NSA printer, scanning that print out and releasing it to a shady Russian-front site. Now that's just dumb. Inkjets (not only ones in NSA buildings) can embed codes in their printouts and you'd better believe the NSA is going to have logs of who printed out what and when.
I guess we can thank her for confirming the NSA discovered Russian interference but most reasonable people would have known that already even if they weren't privy to the details. She'll probably end up in prison for 5-10 years over this.
Two news sites equal in terms of reporting etc. One offers news for free, the other is behind a paywall. Which is more relevant to someone typing a search into Google?
The answer is obviously the first one and a ranking algorithm is going to take relevance into account. I don't see any reason that Google owes any paywall site a free lunch. More to the point, putting paywalls high in the list risks degrades the quality of results and therefore hurts Google.
Google should tell them to GTFO. Maybe even delist paywalls entirely.
Hackers generally attack through innocent 3rd parties, either compromised machines, bots or whatever. So what exactly do you hack back against? And what if there is collateral damage?
Javascript main issue is it started off as you suggested, validating fields, executing little snippets of code etc., and then transmogrified into the hideous run-everything-on-the-web language we all know and love today.
An increasing amount of JS is now machine generated - transcompiled from something else. That might be something light like Typescript but it could also be Dart, GWT, C/C++ via Empscripten etc. Even with asm.js the performance still sucks and since it's machine generated code there is a desire to generate something more low level that gets better performance from a browser. PNaCl and asm.js were both efforts to achieve that, but neither hit the spot for various reasons.
So wasm is definitely welcome news. Finally we have a low level bytecode supported by all major browsers which is potentially capable of being compiled to machine code (sandboxed of course) and running at near native speeds.
Javascript won't be going anywhere, but perhaps with a high level and low level way of writing browser applications, it will return to what it was designed for instead of what it's become.
What is more interesting to me is how this will affect mobile app development. Potentially someone can write an app that executes near-natively that works on virtually any mobile device with repackaging.
KSP for Android - "Your space station will be ready in 23:22 hours, accelerate now by using space goo. Would you like to buy more goo? Thimble of space goo $.99, Canister of space goo $5.99, Tanker of space goo $20.99, Comet of space goo (best value) $199.99"
True but what he was convicted of is sufficient. The other stuff just speaks of his character. He's not some libertarian hero, rather he's an asshole scumbag ready to murder people disrupting his business.
Yes if your budget doesn't stretch to a PS4 and/or if you want to pick up a lot of really decent games for next to nothing. It's also a DVD/bluray player and has various streaming apps. For kids it would be fine.
Slashdot Mirror
But like I said, every language and platform goes through this. The language evolves, gets standards, changes, deprecates stuff, introduces new APIs, removes old ones. Python made a bad choice to string out 2.x so long because it entrenched itself even deeper.
You really live in a naive world if you think intelligence agencies give a rat's ass about your sad little life. Or that you think they operate by the rules that govern society. They do dirty, sneaky, underhanded shit because adversaries do dirty, sneaky, underhanded shit. If that means planting a trojan on some target's machine to see who they're in contact with they'll do it. If that means tapping an underwater cable to read messages they'll do it. All so that when terrorist tries to blow up a plane, or an adversary is about to supply weapons to some rebel group they'll know about it. But thanks to Snowden, they might not. He is a traitor and you are an idiot if you think he is some glorious freedom fighter.
The differences between Python 2 and 3 are relatively minor at a language level so there is no real excuse for prolonging 2x for ANOTHER decade and the inordinate amount of effort required to do so. Also 2to3 meant most code could be ported with relative ease. Ah but all the Python impls like PyPy, Jython etc. chose to hedge their bets and implement around 2.x and now it's a millstone. In the context of this article where it asks if Python will become the dominant programming language, the answer is perhaps it might have been if it didn't have its head up its ass for 10 years. All of this was avoidable.
And besides, someone using Python 2.x is not compelled to move to 3.x but it can be made clear there are no new versions of 2.x and 3.x is where all development lies. It really isn't rocket science.
No it would not have killed both versions. Other projects have managed breaking transitions far more quickly and without wasting nearly a decade supporting two code bases with the subsequent confusion and stagnation that goes with it.
Python uses indentation for blocks which in theory is is even more terse than putting braces around blocks. On the flipside it imposes a coding style and line continuation over multiple lines is a really ugly hack.
Version 3 should have come out and the community told that in 18 months version 2 was going to be mothballed. A clear timeline that would have focused minds and moved the language forwards.
Kenny has only recently resigned as party leader and Taoseach (PM), so it might only be a temporary stay of execution. But May could dig in, form a coalition, or a memorandum of understanding and still lead at least for a while.
I expect for the most part Conservatives will have sufficient majority to push whatever they want. The DUP tends to vote the same way anyway whether they were in coalition or not. So for most things they have an effective majority. The biggest issue is obviously Brexit. The DUP wants a soft Brexit (i.e. customs union, common travel area etc.) with soft borders with the republic of Ireland. The other parties would be in favour of that too. I expect many Conservatives would too. So the prospect of a hard Brexit has definitely diminished.
Guilliani is currently under investigation as part of the Russia probe.
By giving aid and comfort to adversaries everywhere. Nope, he's a traitor.
He committed treason against a country. The United States to be precise. He is no hero or patriot. It is no wonder he is skulking in Russia right now, little more than a mouthpiece and proxy for Putin.
What's less easy to understand is why Slashdot is shilling articles for a traitor sitting in Russia at this very moment for stealing classified material.
If you can't know in the majority of cases if a person is a US citizen without a disproportionate and arguably even more intrusive investigation, and in some cases never know, then what's the purpose of the question again?
It would be better to ask how many names are immediately identifiable as US citizens or whose name have accidentally been exposed contrary to the rules governing FISA.
As long as the default was off to filter them then I'm okay about that. The quality / relevance of search results suffers when high ranked results end up at paywall dead ends. It's no good for users and no good for Google.
I guess we can thank her for confirming the NSA discovered Russian interference but most reasonable people would have known that already even if they weren't privy to the details. She'll probably end up in prison for 5-10 years over this.
The answer is obviously the first one and a ranking algorithm is going to take relevance into account. I don't see any reason that Google owes any paywall site a free lunch. More to the point, putting paywalls high in the list risks degrades the quality of results and therefore hurts Google.
Google should tell them to GTFO. Maybe even delist paywalls entirely.
Hackers generally attack through innocent 3rd parties, either compromised machines, bots or whatever. So what exactly do you hack back against? And what if there is collateral damage?
That is a sensible solution and one that would stop mobile / tablet / laptop manufacturers from sealing in batteries. A double win.
An increasing amount of JS is now machine generated - transcompiled from something else. That might be something light like Typescript but it could also be Dart, GWT, C/C++ via Empscripten etc. Even with asm.js the performance still sucks and since it's machine generated code there is a desire to generate something more low level that gets better performance from a browser. PNaCl and asm.js were both efforts to achieve that, but neither hit the spot for various reasons.
So wasm is definitely welcome news. Finally we have a low level bytecode supported by all major browsers which is potentially capable of being compiled to machine code (sandboxed of course) and running at near native speeds.
Javascript won't be going anywhere, but perhaps with a high level and low level way of writing browser applications, it will return to what it was designed for instead of what it's become.
What is more interesting to me is how this will affect mobile app development. Potentially someone can write an app that executes near-natively that works on virtually any mobile device with repackaging.
KSP for Android - "Your space station will be ready in 23:22 hours, accelerate now by using space goo. Would you like to buy more goo? Thimble of space goo $.99, Canister of space goo $5.99, Tanker of space goo $20.99, Comet of space goo (best value) $199.99"
True but what he was convicted of is sufficient. The other stuff just speaks of his character. He's not some libertarian hero, rather he's an asshole scumbag ready to murder people disrupting his business.
Yes if your budget doesn't stretch to a PS4 and/or if you want to pick up a lot of really decent games for next to nothing. It's also a DVD/bluray player and has various streaming apps. For kids it would be fine.
Speaking of ports, there is no traditional 3.5mm headphone jack — which is a bummer. We’re told that it will ship with a headphone dongle in the box.
Dear oh dear
sorry I meant "without". I shouldn't type comments until the caffeine kicks in.
I doubt many Surface devices, especially at the upper end are used with a keyboard so it's basically just an excuse to gouge customers.