You do not ask for the basic income - it arrives automatically on your bank account every month. The trick is that taxation is modified so that people like me - with a decent salary - will end up the same as now after taxation.
To understand why this is useful, one thing to realize is that our taxation is a very clean and automated process, while the social benefits are a horrid mess that requires a lot of paperwork.
I live in Europe - Finland, and I'm commenting from the POV of our starting basic income experiment. I have no idea of how basic income would work in the US.
I live in Europe, in Finland. So at worst I'm making a Finland centric comment about Europe. I was describing our system, but I believe many of the rich western europe countries have similar.
And I do not think the EU is doing anything about this - it is several member states doing experiments for themselves.
All of these basic income articles always get these "free moneys" comments, while the actual plan is not about giving unemployed people more money than what they now receive. The idea is to make taking any work always beneficial compared to unemployment. The current system - where you have to demonstrate that you have no work - has the problem that taking a short gig may you may end up losing money before you can again show that you are unemployed.
Also hopefully we will get less bureaucrazy etc.
Even now, every refugee that is granted refugee status will start receiving unemployment benefits.
I don't know about Romania, but at least here in Finland, you cannot really fire a single employee for bad performance. If the guy cannot do his job at all, then maybe, but just for being the bottom of the barrel is not cause for firing. On the other hand, if the company does not need the employees work any more, they can fire him, but then they cannot immediate hire someone else to do it.
All this means is that when a company wants someone to leave, they 1) sometimes offer money if you resign or 2) try to find something actionable, like being at work drunk.
That is not really possible. Amazon is getting to a monopoly position if you want to use all the modern Cloud stuff. Sure, you can get boxes from many different providers, but AWS has a ton of other services that you cannot buy from others and even more importantly, all the 3rd party Cloud services are running on AWS so they are faster if you are on AWS too.
I would not be surprised if in 10 years Amazon would be a verb for running server software like google is now for search.
No, they are not metaphors. They are real. But the person saying those words in Luke 19:27 is some imaginary king in Jesuses story. I have no idea what the point of the parable is, but it is not a literal command, like the quote makes it sound.
That may be true for the 4 million Syrian refugees that are mostly in the camps near Syria. The refugees that get smuggled to Europe are not all from Syria and do not share that distribution. They are mostly young men. During 2014 refugees from Iraq to Finland were 84% male. I cannot find statistics for 2015, but even the totally pro-refugee media admits that they are young men.
It would be great if the refugees coming to Europe would share the balanced gender and age distribution of the refugees on the camps.
Exactly this! I'm from Finland. The idea of basic income means different things for different people around here, but AFAICT the idea is not to give people more money. Instead the idea is to:
- give people the same amount of money they now get from unemployment benefits etc. but without asking any questions. - tax the money back from people that make a living wage working.
This should have the benefits that:
- If you are unemployed, you can take even just one shift of work and get some money without losing too much of your benefits. This does not currently work too well, because you have to show that you are unemployed to get the benefits. - If you get some benefits and do some work, you should always get more money by working more. In our current system, there are traps that may actually make you earn less by working more, because you lose more benefits. - We should need a lot less people working for the public sector handing out benefits.
So the idea is to make working always desireable and lessen bureaucracy.
I'm from Finland. The idea of basic income means different things for different people around here, but AFAICT the idea is not to give people more money. Instead the idea is to:
- give people the same amount of money they now get from unemployment benefits etc. but without asking any questions. - tax the money back from people that make a living wage working.
This should have the benefits that:
- If you are unemployed, you can take even just one shift of work and get some money without losing too much of your benefits. This does not currently work too well, because you have to show that you are unemployed to get the benefits. - If you get some benefits and do some work, you should always get more money by working more. In our current system, there are traps that may actually make you earn less by working more, because you lose more benefits. - We should need a lot less people working for the public sector handing out benefits.
So the idea is to make working always desireable and lessen bureaucracy.
Exactly! Looks like we need to have all the antitrust discussions again - how it's ok to have a monopoly but not ok to use that to grab market share on other markets, how monopoly power does not mean 100% market share etc. Too many are too young to remember from the MS antitrust days or maybe they have forgotten all that.
And if you think that it's wrong of EU to investigate an American company, think about it this way: with EU and US doing these investigations, we can have more faith in that all monopoly abusing companies will be investigated somewhere - even if their home country is turning a blind eye. This is good on both sides - it's not like this will really have a huge effect on Google anyway.
I bought Dycky Shine 3 Tenkeyless and I am loving it. The color led games were fun for about a day, but the mechanical keyboard without the number keypad is just awesome. I guess many manyfacturers make fine mechanical keyboards, but if you don't use the number keypad, consider a tenkeyless keyboard. It is so nice to have the mouse closer to the keyboard.
I watched the document earlier today. It's not gloomy. It has a very clear call to action with many realistic ideas of how to combat pollution. Actually watching it made me think that maybe China can get this pollution situation fixed some day.
I guess they are incompetent because they are having the same trouble with another reactor in France.
For a long time Areva was complaining that TVO, the company that bought the reactor in finland, was not doing everything required and that the safety requirements where somehow wrong, but since they have the same trouble in France with very favourable regulators - they must be incompetent.
The main problem has been to automation system. For the nuclear reactor safety standards, there must be two completely separate systems, so the other can be used as backup. I believe they have had a lot of trouble in creating two systems that are really separate, so that the other can really be used as a backup. Actual construction work at the site has been slowing down, because the designs just could not be finished.
The reactor was bought with a fixed price contract by a private company called TVO. Areva has not been getting any extra money out of Finland. They are trying to sue the company that bought the reactor, TVO, but that is still ongoing and there is a countersuit too.
So I, as a finnish tax payer, have no direct stake in this. Of course, electricity prices might go down, if the reactor finally came online.
All production Java applications are compiled in debug mode. This way the problems can be properly debugged. Some application frameworks even require debug compilation to be able to do their runtime AOP.
That said: it is incompetence to show stack traces or other confusing errors to users. They are supposed to go to a log file.
That said: Some people are always incompetent, but after weeks of overtime, everyone will be incompetent.
Their phone only has 1GB of memory and that works pretty well, so I think 2GB on tablet should be ok?
Anyway, with the price given this is in the cheap tablet category and not competing with the over twice more expensive iPads. I ordered it just because the phone has had regular software updates unlike the Samsung (tablet) and Nokia (phones) devices I have previously had.
People with health care should be more able to prosper because they are healthy and can work. People with untreated sickness are not going to prosper regardless if how incentivized they are to work harder.
EU actually does have minimum and maximum levels for some taxes. So as a member of EU they are not completely free to choose the level of their taxes. I also think that Ireland has been one of the countries opposing a raise in the minimum tax paid by companies. But anyway, the current beef is like you said.
On the Play webserver the user "session" is a signed cookie. So if you have very little data, you can store it there and you always have it regardless of the server rendering the response. If you need more user specific data you can store keys in the cookie and get the session from a backend mongodb or memcached or akka cluster or something else that scales easier then an RDBMS. With the Plays ability to easily fetch data concurrently from multiple backend systems, this is actually a good way to go. Or you can just have all the user specific stuff fetched with ajax from some other servers to distribute the load.
I don't think it means what you think it means. Obviously the manifesto is so short on details that it can be interpreted in many ways. I think the failure tolerance is more about e.g. tolerance of losing machines or tolerance of overloading - and that seems to be working.
I have previous experience about J2EE/JEE application servers and they always seemed to have the problem that when overloaded with traffic they might do anything. And after being severely overloaded they often do not recover back to normal. Also people often did not use J2EE session replication, because it was considered a pain.
Now I'm building an app with Scala/Play framework and we don't have user sesssions or the web servers so scaling and server failures are not a problem. Also we just ran some performance / load tests and the servers work fine up to 100% load and then just start to lose some requests. This is much preferrable to the "all bets are off" that I have seen on Tomcat or other servlet containers. Another reactive benefit from the Play server is that it is super easy to use many threads for building a single http reply and this really helps in giving users timely replys.
So while the manifesto is of course marketing, there are some good things in the new ways of doing things.
I work on business software projects in Finland. We'd like to use AWS on many of our projects, because it's very convenient and a lot of PaaS and other tools are provided on there. However, I have not met a single client that would allow us to use AWS or some other US based service for storing data. So we use the local clouds that only offer IaaS servers and not much else.
And this has changed a lot in just a couple of years.
Yes, in scala there are binary incompatibilities between major versions.
My reply was that with Java 8 and byte code enhancement there are binary incompatibilities in Java too. You cannot just avoid Scala to avoid binary incompatibility problems.
In other words, don't bother with Scala just yet since we haven't made up our minds about the syntax and will probably start all over.
One of the links actually lists the changes they are thinking of. To me they all make sense and they won't change the language too much while making the life of the compiler easier - and the result more predictable to humans.
Let me know when you get that binary compatibility between versions of Scala figured out.
Just a few months ago I saw a project at work that could not migrate to Java 8 because some of the libraries in the project do not work with Java 8 libs. The problem is that the lib in question wants to do bytecode enhancement and fails with the new lib format. Scala is more complex, no question about it, but I don't need aspects or bytecode enhancement or reflection and all that reduces complexity quite nicely.
Slashdot Mirror
You do not ask for the basic income - it arrives automatically on your bank account every month. The trick is that taxation is modified so that people like me - with a decent salary - will end up the same as now after taxation.
To understand why this is useful, one thing to realize is that our taxation is a very clean and automated process, while the social benefits are a horrid mess that requires a lot of paperwork.
I live in Europe - Finland, and I'm commenting from the POV of our starting basic income experiment. I have no idea of how basic income would work in the US.
I live in Europe, in Finland. So at worst I'm making a Finland centric comment about Europe. I was describing our system, but I believe many of the rich western europe countries have similar.
And I do not think the EU is doing anything about this - it is several member states doing experiments for themselves.
All of these basic income articles always get these "free moneys" comments, while the actual plan is not about giving unemployed people more money than what they now receive. The idea is to make taking any work always beneficial compared to unemployment. The current system - where you have to demonstrate that you have no work - has the problem that taking a short gig may you may end up losing money before you can again show that you are unemployed.
Also hopefully we will get less bureaucrazy etc.
Even now, every refugee that is granted refugee status will start receiving unemployment benefits.
I don't know about Romania, but at least here in Finland, you cannot really fire a single employee for bad performance. If the guy cannot do his job at all, then maybe, but just for being the bottom of the barrel is not cause for firing. On the other hand, if the company does not need the employees work any more, they can fire him, but then they cannot immediate hire someone else to do it.
All this means is that when a company wants someone to leave, they 1) sometimes offer money if you resign or 2) try to find something actionable, like being at work drunk.
That is not really possible. Amazon is getting to a monopoly position if you want to use all the modern Cloud stuff. Sure, you can get boxes from many different providers, but AWS has a ton of other services that you cannot buy from others and even more importantly, all the 3rd party Cloud services are running on AWS so they are faster if you are on AWS too.
I would not be surprised if in 10 years Amazon would be a verb for running server software like google is now for search.
No, they are not metaphors. They are real. But the person saying those words in Luke 19:27 is some imaginary king in Jesuses story. I have no idea what the point of the parable is, but it is not a literal command, like the quote makes it sound.
That may be true for the 4 million Syrian refugees that are mostly in the camps near Syria. The refugees that get smuggled to Europe are not all from Syria and do not share that distribution. They are mostly young men. During 2014 refugees from Iraq to Finland were 84% male. I cannot find statistics for 2015, but even the totally pro-refugee media admits that they are young men.
It would be great if the refugees coming to Europe would share the balanced gender and age distribution of the refugees on the camps.
If it is not for nerds, then who is it for? Certainly nerds are the only people that will potentially vote for Lessig?
Where did the GP claim some other religion was better? What does the truthfulness of any religion have to do with the points GP made?
Exactly this! I'm from Finland. The idea of basic income means different things for different people around here, but AFAICT the idea is not to give people more money. Instead the idea is to:
- give people the same amount of money they now get from unemployment benefits etc. but without asking any questions.
- tax the money back from people that make a living wage working.
This should have the benefits that:
- If you are unemployed, you can take even just one shift of work and get some money without losing too much of your benefits. This does not currently work too well, because you have to show that you are unemployed to get the benefits.
- If you get some benefits and do some work, you should always get more money by working more. In our current system, there are traps that may actually make you earn less by working more, because you lose more benefits.
- We should need a lot less people working for the public sector handing out benefits.
So the idea is to make working always desireable and lessen bureaucracy.
I'm from Finland. The idea of basic income means different things for different people around here, but AFAICT the idea is not to give people more money. Instead the idea is to:
- give people the same amount of money they now get from unemployment benefits etc. but without asking any questions.
- tax the money back from people that make a living wage working.
This should have the benefits that:
- If you are unemployed, you can take even just one shift of work and get some money without losing too much of your benefits. This does not currently work too well, because you have to show that you are unemployed to get the benefits.
- If you get some benefits and do some work, you should always get more money by working more. In our current system, there are traps that may actually make you earn less by working more, because you lose more benefits.
- We should need a lot less people working for the public sector handing out benefits.
So the idea is to make working always desireable and lessen bureaucracy.
Exactly! Looks like we need to have all the antitrust discussions again - how it's ok to have a monopoly but not ok to use that to grab market share on other markets, how monopoly power does not mean 100% market share etc. Too many are too young to remember from the MS antitrust days or maybe they have forgotten all that.
And if you think that it's wrong of EU to investigate an American company, think about it this way: with EU and US doing these investigations, we can have more faith in that all monopoly abusing companies will be investigated somewhere - even if their home country is turning a blind eye. This is good on both sides - it's not like this will really have a huge effect on Google anyway.
I bought Dycky Shine 3 Tenkeyless and I am loving it. The color led games were fun for about a day, but the mechanical keyboard without the number keypad is just awesome. I guess many manyfacturers make fine mechanical keyboards, but if you don't use the number keypad, consider a tenkeyless keyboard. It is so nice to have the mouse closer to the keyboard.
I watched the document earlier today. It's not gloomy. It has a very clear call to action with many realistic ideas of how to combat pollution. Actually watching it made me think that maybe China can get this pollution situation fixed some day.
Maybe you should watch it too?
I guess they are incompetent because they are having the same trouble with another reactor in France.
For a long time Areva was complaining that TVO, the company that bought the reactor in finland, was not doing everything required and that the safety requirements where somehow wrong, but since they have the same trouble in France with very favourable regulators - they must be incompetent.
The main problem has been to automation system. For the nuclear reactor safety standards, there must be two completely separate systems, so the other can be used as backup. I believe they have had a lot of trouble in creating two systems that are really separate, so that the other can really be used as a backup. Actual construction work at the site has been slowing down, because the designs just could not be finished.
The reactor was bought with a fixed price contract by a private company called TVO. Areva has not been getting any extra money out of Finland. They are trying to sue the company that bought the reactor, TVO, but that is still ongoing and there is a countersuit too.
So I, as a finnish tax payer, have no direct stake in this. Of course, electricity prices might go down, if the reactor finally came online.
All production Java applications are compiled in debug mode. This way the problems can be properly debugged. Some application frameworks even require debug compilation to be able to do their runtime AOP.
That said: it is incompetence to show stack traces or other confusing errors to users. They are supposed to go to a log file.
That said: Some people are always incompetent, but after weeks of overtime, everyone will be incompetent.
Their phone only has 1GB of memory and that works pretty well, so I think 2GB on tablet should be ok?
Anyway, with the price given this is in the cheap tablet category and not competing with the over twice more expensive iPads. I ordered it just because the phone has had regular software updates unlike the Samsung (tablet) and Nokia (phones) devices I have previously had.
People with health care should be more able to prosper because they are healthy and can work. People with untreated sickness are not going to prosper regardless if how incentivized they are to work harder.
EU actually does have minimum and maximum levels for some taxes. So as a member of EU they are not completely free to choose the level of their taxes. I also think that Ireland has been one of the countries opposing a raise in the minimum tax paid by companies. But anyway, the current beef is like you said.
On the Play webserver the user "session" is a signed cookie. So if you have very little data, you can store it there and you always have it regardless of the server rendering the response. If you need more user specific data you can store keys in the cookie and get the session from a backend mongodb or memcached or akka cluster or something else that scales easier then an RDBMS. With the Plays ability to easily fetch data concurrently from multiple backend systems, this is actually a good way to go. Or you can just have all the user specific stuff fetched with ajax from some other servers to distribute the load.
I don't think it means what you think it means. Obviously the manifesto is so short on details that it can be interpreted in many ways. I think the failure tolerance is more about e.g. tolerance of losing machines or tolerance of overloading - and that seems to be working.
I have previous experience about J2EE/JEE application servers and they always seemed to have the problem that when overloaded with traffic they might do anything. And after being severely overloaded they often do not recover back to normal. Also people often did not use J2EE session replication, because it was considered a pain.
Now I'm building an app with Scala/Play framework and we don't have user sesssions or the web servers so scaling and server failures are not a problem. Also we just ran some performance / load tests and the servers work fine up to 100% load and then just start to lose some requests. This is much preferrable to the "all bets are off" that I have seen on Tomcat or other servlet containers. Another reactive benefit from the Play server is that it is super easy to use many threads for building a single http reply and this really helps in giving users timely replys.
So while the manifesto is of course marketing, there are some good things in the new ways of doing things.
I work on business software projects in Finland. We'd like to use AWS on many of our projects, because it's very convenient and a lot of PaaS and other tools are provided on there. However, I have not met a single client that would allow us to use AWS or some other US based service for storing data. So we use the local clouds that only offer IaaS servers and not much else.
And this has changed a lot in just a couple of years.
Yes, in scala there are binary incompatibilities between major versions.
My reply was that with Java 8 and byte code enhancement there are binary incompatibilities in Java too. You cannot just avoid Scala to avoid binary incompatibility problems.
In other words, don't bother with Scala just yet since we haven't made up our minds about the syntax and will probably start all over.
One of the links actually lists the changes they are thinking of. To me they all make sense and they won't change the language too much while making the life of the compiler easier - and the result more predictable to humans.
Let me know when you get that binary compatibility between versions of Scala figured out.
Just a few months ago I saw a project at work that could not migrate to Java 8 because some of the libraries in the project do not work with Java 8 libs. The problem is that the lib in question wants to do bytecode enhancement and fails with the new lib format. Scala is more complex, no question about it, but I don't need aspects or bytecode enhancement or reflection and all that reduces complexity quite nicely.