I wish there was a service where you'd send a url of an article such as this one and it'd spit out a summary with only the relevant data and without all the surrounding cruft.
Something like a tl;dr for this type of articles.
It's called an abstract, and it's a thing for scientific papers. If you want literally none of the human side of a story or discovery, research papers are a great solution and don't need to be recompiled from longform journalism.
Not only that, but consider how many jobs we could create if only we banned the use of combine harvesters, tractors, various machines in factories all over the world etc.
"Should we condemn them" - manipulatively dramatic language imho. Sometimes we have to step up and take on a burden we might prefer not to - it's done to improve a situation. You want the country's strong to abandon the country and its weak? Or do you want the whole population of every poor country to migrate, should they want?
I'm just considering a not unlikely scenario where a smart, capable person wants to get away from a country ruled by a corrupt or oppressive government. What if the majority of the people continually vote for such a government and this smart (strong, as you put it) person sees no chance of that changing in the foreseeable future, should that person be forced to live there even if they don't want to?
"forced to live there" is exactly the same manipulative language being used shamelessly here. You should really consider avoiding such use as it detracts from your argument.
On the other foot, should we be "forced" to accept people from corrupt nations? What is the test of character we give these incoming people to prevent the same "corruption-tolerant" people from ruining our own system of government?
"forced to live there" is exactly the same manipulative language being used shamelessly here. You should really consider avoiding such use as it detracts from your argument.
Fair enough. What would be another way to say that a person is denied living in any country other than the one of their origin?
The natural result of having borders? If you think people should be able to live wherever they want then where do you draw the line? Can I come live in your house and sleep in your bed whenever I want?
Did you just compare countries with houses ? Do people still use this tired argument ? The line is pretty obvious, it's called property of usage, you can't be denied what you actually need to live a decent life as defined by your society, but arbitrary borders based on the arbitrary, random fact that someone was born at a random place in earth is one of the worst criteria we can use
Instead of grasping on semantics of his language, why don't you try understanding the meaning? At the end of the day what you propose limits human freedom for a greater collective "good". Good luck with that.
One man's freedom is another man's slavery. If having private property and, by extension, state borders is an infringement on freedom then I think we have larger ideals to collide than this small one we started with.
The whole point (or rather, one of the points) of Java and .net are that they are NOT compiled to native code but to bytecode so that you can write code once and then run it on many different systems without having to compile it again.
One does not preclude the other, it is only a matter of distribution, like the mainframes taught us eons ago, by combining JIT/AOT on their toolchains.
The fact that Oracle, Microsoft, Google and Apple are now on the JIT/AOT train, tells it all.
To be fair, .NET always had AOT native compilation support from the early days, but NGEN is a simple AOT compiler only meant for faster startup.
Even hello world programs tend to show different performance characteristics on different OS/platforms. The idea of write once, run everywhere is over. In a moderately complex software, changing the OS/platform is a non trivial problem. Recompiling the code (which is mostly automated) is the least problematic part of it.
Are you familiar with the joys of autoconf, cmake and friends? Have you tried writing a non-trivial application that simply compiles on different flavors of Linux and Windows? Compiling on different platforms is also a non-trivial problem. Having a virtualised platform that abstracts away differences between OS makes it vastly easier to write portable applications.
For many applications running on a VM on different platforms Just Works. The idea is most definitely not over, in fact it is becoming ever more popular. Just look at the rise of abominations like Electron.
Those joys are only enjoyed for those that insist into using C with POSIX APIs covering for lack of a rich standard library.
We don't need VMs, what we need is rich libraries and there are plenty of languages with support for AOT compilation to native code with such libraries.
Something that even C++ is finally adopting.
Regarding Electron, I hope it joins MSHTML in a couple of years.
What I learned from the last chart is that Clojure devs earn the most money regardless of whether they use spaces or tabs.
Being an Elixir programmer also pays off nicely but for heaven's sake don't use tabs unless you want to earn only half as much as you could if you used spaces.
I would expect that initiating a payment from your account directly from code would be forbidden by the platform itself. I'm thinking about this more in the terms of hooks that get called when a payment is received or sent. In essence, what do I want to happen when I'm sending or receiving money?
Like you, I thought that this was pretty unimpressive at first. It seemed to me that this is just a regular bank account and that they expose some API and you have to program the web/mobile app yourself. The homepage is rather uninformative and I didn't really get what this is about until I went to their press release page: https://root.co.za/press/. Then it hit me. You can write small pieces of code, sort of like small apps, to manage what happens when you send or receive money. What's even more interesting is that you can share these apps on their Root platform, sort of like an app store for internet/mobile banking functionalities it seems.They mention some examples of what you could do and this looks seriously interesting now.
Replying to myself here because I can no longer edit my comment. Just wanted to say that, while this is potentially a huge thing, there are certain things that need to be taken into account.
First of all, there's heavy regulation when it comes to banking software. There are laws and bank regulations that are here to prevent people from losing their money and/or suing the bank for some reason or another. Root needs to take great care to ensure that the software written by their users stays within the boundaries of south african law and their own bank regulations.
Second, the software absolutely needs to be reviewed not just by people from Root but also by a reputable independent consulting company.
Third, Root mustn't allow direct initiation of transactions from their platform to prevent potential disastrous effects due to bugs. You should be able to write code that does something when the money is being received or sent from your account but not code that charges your account.
I've been long enough here on HN to remember how people used to laugh at Java in the comments, bemoaning the time it took to set everything up before you can start working with it (although it wasn't really that much trouble then, and it certainly isn't now) compared to how easy it was to start working with Javascript ("Hey, all you need is a browser and an editor"). How the tables have turned.
