I don't disbelieve you, I'm just wondering what type of site that is since English Wikipedia is several orders of magnitude lower than that.
787 karma · joined July 5, 2016
I don't disbelieve you, I'm just wondering what type of site that is since English Wikipedia is several orders of magnitude lower than that.
Besides, the direction and relative values show clear and growing dominance.
It is awful for actual third-party passwords.
With cursors you just hold shift and use down-arrows to (visually) select the lines you want. Add in Ctrl and you can move word-boundaries, add home-end and you can do beginning/end lines / pages too.
The whole thing is still quicker than vi but with the added benefits of getting much more visual feedback on what is happening and the ability to use the mouse to also quickly select things.
Personally I can distinguish every time at 0.06.
I find it difficult to believe the rest of the hardware loop has 40ms latency, it would be difficult for smooth rendering to occur if it did.
I suspect that part of this is 'training' yourself but also what the researchers meant. They may very well have meant that above 100ms is jarring and noticed as a delay but below 100ms is not seen as a delay rather than truly being unable to notice in an A/B test.
I suspect this test would be more difficult if it sometimes did A/A and B/B.
c# just isn't favoured by hobbyists except for game-programming. But in business world (at least from my UK perspective) where nothing comes close to github, c# still seems as healthy as ever and that doesn't depend on unity at all.
All the projects I've seen, even the ones where there are "minimum viable projects" have too much pressure from above (or have already been sold) so they aren't allowed to fail.
So I agree testing should happen as early as possible, but too often they're not real tests because failure isn't allowed.
Contrast that to software engineering, where beginning before you have requirements is seen as a requirement of being agile.
I don't see a privacy policy or other page which makes it clear what information you collect and how that information is stored.
How is session management handled from the point of view of administering the service, how does the service track users and for how long is that information stored?
In the real world, people will migrate to what works for keeping people inline. Appealing to better practice will be mowed down by actual practice. Instead write tools which encourage better practice.
This really isn't "what a right wing person sees on facebook".
Is that a fair and democratic process or just technocrats doing their best based on their own fallible models?
You can't just take information away or try to "curate" the information seen, that's what censorship is.
We just need to learn to live in a world where everyone knows too much about others and where it can be difficult to tell the difference between truth and lie.
A being a space where someone is free to express themselves. For the right, whether you agree with them or not, that space was no longer the mainstream.
By labeling yours a "safe space" and theirs as "hate space" you are part of the problem.
If I visit a news site with a "share on facebook" widget which uses a facebook endpoint to get my facebook identity, am I an active facebook user?
If I have the mobile app installed which runs in the background getting notifications I never read, am I an active facebook user?
I'll be sure to check more closely next time I'm logged on.
I'm surprised to see Designated Survivor listed there, watching it felt like it was yanked from network TV and stuck on netflix. It has frequent recaps, obvious gaps where commercial breaks should be, and the same few ideas hyped through the season.
But I guess that's why netflix works, one person's trash is another person's treasure. We all find something that interests us.
Just because something is turing complete doesn't mean that a generator has to be able to generate anything possible.
If boilerplate is an issue, scaffolding / code generators can be a quick fix.
If it's a low traffic site, why not just build a small site and use a cheap shared host?
My prediction: In 5 years 16GB will be fine.
Why? Because RAM requirements passed from "We need more, it'll speed things up" to "We've got enough" a while back, and there just isn't much you can do with the extra. Once you're no longer space constrained it just ceases to move the needle.
I'm not defending Apple here, but generally it's hard to think of something that would require 32GB of ram that doesn't better belong on a server. Once you get to that kind of size you'll probably want ECC or stable uptime or other features you'll get on an actual server rather than a machine you turn on and off several times a day.
For smaller sites, the number of parts often isn't huge, so boilerplate isn't a big deal.
I personally doubt this will be revealed to be a software security issue.
If you run a central message bus off which people can produce their own applications, you'll find yourself having to deal with everything that ISPs and mail providers have to deal with. That means being asked to keep logs for years, dealing with DMCA takedowns, filtering the worst of the internet, etc.
And for what? As soon as anyone relying on it achieves scale they'll re-implement it themselves.
Besides, what you've described is the opposite of a protocol: an inner platform.