> But proven bank deposits over multiple years also counts.
That's just one factor. Banks are looking to minimize risk and from the perspective of banks, self-employment increases risk. That's not to say banks won't loan to you, just that the hurdle is much higher for you to prove that you are not a risk. Chances are your interest rates will still suffer even when a bank decides to loan to you.
> high price communities where everything works, surrounded by large swaths of shanty towns where nothing works.
This isn't something that's only attributable to CA. Economically depressed towns relatively close to highly concentrated areas of wealth are all over America. Also, the scale of poverty in places like the south, Appalachia, the rust belt, rural America often meets or exceeds that of third-world countries.
Wholesale data collection has become normalized in the US. For-profits, non-profits, it doesn't matter the industry, everyone is obsessed with capturing as much data as possible and believe it's just the standard way of business. No one outside of HN cares about PII or has an understanding of things like GDPR (it's just for the Europeans). Consumers are clueless or otherwise feel hopeless.
Just want to say for the sake of others reading that this comment is exaggerating + generalizing a bit.
Everyone is not obsessed with turning data into revenue. Most smaller tech companies (ie. Sub billions in revenue) are not in the game of monetizing data. My feeling is the market exists mostly between very well establish and very large companies (such as ISPs, advertising networks), but that same market doesn’t exist between newer / smaller companies that haven’t reached massive scale.
To anyone in the EU: is GDPR something that your non-technical friend will have heard of and knows what it is? Or is it similar to the US, where 75% of people probably haven’t heard of it or if they have, couldn’t say what the regulation does.
Everyone in the EU has heard of it, at least for the fact that everyone received a whole bunch of email that mentioned it on May 25th 2018. I'd say a lot of people know that "it's about privacy"; the actual understanding obviously varies.
No one heard about it, at least in Spain. My father asked me about it because he heard it on the news, but I'd say that 99% of my non-tech friends have no idea of what it is about. Anyway, I work for a large telco and they are very paranoid liabilities involving data. It's a behemoth, so you wouldn't expect them to be this careful.
As far as I remember, they still sell some anonymized data (they had some demos on how to plan public transport with location data) and I'd bet they are not doing much with DNS data.
> To anyone in the EU: is GDPR something that your non-technical friend will have heard of and knows what it is? Or is it similar to the US, where 75% of people probably haven’t heard of it or if they have, couldn’t say what the regulation does.
Basically everyone who is in EU needs to keep GDPR in mind. Especially if you are employed, then you need to keep in mind GDPR for the interests of your employer so that they are abiding the law, and won't get fined. It is actually legal people who know GDPR very well; not so much tech people. In a lot of Dutch companies a "functionaris gegevensbescherming" (FG; data protection officer) is mandatory, who basically deal with PII, and have known about GDPR (AVG) ever since it was announced it was going to be active (2 years before it was active). The Dutch professional association for the data protection officer was founded in 2003 [1].
On top of that, it was widely covered in newspapers, daily news, etc. If you are in EU and you have not heard about it you are living under a rock, or you're not a working adult (nothing wrong with either).
Anyone working in an office will have probably come in contact with GDPR. Blue collar workers probably not so much.
Maybe people will know it as the cause of cookie popup screens. But I'm also grossly over-estimating computer literacy among the general population so maybe not.
Anyone in the UK who does an office job has heard of GDPR. Most companies are having to update practices to comply with it. It's actually amazing how effective it's been at curbing the "let's just store everything" behaviour.
I think the lede is buried here, since it doesn't sound like any of them regretted their decision of seeking more meaningful work. The take-away seems to be that it may not happen right away with the first job you take and it may take some time to get adjusted (from a high-earning lifestyle).
Yes each of those websites still use PHP under the hood. But by that argument each of those websites can be counted as using C as well. As well as machine code.
It has nothing to do with the code being spaghetti or not. It's about a level of abstraction where I no longer consider something made with wordpress as something created with PHP. The PHP was allready created and then someone just clicked a few menus to choose what existing PHP he or she wanted.
The more fitting category would be just calling such websites "Wordpress" websites and not PHP websites.
The categorisation you are trying to make us accept is ridiculous.
I can deploy a python web application I have written to a new web server within minutes by clicking deploy in bitbucket.
So using your definition:
* The code is already written.
* I clicked a few menus and I had the python code I wanted running.
It isn't a python application. However the web application when it receives a request will run python code. It is clearly a python based web application.
I wouldn't consider it python code if it is a cookie cutter website where the creator didn't have to write a single line of python. It's not about deployment it's about the process of creation. Why don't you consider each and every website running PHP also a C website?
> I wouldn't consider it python code if it is a cookie cutter website where the creator didn't have to write a single line of python.
So if I got someone else to press the deploy button in bitbucket, it suddenly isn't python code? That doesn't make sense does it?
> Why don't you consider each and every website running PHP also a C website?
The web site/app logic is written in PHP, not C. The runtime for the vast majority of PHP deployments happens to be written in C.
Additionally while I did say interpreted earlier that really isn't true anymore. PHP runtimes these days tend to break the PHP script down into byte-code. There are alternative runtimes for PHP just as there is Java or .NET.
There are at least 4 I can think of. Two of those aren't C (C++ and .NET). However there is nothing stopping you from writing a runtime that runs on the JVM / Lisp / Go / Brainfuck / Lol code / 68k assembler.
> So if I got someone else to press the deploy button in bitbucket, it suddenly isn't python code? That doesn't make sense does it?
You completely ignored the most important sentence in my comment which addresses this.
> The web site/app logic is written in PHP, not C. The runtime for the vast majority of PHP deployments happens to be written in C.
The logic is written in PHP just as much as it is written in C. The logic is actually written in the language the creator used. Which is the wordpress UI.
Eh, that's not really the case anymore either. It's made many improvements over the years. Not that I'm saying it's some wonderful language, but you can't really compare it to the PHP 4/early 5 days. I think credit is deserved to the folks who have brought PHP to where it is today.
I thought you were kidding and then I read their bio. What an interesting choice for a startup shaving company. I'm surprised Unilever hasn't axed it by now after they made the acquisition.
That's just one factor. Banks are looking to minimize risk and from the perspective of banks, self-employment increases risk. That's not to say banks won't loan to you, just that the hurdle is much higher for you to prove that you are not a risk. Chances are your interest rates will still suffer even when a bank decides to loan to you.