HN user
likely in order to have those paths easier to copy and paste, but it does so only if !isatty().
I thought the reason was to aid shell scripts that assumed no whitespaces in file names, wasn't it? Also, I believe I've seen single quotes when using `ls` on a terminal, so the behavior is not only for `!isatty()`.
%n takes a pointer and writes (!!) the number of bytes printed so far.
Okay, everyone probably knows this. Let's get a bit more advanced.
Ok, but I didn't know about that. What's the use?
Does anyone else experience the same?
The first time I experienced such a feeling was when Visual Studio .NET came out. Compared to the previous version, Visual Studio 6, the dialogs and wizards in VS.NET gave me a "web-like" feeling. I guess it was one of the first attemps to use the web technologies to make a desktop app. Along with the Active Desktop feature, they were truly ahead of time.
However, that doesn't mean I loved them. VS.NET was slow as hell and I believe it was one of the reasons why VS6 lasted for so long.
It's strange nobody mentioned NX (NoMachine). When I tried it ~10 years ago, it was much faster than VNC, nearly identical to RDP. Why isn't it more popular?
I was also annoyed by it not remembering the scroll position. The site doesn't live up to its name.
This problem also seems to stem from the fact that Zoom has been used primarily in the corporate settings until now, which kinda validates their claim. Definitely not ideal, but understandable.
Do not attempt to check AGPL-licensed code into google3
What is this "google3" thing? Is this the name of their monorepo?
How do you even remember a thread from last year? I'm always surprised by your vast knowledge required for moderation. Possibly with a help of some internal search tools?
I'm in a similar boat with you, so I have a few questions:
1. Why did you switch? Are you satisfied with the new experience?
2. Why was some of the history needed to be squashed? Were there any technical concerns?
But it doesn't have to be VBA. Any language with a decent OLE Automation library would suffice. I've been using Python to automate my Excel files, and am really happy about that. I tried to learn VBA, but could not adapt to its archaic syntax and the clunky VBA editor that comes with Excel.
C and C++ already have such a thing, IIUC. The literal 0 is considered the same as nullptr, if compared to another pointer.
It is a bit worrying that such an overloaded meaning is added again to the language.
I guess what has changed is me, not the computing environment. When I was young, I easily grew impatient when things were going slow. Nowadays I still kinda feel nervous, but not to the point to warrant such bookkeeping methods.
I often would use the mouse cursor to 'mark' the position of the loading bar (we really are spoiled for speed these days).
This is just me, oh my gosh. I thought I was the only one who did that. But now I come to think about it, it can't be true.
It has been a really long time since I used that technique last time...
I'm currently using Galaxy S9 and it is the first phone I decided not to root. I've always rooted my phones since I was introduced to Android, but this time Samsung tied its crucial functionalities with Knox. And Samsung Pay was just too important to me. Too bad more manufacturers are doing this.
I remember him as a very Torvalds-like person, for better or worse.
I wanted him to stay a little more around the Rust 1.0 era because I thought as many warts as possible should have been fixed before the backward compatibility guarantee was made, but he left too early.
Didn't know about the CopperheadOS incident, too bad such a situation happened to him. Good to see it's kinda resolved now.
Wait, how do they build dc? Is there a B compiler for 64-bit systems?
I believe you already know this, hence the "probably" part, but such analog media can easily be produced from (modified) digital media, thus no credibility.
zsh is better than bash in nearly all aspects, at least in my use cases, so this is a great news for me. Is there anything that can be done in bash but not in zsh?
Only one side of the note is printed to resemble currency so as not to run afoul of counterfeiting laws.
Doesn't it? To know for sure we need to take it to the court.
This is another language whose syntax is similar to Rust's. I wonder why the author chose it, in spite of its Go heritage.
Somewhere in Explorer something is passing one of these shell names to a file API, which is interpreting it as a Drive Relative path for the ‘:’ drive.
Isn't this just a pure bug? I'm quite surprised such an intimidating behavior still exists in today's Windows...
What I meant by "automatic" was Ubuntu/Debian's unattended upgrade feature. I've used it for years without any problem, and it has relieved much of my maintenance burden.
Maybe I need to enable it in containers too? I have no idea how to use it on (containerized) Alpine Linux though.
Even without unattended upgrades, finding the list of `Dockerfile`s and `docker-compose.xml`s that might be affected by a new vulnerability sounds more complicated to me. Until now it hasn't been that difficult but I'm still a bit nervous if I somehow missed some vulnerable images.
When I learned Docker for the first time I was so surprised that so few people mention the problem. As one who is used to automatic secutity updates provided by Linux distributions, relying on manual `docker build`s gives me anxiety. I use Docker because it solves many of my problems, but I have not been able to feel easy from potential security concerns from the beginning.
Build-time performance is much improved in .NET Core 2.1, particularly for incremental build. These improvements apply to both dotnet build on the commandline and to builds in Visual Studio.
It is good to see some improvements. Currently, `dotnet build` takes at least 3 seconds to compile a simple hello world project on my system, even when the source code isn't changed at all. At first I thought I did something wrong, but no, others were suffering from this too.[1][2]
This occurs because every `dotnet build` run tries to resolve the dependencies and inspect the file structure to see if any changes are made. And for some reason those operations are dog slow. Visual Studio doesn't have this problem, as it knows the file structure and the dependencies beforehand, so it can determine whether there should be a recompilation easily. I wanted to use VS too but it was too slow for my tiny laptop, so I'm stuck with VS Code.
I hope the improvements are big enough that I can reevaluate using .NET Core again. The build time was a huge obstacle to my iteration cycle, so I had to use TypeScript in my previous project. I sincerely want to code my backends in C#.
Hijacking `ctrl+f` in a webpage should reserve a special spot in hell for the person that decided it was a good idea
But they do it for a good reason. IIRC Discourse does not load all the contents initially so your conventional Ctrl+F won't work correctly. Mind you, I also hate the hijack, but in this case I decided to bear with the unfortunate reality.
I hated the idea of using comments as directives when Go 1.4 introduced //go:generate. But, holy, they were there from the beginning?
They bring back my painful memories of the old days when I had to use conditional comments to support IE6...
the only results I found was something like multiple verbose lines of instantiating an http client and calling methods on it.
I blame the documentation. Not the official documentation (they're not excellent, but OK), but various outdated resources residing in many blogs and sites, including Stack Overflow. I mean, what's wrong with
iwr REMOTE_URL -o LOCAL_FILENAME
There's also the fact that lots of stuff in windows wasn't designed to be accessible through the cli. You can't, for example, make a powershell script to toggle an audio output device on and off
This is just one example. On the other hand, I found nearly every thing I had done using GUI could be replaced by a few lines of PowerShell code. Actually automating my day-to-day GUI operations was my way to learn PowerShell, and mostly it worked great. Microsoft is adding tons of commands each release to expose more system functionalities. There are exceptions of course, but "lots of stuff" is a bit exaggerated.
Why in the design of Windows aren't programs installed or symlinked in the PATH by default? I guess that was a design choice somewhere along the history of Windows/DOS. Is there a reason?
Windows' way of program executable placement is using the holy Registry. It's called 'Application Registration'[1] and was introduced to reduce the needs to modify the system-wide PATH variable. (They thought it was a bad idea to modify a system variable so frequently, and I partially agree.)
You can find registered applications in `HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths`. Very few programs use that feature, which is unfortunate, but popular applications like Chrome and Firefox register themselves in it. That's why you can invoke `chrome` in the 'Run' dialog.
Edit: Another context to add: at the time App Paths was added, to modify PATH you had to edit AUTOEXEC.BAT manually which was painful. Not only that, but also PATH had a length limitation of 128 characters. You can find more details in the Raymond Chen's blog, as useful as always.[2]
[1] https://msdn.microsoft.com/en-us/library/windows/desktop/ee8...
[2] https://blogs.msdn.microsoft.com/oldnewthing/20110725-00/?p=...
I see. I'm also kinda a "runs Vim and writes Makefiles" guy, but I'm more hopeful about the Ubuntu layer being more seamlessly integrated into the native rather than waiting for Cygwin to improve. After all, WSL is official, and Microsoft seems to put a lot of efforts into it.
As a side note, like you said, Cygwin is slow. I once measured how much time compiling things consumed on both Cygwin/MSYS2 and WSL. `./configure` was 3 times faster on WSL, and `make` was 2 times faster. I assume the reason to be WSL's process management being lighter. This is another reason I'm looking forward to see the improvements to WSL's native integration.
Windows does have a C# compiler by default. It is located in the `Windows\Microsoft.NET` folder. Not very discoverable, though.
And starting with Windows 10 a metro app called 'Code Writer' seems to be installed by default for coding. (At least it's there in my installation.) I didn't try it though.