kmiroslav
No, they're not.
There are a few necessary conditions for this kind of symbiosis to work well:
- The language has to be statically typed. Without type information, the IDE is completely blind and can barely help you at all without human supervision.
- The IDE has to be written on top of the same runtime as the language it's editing. This is what makes Eclipse/IDEA and Visual Studio so spectacular: they understand the bytecode they are working with.
These are necessary conditions but they're not sufficient. You can still write crappy IDE's if these conditions are met, but thankfully, IDEA/Eclipse/Visual Studio are technical wonders that multiply the productivity of their users.
For example, in Go, the simple action of selecting the the surrounding expression simply doesn't exist anywhere. It's the most basic automatic action that's trivial to do with the proper language and IDE, and yet nonexistent in Go. Along with tens of others.
That's the price to pay when a language is designed without any consideration for its tooling nor basic things we learned about language design these past twenty years.
In this particular case, the IDE could automatically remove the imports when you remove the corresponding symbol from your source, or automatically add the import when you introduce a new symbol.
The "can be supplied by any external tool" is a cop out that was acceptable in the 20th century but this is 2016, we have a higher bar for developer productivity.
Anyone using a modern IDE pretty much never even thinks about imports, which are (and should be) automatically managed by the tool, not by the programmer.
It only takes one of these moon shots to be successful to bring in extraordinary revenues, and Google has always been crystal clear that following such path was in their DNA.
What's the difference with simply going to "http://twitter.com"?
This looks more like a bug than a vulnerability, what am I missing?
The simple truth is that today, statically typed languages have all the advantages that once used to be the exclusivity of dynamically typed languages, while the reverse is still not true.
In 2016, there is really very little reason to pick a dynamically typed language for any serious project.
Javascript is going to be around for a while because of inertia, but it's pretty much the last mainstream dynamically typed language we'll see.
Well, it does mean something. Go is evidence that languages can gain momentum very fast so the fact that Dart still hasn't should be a bit of a concern (and probably partially caused by Typescript's popularity).
listOf(1, 2, 3, 4).filter { it % 2 == 0 }You know, it wouldn't surprise me in the least if you're the only developer who ever created a language and whose day job is not writing code.
Hat's off to you, seriously impressive.
Same reasons books are structured as sequential lines: easier to read for humans.
And the reason why source code is still heavily text based and why introducing more WYSIWIG to it would be disastrous is that all the peripheral tooling would become a nightmare (diffs, code reviews, source control, etc...).
I was referring to the fact that when a result is so close, the vote might have a different outcome simply based on who shows up to vote that day. If there's a revote, more people against leaving might show up because they didn't realize they would lose. And then if a third vote is held, the result might swing again.
Our country is clearly split right now, but the road ahead for the brexit outcome is terrifying and full of unknowns, as the commentator acutely outlined. Is it worth going through so much turmoil when there is barely an inch above a majority that voted this way?
My answer would be a resounding "yes" if the result was 70%/30%. But 52%/48%? Maybe we should spend some time thinking this through before enacting Article 50. And all the current leaders seem to think this way right now given how discreet they have become as the reality is slowly sinking in.
Practically... it's a 52%/48% vote. Hardly a mandate. Some people say a revote might yield an opposite result, which means the current outcome is probably under the margin of error.
It wouldn't exactly be a miscarriage of democracy to not follow through and see how things unfold in the next couple of years, and maybe vote again to see if the gap widens or if our country remains split in the middle on the issue.
At any rate, this comment about the situation is frighteningly deep and chilling.
Come to think of it, the trick to make something private in order to "remove" it is one of these very few areas where C++ makes you pay for something you don't use, so I'm not surprised that there is now a special keyword (well, a repurposed keyword) to address that.
Sure, a few countries will try to follow suit and try to leave the EU but imagine a future when, in a couple of years, Britain's economy has dropped below #10, unemployment is at an all time low, the deficit has ballooned, etc...
What do you think EU members will think by then? They will certainly want to stick around.
The bottom line is that the current decision was made by voters who are swayed by immigration and talking points from crafty politicians but who have little understanding of how global economy works.
Let's see what the situation is in 2018.
I'd argue that neither of these are really a good measure, I'm more interested in the concepts that a source file captures than its size in kb, because these concepts correlate directly to how easy it will be to evolve that code base in the future. There is a point of diminishing return in trying to make the code too compact, which basically means you're optimizing in one dimension at the detriments of all the others.
Obviously, message passing is alive and well for network protocols.