recentpopularlog in

dirtystylus : via:peter_chappy   36

Codename: nvUltra -
“The biggest difference is that it works with multiple folders and sub-folders. You pick a folder, it indexes it, and you can use it just like nvALT. But then you can open another folder, or create a new one and start editing. It allows you to create folders anywhere, maybe one on Dropbox or iCloud Drive that’s shared, one on an encrypted disk that’s private, one for work, one for home, one for every writing project. You’re not limited to tags (though you can search by and sync with macOS tags within the app), and you can sort your notes into subfolders as well.”
via:peter_chappy  nvalt  markdown  writing  notetaking 
12 weeks ago by dirtystylus
How is JavaScript used within the Spotify desktop application? Is it packaged up and run locally only retrieving the assets as and when needed? What JavaScript VM is used? - Quora
This organization structure, combined with the global-ish nature of JavaScript in the browser, has made us build the desktop client UI out of many small, self-contained web apps called Spotlets. They all run inside Chromium Embedded Framework, each app living within their own little iframe, which gives squads the ability to work with whatever frameworks they need, without the need to coordinate tooling and dependencies with other squads. While this approach has the disadvantage that we have many duplicate instances of different versions of libraries, increasing the size of the app, but it offers the massive advantage that introducing a library is a discussion between a few people instead of decision that involves ~100 people and their various needs. Not only would such a big discussion extremely time-consuming and hard, it would also force us to use a least-common-denominator approach to picking libraries, instead of picking the ones specifically tailored to the problem domain of each squad. Considering the size of a single song compared to the size of a JavaScript library, this trade-off is a no-brainer for us.
programming  javascript  music  spotify  codearchitecture  npm  via:peter_chappy 
july 2018 by dirtystylus
Kabir Shah
I'm a maker & student based in California.

I design in Figma and Sketch. I program in HTML/CSS/JavaScript for the web, Crystal for servers, Python for AI, and C for systems.
portfolio  webdev  teens  via:peter_chappy  ui  ux  css  webdesign  opensource 
september 2017 by dirtystylus
For an Inclusive Culture, Try Working Less – Hacker Noon
I don’t know how useful this will be to anyone else, but the lesson I’m taking for myself going forward is this: if you want to build an inclusive culture, build a minimum culture. Build it around professionalism, boundaries, and work-life balance. Make sure your senior staff walks the walk, and spreads the word.

I’m reminded here of the idea behind “Getting to Yes”, that classic work on negotiation. The idea is that, in negotiation, if you work to constrain the number of things the involved parties have to agree on, you increase your chances of coming to agreement. You set aside your desires and, in service of coming to agreement, just focus on your needs. Seems obvious in retrospect, but was actually revolutionary in the business world.
management  techculture  workculture  diversity  inclusion  via:peter_chappy 
june 2017 by dirtystylus
jevakallio/redux-offline: Build Offline-First Apps for Web and React Native
Redux Offline is very, very new. If you find a bug, good job for being an early adopter!
via:peter_chappy  offline  offlinefirst  reactjs  redux  github 
march 2017 by dirtystylus
Scrolling on the web: A primer - Microsoft Edge Dev BlogMicrosoft Edge Dev Blog
As this table demonstrates, scrolling performance can vary dramatically from browser to browser, and even from OS to OS. If you’re only testing on one browser with one scrolling method, then you might be getting a very narrow view of your site’s performance as it’s actually experienced by users!

You might naïvely think that a function that doesn’t call preventDefault() can’t block scrolling at all, or that, at the very worst, it can only block for the duration of the function itself. The truth, however, is that even an empty listener will totally block scrolling until any JavaScript operation on the page has finished, which you can verify with this demo.

Even though the wheel listener has nothing to do with our big blocking JavaScript operation, they share the same JavaScript event loop, and so the background thread must wait for the longer JavaScript operation to finish before it can get a response from the listener function.

Why does it have to wait? Well, JavaScript is a dynamic language, and the browser can’t know for sure that preventDefault() will never get called. Even if it’s obvious to the developer that the function is just doing a simple console.log(), browser vendors have opted not to take any chances. In fact, even an empty function() {} will exhibit this behavior.
via:peter_chappy  scrolling  webdev  webdesign  javascript  performance  touch  animation 
march 2017 by dirtystylus

Copy this bookmark:

to read