nilsandrey

Highly recommended indeed

Hi @acabal. I'm interesting on a RSS address for your blog. I'm seeing you publish tech stuff. Thanks for all the work you've done and shared.

Locally could be easier to rely on background run of a docker image instead of another console serving the files, just to run and forget, just use it by the dependent project you probably could be working on (Dependent on the static content). I'm agreed on the cloud it's better use the plethora of services available for static content directly like Cloudflare.

I think is not precisely an active project, but it's open on GitHub[1], I guess we can try to open issues there.

- [1] https://github.com/lipanski/docker-static-website

I use them too. Sometimes I like to have some repos with the static content, which get deployed by a CD tool to those services. It's common for me when debugging or testing locally in my PC or LAN, to include some docker build for those repos which I don't use at production time, but I used it locally. Maybe is not a big problem at all, but I use it that way, specially when in my projects the CND used is not a free one. Makes sense?

You can personalize new tab page (upper right corner wheel button) and uncheck:

- Sponsored shortcuts

- Recommended by Pocket

This is exactly the problem we all always have with trying new services and dealing with relatives, friends, coworkers, and new networking pales which is ultimately the daily communication targets.

This remember me a system that helps me a lot:

https://plaintext-productivity.net/

You need a native program to access the web, so for now, always you'll need at least one native program ;)

Now, seriously, as muzani states indirectly, the preferred way will be divided as long as implies another layer and a difference in available device services. Also, you mentioned a disadvantage of the stores but think about the distribution network in terms of online presence to being noticed. There're plenty of pros and cons in every aspect.

Regarding the update point, like in desktop OS, with Android, you didn't need to wait, just take the APK file and install it. From the perspective of your sentence, it's only a problem (or situation) of the Apple ecosystem, not related to the web/native. They can't control the web but if they could they will. From the perspective of the consumer, some say they are fine with the gatekeeper, adding a layer of security and quality assurance.

No, about that they just enriched the Basic plan to now include a single sign-on (SSO) without changing the current price.

IMHO there's more misuse than overrating

This works for me in Angular too, on Windows, WSL2 and Docker Desktop.

The environment variable is used actually by the chokidar[1] package, which is used by webpack, angular-cli and others.

[1] https://www.npmjs.com/package/chokidar

I'm using it too, it's great. Also you may check the auto-create flag, allowing new tabs belonging to the source page's group.

In Edge it does persist for me. Seems to doesn't persists between updates.

I liked the idea, but I'm expecting the home page to be more like "https://bloggingfordevs.com/trends/" with a link or banner link or something to the stuff it's at home today; at least having the links to trends at first instead of need to moving to the bottom to see them. I'm afraid some colleagues didn't found out and just kept on the first page.

You directly go to dark mode ;) it's more popular I known; I like to suggest a light mode; maybe you can read it from the system like StackOverflow.

In the section "Merging stacked Pull Requests" is mentioned:

"...we must start merging from the top, i.e., the last opened pull request. Doing otherwise will result in a state where we cannot merge our pull requests anymore."

I think with the idea of PR re-targeting[1] that section could be enriched just to cover premature merging, accidentally or needed.

[1] https://twitter.com/getupleveled/status/1300714078198018049?...

Accessibility improvements - New screen reader capabilities.

Windows ARM builds - Windows on ARM is now available in stable.

New JavaScript debugger - Debug in the terminal, profiling support.

Source Control unified view - All repositories displayed in a single view.

View and sort pending changes - View files as a tree or list, sort by name, path, or status.

Edit complex settings - Edit object settings from the Settings editor.

New HexEditor extension - Edit files in hexadecimal format from within VS Code.

Notebook UI updates - Improved UX and undo/redo support.

Remote Development tutorials - Learn to develop over SSH, inside Containers, and in WSL.

Java Pack Installer for macOS - Get set up to develop in Java with VS Code on macOS.

Source: https://github.com/google/web-stories-wp

Yes, it's nice. I saved for myself at:

https://gist.github.com/nilsandrey/c1f66819de40b26eed4bf71ac...

Check out https://www.zendesk.com/

You can see some alternatives (Paid, free, on-premises, on-line, ...):

https://alternativeto.net/software/zendesk/

I've worked with non-geeks for many years and the best results were achieved with Sharepoint or O365. The versioning system it's simpler for them than GIT; it has a lot of missings but has great support on the clients' apps, specially MSWord and the revision and merge features.

There's a variant to use TortoiseGit as a git desktop client (only Windows) versioning directly office documents because of that one pops up the resolution of the conflicts directly with the office apps.

There're some folks followed me to markdown-git using desktop clients like Typora and Gitbook (editor and other services), but it's not suitable for everyone.

Just use Samsung Internet forced dark mode ;)

https://telegra.ph/file/5db81368584364c580454.jpg

I see your point now, I was preferring containers because I have this scenario where I want the data separation it provides without the need of reinstalling add-ons, especially on a temporal container/profile. The shared window can be nice on some particular moments where I don't need to have a lot of pages opened and are continuously changing from tab to tab.

Thinking over about you said, now I think I like things from the two worlds, maybe better interface to containers or even better UI for profiles, with options to overcome the containers (maybe should be better for the average user instead of having both).

For the time being, I prefer to have both options (don't have it now) but I think both can be improved.

Thanks, it's great. I'm a fan of mind mapping[1] to express some ideas.

[1] https://en.wikipedia.org/wiki/Mind_map

Please, write your documentation in whatever tool you like, including Markdown, and being Markdown better than others like a word document or directly PDF for accompanying code. If it's about a code, better living with him in the same repo.

Threads about it on twitter: https://twitter.com/anildash/status/1240655355698458624?s=20

I think I understand your point, but thinking about releasing a hotfix over an old version is a way of maintaining multiple versions... I work once with a team supporting multiple versions of a really complex app(in the sense of a lot of features and DB entities). They support his clients (on-premises) with eventual hotfixes, one service-pack and one version a year.

Some times they were working on changes on a release before a hotfix was addressed, and with cherry-pick's like operations, they took the changes of the hotfixes and applied to the service-pack and new versions with less effort than before they used the model.

With a dev team of 10 programmers, 20 on IT support and hundreds of client's deployments they build a profitable business (subscription-based and in-site support) where the branching model helps a lot.

They spend less time managing the releases, switching context for priority support and dealing with more changes in less time.

Strongly agreed with the new author note. I used the same ideas with the teams I've been coaching: "Consider your context...." as the need or not of support for multiple versions and "...Decide for yourself.

From Node Weekly #326[1]:

The Main npm Repository Suffered an Outage on Monday[2] – But Here's What to Do For Next Time.. — For a period of time on Monday, the main npm repository was returning 429 “Too Many Requests” responses, breaking some people’s installations and CI processes (here’s a postmortem of why[3] – it was due to a Cloudflare policy change and not npm's fault).

This sort of thing happens from time to time, but is a good reminder to be aware of being able to switch to alternative mirrors[4] or begin caching and proxying the fetching of dependencies via a tool like Verdaccio[5]. More ideas in this Twitter thread[6].

[1] https://nodeweekly.com/issues/326

[2] https://github.com/npm/cli/issues/836

[3] https://github.com/npm/cli/issues/836#issuecomment-587019096

[4] https://open-registry.dev/

[5] https://verdaccio.org/en/

[6] https://twitter.com/bitandbang/status/1229467759437910016

I'll miss GetPocket app, despite what the article said it works offline on Desktop. Anyone known about an alternative?