News for hackers. Stuff that matters.
Re:How much your computer can do in a second by agumonkey on Sunday March 26, 2017 @11:10AM (#13961153)
The market is wasteful. Lots of things are subpar because of the competition requiring adhoc solutions pushed to market, then becoming standard, so on and so forth. You can blame the game or not. At least if there was some acknowledgement of that process and a little cleanup time to spread good ideas and good fix ...

Personally I always feel weird booting up old boxes (say old = Pentium 2) and realizing how much the whole platform could do. It also felt quite sufficient in terms of UX and presentation.

That's odd because, everybody (I assume) feels how quickly we feel our newest gear gets slow, and how a new generation improves speed. But when I pop a very old system I don't feel slowed down much. It's just of a lesser resolution (hi res images, sound, videos); which for my needs doesn't really matter.

Re:How much your computer can do in a second by gizmo on Sunday March 26, 2017 @11:32AM (#13961259)
An eye-opening experience is running an IDE like Visual Studio 6 or a really old version of Photoshop on a modern machine. It starts instantly, compile times are a fraction of what we're used to. The interface is totally responsive. It's remarkable how much better software feels when everything is instant.
Re:How much your computer can do in a second by em3rgent0rdr on Sunday March 26, 2017 @01:24PM (#13961851)
It's remarkable how much better software feels when the software was developed on a slow machine.

Unfortunately devs invest in the fastest equiplent, so they don't experience how their code runs on the average end user who doesn't upgrade every couple years.

In can be useful to test your code in a VM that is deliberately slowed down, so can get a feel for user experience on a slower machine. Then you'll know what parts need to be optimized.

Re:How much your computer can do in a second by Gracana on Sunday March 26, 2017 @06:42PM (#13963790)
> Unfortunately devs invest in the fastest equiplent, so they don't experience how their code runs on the average end user who doesn't upgrade every couple years.

As someone who doesn't spend much on computer upgrades, I notice this everywhere. Especially when it comes to web development, where everything is optimized for chrome on mac. Don't have a laptop made in the last year? Enjoy a janky-scrolling slow-loading hard-to-read mess.

Re:How much your computer can do in a second by snackai on Sunday March 26, 2017 @08:46PM (#13964303)
Also, the web devs have no idea how slow the connections in even the western world can be. At least I think so, if they had to experience a 4 Mbit/s connection more often they wouldn't push for Angular and such.
Re:How much your computer can do in a second by adrianN on Monday March 27, 2017 @04:05AM (#13965919)
4Mbit/s is slow nowadays?
Re:How much your computer can do in a second by megablast on Sunday March 26, 2017 @06:24PM (#13963686)
Unfortunately devs aren't given any time to optimise it to run on slow machines. It is not a priority.
Re:How much your computer can do in a second by ryukafalz on Sunday March 26, 2017 @07:35PM (#13964021)
You don't necessarily need to specifically optimize for it: just do your development on a slower machine. If you're using a compiled language, you can offload compilation with something like distcc for productivity's sake, but all your testing should be on the slow machine.

It'll be pretty clear if some change you've made is going to impact people on older hardware, because you'll notice the moment you make the change. And if it's unbearably slow for you, it will be for a good chunk of your users as well.

Re:How much your computer can do in a second by userbinator on Sunday March 26, 2017 @11:51AM (#13961349)
Developer tools like Visual Studio are somewhat ironic in that the developers who create inefficient software are essentially seeing this reflected indirectly in their tools also becoming inefficient. A perverse version of "do unto others as you would have them do unto you"?
Re:How much your computer can do in a second by agumonkey on Sunday March 26, 2017 @11:56AM (#13961377)
I used to think that of the java world. It wasn't above some critical mass / threshold of simplicity, and everybody that liked java lacked that simplicity, and every solutions they tried to add to java just added more cruft (xml, j2ee beans, IDEs)
Re:How much your computer can do in a second by bcook on Sunday March 26, 2017 @12:33PM (#13961572)
Similarly, I run a very barebones Openbox Arch Linux install on my ancient 2Ghz Turion 64 laptop and I recently booted Windows XP on it and I was blown away by how fluid & responsive the entire system was compared to my much newer Linux-based OS.
Re:How much your computer can do in a second by agumonkey on Sunday March 26, 2017 @12:35PM (#13961584)
Also, surprisingly, XP could handle 64MB decently (even for a nazi like me)
Re:How much your computer can do in a second by flukus on Sunday March 26, 2017 @08:05PM (#13964162)
My memory is very blurred, but I thought 32MB (maybe less) was still pretty standard when XP came out.
Re:How much your computer can do in a second by logicallee on Sunday March 26, 2017 @11:57AM (#13961381)
>An eye-opening experience is running an IDE like Visual Studio 6 or a really old version of Photoshop on a modern machine. It starts instantly, compile times are a fraction of what we're used to. The interface is totally responsive.

If you gave that to a Product Manager candidate (as part of an interview) and pretended it's your current product (assume they didn't know it already), asked them to play around with it for ten minutes and as their task come up with some thoughts regarding what they would add or improve, their eyes would pop open and they would say, "WOWWW!! THIS LOOKS LIKE IT ISN'T DOING ANYTHING -- THERE IS A LOT OF ROOM FOR IMPROVEMENT HERE."

And in just fifteen minutes, they would gleefully tell you exactly how they would break it. (By adding crap to make it slow.)

(Note: this could be run as a real experiment, but the results above are my personal prediction - maybe it wouldn't happen as I predict.)

I really do think product managers are the people to blame here. To them, fast = broken or not doing anything. It's not done (to them) until it's (to us) broken.

Re:How much your computer can do in a second by flukus on Sunday March 26, 2017 @08:09PM (#13964180)
A lot of places I've worked had government incentives to do this too. Adding features is "R&D" and attracts less payroll tax than optimizing bugs does. Other companies structure themselves this way, a feature is something you can charge to another department, an optimization isn't.
Re:How much your computer can do in a second by dbattaglia on Sunday March 26, 2017 @09:36PM (#13964489)
I've worked at one place in particular that fell in love with what I call FDD, Finance Driven Development. There's few things more demoralizing than watching systems you helped design fall apart because bug fixes aren't capitalizable.
Re:How much your computer can do in a second by tedunangst on Sunday March 26, 2017 @12:03PM (#13961408)
Or start with the current version, then demo the ancient version, and claim you've "streamlined and tuned" the program?
Re:How much your computer can do in a second by logicallee on Sunday March 26, 2017 @12:19PM (#13961486)
What I was getting at is that the suggestions to add crap would come from the product manager candidate themselves - thereby "proving" (if the results match my prediction) that the requirement for slow unresponsive interfaces come directly from the PM's, who would add it if it weren't already slow.

Like, I want the experiment to test if a product isn't already slow, would a product manager actively make it slow? (I think, "yes".)

Re:How much your computer can do in a second by gizmo on Sunday March 26, 2017 @12:33PM (#13961573)
When software is too slow it hurts sales. When software lacks features that hurts sales too. Faster doesn't make for compelling marketing (anybody can claim their software is fast) but you can get people to upgrade for new features. So features are added with every release and performance improvements are made up so to the point where it's "good enough" again. You don't need a product manager conspiracy to explain why software is bloated and slow.
Re:How much your computer can do in a second by logicallee on Sunday March 26, 2017 @12:48PM (#13961649)
Okay, so let's update the experiment protocol.

So the hypothesis is that if it's too fast it's not considered done by a product manager. So as an updated test protocol, let us repeat with two groups of Product Managers, and this time they must evaluate the software, which they have never used before. Some candidates get the older version on the metal, and others get the older version slowed down 10x for example by running in a VM on the test machine, or simply being shown to them running on older hardware but otherwise an identical setup.

My hypothesis is that the exact same software running slowly would be objectively judged as better by Product Managers than the same software running instantly. That instant execution is considered an explicit negative point - completely independent of features. So that if the old software running slowly gets 7.5/10 rating by the Product Managers asked to evauate it, it would get only a 5/10 rating if it runs instantly.

This controls for the features which you mention. So I've suggested a test protocol, of course I can't verify it just at this moment but at least I am being scientific in my suggestion that Product Managers simply rate fast software worse. If you have an alternative protocol to test this, one that is easier to run, I'd like to hear it.

Re:How much your computer can do in a second by gizmo on Sunday March 26, 2017 @02:25PM (#13962232)
If slowness is the goal and if product managers insist on slowness, then you'd expect a lot of sleep() calls in commercial software (which has product managers) and no sleep() calls in open source software. This doesn't happen.

What we see is that commercial software has better documentation, gets more long term maintenance and support, and supports more cumbersome enterprise features. Exactly what you'd expect when you have salespeople and product managers who talk to customers.

Your hypothesis is falsifiable, which is a necessary but not a sufficient condition for it to be scientific. For it to be scientific you would also have to provide evidence that your hypothesis is more plausible than the alternatives, before you do any experiments. After all, it's easy to come up with thousands of silly hypothesis, and by happenstance some of them will get a positive correlation when tested. So every hypothesis has to undergo serious scrutiny.

Re:How much your computer can do in a second by tedunangst on Sunday March 26, 2017 @02:57PM (#13962433)
Actually, some software like facial recognition or OCR, does have sleep calls inserted because people don't believe it can be done as fast as it can be done. Thus, whenever I deposit checks at the ATM, I have to stand there and watch as some entirely unnecessary animation pretends to scan my check for ten seconds before I can have my card back.
Re:How much your computer can do in a second by gizmo on Sunday March 26, 2017 @03:16PM (#13962550)
Yes, the same applies to save buttons. If saving takes less than 200ms people are not confident the save really happened. There are also UI animations that deliberately slow things down to prevent the user from getting disoriented. This doesn't prove that product managers want software to be slow though.
Re:How much your computer can do in a second by tedunangst on Sunday March 26, 2017 @03:25PM (#13962598)
Agreed. I think PMs have their own motivations, but ruining things for others is not explicitly part of their grand plan.
Re:How much your computer can do in a second by logicallee on Sunday March 26, 2017 @05:48PM (#13963499)
I don't think it's fair of you to switch to the language "ruining things for others" - of course they don't want to explicitly "ruin things".

If you had said, "I don't think making sure that things don't happen instantly is explicitly part of their grand plan" then I would dispute that statement. (Yes, making sure things don't happen instantly is explicitly/implicitly part of their grand plan.)

They want users to have an "experience" not just click a button or press a key and instantly see the result. It is very explicitly part of their plan, and if the algorithms don't slow things down enough, they actually request animations or loading screens that do so.

Some of it may be implicit, rather than explicit. For example, a front-end javascript framework might actually produce pixel for pixel the exact same result as a simple HTML file generated more quickly on the back-end might do, but could still be a preferable "experience".

All this could be tested explicitly. For example two groups of PM's could evaluate web sites, where one included Working... screens where a javascript framework slowly renders something client-side, and the other could have pixel-for-pixel the same thing served from the server, using less bandwidth than it took to even transfer the javascript files over, so that the result is served much, much faster.

I hereby formally predict that some PM's will prefer the slower version for the exact and only reason that it is a slower user experience, and that this could be verified with a double-blind and carefully controlled experiment. I've put my claim out there, and it is easily falsifiable as well as has explanatory power in terms of the software we actually see.

Very simply: some PM's prefer a slower user experience. (I claim.)

Re:How much your computer can do in a second by Johnny555 on Monday March 27, 2017 @12:38AM (#13965212)
I think that's the time to scan both sides of the check (which is not done with a photo scanner, but with a sheet fed scanner, so it's not instantaneous), upload the image (potentially over a very slow network link), add it to the OCR queue on the server, do the OCR, save the image, and return the results back to the ATM machine.

I highly doubt the ATM maker put in sleep calls to intentionally slow it down -- no one is going to be surprised if it takes 1 second instead of 10 seconds to scan a check.

The bank could optimize for time, but it's not their time, it's their customer's time and they are already saving so much money over a teller transaction, they likely don't care about saving customers a few seconds.

Re:How much your computer can do in a second by FridgeSeal on Sunday March 26, 2017 @06:17PM (#13963645)
This strikes me as some kind of terrible vicious cycle: tradeoffs against performance (towards build speed) were made > users got used to slower software > users unconsciously prefer/select for slower software.

When you do get to use it, using performant software is a really great experience, so how to we train users to appreciate this?

Re:How much your computer can do in a second by nostrademons on Sunday March 26, 2017 @07:23PM (#13963962)
Sometimes companies do decide to make speed a priority, and earn literally hundreds of billions of dollars off it. One of Google's key features over Yahoo+Altavista was that it loaded instantly; they cut out all the crap from the homepage so you could get yourself to a result in under a second.

Ditto BitTorrent clients like uTorrent and Transmission; the first generation of BitTorrent clients were written in Python or Java, and felt like it. When users started complaining about how they would lock up your machine, somebody actually bothered to write one in highly-optimized native Win32 C, with no frameworks.

You have to understand what the customer is optimizing for though. Someone standing at an ATM is optimizing for confidence, not speed; they already took the time to drive to the ATM, so depositing their check in 1 second vs. 10 seconds doesn't matter when the whole trip takes them 10 minutes. Someone who's responsible for depositing 1000s of checks for a major business, using an office scanner, cares a lot. But I really doubt that industrial-strength check cashing apps put a sleep() statement when scanning the checks.

Re:How much your computer can do in a second by logicallee on Sunday March 26, 2017 @02:56PM (#13962422)
>If slowness is the goal and if product managers insist on slowness, then you'd expect a lot of sleep() calls in commercial software (which has product managers) and no sleep() calls in open source software. This doesn't happen.

Why do you say this doesn't happen, when it does, in fact, happen? An example of which would be this:

http://osxdaily.com/2015/01/06/make-the-window-resizing-anim...

This is a very explicit "sleep". It is far from the only one. Are you saying someone didn't think the slower animation was "better" than the faster animation - that the default time wasn't picked by a product manager?

>What we see is that commercial software has better documentation, gets more long term maintenance and support, and supports more cumbersome enterprise features. Exactly what you'd expect when you have salespeople and product managers who talk to customers.

We also see fancy loading graphics and I consider it extremely plausible that product managers consider fast/instant operation as room to add something to slow it down. I am not sure why you're debating this.

Regarding your open-source claim, this comment - https://news.ycombinator.com/item?id=13940014#13940458 - shows that fancy progress bar animations are considered more important, even in a commandline utility, and even under Linux. In other words, the fact that these progress bar animations slowed core functionality by 50% was -- in point of fact -- not an issue. Someone spent the time to create them, test them, commit them, and these were accepted: someone considered it objectively (or subjectively) better.

>Your hypothesis is falsifiable, which is a necessary but not a sufficient condition for it to be scientific. For it to be scientific you would also have to provide evidence that your hypothesis is more plausible than the alternatives, before you do any experiments.

You don't think surveying the actual decisions made in cases (such as the two examples just quoted, the window animation speed and the progress bar speed) where there was no functional difference except slowness, to be a plausible reason for supposing that people in charge of these choices choose a slower version? I think it's quite plausible that for whatever reason, slow software is preferred explicitly and implicitly.

>After all, it's easy to come up with thousands of silly hypothesis, and by happenstance some of them will get a positive correlation when tested. So every hypothesis has to undergo serious scrutiny.

I didn't spend much time looking through it in the original leak (on Wikileaks) but Bruce Schneier quoted on his blog Do's and Don'ts by an intelligence agency:

https://www.schneier.com/blog/archives/2017/03/the_cias_deve...

The parts I'd like to draw attention to:

- DO NOT perform operations that will cause the target computer to be unresponsive to the user (e.g. CPU spikes, screen flashes, screen "freezing", etc).

- DO make all reasonable efforts to minimize binary file size for all binaries that will be uploaded to a remote target (without the use of packers or compression). Ideal binary file sizes should be under 150KB for a fully featured tool. Rationale: Shortens overall "time on air" not only to get the tool on target, but to time to execute functionality and clean-up.

- DO NOT perform Disk I/O operations that will cause the system to become unresponsive to the user or alerting to a System Administrator.

Now I would just like to note that the other requirements are actually SUPER advanced - the binaries are expected to include complete encryption and decryption, as well as generating completely standard and compliant HTTP traffic that it is wrapped in, under another layer of functionality. There's a ton these binaries do.

You will very rarely see requirements similar to what I just quoted in most open source or commercial software. While I realize that when binaries involve active involvement with the user, they will necessarily be a bit more bloated/slower/etc.

But most software does not seem to care about being unresponsive, having huge binary sizes, causing CPU spikes, and generally being slow. I don't want you to misunderstand. I am quoting the above requirements for a piece of spyware to show you requirements that are emphatically NOT in any Product Manager's vocabulary. No Product Manager ever seems to tell their programmers to make a tiny, streamlined product that does not cause any unexpected delays or runs like molasses instead of instantly.

So I would say that on the whole my hypothesis that slower software is considered objectively better by Product Managers has high plausibility. The fact is, you are already suggesting that if the slower software is evaluated as better than the instant software, it will be "by happenstance."

Maybe so - but the fact that product managers choose slowness over speed every day, everywhere, speaks otherwise. Unfortunately I am not in a position to show this scientifically, and also social science experiments are particularly difficult to produce or replicate, with close to half being unreproduceable:

http://www.nature.com/news/over-half-of-psychology-studies-f...

"Over half of psychology studies fail reproducibility test".

So if you are a product manager, I would just like you to compare the requirements you've ever given out, to the ones I've just quoted (which I consider great requirements.) Of course, I use some minimal programs that meet the description. But as a rule these are programs produced by a single programmer, with no PM in sight.

It was nice to talk to you but you seem to view the software landscape differently from how I do. I think it's easy to see that our perspectives are very different.

Re:How much your computer can do in a second by mwcampbell on Sunday March 26, 2017 @12:29PM (#13961544)
On further consideration, though it's common to talk about an upgrade treadmill or "what Andy giveth, Bill taketh away", software actually does get better over time, and we shouldn't look back so fondly on older versions. To pick just one example, software in the 90s didn't have inline spell checking as you type, a feature that came in handy for me just a few minutes ago while editing my other comment. Still, the question remains: why doesn't everything feel instant on our current systems, and what do we do about it?
Re:How much your computer can do in a second by MagnumOpus on Sunday March 26, 2017 @03:47PM (#13962782)
> To pick just one example, software in the 90s didn't have inline spell checking

To pick on your example - it is interesting that you have to go back 20 years to find a feature beneficial for the everyman, and that you are still wrong: Just about every word processor starting from MS Word 95 came with inline spell checkers. (And indeed I prefer the snappiness and identical feature set of my copy of Office 2003 to the ribbon-laden gigabyte-guzzling mostrosities of Office 201x, just as I prefer a 15-year-old Winamp to the latest Itunes player.)

Re:How much your computer can do in a second by klibertp on Sunday March 26, 2017 @04:00PM (#13962873)
> To pick just one example, software in the 90s didn't have inline spell checking as you type

What? Which 90s exactly did you live through? Because I seem to remember MS Word 6.0 having not just spell checking as you type, but also the dreaded autocorrection feature. That was in 1993 according to Wikipedia.

Re:How much your computer can do in a second by mwcampbell on Sunday March 26, 2017 @11:52AM (#13961353)
So is there any way to stop this treadmill, short of overthrowing capitalism itself?

Edit: If that seems like a non-sequitur, I said it because the parent comment started by saying that the market is wasteful.

Re:How much your computer can do in a second by userbinator on Sunday March 26, 2017 @12:09PM (#13961427)
I don't think capitalism is to blame, as this is endemic even in free software. The way to stop this is to stop repeating dogmatic myths about optimisation, consider efficiency/optimisation as an integrated part of the design process and not something to be applied afterwards, and focus on "user time is expensive" instead of "developer time is expensive" --- and sometimes, those users may also be developers.
Re:How much your computer can do in a second by chii on Sunday March 26, 2017 @06:14PM (#13963627)
> user time is expensive

that's not always true, especially from the point of view of the dev.

Re:How much your computer can do in a second by username223 on Sunday March 26, 2017 @07:29PM (#13963992)
Yep. With forced auto-updates, software companies have implemented "software gavage," and the devs are just getting paid to push code down users' throats. It's much harder to entice users with something they might actually want.
Re:How much your computer can do in a second by gizmo on Sunday March 26, 2017 @12:02PM (#13961402)
There is certainly a case to be made for overthrowing capitalism, but I don't see why an anti-capitalist revolution would automatically result in a society with higher quality software.

Open source software suffers from much the same problems as commercial software. There is much about writing good software we haven't figured out how to do yet as an industry, and in the meantime we have to work with tools that are totally inadequate.

Re:How much your computer can do in a second by mwcampbell on Sunday March 26, 2017 @12:48PM (#13961650)
Why do you think our tools are inadequate? What would adequate tools be able to do that our current ones can't?
Re:How much your computer can do in a second by gizmo on Sunday March 26, 2017 @02:52PM (#13962395)
Way too much to cover in depth. In short, it's all terrible. We're mostly using tools from the 70s, and we're still to this day plagued by use-after-free and out-of-bounds errors, nullpointer exceptions, awful debuggers, race conditions, slow compilation times, bad primitives for multithreaded work, just to name a few. We've known for decades that we can do better and ways to do better have been studied in depth by academia.

That's just the basics. Then there is futuristic things: Why can't we move running processes from one physical machine to another? Where are the debuggers that allow you to go back and forward in time? Why can't we visualize the data structures in our program and trivially change the data layout to see how that affects performance?

When I look at the demo of the Xerox Sparc interface (1982) and compare that to where we are today it's pretty clear to me we messed up big time somewhere along the road: https://www.youtube.com/watch?v=Cn4vC80Pv6Q

Re:How much your computer can do in a second by nostrademons on Sunday March 26, 2017 @07:47PM (#13964083)
For people who have an exceptionally high tolerance for learning what people actually care about and why the shitty technological solutions won in the marketplace, this is probably an opportunity.

When I entered the workforce in 2005 after learning all about bygone languages (Common Lisp, Smalltalk, Dylan, Haskell, Erlang, Ocaml, etc.) in college, it was really, really painful going back to Java. Java had gotten so many fundamental language features wrong when better alternatives were well-known in research literature. Monitors instead of CSP, null types instead of Maybe, inner classes instead of closures, manifest typing instead of type inference, no first-class functions, mutability everywhere, conflation of modules & classes, not even a semblance of pattern-matching. But I could use it to write software that performed well, that could be deployed with tooling that everybody used, that had a wide base of available libraries, that had IDEs and other tooling available, and that other programmers could maintain.

It's 12 years later, and all of my recent projects have been in some combination of Swift, Rust, Kotlin, or ES6+React. And most of these languages have: promises & message-passing instead of explicit locks; Optional types or at least some form of null-safety; lexical closures; type inference; first-class functions; immutable-by-default; module systems that don't require that you shove everything into a class; and pattern-matching. But they also did the hard work of figuring out an interoperability story with some large existing body of code; of writing decent package managers and easy build systems; of making the language reasonably performant for most everyday tasks; and of (in Swift & Kotlin's case) providing full support within an IDE. All the language features that were common in research languages of 2005 but missing in industrial programming of the time are now very usable in the industrial programming of now.

I wouldn't be surprised to see a similar renaissance in tooling over the next decade, with exotic features like time-traveling debuggers, fully-inspectable systems, and migratable processes becoming standard in the next generation of IDEs.

Re:How much your computer can do in a second by TeMPOraL on Sunday March 26, 2017 @03:27PM (#13962617)
> We're mostly using tools from the 70s

We're using the shittier tools from the 70s, because the better tools died off - which is sad, because we still didn't manage to recreate some of the features those tools offered. The success of UNIX and C seems to be caused by the same phenomenon that causes Electron to succeed and bloat to proliferate - what wins aren't good solutions, but those which get popular quickly.

Re:How much your computer can do in a second by chii on Sunday March 26, 2017 @06:17PM (#13963642)
> aren't good solutions, but those which get popular quickly.

but by the judgement of a majority, those tools are good! That's why it got popular. Any personal sense of aesthetics from you (or anyone) doesn't matter at all here, and most people who call tools that failed 'good' are only judging it by personal aesthetics.

Re:How much your computer can do in a second by TeMPOraL on Monday March 27, 2017 @12:33AM (#13965190)
I'm not talking aesthetics here; I'm talking about shitty engineering. Often legitimized by nonsense phrases like "worse is better" these days.
Re:How much your computer can do in a second by ue_ on Sunday March 26, 2017 @12:09PM (#13961428)
Within capitalism, products are made to maximise exchange value rather than use value. This is because it is more profitable to optimise for products to be exchanged rather than used. In fact, it can be detrimental to maximise use value, because a product that can be used for longer will mean that fewer people will have motivation to purchase another one any time soon.

I like the idea of overthrowing capitalism itself to resolve this.

Re:How much your computer can do in a second by icantdrive55 on Sunday March 26, 2017 @12:04PM (#13961411)
This will sound pathetic, and it's partially because I don't have much of a life, and spend way too much time with electronics, but one of my biggest regrets is---

Upgrading.

I've always fell for the increased security, and blah, blah, blah, but in the end I have a device, I once used, become slow, programs become useless, or my plethora of USB devises don't have the right updated firmware.

I have a Mac, and a MacBook Pro I'm thinking about wiping clean, and installing the original operating systems. It's just a pain, and yes--I know security is important.

I did finally learn on the IPad, but I'm still not completely sure I'm doing the right thing. I must have hit "tomorrow for 9.3.5---three hundred times. I just don't want to make this devise slower. I paid way too much years ago, and I hate putting things in my electronic graveyard--my closet.

Re:How much your computer can do in a second by angry_octet on Sunday March 26, 2017 @07:54PM (#13964109)
I can't upvote your most recent comment because you're attracted too many haters too quickly and the comment is in purgatory unjustly. In fact, I think you've attracted some regular haters, though I can't prove it. I suspect someone doesn't like your anecdotal style, but it is just as valid as an unsupported generalisation.