635 karma · joined August 3, 2016
My switch a few years back has been almost universally positive, though I do read less as a result.
> Do you want to be Oracle? Because this is how you become Oracle. -1
Revenue: "US$39.83 billion (2018)" - I can see a few reasons why they might hah
https://github.com/python/cpython/pull/8122/files#diff-0ad86...
This just seems a little too commercial to me and I'm not sure I like the phrasing. I fully understand the need for Troy to be sponsored and it's great that 1Password works well with his tooling, but it's not the only solution. I'd feel a little less uneasy if it was phrased in such a way as "Use a password manager, like 1Password".
I guess naively I'm thinking some sort of light/display which says "Amazon is sending/retrieving data" - it would need to be from a third party to have integrity, and I suppose in order to actually allay the fears of the masses it would need to be plug-and-playable.
Does such a thing actually exist?
This isn't a dig at Linux it's simply that we still have lazy content creators using things such as Silverlight to provide content. These applications "just work" on Windows, and when they are at all possible on Linux, they tend to require a lot of manual effort and simply aren't as good as the Windows solutions (Google Drive, Spotify, VPN applications etc.).
I also use my personal laptop for dev, and as I'm an OSS-stack developer, I use Linux. Having the ability to run Linux natively on Windows is superb, and is genuinely usable for work purposes for the most part.
The article doesn't capture a few other bugbears with WSL. The file system is slooooooow (really slow), quite a few applications just flat-out don't work, and others are buggy as hell (psql e.g.). Would I use it in a serious work capacity daily? No - but I'm certainly appreciative that I can use it and it works pretty well 95% of the time.
For example when I'm working on a feature I tend to do n things at once, but I then want to create logical commits which separate the work into logical unit which could be reverted etc. as necessary. If in this process I notice that I've forgotten something (or for that matter, realise later than I've introduced a bug / broken tests) I'll tend to create a patch commit for that logical unit and then `git rebase -i HEAD~n` and then fixup that patch into the original commit.
Also, whenever I'm done for the day instead of stashing I: `git commit -am "wip"; git push; git reset HEAD~1 --soft` (i.e. push my changes up to Origin to avoid any localized mishaps with my PC resulting in a loss of work). I then force push to my feature branch.
I know that both of these "change history", but as long as they're isolated to my own feature branches I see no reason to avoid doing so...
These things always make me chuckle