1,028 karma · joined October 28, 2012
C++ has the advantage of an incredible amount of code written in over the years that mostly works. It also executes fast. It's also easy to find developers for it. With the new addons to the specification it's even possible to write readable code with it.. However, it has a stupidly long, verbose and feature creepy standard (well over 1000 pages), which results in no developer reading it. Because of it's design, compilation times tend to take long (as a ridiculous amount of headers are included even in the most simple applications).
Go is pretty much the opposite. It has a lean and readable spec (on purpose) and a fairly common canonical syntax without much discussion about it. Because it's relatively new, there is not much written in it however. It has some specific strengths, like a concurrency implementation that abstracts most of the process/thread/mutex stuff. With this, it does appeal to new projects that don't depend on libraries written in other languages. There is no point in porting multi-million SLOC applications to Go though, as that would be incredibly time-consuming. It has the potential to surpass C++ in a few decades though, as it operates in the same domain (systems programming).
Python is a versatile scripting language. It has nice syntax and is incredibly flexible at manipulating data. Add to it the well documented, feature-rich standard library. With it you can evaluate data with incredible flexibility and it has a fairly complete feature set for general programming tasks that span multiple OSs. The downside is that it's slow in execution and needs the interpreter along the scripts. Especially for smaller tasks and simple automation it is the first choice however because of it's small footprint in constraints (you can just edit and drop a scriptfile anywhere on a Linux system and it works).
Java.. I'm not entirely sure what Java does well. I hear praise for the JVM, but generally I get the impression that it is plagued by legal issues, alien looking GUI tools, more than verbose syntax and it also has a stupidly long specification (almost half of C++'s). Maybe someone can shed light on this one. Tools maybe?
Colonists on Mars would have to deal with extreme environmental conditions and therefore be forced to invest the majority of resources in science and engineering instead of politics and entrenched systems.
Also, martians would be natural space travelers. Mars has a gravity that's less than half of Earth's, so they would get off that rock much easier and they would have a wealth of natural resources through asteroid mining that they could sell to earth together with advanced technology.
After a few centuries the martians would push the technological boundary far beyond what we have now and give Earth the motivation to follow suit to ensure sovereignty.
So unless they convince me that they managed to get their internal structural problems under control, I don't think they get anytime to Mars within this century. And certainly not before the private sector does.
http://en.wikipedia.org/wiki/Constellation_program
p.s.: There is a free movie on YouTube telling the tale: https://www.youtube.com/watch?v=tcTZvNLL0-w
But I think that the field of IT is still extremely young and that in the future larger companies will discover that collaborating on open source platform and infrastructure projects will give them much better synergy effects and lower IT costs by removing the license cost and at the same time lowering the support cost. Compared to history, the 20-30 years that mainstream computing has is really just a spark and there is so much change coming that will be directed by market and competition.
Putting on Apples shoes I think this decision was more guided by financial, risk and PR motivations.
Apple is a mass technology company focused on synergies. Dealing with red tape and custom data decryption is definitely outside that area. It adds additional cost, not just for the work performed, but also organisational overhead (they probably have to hire people for this, open new organisational units or divert existing resources from more useful work). I'm sure that can't be simply expressed in numbers and much less covered by the government, even if they pay for the services.
There is the risk which has a technical nature: if a black hat / leak (e.g. disgruntled employee) / someone outside the organisation ever acquires the means to unlock costumer phones outside the confines of Apple, all hell would break loose. And while I'm sure they make proper precautions, not having to deal with this as a risk is likely more desirable.
The PR side is the most obvious one: there are lot's of people that are not comfortable that Apple can simply unlock their data and will buy something else just because they are not so forthcoming with the court warrants. More importantly, businesses will have a very hand time to justify the risk of information leakage because they use a product that has outside access vectors.
So this decision seems to make perfect sense to me from a business perspective: less cost + operational overhead, less risk of something going horribly wrong and better PR light. What's not to love about it?
Note: IANAL, I don't own any Apple devices and I'm not a U.S. citizen nor do I live in the U.S.
Year Version Year-Delta
1983; 1.0; 0
1989; 2.0; +6 years
1998; C++98; +9 years (first ISO standard)
2003; C++03; +5 years (minor update)
2011; C++11; +8 years (major update)
2014; C++14; +3 years (minor update)
The C++14 version was the first that arrived on schedule. The next major version is planned for 2017. The future looks quite promising for C++.
Train rides in western Europe are not that expensive and certainly not worth the hassle with airplanes over such short distances. Also, you can buy 25% and 50% discount cards for all tickets for a year for only a few EUR's. (25% for a year = 62 EUR, 50% for 515 EUR for inland travel in Germany).
http://www.isciencetimes.com/articles/6087/20130919/nasa-plu...
Question: Does your application has x, y and z feature and can be integrated in our process easily?
Answer: Sure, all there. Just have to tweak a few settings in the GUI.
Truth: We have a bare-bone product and a semi-documented API. Feel free to implement all the features you want and adapt it to your process. We can provide you professional services (for a price, of course).
Example: https://github.com/skriticos/tac_workflow/blob/9890e66d60851...
I don't see the issue with the object hierarchies either. You have your QObject and QWidget classes that are important and then all the stuff that builds on that. Not that complicated really once you get into it.
The UTF-16 thing is ugly, yea, but I did never see a practical issue with it.
TLDR:
* Qt has a community of people developing applications, has good documentation (precise, good coverage) and people who care
* Gtk+ has a bunch of Gnome developers, if you want to develop an application, you're out of luck
The central question is: did he really knowingly sign a non-compete agreement and is it lawful in the jurisdiction?
Yes, he signed the contract, which was likely a 20 page standard issue paper that was mostly written by Amazon lawyers in small print.
Now most of us don't send a copy of employment contracts to our layers and discuss it with them for hours before signing (that's kind of expensive).
That's why there are some limitations on what can go into a contract in some places (at least in Europe, but I assume the U.S. has something similar). For instance they can't write in there that you will be their slave, providing unpaid work without the ability to quit, be beaten as motivation and lawfully enforce it, even if you sign the paper.
Other things need to be explicitly clarified to be accepted at court. For instance, if a big software corporation would add a clause to their license agreement on page 25 that your house belongs to them if you click on "I Agree", it would most likely not hold ground in a court. If they explicitly explained this to you (with a few witnesses), it might be heard in court.
The question here is (and it's far from clear cut) is if this contract holds it's ground in court.
Back to the central point: this means, that Amazon might have to prove that they made a good effort to clarify this clause in the contract explicitly and it's lawful in the state he worked. That's up to the court to decide.
Now if they can prove that they did make a good faith effort to clarify his contract, he agreed and then went on and willfully broke it, then he is in a troublesome spot.
INAL, this is not an advice for anything and I'm not liable for any of the above.
I personally think that a lot of jobs today don't justify driving around at all. What difference does it make if you code in the crowded building of your employer or at home and use tele-conferences to talk with each other? Maybe you would even be more productive if you got rid of all the stress caused by commuting around a substantial portion of the day.
I guess a good chunk of the office work done today could be replaced by remote work, but employers insist on everyone to get into the car, commute and thereby congest roads and burn up non-renewable petrol.
I am seriously wondering why the working population don't bill the time and expenses of commuting to the employers? Most entrepreneurs do. You pay $50-$100 for the plumber to come to your place (just to come there, work is billed extra). Why not office workers?
Anyway, good times. I'm throwing money at all the Linux games. Hope the trend continues.