Dinius
Dinius on Hacker News
> if you use an English word as a command, such as ‘return’, it means you can never type out that word.
Not exactly true. The word by itself would be recognized as a command, but in a sentence it’ll be treated as any other word, assuming you don’t pause for too long before it.
The first heading overflows on mobile, hiding the "a" and "y" in "application delivery"and causing horizontal scrolling.
If that was truly the case, they ought to have moved away from flash "a long time ago".
Also, the color choices of the navigation dropdown literally makes it impossible to read it on my dimmed mobile screen, change it/increase the contrast.
Fix it for mobile. Quick glance says the headings are overflowing the width causing horizontal scroll, and the two buttons near the top are overlapping each other.
Bandwidth for lightsail is 1tb, not 5tb like the article says.
TL;DR: Don’t trust AWS status reports, they’re lies
Or as some would say, alternative facts.
One powerful computer, hooked up to 3 locations in my house:
1: a heavily modified recliner chair with a monitor on an adjustable swing arm, where I tend to spend most of my time.
2: next to it, a backapp chair coupled with a separate mount for the "recliner monitor" so I can use the same monitor but elevated.
3: upstairs, standing desk, where I don't spend enough time.
All keybords are in the 60% form factor. I don't use mice, in other words my hands never leave the keyboard. This coupled with heavy customization to keyboard layout and functionality (custom layout, Autohotkey, etc) has worked wonders for RSI.
Two monitors, Eizo 27" IPS 2560x1440 by the recliner, 144hz IPS monitor with same size and resolution at the standing desk.
I also have a separate computer hooked up to the tv, a laptop hooked up to another screen, a cheap chineese tablet in the kitchen keeping track of temperatures and misc news etc, and an "old" t420 laptop which isn't in active use. I only work on the one main computer though, and I only ever use one monitor at a time (personal preference).
Vimium and stylish haven't been mentioned yet.
Site activity on the bottom of the page goes back to February 12, 2009
So basically just the existing Go plugin (give or take a feature or two) shoved into a standalone editor which, knowing Jetbrains, is sure to be flust with new bugs for the foreseeable future..
Not to sound negative or anything.
Performance, easy concurrency, and because the language itself is very "straightforward".
Win10, Chrome 54.0.2840.99, works fine here. (They link to PDF files though, more likely that's the problem I suppose).
Something like this: (PHP felt like the right approach here :p)
if ($selectedOption == SECURITY_QUESTION)
{
if (isset($_POST["SecurityQuestion0"]) && isset(["SecurityQuestion1"]))
{
if ($_POST["SecurityQuestion0"] != $answer0 || $_POST["SecurityQuestion1"] != $answer1)
{
// invalid answers
return;
}
}
authenticateUser();
}
Simply stop and disable the windows update service, and turn it on when you have time to actually install updates. Been doing it this way for more than a year now without problems.
Of course you'll have to remember to turn it on to check for updates, but that's no different from using manual updates in past versions of Windows. The only downside is that certain things, i.e. Add/remove features might not work 100% while the service is disabled.
Not to disregard that NW.js might be a better choice in this case due to the API support.
But generally speaking, Electron:
- Is more tested in
production (VS Code, Atom, [1])
- Has a larger and more active community
- Has (at least in the past) started using newer versions of Node and Chrome long before NW.js (Especially with Node when v4 came out this was a relevant drawback)
- Tested both the newest versions on Windows 10 right now, Electron used ~50mb less RAM, and less CPU. (Of course this isn't a very relevant test, more of an observation, these numbers could vary greatly between systems and platforms).
On the flip side, some reasons to use NW.js:
- "Source code protection", which gives a ~30% performance reduction. Electron devs has chosen not to implement this due to that drawback.
- Better support for transparent windows, at least in the past. (At the expense of disabling hardware acceleration).
Note that some of this information might be a few months out of date, mostly in regards to NW.js.
[1]: http://electron.atom.io/#apps
