You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
💻
A'braham Barakhyahu
BlessYAHU
💻
React/Nextjs/.NET developer,
Javascript Functional/FRP enthusiast ,
Fringe tools explorer
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Efficient outerHTML polyfill that doesn't use cloneNode(true)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Twit: ServiceStack IContainerAdapter for Castle Windsor
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Even though the browser landscape in my line of work has gotten better (as in, projects don't use IE6 or IE7 anymore), I still need to deal with "legacy" browsers. Since IE8 has been around for ?? years and is becoming the [new IE6], the term legacy fits.
I came across an issue where it was taking some time for javascript objects to initialize after a page load on IE8 for an application I was building. I just read about delaying object initialization using event capturing to increase performance[link]. Makes sense, no need to initialize objects until they are about to be used. Of course the rub is that IE8 doesn't do event capturing. I could shake my fist at IE for being behind the times and the bane of web developer existence..but I chose to find another way to implement the concept.
The UI item in question was a an piece of a bigger UI element, and getting to it (to click it) required mousing over the containing UI element. I could use the mouseover event t
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm doing some research on how companies use GitHub Enterprise (or public GitHub) internally. If you can help out by answering a few questions, I'd greatly appreciate it.
What is the primary setup? Is there an organization and each official repo is owned by that organization?
Does every engineer have a fork of each repo they're working on?
Are engineers allowed to push directly to the official repo? Or must all commits go through a pull request?
Do engineers work on feature branches on the main repo or on their own forks?
Do you require engineers to squash commits and rebase before merging?
Overall, what is the workflow for getting a new commit into the main repository?
What sort of hooks do you make use of?
Are there any ops issues you encountered? (Scaling, unforeseen downtime, etc.)