People like Vim because it's tiny, simple, powerful, and runs literally anywhere including platforms and situations (SSH, console on an embedded device serial port) where a GUI isn't available. Even the tiniest of Linux embedded systems that have user-interactive capability at all tend to have some sort of vi clone available, plus every Mac OS X, BSD, etc. come with it by default too. On Windows it's easy enough to install. Vim (well, vi clones in general) is pretty universal and has a ton of momentum behind it. You're probably not going to be running Notepad++ on Mac OS X or Linux, nor will you find it in BusyBox. Vim's memory usage is negligible compared to every GUI editor; I just opened a.c file and gVim 7 on Windows used 4MB total.
I don't know who those people are, nor do I care who they are or what their opinions are. IRC sucks and always has. An assertion of "inferior" always seems to be missing important parts of the assertion: to whom, for what purposes? Forums and mailing lists are objectively better than any chat application for situations where clearly thought out and sometimes very detailed responses that can be skimmed at the reader's leisure are desirable. I can subscribe to a mailing list or read a forum without a site-specific account; I can't do that with proprietary IRC on steroids clients like Slack and Discord. If I need to discuss in near real-time, chat makes a lot more sense and mailing lists and forums are unnecessarily slow and frustrating.
Uh...what part of "-style chat interface" did you not get? They didn't say it was IRC full stop, they said it's a chat interface in a similar style to IRC. Does storage and forwarding of messages and files while you're offline require a full web client and server packaged together as client software? Does voice chat? Does a membership and permissions system require that? None of what you're saying addresses the complaint being made regarding extreme resource usage for relatively simple software.
Remember that Skype supported chat, voice, and offline messaging even in the mid-2000s. It was built to work even on old Windows 2000 machines and in 2005 when even cheaper new machines were shipping with 512MB standard, it required that the machine have a minimum of 128MB of RAM for Skype plus the entire OS and other running software. Meanwhile, the post you responded to complained about multiple GB of RAM used by Slack a single application that doesn't do very much more than Skype from 2005 did and offers a proprietary system only instead of a universal standard like IRC or XMPP.
"App" is a short name for "application" and "application" in computer terms is just a synonym for "computer program used directly by the user." GUI interfaces are not required. Text-mode DOS programs were also referred to as "applications." While they are not 100% synonymous (the Linux kernel is not an "application," for example, nor is a system service such as a print spooler or database engine core) they are synonymous when referring to programs that are directly utilized by the computer's user. grep, sed, perl, Word, iMessage, and Firefox are all categorizable as both applications and programs, or just "application programs." The most correct term to exclude non-GUI software would be "desktop application" which implies a graphical "desktop" environment is required, though in the age of smartphones the desktop paradigm is not always part of a GUI anymore.
tl;dr: all apps are programs, not all programs are apps, GEOS is better than Windows 10
Second this. I have run a computer repair shop for 10 years and I'd love to help someone like OP get their stuff straightened out. I'm in the computer service business because I both enjoy it and am damn good at it. I'm not perfect by any means, and I'm not going to offer some sales-tactic bogus "warranty" on my services that is extremely easily BOFH'd out of anyway (never underestimate a retail computer service guy's ability to make something up on the spot) but I bet you that within a month of bringing me on board the improvements in their systems would be paying my invoices.
See, the thing is that I'm only one person and I don't NEED them, so I don't run around actively searching for them, and even if I did...how would I ever find out that they had a need in the first place? They have to search for me and come to me. They need to make that phone call and tell me what's going on and ask if I can help them. I'd probably say yes. If they don't look around and ask questions, they'll never find what they're after; they'll get another "three-year warranty" snake that collects a fat paycheck for doing a lackluster job.
Oh yeah, that's right, but you forgot the bestest part: 9/10 times, they just go ahead and mark their boilerplate as the "solution" and then the comments get flooded with extremely angry techies who can see that the suggestions will do nothing to help. If someone said that their printer was printing PCL errors, the idiots would suggest a "clean boot state" and mark that as answered when it's plain to anyone that "clean boot" will do nothing to help at all.
Then guess what the follow-up advice is? "Reinstall Windows." Except imagine it with more flowery non-native speaker nonsense. "Kindly please install the operating system to a clean status." Or perhaps "kindly bend over and let Microsoft service the customer."
Cleaning up old folders immediately after redirection is fine; they should have been moved as part of the redirection process, so there should be an empty folder that gets deleted upon completion of redirection. Cleaning up old folders DURING A FEATURE UPDATE that WOULD HAVE been cleaned up after a redirection is a big fat no-no that never should have been written into the code in the first place. Anyone who understands what user shell folder redirection is and what its purpose is can plainly see how bad of an idea it is: if the folder exists after redirection then it's a user-created data folder, not part of a redirection, and should be considered untouchable by all OS self-maintenance such as updates. There are clearly some seriously dysfunctional programmers and sysadmins making their way into Microsoft. The simple fact that this sort of stupid mistake made it out the door is proof that Microsoft has a staff competence issue. Perhaps they can't help in MS Answers because they are losing the ability to maintain the system properly in the first place.
I'm going to copy and paste the most salient points of the stock BS answer that is given to almost EVERYONE that has an issue with Windows 10 these days and says something about it on the Microsoft Answers forum:
This issue may occur either due to software conflicts or if unused files are present in Windows. I would suggest you to run system maintenance troubleshooter and check if it helps.... If it does not help, then perform clean boot and check. Refer this article: How to perform a clean boot in Windows... After you have finished troubleshooting, follow these steps from section “How to reset the computer to start as usual after clean boot troubleshooting” to reset the computer to start as usual.
And then in the following comments there are floods of users saying THIS DID NOT HELP, PLEASE GIVE US SOME F***ING REAL HELP. It's like this regardless of the actual problem. It's always someone with an Indian name posting the "solution" and it's always the same basic boilerplate garbage suggestions that don't solve the problem. There is never any follow-up. There is an intervention by an actual Microsoft product team employee that can legitimately help on an extremely rare basis. On a related note, I'm fairly convinced that Feedback Hub is a fancy way of referring to/dev/null because Microsoft seems to ignore all user feedback that doesn't align with what they wanted to do anyway.
I swear, dealing with the Windows 8+ era Microsoft is like dealing with a petulant three-year-old on a constant basis, one that will deactivate or crash your shit at random and pull a South Park BP executive style "we're sorry!" when it becomes big tech news.
It was an analogy, not a straw man. I used your expressed logic to show how foolish that logic was. Not everyone is as blatantly self-centered as you seem to be. You speak for one user out of billions; you are way below the noise floor. The ban on Napalm Girl, on the other hand, sparked outrage from many thousands. It seems you've already lost the popular vote on the subject.
The definitive Facebook nudity policy mistake: Napalm Girl from the Vietnam War. The moral terror that photo inspires must never be forgotten...but hey, we gotta ban it because prepubescent genitals! Not the destruction, violence, pain, and mortal horror, mind you. Just the naked kid with third-degree burns on her back and arm. Someone might mistake it for pornography, you know.
If you want to know what happened to the girl after that photo, I encourage you to read this. It's definitely worth it.
Accent on "clear." The Contributor Covenant is intentionally vague and interpretation is highly subjective, modifiable on-the-fly based upon what others say their feelings are. Clear community guidelines also don't have a bullet-point that says, and I quote, "Other conduct which could reasonably be considered inappropriate in a professional setting." What is reasonable, appropriate, and/or professional varies so wildly between different people, corporate cultures, and cultures in general that such a statement can only exist to open the doors to abuse by bad faith actors.
It seems like a good idea to include a blanket "...but we might not have thought of everything so here's a vague rule covering those eventualities" when you're dealing exclusively with those acting in good faith, but legal codes are written in legalese instead of vague "be nice, don't be not-nice" statements (like that of any given Code of Conduct) because any subjectivity in the rules that bind a person makes it impossible for them to know that they're breaking rules a priori, requiring that a rule be broken to discover what breaks the rules. Judicial systems must suffer through this because no law can be crafted to cover every possible current and future possibility, but it is extremely undesirable and problematic to intentionally set up the rules this way if you have a need for rules in the first place.
In other words, if a Code of Conduct is determined to be necessary (only true if bad actors already exist or are very likely to appear) then that determination automatically indicates a Code of Conduct such as the Contributor Covenant is not appropriate and will only shift problems from poor conduct to extensive rules lawyering by the same bad actors the project was trying to avoid, and with vague rules there are a myriad of ways to verbally bend them to fit a particular narrative. Carefully worded by-laws that are concrete and close loopholes of vagueness are the only workable and acceptable solution.
Codes of Conduct are only "required" if you have a sudden influx of intolerable people...such as the ones that show up screeching for a "Code of Conduct." Everyone else that's already involved in an established project capable of being (or at least emulating which is plenty good enough) some sort of a socially capable without someone else providing a scroll of vague platitudes with concrete punishment requirements that can be exploited to oust wrong-thinkers for the most minor and forgivable of transgressions.
Damn straight. No one who uses SQLite is going to swap it out over an incredibly stupid political holy war that most "show me the code" geeks don't give a fuck about and want to go away a million times faster than it appeared on their doorstep.
As well as the ability to disable forced automatic updates entirely. Most of Windows 10's stability and data loss problems stem from automatic updates. Let the user choose where the "threshold" between security and stability should fall.
In the video posted by the artist to Instagram you can see how it's built. It's a bunch of little modeling knife blades and a motor. It doesn't look terribly complex, and it wouldn't take a lot of engineering at all. You can buy push-button key fob remotes on eBay that trigger a relay on the receiving end. All he/she would have to do is have one of those receivers activate the motor while the button is pressed and stop when the button is released. Voila, half-shredded painting.
Between this and the copyright/link tax shit, the EU is basically begging to be cut off from the rest of the internet. You fucking EU citizens under 50 need to start voting these insane morons out.
There's no reason China can't just shovel the goods through some other East Asian country for a smaller fee than the tariffs cost and lie about the origin of the goods. Oh, see, this was "made in Thailand" so it's not Chinese, so no tariff. The problem with a trade war like this is that if China rebadges the origin of goods and the US doesn't, the US is guaranteed to lose. They already manipulated the snot out of their currency to pilfer the US infrastructure, so it would be zero surprise if they got around the tariffs this way. Ironically, shady stuff like that is what the tariffs are supposed to punish in the first place.
Probably needing the ftype=1 feature that enables d_type support which was not available until a few years ago and requires a fresh run of mkfs.xfs to enable. With d_type you can find out if a file is a directory, link, FIFO, regular file, etc. straight from readdir() without an extra stat() call for every file in the directory, but not all filesystems support it so falling back to stat() when d_type == DT_UNKNOWN is mandatory. I fixed a bug in dupd caused by assuming d_type always returned a good value, which failed on an XFS v4 volume and rendered the program unusable.
Slashdot Mirror
People like Vim because it's tiny, simple, powerful, and runs literally anywhere including platforms and situations (SSH, console on an embedded device serial port) where a GUI isn't available. Even the tiniest of Linux embedded systems that have user-interactive capability at all tend to have some sort of vi clone available, plus every Mac OS X, BSD, etc. come with it by default too. On Windows it's easy enough to install. Vim (well, vi clones in general) is pretty universal and has a ton of momentum behind it. You're probably not going to be running Notepad++ on Mac OS X or Linux, nor will you find it in BusyBox. Vim's memory usage is negligible compared to every GUI editor; I just opened a .c file and gVim 7 on Windows used 4MB total.
I don't know who those people are, nor do I care who they are or what their opinions are. IRC sucks and always has. An assertion of "inferior" always seems to be missing important parts of the assertion: to whom, for what purposes? Forums and mailing lists are objectively better than any chat application for situations where clearly thought out and sometimes very detailed responses that can be skimmed at the reader's leisure are desirable. I can subscribe to a mailing list or read a forum without a site-specific account; I can't do that with proprietary IRC on steroids clients like Slack and Discord. If I need to discuss in near real-time, chat makes a lot more sense and mailing lists and forums are unnecessarily slow and frustrating.
Microsoft centralized Skype for data siphoning and control; everything else is a side effect. Skype has also been absolute trash ever since they did so. P2P Skype worked just fine when both people were behind NATs; it's called UDP hole punching and it is quite effective for the type of NAT that is in widespread use in homes and small businesses. I'd hardly call Electron a native application; if anything, it's more of an elaborate emulator.
Yeah, that's the sort of thing that Skype was for. Well, until they screwed that up too.
Uh...what part of "-style chat interface" did you not get? They didn't say it was IRC full stop, they said it's a chat interface in a similar style to IRC. Does storage and forwarding of messages and files while you're offline require a full web client and server packaged together as client software? Does voice chat? Does a membership and permissions system require that? None of what you're saying addresses the complaint being made regarding extreme resource usage for relatively simple software.
Remember that Skype supported chat, voice, and offline messaging even in the mid-2000s. It was built to work even on old Windows 2000 machines and in 2005 when even cheaper new machines were shipping with 512MB standard, it required that the machine have a minimum of 128MB of RAM for Skype plus the entire OS and other running software. Meanwhile, the post you responded to complained about multiple GB of RAM used by Slack a single application that doesn't do very much more than Skype from 2005 did and offers a proprietary system only instead of a universal standard like IRC or XMPP.
"App" is a short name for "application" and "application" in computer terms is just a synonym for "computer program used directly by the user." GUI interfaces are not required. Text-mode DOS programs were also referred to as "applications." While they are not 100% synonymous (the Linux kernel is not an "application," for example, nor is a system service such as a print spooler or database engine core) they are synonymous when referring to programs that are directly utilized by the computer's user. grep, sed, perl, Word, iMessage, and Firefox are all categorizable as both applications and programs, or just "application programs." The most correct term to exclude non-GUI software would be "desktop application" which implies a graphical "desktop" environment is required, though in the age of smartphones the desktop paradigm is not always part of a GUI anymore.
tl;dr: all apps are programs, not all programs are apps, GEOS is better than Windows 10
Second this. I have run a computer repair shop for 10 years and I'd love to help someone like OP get their stuff straightened out. I'm in the computer service business because I both enjoy it and am damn good at it. I'm not perfect by any means, and I'm not going to offer some sales-tactic bogus "warranty" on my services that is extremely easily BOFH'd out of anyway (never underestimate a retail computer service guy's ability to make something up on the spot) but I bet you that within a month of bringing me on board the improvements in their systems would be paying my invoices.
See, the thing is that I'm only one person and I don't NEED them, so I don't run around actively searching for them, and even if I did...how would I ever find out that they had a need in the first place? They have to search for me and come to me. They need to make that phone call and tell me what's going on and ask if I can help them. I'd probably say yes. If they don't look around and ask questions, they'll never find what they're after; they'll get another "three-year warranty" snake that collects a fat paycheck for doing a lackluster job.
Oh yeah, that's right, but you forgot the bestest part: 9/10 times, they just go ahead and mark their boilerplate as the "solution" and then the comments get flooded with extremely angry techies who can see that the suggestions will do nothing to help. If someone said that their printer was printing PCL errors, the idiots would suggest a "clean boot state" and mark that as answered when it's plain to anyone that "clean boot" will do nothing to help at all.
Then guess what the follow-up advice is? "Reinstall Windows." Except imagine it with more flowery non-native speaker nonsense. "Kindly please install the operating system to a clean status." Or perhaps "kindly bend over and let Microsoft service the customer."
Cleaning up old folders immediately after redirection is fine; they should have been moved as part of the redirection process, so there should be an empty folder that gets deleted upon completion of redirection. Cleaning up old folders DURING A FEATURE UPDATE that WOULD HAVE been cleaned up after a redirection is a big fat no-no that never should have been written into the code in the first place. Anyone who understands what user shell folder redirection is and what its purpose is can plainly see how bad of an idea it is: if the folder exists after redirection then it's a user-created data folder, not part of a redirection, and should be considered untouchable by all OS self-maintenance such as updates. There are clearly some seriously dysfunctional programmers and sysadmins making their way into Microsoft. The simple fact that this sort of stupid mistake made it out the door is proof that Microsoft has a staff competence issue. Perhaps they can't help in MS Answers because they are losing the ability to maintain the system properly in the first place.
I'm going to copy and paste the most salient points of the stock BS answer that is given to almost EVERYONE that has an issue with Windows 10 these days and says something about it on the Microsoft Answers forum:
... If it does not help, then perform clean boot and check. Refer this article: How to perform a clean boot in Windows ... After you have finished troubleshooting, follow these steps from section “How to reset the computer to start as usual after clean boot troubleshooting” to reset the computer to start as usual.
/dev/null because Microsoft seems to ignore all user feedback that doesn't align with what they wanted to do anyway.
This issue may occur either due to software conflicts or if unused files are present in Windows. I would suggest you to run system maintenance troubleshooter and check if it helps.
And then in the following comments there are floods of users saying THIS DID NOT HELP, PLEASE GIVE US SOME F***ING REAL HELP. It's like this regardless of the actual problem. It's always someone with an Indian name posting the "solution" and it's always the same basic boilerplate garbage suggestions that don't solve the problem. There is never any follow-up. There is an intervention by an actual Microsoft product team employee that can legitimately help on an extremely rare basis. On a related note, I'm fairly convinced that Feedback Hub is a fancy way of referring to
I swear, dealing with the Windows 8+ era Microsoft is like dealing with a petulant three-year-old on a constant basis, one that will deactivate or crash your shit at random and pull a South Park BP executive style "we're sorry!" when it becomes big tech news.
The users pay for it. They don't write the checks, but they most certainly are paying for it.
Who decides importance?
It was an analogy, not a straw man. I used your expressed logic to show how foolish that logic was. Not everyone is as blatantly self-centered as you seem to be. You speak for one user out of billions; you are way below the noise floor. The ban on Napalm Girl, on the other hand, sparked outrage from many thousands. It seems you've already lost the popular vote on the subject.
Why do we need to see your comments on Slashdot? Does the world revolve around you? No, it doesn't.
The definitive Facebook nudity policy mistake: Napalm Girl from the Vietnam War. The moral terror that photo inspires must never be forgotten...but hey, we gotta ban it because prepubescent genitals! Not the destruction, violence, pain, and mortal horror, mind you. Just the naked kid with third-degree burns on her back and arm. Someone might mistake it for pornography, you know.
If you want to know what happened to the girl after that photo, I encourage you to read this. It's definitely worth it.
Accent on "clear." The Contributor Covenant is intentionally vague and interpretation is highly subjective, modifiable on-the-fly based upon what others say their feelings are. Clear community guidelines also don't have a bullet-point that says, and I quote, "Other conduct which could reasonably be considered inappropriate in a professional setting." What is reasonable, appropriate, and/or professional varies so wildly between different people, corporate cultures, and cultures in general that such a statement can only exist to open the doors to abuse by bad faith actors.
It seems like a good idea to include a blanket "...but we might not have thought of everything so here's a vague rule covering those eventualities" when you're dealing exclusively with those acting in good faith, but legal codes are written in legalese instead of vague "be nice, don't be not-nice" statements (like that of any given Code of Conduct) because any subjectivity in the rules that bind a person makes it impossible for them to know that they're breaking rules a priori, requiring that a rule be broken to discover what breaks the rules. Judicial systems must suffer through this because no law can be crafted to cover every possible current and future possibility, but it is extremely undesirable and problematic to intentionally set up the rules this way if you have a need for rules in the first place.
In other words, if a Code of Conduct is determined to be necessary (only true if bad actors already exist or are very likely to appear) then that determination automatically indicates a Code of Conduct such as the Contributor Covenant is not appropriate and will only shift problems from poor conduct to extensive rules lawyering by the same bad actors the project was trying to avoid, and with vague rules there are a myriad of ways to verbally bend them to fit a particular narrative. Carefully worded by-laws that are concrete and close loopholes of vagueness are the only workable and acceptable solution.
Codes of Conduct are only "required" if you have a sudden influx of intolerable people...such as the ones that show up screeching for a "Code of Conduct." Everyone else that's already involved in an established project capable of being (or at least emulating which is plenty good enough) some sort of a socially capable without someone else providing a scroll of vague platitudes with concrete punishment requirements that can be exploited to oust wrong-thinkers for the most minor and forgivable of transgressions.
Aww, the poor baby's ideology got sprained.
Damn straight. No one who uses SQLite is going to swap it out over an incredibly stupid political holy war that most "show me the code" geeks don't give a fuck about and want to go away a million times faster than it appeared on their doorstep.
As well as the ability to disable forced automatic updates entirely. Most of Windows 10's stability and data loss problems stem from automatic updates. Let the user choose where the "threshold" between security and stability should fall.
In the video posted by the artist to Instagram you can see how it's built. It's a bunch of little modeling knife blades and a motor. It doesn't look terribly complex, and it wouldn't take a lot of engineering at all. You can buy push-button key fob remotes on eBay that trigger a relay on the receiving end. All he/she would have to do is have one of those receivers activate the motor while the button is pressed and stop when the button is released. Voila, half-shredded painting.
Titling in videos can be annoying and having varied width options for fonts like this can help a lot with video titling. I like this!
Agreed; I was addressing the abysmal young voter turnout relative to old voters. It's almost a 2:1 disparity.
Between this and the copyright/link tax shit, the EU is basically begging to be cut off from the rest of the internet. You fucking EU citizens under 50 need to start voting these insane morons out.
There's no reason China can't just shovel the goods through some other East Asian country for a smaller fee than the tariffs cost and lie about the origin of the goods. Oh, see, this was "made in Thailand" so it's not Chinese, so no tariff. The problem with a trade war like this is that if China rebadges the origin of goods and the US doesn't, the US is guaranteed to lose. They already manipulated the snot out of their currency to pilfer the US infrastructure, so it would be zero surprise if they got around the tariffs this way. Ironically, shady stuff like that is what the tariffs are supposed to punish in the first place.
Probably needing the ftype=1 feature that enables d_type support which was not available until a few years ago and requires a fresh run of mkfs.xfs to enable. With d_type you can find out if a file is a directory, link, FIFO, regular file, etc. straight from readdir() without an extra stat() call for every file in the directory, but not all filesystems support it so falling back to stat() when d_type == DT_UNKNOWN is mandatory. I fixed a bug in dupd caused by assuming d_type always returned a good value, which failed on an XFS v4 volume and rendered the program unusable.