I'm ok with the amount of data "the man" has on me.
There's plenty of causes I care about, IP laws being the big one, but privacy is someone else's cause.
When the big collapse happens and I'm dragged off to the acid mines because I once ate at a Thai restaurant and had my phone turned on at the time, well, then you can be smug.
I just created an empty shell of a google+ account like most people.
I have a feeling this is what is driving google to get away from the mandatory google+ for everything. I reckon half of google+ is empty accounts created to make the prompts go away. To anyone who actually wants to use google+, they add all their friends only to find no actual activity.
For the time being, I can still legally get rid of the crap I don't want and install anything I do on my nexus. It's what makes google the least shitty in a pile of shitty options imo.
...not that I have any particular interest in the code, having seen the last release of slash, and the current bowl of shit that is beta. I'm more interested in the story behind it.
Sure, you can do this. Just as you can just maintain your own local version and not contribute it.
But it doesn't give the same warm fuzzies, isn't really worth it for a small bug fix, and there are plenty of projects out there that will happily accept your contributions.
I guess there is nothing wrong with contributing for the sake of it, but I think it's a lot more fun if you are working on something you care about, or better yet, will directly benefit you.
Most bug fixes I've contributed were just that, fixes to bugs that were giving me grief.
Also as someone else mentioned, communicate with the devs first (I like to join the IRC channel) and make sure they are interested in outside help. Most projects are, but a lot of smaller projects the devs don't want to accept patches from others. It's not that they are mean, it's that the project is their baby and reviewing someone elses work can be a chore. Also someone might already be working on the fix you want to contribute, or that whole area could be planned for a rewrite.. so definitely good idea to ask first.
Lest we forget Pacific Southwest Airlines Flight 1771, which saw a plane load of people killed because some guy didn't like that they got fired for stealing money (which he did, he was caught on camera).
And even if the system is secured (hah), all it takes is some malware on a controllers home computer (or if there is a work issued one, for one of them to let their kid install limewire (or whatever the current virus bag is) on it.
The vast majority of google+ accounts are probably empty shells created so youtube would stop prompting, which kinda makes the service look like a barren wasteland.
Gnome isn't really the problem (although despite not being a gnome user and having all the various anti-gnome flags, I still end up with a few odd packages pulled in by other stuff that screw things up). It's stuff like udev and stuff that depends on it. Straight up adding it to the blacklist (along with systemd itself) helps, but it still seems like for the first time in years, I'm nervous about running updates against world for fear of shit just randomly breaking.
Excessive re-usability was a fad in the mid 2000's, with everyone writing things as abstract as possible with the theory that "we could use this on some future projects". As it turned out, and as you stated, this stuff usually ended up getting used exactly once (in the project it was originally implemented in), all the abstract factories were implemented once, all the configurable dependency injection frameworks remained in a mostly static configuration, and all that was gained was a bunch of complexity (we don't have a "ClientConnection" class, we have a PeerToPeerDataTransfer class with a TCPConnectionBehaviour and a ClientTCPProtocol and a...).
These days things seem better, and most developers restrict reuse to within the scope of their design, or _maybe_ the scope of their companies product lines in cases where there is actually a possibility something may get reused. The days of "just make everything abstract in case" seem to be over.
Obviously this only applies to applications, libraries and things that are intended for wide reuse obviously are permitted a little more leeway.
Not just that, but running a non-systemd system even if you use a distro that uses openrc by default is becoming more of a pain as more and more packages hook into it. As a Gentoo user who is trying to hold off for just a little while longer I've found myself doing a lot of package shuffling and using the package blacklist for the first time in the almost decade I've been a gentoo user.
If you've got 10 years experience, that puts you in your prime. You've got the experience to be valuable, but are still affordable. I assume you're also at a point in your life where you can afford a little financial risk. It's time to use this to get into a job that you will enjoy and has the kind of work culture you want.
A lot of people out of school take the first gig that's willing to hire them. Some by random chance end up loving the job, others learn to accept it but gradually burn out. You sound like the second type. Time for a change.
How much money is Home Depot really gonna lose in this case? Maybe some liability? Probably cheaper to accept the risk than spend money on preventative measures which still might not be enough.
But surely people will be angry and vow to never shop there again? Nope. While it's in the news, sure, but people forget quickly. Remember how big the Sony/PSN thing was. I know people who swore they'd never do business with Sony ever again who currently own a PS4. As a whole, the thing has largely blown over and been forgotten about, as I'm sure this too will be.
Until there are real penalties to these kinda breaches, we'll keep seeing them.
I think it's more that Visa and MasterCard have partially fixed the problem from the other end, by making it harder to actually turn stolen numbers into cash in pocket.
The whole system is still a farce, but I feel slightly better when I buy something online that is outside my usual spending habits and my card is immediately locked followed by a phone call from VISA.
Obviously varies a lot by location, but I've found the Home Depot here to be one of the best as far as having people in departments that know their stuff. Spend a few minutes looking perplexed while staring at an isle and someone will ask if they can help. Last time I was there the guy in the plumbing department was ridiculously helpful.
Sure, if we straight up execute people for stealing credit cards then credit card theft would probably go away.
But then the same can be said about every crime, and personally even as a generally law abiding person, I don't think I want to live in a world where any crime means death by catapult or exile to the acid mines.
Mojang had been promising a proper mod API forever, somehow I doubt Microsoft will deliver.
On the vaguely plus side, if Microsoft lets Minecraft atrophy, at least modders won't be going after a moving target and we might finally get some stability.
I think the mod community is a big part of what is keeping the game popular right now. Most people burn out on vanilla minecraft after a few years, but there is a huge pile of mods that keep the game playable.
Once Microsoft kills off that community (I don't know how, but I'm sure they will), I suspect minecraft will indeed atrophy and die.
Have you ever met anyone considering a VPN who does neither?
Honestly, some people will hear these kind of terms referenced a lot in relation to security and decide they should have them without any understanding of what they actually provide (beyond security of course, which is what they want!).
Slashdot Mirror
In their defense, it's more like "update bash over and over again".
I'm ok with the amount of data "the man" has on me.
There's plenty of causes I care about, IP laws being the big one, but privacy is someone else's cause.
When the big collapse happens and I'm dragged off to the acid mines because I once ate at a Thai restaurant and had my phone turned on at the time, well, then you can be smug.
Unless you ascribe to an inconvenient level of diligence (and I don't), they already can.
I just created an empty shell of a google+ account like most people.
I have a feeling this is what is driving google to get away from the mandatory google+ for everything. I reckon half of google+ is empty accounts created to make the prompts go away. To anyone who actually wants to use google+, they add all their friends only to find no actual activity.
For the time being, I can still legally get rid of the crap I don't want and install anything I do on my nexus. It's what makes google the least shitty in a pile of shitty options imo.
I actually find myself liking google keep. I wanted a simple thing to make quick on-the-fly lists/notes.. and it delivers.
Calendar isn't bad either.
I find hangouts kinda clunky, but I use it because it's what was there and seems to work.
...not that I have any particular interest in the code, having seen the last release of slash, and the current bowl of shit that is beta. I'm more interested in the story behind it.
On a serious note, what ever happened to slash being open source. At some point they closed it up, but does anyone know when/why?
Sure, you can do this. Just as you can just maintain your own local version and not contribute it.
But it doesn't give the same warm fuzzies, isn't really worth it for a small bug fix, and there are plenty of projects out there that will happily accept your contributions.
Totally this.
I guess there is nothing wrong with contributing for the sake of it, but I think it's a lot more fun if you are working on something you care about, or better yet, will directly benefit you.
Most bug fixes I've contributed were just that, fixes to bugs that were giving me grief.
Also as someone else mentioned, communicate with the devs first (I like to join the IRC channel) and make sure they are interested in outside help. Most projects are, but a lot of smaller projects the devs don't want to accept patches from others. It's not that they are mean, it's that the project is their baby and reviewing someone elses work can be a chore. Also someone might already be working on the fix you want to contribute, or that whole area could be planned for a rewrite.. so definitely good idea to ask first.
Lest we forget Pacific Southwest Airlines Flight 1771, which saw a plane load of people killed because some guy didn't like that they got fired for stealing money (which he did, he was caught on camera).
Indeed.
And even if the system is secured (hah), all it takes is some malware on a controllers home computer (or if there is a work issued one, for one of them to let their kid install limewire (or whatever the current virus bag is) on it.
Exactly.
The vast majority of google+ accounts are probably empty shells created so youtube would stop prompting, which kinda makes the service look like a barren wasteland.
Gnome isn't really the problem (although despite not being a gnome user and having all the various anti-gnome flags, I still end up with a few odd packages pulled in by other stuff that screw things up). It's stuff like udev and stuff that depends on it. Straight up adding it to the blacklist (along with systemd itself) helps, but it still seems like for the first time in years, I'm nervous about running updates against world for fear of shit just randomly breaking.
Indeed.
Excessive re-usability was a fad in the mid 2000's, with everyone writing things as abstract as possible with the theory that "we could use this on some future projects". As it turned out, and as you stated, this stuff usually ended up getting used exactly once (in the project it was originally implemented in), all the abstract factories were implemented once, all the configurable dependency injection frameworks remained in a mostly static configuration, and all that was gained was a bunch of complexity (we don't have a "ClientConnection" class, we have a PeerToPeerDataTransfer class with a TCPConnectionBehaviour and a ClientTCPProtocol and a...).
These days things seem better, and most developers restrict reuse to within the scope of their design, or _maybe_ the scope of their companies product lines in cases where there is actually a possibility something may get reused. The days of "just make everything abstract in case" seem to be over.
Obviously this only applies to applications, libraries and things that are intended for wide reuse obviously are permitted a little more leeway.
Not just that, but running a non-systemd system even if you use a distro that uses openrc by default is becoming more of a pain as more and more packages hook into it. As a Gentoo user who is trying to hold off for just a little while longer I've found myself doing a lot of package shuffling and using the package blacklist for the first time in the almost decade I've been a gentoo user.
Totally agree.
If you've got 10 years experience, that puts you in your prime. You've got the experience to be valuable, but are still affordable. I assume you're also at a point in your life where you can afford a little financial risk. It's time to use this to get into a job that you will enjoy and has the kind of work culture you want.
A lot of people out of school take the first gig that's willing to hire them. Some by random chance end up loving the job, others learn to accept it but gradually burn out. You sound like the second type. Time for a change.
And the reason is obvious, people don't care.
How much money is Home Depot really gonna lose in this case? Maybe some liability? Probably cheaper to accept the risk than spend money on preventative measures which still might not be enough.
But surely people will be angry and vow to never shop there again? Nope. While it's in the news, sure, but people forget quickly. Remember how big the Sony/PSN thing was. I know people who swore they'd never do business with Sony ever again who currently own a PS4. As a whole, the thing has largely blown over and been forgotten about, as I'm sure this too will be.
Until there are real penalties to these kinda breaches, we'll keep seeing them.
I think it's more that Visa and MasterCard have partially fixed the problem from the other end, by making it harder to actually turn stolen numbers into cash in pocket.
The whole system is still a farce, but I feel slightly better when I buy something online that is outside my usual spending habits and my card is immediately locked followed by a phone call from VISA.
Obviously varies a lot by location, but I've found the Home Depot here to be one of the best as far as having people in departments that know their stuff. Spend a few minutes looking perplexed while staring at an isle and someone will ask if they can help. Last time I was there the guy in the plumbing department was ridiculously helpful.
And we have Chip & Pin here (Canada).
Sure, if we straight up execute people for stealing credit cards then credit card theft would probably go away.
But then the same can be said about every crime, and personally even as a generally law abiding person, I don't think I want to live in a world where any crime means death by catapult or exile to the acid mines.
Mojang had been promising a proper mod API forever, somehow I doubt Microsoft will deliver.
On the vaguely plus side, if Microsoft lets Minecraft atrophy, at least modders won't be going after a moving target and we might finally get some stability.
I think the mod community is a big part of what is keeping the game popular right now. Most people burn out on vanilla minecraft after a few years, but there is a huge pile of mods that keep the game playable.
Once Microsoft kills off that community (I don't know how, but I'm sure they will), I suspect minecraft will indeed atrophy and die.
Yeah yeah, that takes care of the obligatory reminder that funding something on kickstarter isn't the same as buying it at a store..
Maybe some people don't get that, but I for one back projects knowing full well that it's a gamble, and I've been pretty lucky.
Have you ever met anyone considering a VPN who does neither?
Honestly, some people will hear these kind of terms referenced a lot in relation to security and decide they should have them without any understanding of what they actually provide (beyond security of course, which is what they want!).