If only all the sites stopped embedding the social media buttons, i don't mind people on Facebook, twitter, instagram, etc etc, i do mind their tracking buttons everywhere.
The threshold for most people is slightly lower than a quarter second, but it's certainly the case that above a quarter-second users will notice the delay[0].
However, people may be primed for longer delays still seeming instant. e.g. Smartphones for many years had a built-in 300ms delay on any click event, and even without that event typically still have delays on many 'instant' actions.
So while the delay will be registered as being present, it may not be registered as "this site is slow" but "it's just a natural delay".
I completely agree, a quarter of a second is absolutely not instantaneous.
Especially not to oddballs like me that has some kind of perceptive 'bug', it's like I lack a 'motion filter'. One effect being that movement in computer games doesn't feel completely fluid until the refresh rate is close to 200Hz.
Before internet and slow loading web pages might have lowered peoples expectations, I remember Human-computer interaction guidelines stating that < 0.1 was experienced as instantaneous in almost all cases. Above 1s without feedback started to cause measurable stress in test subjects.
Since this was before computers were ubiquitous, it's probably a good measure for how we react on a more basal, subconscious level. Anything measured today is likely to be include learned expectations, so a quarter of a second seems like reasonable learned expectation of the perception of instantaneous in that particular context.
This isn't about raw physics and biology but rather the use of business applications by users, specifically with regards to analytics and exploratory queries.
Anything less than a second to run a query and return results is considered "instant" (also sometimes "interactive") for analysis.
What? No human trades that quickly, and this is not about automated HFT trading systems but rather running database queries and what typical business users expect as "instant" results.
oofff... wipes a tear (honestly) i still have the computer of my father, i can't get myself to power it up and go through it. I'm saving it for a day i do feel up to it.
> A 3 line file, be it long lines, shouldn't happen
No. It should not.
But that’s completely unfair. Xi does not even claim to be beta. I haven’t touched it in months. But when I did, it was a good (start of) a Mac frontend that was clearly not finished.
The only people I imagine using it now probably use it to dogfood the backend and piece together a solid plugin API.
I would prefer Xi-style win the mind share. Native front ends that tie to a common solid backend that a large community can share to build strong plugin support.
I’ll settle for xray-style, a better cross-platform frontend that doesn’t redraw large portions of the DOM quite so often. Javascript is fast enough. A good (heh) extension language. The drawing layer is what makes Electron a slow, bloated choice for a text editor.
Since Atom came out, I have had a backgrounded dream that once things settled, they would write a faster front end for the text. But that is difficult to do if your API is “can you do it in the DOM with javascript?
But they are atom.io. They can change their API if they need to.
VS Code, with its well-bounded API is a much better candidate. And I would love to be surprised by a Microsoft skunkworks non-Electron release.
Xi, is a solid idea. Don’t know if they can build a community out of nothing. I am worried that an API of ”here is a JSON firehose, hook up whatever you want to it” will fragment the backend.
I think Xi would be well served by saying “Here is your firehose, but, the official way is our VS Code emulation plugin.” Or something solid and well-defined.
It is unclear where Xi is going so far, that may happen.
Yeah, getting Webmin security right is possible but very challenging. Whenever I'm doing a security assessment at a client and I see traffic to/from servers on port 10000 I always make a note that there's probably some vulnerabilities there that our pentest guys will want to explore.
I have no idea if Cockpit is any more secure, but Webmin does have its fair share of security issues.
Personally, no, i don't want a webserver managing my servers. But i surely hope not the same mistakes or security issues arise that happened for webmin.
The security on this is actually a lot better than most cameras--all the traffic is SSL using trusted client certs. To get into the traffic they had to tear the device apart and extract the cert. After that they could MITM the traffic between the camera and the remote server and observe some bad security. Unfortunately they also published the extracted certificate on their blog which is not cool.
They unfortunately did not have to tear the device apart and extract the cert, they state that each device uses the same one, valid until 2038, which was exposed in a previous exploit (and was likely previously available online as a result).
Though it was definitely a bad idea to post it again on their site.
I miss the 'ads' part of AMP in the article? One of the main goals is to serve ads better/faster.
"The AMP Project is an open-source initiative aiming to make the web better for all. The project enables the creation of websites and ads that are consistently fast, beautiful and high-performing across devices and distribution platforms."
