Boom!
In a split second GitHub went to
from
from 
Archive for July 6th, 2016
GitHub has majour service outages…
Posted by jpluimers on 2016/07/06
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management | Leave a Comment »
Vysor Pro Feature – Go Wireless to mirror and control your device without a USB Cable…
Posted by jpluimers on 2016/07/06
If you have a Vysor Pro (either subscription or one-time payment for life-long usage), then you can use this new New Vysor Feature – Go Wireless Click that button to mirror and control your without a USB cable…
There are more Pro features to come; currently they are:
- High Quality Mirroring
- Fullscreen Mode
- Go Wireless
- Vysor Share
- Drag and Drop Files
- Access to all future features
If Google Pay doesn’t work in your country, then you can use PayPal. When that doesn’t work either, well…
Another nice Vysor Pro feature: Vysor Share Server – an easy Android device farm: You can share all your Android devices at once using the new Share All feature. – Koushik Dutta (Koush) – Google+
Vysor links:
- short: https://goo.gl/FvMqnY
- long: https://chrome.google.com/webstore/detail/vysor/gidgenkbbabolejbgbpnhbimgjbffefm
History:
Vysor test server
I made a thing. Check it out if you’re an Android dev or tester.Will only take a few minutes. It’s neat. – Koushik Dutta (Koush) – Google+
Source: I made a thing. Check it out if you’re an Android dev or tester. Will only…
and
There are few apps that let you share your Android device screen through PC, but today we
Source: How to Mirror Your Android Screen To PC! [Vysor] | HowTo.HighOnAndroid.com
–jeroen
Share this:
Posted in Android, Android, Development, Mobile Development, Power User, Vysor | Leave a Comment »
case insensitive files systems and git – Lesson Learned – I Can’t Get My Git Repo Clean! | DrupalEasy
Posted by jpluimers on 2016/07/06
via: Lesson Learned – I Can’t Get My Git Repo Clean! | DrupalEasy
One file kept getting added to the git modified list: service/src/main/MySOAPdefinition.pas.
It was part of a repository that had been migrated from SVN (more on that in a future blog post) and along the way been renamed in directory service/src/main from MySOAPdefinition.pas to MySoapDefinition.pas. SVN (and TortoiseSVN) don’t object to this. But git does.
You’d see this on the command-line:
>git status
On branch develop
Your branch is up-to-date with 'origin/develop'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: service/src/main/MySOAPdefinition.pas
no changes added to commit (use "git add" and/or "git commit -a")
>git add service\src\main\MySoapDefinition.pas
>git status
On branch develop
Your branch is up-to-date with 'origin/develop'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: service/src/main/MySOAPdefinition.pas
no changes added to commit (use "git add" and/or "git commit -a")
Basically the add would do nothing.
On Windows, this is how to get around this:
Share this:
Posted in Delphi, Delphi XE8, Development, git, OS X, OS X Maverick, Power User, Software Development, Source Code Management, SourceTree, Windows, Windows 7 | 1 Comment »
Latency Numbers every Programmer and Architect should know
Posted by jpluimers on 2016/07/06
Via +Martin Blais, Philippe Beaudoin, Lars Fosdal as Useful resource……:
Hit the cache, Jack…
Interactive Chart of Latency Numbers every Programmer Should Know (from 1990s until 2020s including script to draw the cart).
Also, this variant by Erik Meijer from Coursera (https://www.coursera.org/course/reactive): https://d396qusza40orc.cloudfront.net/reactive/lecture_slides/Latency%20as%20an%20Effect%201.pdf#page=10
Via Asbjørn Heid:
Following up on +Lars Fosdal’s earlier post here’s a talk by Herb Stutter which goes into more detail of where the performance is these days.
It’s a general talk, not C++ specific. Recommend it to get some idea of what goes on under the hood these days, and so one doesn’t try to do some premature optimization which may turn out to be bad.
–jeroen
Table as of 2016:
- 1 ns: L1 cache reference
- 3 ns: Branch mispredict
- 4 ns: L2 cache reference
- 17ns: Mutex lock/unlock
- 100ns: Main memory reference
- 2000ns: Compress 1 kilibyte with Zippy
- 16000ns: SSD random read
- 19000ns: Read 1000000 bytes sequentially from memory
- 500000ns: Round trip in same data center
- 100000ns: Read 1000000 bytes sequentially from SSD
- 3000000ns: Disk seek
- 1000000ns: Read 1000000 bytes sequentially from disk
- 150000000ns: Packet round trip California to the Netherlands
Part of the 2015 numbers:
Share this:
Posted in Development, Software Development | Leave a Comment »
