Hacker Newsnew | past | comments | ask | show | jobs | submit | krunaldo's commentslogin

Well, first you have to calculate that the company pays 31.42% of your total salary in payroll taxes. This is illegal to print or show in any way or form to the employee from the employer.

Then on most goods there is a 25% tax, additional taxes other categories of goods such as gas, cars, alcohol and so forth.

So if the company pays you 60k SEK, you'll see ~45k on your payroll slip. The 61% percentage is the average total tax burden on a individual from all of these taxes.


Payroll tax is not your salary - it's tax on their employment of you, of an amount due that's proportional to your salary. It's the company's money, not yours.

(Would they pay you more if that tax wasn't due? Well, possibly, I suppose. Or they might just pay you the same, and then buy more stuff, employ more people, pay the company owners more money, that sort of thing.)


What are you smoking? Change it, it is bad for logic: any tax a company pays for you is from the money you bring in, not from the shareholders personal bank accounts. Nobody pays for the pleasure to have someone as an employee, but for the employee to deliver more than what is paid, otherwise you go under.


Reduce the payroll tax, and, what then? Same amount of money coming in, same going out on salaries, less going out on payroll tax. Now the business has options. It can buy more stuff; it can employ more people at similar salaries; it can give the owners more money.

But the argument being made appeared to be that it will give its existing employees pay rises, to each one in line with how much payroll tax it was paying for each of them previously - but this just strikes me as a bit unlikely.


> It can buy more stuff; it can employ more people at similar salaries; it can give the owners more money.

Don't they also have to compete with other employers in the labor market for labor. How can they possibly keep paying the same salaries.


In Romania by law the company contribution was included in the payroll; there was no change in salaries, but people were finally able to see the total taxes they paid and calculate the percentage correctly: it was about double vs what they thought.


The 61% number in this case came from the top marginal tax rate on income in Sweden. The fact that it's roughly the same is payroll + income tax is a coincidence.


You'll have to calculate how much it costs to buy the car and the loss of value when you estimate to sell into that as well to get a fair comparision.


crontab -e is the way to edit your cron. A similar command exists for editing the sudoers file which is visudo. This will ensure your configuration is a valid syntax as well as do an atomic swap of the file.

Otherwise adding a file or deleting a file in /etc/cron.d/ is the way to go for automatic(ansbile, puppet etc) and package installations.


I'm surprised that people would edit cron in any other way, crontab -e is one of the first commands most intro to Linux manuals teaches.

However crontab -r has to be one of the most poorly thought out commands in UNIX. It removes the cron file and since r is only one character over from e on qwerty keyboards it's a painful and surprising typo.


first thing when logging into new server: place /etc under git. then loss of cron files (or any config file) is easily recovered from.


Except that crontabs are usually somewhere in /var. :)


Which is why I only use system-wide crontabs, in /etc/cron.d

Instead of per-user crontabs. Much easier to manage.

With cron.d you can specify what user each cron entry should run as, so it is equivalent.


This is a brilliant idea - thank you!


I cannot count the number of times this has helped or saved me. You can keep the /etc git repo local. Or if its a critical server, push to github private repo. Seeing a history of your /etc edits is a very reassuring feeling.


what if you are managing the crons externally, eg puppet, crontab -e is not always option


1. If you don't have a test process for changes made with puppet, this is hardly a problem with cron.

2. Puppet handled that parsing for you and will throw errors if your syntax is wrong


I can't tell you the amount of times I've hit -r by mistake and regretted it..


I can. 0. There, more anecdata.

Honestly though, I never use `-e` either. I keep a ~/.crontab and edit that, and then `crontab ~/.crontab`.

Voila, backup/time machine/git friendly crontab.


I got bit by this once, and had to rescue the crontab out off the disk with GNU strings :(


Have a cronjob that backs up your crontab?


Use /bin/cat as editor. That should work nicely from Puppet.


crontab -e is the way to edit your cron. A similar command exists for editing the sudoers file which is visudo. This will ensure your configuration is a valid syntax as well as do an atomic swap of the file.

And there's "vipw" for the password file. Each of them with their own separate updating bugs.


Nitpick, Deaths due to TERRORIST attacks. Not arbitrary deaths....

"From this it follows that the average Muslim is responsible for approx 48 times more deaths than the average American of any religion."

^ This statement is false as it assumes all deaths are from terrorist attacks, based on your previous statement of 48 times more likely to commit TERRORIST attacks, of which has a silly low death rate compared to ANYTHING else in the US.


Interesting stuff, anyone know if there are other startups in China doing products that require large amounts of RnD, similar to http://traintracks.io , that's mentioned in the article.



They are. As I pointed out in my other comment:

"All Red Hat Software Collections components are fully supported under Red Hat Enterprise Linux subscription terms of service. Components are functionally complete and intended for production use. " [0]

[0] <https://access.redhat.com/products/Red_Hat_Enterprise_Linux/...


Assuming they are using RHEL/CentOS 6.

You can get supported ruby 1.9.3 on RHEL6 or CentOS6 https://www.softwarecollections.org/en/scls/rhscl/ruby193/ or https://wiki.centos.org/AdditionalResources/Repositories/SCL

Unless they are unwilling to upgrade their rails and using the ruby version as an excuse :) Best of luck to you!


Software Collections aren't "supported" in the same fashion that core RedHat packages are (i.e timely security fixes, backported if needs be, for the lifetime of the OS release).

From the ruby193 SCL page you linked to:

"Community Project: Maintained by upstream communities of developers. The software is cared for, but the developers make no commitments to update the repositories in a timely manner."


Yeah, if they are in CentOS land it will be a bit touch and go (as usual).

But if you have a redhat subscription they are fully supported. I should have pointed that out in my first comment though, thanks for bringing it up :)

"All Red Hat Software Collections components are fully supported under Red Hat Enterprise Linux subscription terms of service. Components are functionally complete and intended for production use. " [0]

[0] <https://access.redhat.com/products/Red_Hat_Enterprise_Linux/...


An r720 from dell or similar model from dell with 600GB*2 SSD intel s3500DC model, 20 cores & 256GB of RAM will go for 5k-7k. You can bump this to 386GB of ram without going above 10k.


And up to 768GB if you go with 32GB LRDIMMs for about $14k (intel oem chassis).


When I changed the country to Japan, the sticker price jumped from 2000 USD to 15,000 USD eq. for a very basic system. I am just at a loss as to what can explain this disparity. Guess I will have to call up my vendor to get a comparable quote.


My tip is always to try to get in contact with a couple of reseller and play them out against each other in the price department.

If you are looking for larger purchases 50k+ USD than you should talk directly with Dell, HP or comparable vendor and put them into the play off for who you choose :)


I always do that. I have worked with Strategic Sourcing for a while...so... ;-)


Most of these are related to portable openssh and not openssh. These are two very different teams.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: