Something Later

Fastness in software is like great margins in a book — makes you smile without necessarily knowing why.

Minimal port of SSHFS to Windows; uses Cygwin for the POSIX environment and WinFsp for the FUSE functionality.

PowerShell script for automation of routine tasks done after fresh installations of Windows 10 / Server 2016 / Server 2019

In the last year and a half of working in React, easily my favorite thing about working with React isn’t specific to React. It’s the idea of a directly consumable components. Ultimately, this is why I’m so excited about diving into web components, because they are native to the web and interoperable with different JS frameworks.

An important essay on the tectonic shift that componenitized front-end development, à la React, has wrought on the front-end design/development space and how Brad Frost carved out a space between the "front of the front-end" and the "back of the front-end".

I share his optimism for native web components as a way out of the React-specific morass.

1. Setup the virtualbox to use 2 adapters:

   • The first adapter is set to NAT (that will give you the internet connection).
   • The second adapter is set to host only.

2. Start the virtual machine and assign a static IP for the second adapter in Ubuntu (for instance 192.168.56.56). The host Windows will have 192.168.56.1 as IP for the internal network (VirtualBox Host-Only Network is the name in network connections in Windows). What this will give you is being able to access the apache server on ubuntu, from windows, by going to 192.168.56.56. Also, Ubuntu will have internet access, since the first adapter (set to NAT) will take care of that.

3. Now, to make the connection available both ways (accessing the windows host from the ubuntu guest) there's still one more step to be performed. Windows will automatically add the virtualbox host-only network to the list of public networks and that cannot be changed. This entails that the firewall will prevent proper access.

4. To overcome this and not make any security breaches in your setup:

   • go to the windows firewall section, in control panel,
   • click on advanced settings. In the page that pops up,
   • click on inbound rules (left column), then on new rule (right column). Chose custom rule, set the rule to allow all programs, and any protocol. For the scope, add in the first box (local IP addresses) 192.168.56.1, and in the second box (remote IP) 192.168.56.56. Click next, select allow the connection, next, check all profiles, next, give it a name and save.

Open source tool for developing UI components in isolation.

"Real life pattern libraries, code standards documents and content style guides."

A collection of open and indie Mac, iOS, and web apps that help promote the open web.