Not all taxes are arbitrary. You can't argue that taxes on natural resources are arbitrary. Take mineral resources as an example. I think it's very difficult to find the idea of taxing the use of these resources as absurd in a similar fashion to those presented by this article. Same can be said about radio spectrum.
If we applied the same philosophy to land, we'd need much fewer "arbitrary" tax types and percentages.
Our tax systems are indeed deeply flawed and arguing that any system is arbitrary and equally absurd/paradoxical/inefficient is incorrect since there are examples of ethical (and I would argue necessary) taxes.
Sector Labs | Senior Full Stack Developer | REMOTE, but only from Europe | Full-Time | www.sectorlabs.ro/jobs
We're building software for the real estate and general classifieds industry and operating web sites with millions of users across Asia and North Africa.
Our stack is Python & JavaScript based.
Key highlights:
• high degree of developer autonomy, e.g. we encourage contributors to own the product, we don't have daily stand ups and we barely have regular meetings
• conservative mindset when it comes to the tech stack, we judiciously add new dependencies and we care a lot about the code we write so it keeps its value on the long term
• ruthlessly efficient in delivering software that's cheap to run, scale and maintain
This guide is nice as it provides a short introduction into Angular's features.
I would kindly recommend you to read the Conceptual Overview section of the AngularJS Developer Guide (http://docs.angularjs.org/guide/concepts). This covers the heart of the framework and also parts of its philosophy. If you want to understand WHY AngularJS works the way it does not only WHAT it does then this page will really help you. You will also understand why this is a masterpiece of engineering.
Maybe it would also be interesting to have phones with e-ink displays on its sides, for things such as notifications, weather conditions and phone status.
Maybe you would be interested in watching a discussion between the leaders of these two projects. I think Dart shouldn't be dismissed as a "ridiculous" ambition. I would also like to point out that Dart compiles to JavaScript the same way as TypeScript, so your remark regarding replacing the JavaScript runtimes in all browsers is an exaggeration
I'm wondering how to make use of an existing object system. We already have a JS framework that simulates classes and inheritance in the Java-style OOP.
Yes, these are valid disadvantages of doing rendering code on the client. In your case, and many other similar to yours, using Go with abstract interfacing wouldn't be practical.
Maybe they are afraid of introducing some features they would later regret. This is not a hobby project of some lone hacker, it's meant to compile Google's infrastructure.
I really don't see why user code has to have the same capabilities as the runtime. It looks more like a philosophical request than a practical one.
First, you're saying Go will be an excellent systems programming language, which is its main stated purpose. To me, it already means that it's something that's worth looking at.
Then, you claim it doesn't work like established alternatives, so it must be over hyped. Like anything new, it's normal to see hype, misinformed opinions, advertising and enthusiasm about it.
I haven't written a line of Go, but it's going to be the next programming language that I learn because I find its concurrency model very compelling.
It actually scales better because you're distributing the rendering effort on more machines.
You can serve client-side code on demand, the same way you're serving HTML on demand. There are multiple methods of running a rich client HTML application in a modular fashion. For example, you can load new JavaScript and CSS on demand, or you could do a hybrid approach, by reloading the complete page from module to module. Most MVC frameworks for JavaScript support dynamic loading.
This issue has been addressed in the FAQ. They say generics might get added at some point, but they don't want to rush it. C# 1.0 didn't have generics either.
http://golang.org/doc/go_faq.html#generics
We use http://www.tandberg.com/ and I find it incredibly good. I recommend you to go see a real demo, because you can't grasp the real feel by just looking at some pictures. It's quite expensive, but in my opinion it's worth every dollar.