Slashdot Mirror
2017: The Year in Programming Languages (infoworld.com)
InfoWorld writes that 2017 "presented a mixed bag of improvements to both long-established and newer programming languages." An anonymous reader quotes their report:
Developers followed a soap opera over Java, with major disagreements over a modularization plan for standard Java and, in a surprising twist, Oracle washing its hands of the Java EE enterprise variant. Microsoft's TypeScript, meanwhile, has increased in popularity by making life easier for developers looking for an alternative to JavaScript. Microsoft also launched Q#, a language for quantum computing...
In web development, developers received a lot of help building with JavaScript itself or with JavaScript alternatives. Among the tools released in 2017 were: Google's Angular 5 JavaScript framework, released in November, featuring a build optimizer and supports progressive web apps and use of Material Design components... And React, the JavaScript UI library from Facebook, went to Version 16 in September, featuring a rewriting of the React core to boost responsiveness for complex applications...
TypeScript was not the only JavaScript alternative making waves this year. For web developers who would rather use Google's Go (Golang) language instead of JavaScript, the beta Joy compiler introduced in December promises to allow cross-compilation. Another language that offers compilation to JavaScript -- although it began on the JVM -- is Kotlin, which has experienced rising fortunes this year. It was boosted considerably by Google endorsing it in May for building Android applications, which has been chiefly the domain of Java...
2017 also saw the release of the long-awaited C++ 17.
Another 2017 memory: Eric Raymond admitting that he hates C++, and predicting that Go (but not Rust) will eventually replace C -- if not a new language like Cx.
In web development, developers received a lot of help building with JavaScript itself or with JavaScript alternatives. Among the tools released in 2017 were: Google's Angular 5 JavaScript framework, released in November, featuring a build optimizer and supports progressive web apps and use of Material Design components... And React, the JavaScript UI library from Facebook, went to Version 16 in September, featuring a rewriting of the React core to boost responsiveness for complex applications...
TypeScript was not the only JavaScript alternative making waves this year. For web developers who would rather use Google's Go (Golang) language instead of JavaScript, the beta Joy compiler introduced in December promises to allow cross-compilation. Another language that offers compilation to JavaScript -- although it began on the JVM -- is Kotlin, which has experienced rising fortunes this year. It was boosted considerably by Google endorsing it in May for building Android applications, which has been chiefly the domain of Java...
2017 also saw the release of the long-awaited C++ 17.
Another 2017 memory: Eric Raymond admitting that he hates C++, and predicting that Go (but not Rust) will eventually replace C -- if not a new language like Cx.
Then add the standardization of WebAssembly, C++17 is going to gain even more momentum in places we don't expect.
Those who do not learn from commit history are doomed to regress it.
Perhaps the most important change in 2017 was the deployment of WebAssembly. It's the most important because it's the final nail in the coffin for readable JavaScript. Already it's being exploited and wasting everyone's computing power to scrape up cryptopennies. JavaScript as we know it is now over and the age of exploitation is in motion.
Congratulations everyone, JavaScript is now a complete noose around your neck just waiting to be pulled! ;)
Anons need not reply. Questions end with a question mark.
It may be an unpopular opinion, but I actually like Enterprise. I have it at work and uh, found a box that fell off of a truck.
The difference between Pro and Enterprise is night and day. For some reason "Pro" still has crap like Candy Crush in the menu. Enterprise comes bare bones. The released "Professional" is a slap in the face to professionals that just want a desktop OS.
In a house with Ubuntu LTS, FreeBSD, and MacOS X I actually like Windows 10 Enterprise. It's like they actually designed it for *drum roll* desktop users. I don't see how they can claim "Pro" is targeted towards business users. Random junk games showing up in the Menu is not something I want on a business desktop. That should have stopped at Home.
I printed out a keyboard shortcut cheat sheet and can do almost everything without the mouse. If you ignore the close and minimize widgets I can get by using Windows 10 like Awesome WM. UEFI boot doesn't feel tacked on. I don't go through driver hell every time I reinstall, it actually manages to find them or have them installed. (Windows 7 didn't have basic Intel gigabit ethernet drivers...).
I put off upgrading for so long because of the flaming trash heap that was Windows 10 Home on my wife's computer. I also know quite a few others that did the same. Make the installer ask some basic computer questions ("What is an IP address") and give professional users a professional desktop and it might not have the reputation it does.
How can something that only lives in a single browser make programners' lives easier?
I'm not web developer, but from my limited experiments with TypeScript, it looked like it transpiles into something which was running under IE, Edge, Firefox and Chrome (tried only these). Are you saying that some more advanced features of TypeScript work only in Edge? Or only in IE?
What do you like about Windows 10? I had to set it up for my mother and, while I've done some work with MSR and am quite impressed with some of the technology that they've put into it, the UI is terrible. A few examples:
It felt like GNOME or KDE back in the 1.x or pre-1 days, when there was no consistency and lots of known-bad UI decisions everywhere.
I am TheRaven on Soylent News
Not only C++. With WebAssembly one can have a python, swift or go interpreter in the browser. WebAssembly will probably start reducing market share for Javascript which to me is a good thing as I've wasted uncountable hours nitpicking small syntax javascript errors that were causing problems.
I still think C++ has lots of flaws that are totally unnecessary. For example designers insist on not making syntatical breaking changes in C++ which to me is senseless. They could come up with a common bytecode as swift has already done. Then you can just simplify C++ making breaking changes as there will be still binary compatiblity (which at the end of the day is what one wants). That would lead to huge amount of reduction of unnecessary complexity in C++, cleaner code, remove unnecessary undefined behaviour, faster compile times... That would make C++ developers way happier and probably increase its usage with has been stagnant for a long time already.
Typescript transpiles to Javascript. Standard Javascript, in several target versions. The 90's called and they want their worldview back.
I don't trust atoms -- they make up stuff.
The article seems to contain a typo; I'm sure he meant cixl, not cx. Take it from Eric Raymond, this is the future of programming: cixl - a minimal, decently typed scripting language https://github.com/basic-gongf...
Last time I checked, the generated JS looked quite good and readable. TS and JS are not too far, so the generated JS looks similar, and preserves the structure of the TS code. In case of an incompatible or nasty change, I can always go on with the output JS.
Meanwhile, I get extra nice compile time type checks, and even opt in NULL checks. It is amazing how many bugs were caught by the TS compiler that would have been a hard to find runtime error...
It's not senseless. C++ programs are written for systems intended to last a long time. So no one really wants to have their program suddenly uncompilable. Sure, they have no problem if changes are made that makes other people's projects uncompilable, but not their own. So when you factor in the fact that everyone uses C++ in a way that suits them, that means no breaking changes to the syntax can be made.
I would argue this would be C++'s strength for WebAssembly. Unlike with the Javascript, or even HTML situation, web developers finally have an environment where they don't have to cater for every breaking change. Your issue with Javascript is exacerbated by constant churn of incompatible upgrades. C++ does not have this problem and it's a good thing.
Those who do not learn from commit history are doomed to regress it.
One thing has remained constant and that is C++. No reshuffling of syntax, but introductions of new syntax when library solutions do not go far enough. No fear of losing backwards compatibility either.
Those who do not learn from commit history are doomed to regress it.
Make a list of major tech companies that have a significant investment in C++ code. Make a list of companies that are gcc contributors and companies that are clang contributors. You'll find a huge intersection between the first and third lists and a much smaller intersection between the first and second. You'll also find that most of the companies in the second list are also in the third.
I had it summed up to me quite well by a friend at ARM. He said that their customers basically come in two categories: those that don't care whether they use gcc or clang and those that won't allow GPLv3 code in the door. As a result, guess where they're investing all of their compiler resources. These days, I think most gcc development is done by RedHat, and even that are now investing in LLVM.
I am TheRaven on Soylent News
As far as I can see, Windows 10 Enterprise is a very different product to the Home/Pro editions. Windows 10 seems to have a few modest technical improvements under the hood, but the things that have stopped us moving to it are the usual objections to telemetry, forced updates, adware, etc. The Enterprise version seems to have useful controls over those, which isn't surprising since clearly no large corporate IT department is going to surrender control of their essential systems to Microsoft. It's just surprising that the Pro edition, which in previous versions has been aimed at smaller businesses, independent professionals and maybe power users, doesn't appear to be suitable for a lot of professional users in Windows 10.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.