Earlier quoted context omitted.
The author is one of the most influential NFT critics: e.g. https://amp.smh.com.au/business/companies/extortion-why-web3...
Thanks forkfork. I'm _absolutely_ not an NFT shill and my avatar is funny af because NFT/Web3 is meant to be decentralised but it's built on central platforms. The avatar/pfp that I use received a DCMA takedown thus is an doubley illegal NFT [this will make sense if folks are aware of the RRBAYC lawsuit] that I can't change. It exists in "my wallet" but it can't be used anywhere. ps. The first ever Crypto Policy Symp…
Visual Studio Code is designed to fracture
131–140 of 149 posts
Re: Visual Studio Code is designed to fracture
#132I was reading [this]( https://news.ycombinator.com/item?id=27687450 ) yesterday, and somebody said something to the effect that we should trust Microsoft, because they've turned around on OpenSource. That we should judge them by their "years now" actions, instead of the past. I tried to formulate a response to this which explained why we couldn't trust them, and it was all a slow-burn ruse, but gave up. This article…
embrace, extend, extort?
Re: Visual Studio Code is designed to fracture
#133Re: Visual Studio Code is designed to fracture
#134Holy hell, this blog is virtually unreadable. Article content aside, the fact that after pretty much every single paragraph there's 1-2 giant links to some other article and/or an ad is just infurianting and makes it impossible to focus. I stopped reading after the first few and will be adding this site to my blocklist.
When I first saw them I thought maybe they were ads, or there was a mistake and I ran into the end of the article early.
I liked the post, though! Geoffrey, please reconsider this citation style where you have an ellipsis and then giant link previews. I think it distracts from good content. Could similar link previews upon hover still scratch the itch that drove you to try these link previews?
Re: Visual Studio Code is designed to fracture
#135Earlier quoted context omitted.
See, what I would do in my case is I would just make a bash script for sftp. I'm not even sure if small devs benefit from such a bloated editor: the time you have to invest in writing a script or learning a command-line tool is to some extent time invested in learning a fungible skill, whereas time you invest in learning a graphical tool is usually not as extensible or reliable. A major time-sink in a previous job si…
The upshot of such a graphical IDE for me is basically lots of panes and windows to rapidly search in. I might have one library I've branched 7 times for 12 projects and need to have a few open and jump quickly to which version some line of code is referencing. It also helps with keeping version control and history right next to the working files. A bash script would be fine for syncing but it's not going to give me…
Your workflow sounds particular, if you want to upload hodgepodges of multiple branches to various environments manually. But I think you could do the same kind of thing pretty well with lsyncd + git-worktree with a checkout for each environment, plus additional checkouts for whatever you're developing. Check out a different version of a file in the worktree associated with staging, and lsyncd automatically syncs that change to staging.
(It sounds like VSCode serves you very well for now, so I'm not urging you to change or anything. Just thinking aloud about some alternatives and what using them might look like for use cases similar to yours.)
Re: Visual Studio Code is designed to fracture
#136I was reading [this]( https://news.ycombinator.com/item?id=27687450 ) yesterday, and somebody said something to the effect that we should trust Microsoft, because they've turned around on OpenSource. That we should judge them by their "years now" actions, instead of the past. I tried to formulate a response to this which explained why we couldn't trust them, and it was all a slow-burn ruse, but gave up. This article…
Re: Visual Studio Code is designed to fracture
#137I had to use VS Code it briefly for a class, and was kind of shocked by the telemetry stuff, and that it's just ignore-accepted by both the students and the instructors. But what turned me off more was this janky feeling around the whole application, something I don't remember experiencing in many other Microsoft tools, such as VB. It feels like it was designed from the code up rather than from the interface down, an…
FYI you can get around HSTS errors on Chromium-based browsers by typing thisisunsafe. Source: https://chromium.googlesource.com/chromium/src/+/d8fc089b62c...
/**
* This allows errors to be skippped by typing a secret phrase into the page.
* @param {string} e The key that was just pressed.
*/
function handleKeypress(e) {
// HTTPS errors are serious and should not be ignored. For testing purposes,
// other approaches are both safer and have fewer side-effects.
// See https://goo.gl/ZcZixP for more details.
var BYPASS_SEQUENCE = window.atob('dGhpc2lzdW5zYWZl');
if (BYPASS_SEQUENCE.charCodeAt(keyPressState) == e.keyCode) {
keyPressState++;
if (keyPressState == BYPASS_SEQUENCE.length) {
sendCommand(SecurityInterstitialCommandId.CMD_PROCEED);
keyPressState = 0;
}
} else {
keyPressState = 0;
}
}Re: Visual Studio Code is designed to fracture
#138I had to use VS Code it briefly for a class, and was kind of shocked by the telemetry stuff, and that it's just ignore-accepted by both the students and the instructors. But what turned me off more was this janky feeling around the whole application, something I don't remember experiencing in many other Microsoft tools, such as VB. It feels like it was designed from the code up rather than from the interface down, an…
> The situation with bad application behaviors being "baked into the code" and propagating to all the "free" distributions is very sad, similar to what's happening with both Chrome and Firefox. > For example, HSTS is now baked into the all the standard distributions and there's absolutely no way (that I've found) to turn it off. I understand the "security" reasons behind it for regular users, but as someone mindful a…
Baffling to me is that one would assume .dev domains are being used for development adjacent purposes. I might, for example, have a piece of in-development software or infrastructure where it is not convenient or even possible without significant effort to get a valid SSL certificate. Now I just can't use that with my .dev domain. Can't use self signed certs on a "development" domain either - who would want to do that though! :)
Re: Visual Studio Code is designed to fracture
#139Earlier quoted context omitted.
Thanks forkfork. I'm _absolutely_ not an NFT shill and my avatar is funny af because NFT/Web3 is meant to be decentralised but it's built on central platforms. The avatar/pfp that I use received a DCMA takedown thus is an doubley illegal NFT [this will make sense if folks are aware of the RRBAYC lawsuit] that I can't change. It exists in "my wallet" but it can't be used anywhere. ps. The first ever Crypto Policy Symp…
I'm not sure it's "funny af," but I'm glad to hear that you're opposed to them.
- https://www.washingtonpost.com/business/2022/06/29/bored-ape...
Re: Visual Studio Code is designed to fracture
#140Earlier quoted context omitted.
FYI you can get around HSTS errors on Chromium-based browsers by typing thisisunsafe. Source: https://chromium.googlesource.com/chromium/src/+/d8fc089b62c...
Doesn't that page indicate something else? /** * This allows errors to be skippped by typing a secret phrase into the page. * @param {string} e The key that was just pressed. */ function handleKeypress(e) { // HTTPS errors are serious and should not be ignored. For testing purposes, // other approaches are both safer and have fewer side-effects. // See https://goo.gl/ZcZixP for more details. var BYPASS_SEQUENCE = win…
window.atob('dGhpc2lzdW5zYWZl');
evaluates to thisisunsafe