Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ChrisSD
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
121.
▲
by
ChrisSD
4y ago
The difference between Windows ".." and unixy ".." is that the former is done lexically whereas the latter is a link to the canonical parent. E.g. on Windows: "path\to\..\file" is always the equivalent of "
122.
▲
by
ChrisSD
4y ago
You seem to have misunderstood me. The distinction I'm making is not between kernel panic or undefined behaviour. The distinction is between undefined behaviour and defined behaviour. That defined behaviour can be anything, even includ
123.
▲
by
ChrisSD
4y ago
There's no "walking back" here. From Rust 1.0 the language was "guaranteed memory safety " https://web.archive.org/web/20150516132407/https://www.rust-...
124.
▲
by
ChrisSD
4y ago
That's all very well but the Rust-in-Linux advocates are advocating for #2 and fully agree with Linus on #1. So attacking #1 is attacking straw.
125.
▲
by
ChrisSD
4y ago
What is better: continuing to "limp along" in some unknown corrupted state (aka undefined behaviour) or in a well defined (albeit invalid) state?
126.
▲
by
ChrisSD
4y ago
Yeah, I'd emphasize that moving something to the standard library doesn't magically solve maintenance issues. In fact if the community can't even maintain something then that's a strong argument for it not to be moved so
127.
▲
by
ChrisSD
4y ago
I've recently simplified my note-taking workflow but there are complexities. IMHO, a note taking application needs a way to at least do the following with notes: * View and edit * Organise * Search * Sync All in one solutions can be ni
128.
▲
Rust Foundation Trademark Policy: Review and Survey
(foundation.rust-lang.org)
1 points
by
ChrisSD
4y ago
|
0 comments
129.
▲
by
ChrisSD
4y ago
It's a quirk of history, imho. If Win32 had been written without concern for what came before, it probably would have more closely followed NT conventions. But it wasn't. It followed on from Win16 and DOS so, to an extent, it emu
130.
▲
by
ChrisSD
4y ago
There is an official Universal CRT Redistributable.
131.
▲
by
ChrisSD
4y ago
The UCRT has even been present since Windows 7, if users keep up with updates. Or if applications bundle the UCRT installer with their own.
132.
▲
by
ChrisSD
4y ago
It does take a bit of getting used to. Zulip is kind of a cross between chat and a forum. However, once I did get used to it I think it's been great. Organizing chat into defined topics is super useful for following discussions you
133.
▲
by
ChrisSD
4y ago
The registry is the raw database. The Policy Editor is the human interface with comments and other niceties.
134.
▲
by
ChrisSD
4y ago
Note that this is a serious language proposal, but with a funny placeholder name so as to avoid bikeshedding until the feature is ready.
135.
▲
by
ChrisSD
4y ago
Note that there are plans to integrate crossbeam's channel implementation into the standard library. This won't change the public API but would at least vastly improve the implementation. A similar thing was done with changing th
136.
▲
by
ChrisSD
5y ago
This is true of *nix but on Windows they can be absent. In face this is the default for GUI applications.
137.
▲
by
ChrisSD
5y ago
A third way is to grant the parent process access to the child such that they can use the child process handle to "remotely" set restrictions, write memory, start a thread, etc.
138.
▲
by
ChrisSD
5y ago
With the caveat that ESU (Extended security Updates) cost companies increasing $$$ for every year after extended support ended.
139.
▲
by
ChrisSD
5y ago
The issue there is that the Windows kernel does not validate Unicode. Linux has the same essential problem. Or more so, in that it does not specify an encoding at all.
140.
▲
by
ChrisSD
5y ago
> Rust (LLVM) pragmatically call[s] CommandLineToArgv This is not correct. It calls `GetCommandLine` to get the raw command line string and then attempts to parse it in the same way as modern C/C++. https://github.com
141.
▲
by
ChrisSD
5y ago
Yes the shell interprets it first. `cmd.exe` does very little processing and mostly passes on the literal string. But what it does do can be confusing (e.g. `^` is an escape character which is annoying if you were trying to pass in a regex)
142.
▲
by
ChrisSD
5y ago
It's truly weird and I don't understand it. I mean not to defend Firefox but the HN reaction is almost comically extreme. --- Chrome: ...and so our company's puppy kicking campaign was a total success. In other news, we'
143.
▲
by
ChrisSD
5y ago
> Microsoft is also shipping pre-compiled projections for Rust/WinRT. Eh, sort of. They're basically shipping the Rust equivalent of C header files and import libraries. Whereas before they would parse metadata in a build scrip
144.
▲
by
ChrisSD
5y ago
For whatever it's worth Rob Pike seems to credit Ken Thompson for the invention, though they both worked together to make it the encoding used by Plan 9 and to advocate for its use more widely.
145.
▲
by
ChrisSD
5y ago
As I said, there are many reasons UTF-8 is a better encoding. And indeed compact, backwards compatible, encoding of ASCII is one of them.
146.
▲
by
ChrisSD
5y ago
There are many reasons why UTF-8 is a better encoding but UTF-16 does at least have the benefit of being simpler. Every scalar value is either encoded as a single unit or a pair of units (leading surrogate + trailing surrogate). However, Po
147.
▲
by
ChrisSD
5y ago
It should be noted that Cargo (the Rust package manager) has slightly stricter requirements here: https://doc.rust-lang.org/cargo/reference/semver.html > Initial development releases starting with "0.y.z&q
148.
▲
by
ChrisSD
5y ago
https://users.rust-lang.org/t/psa-please-specify-precise-dep... Essentially there are a few popular Rust libraries that add functions in patch versions (or have done so in the past). This makes it necessary for users o
149.
▲
by
ChrisSD
5y ago
It's essentially the old adage about selling shovels during a gold rush.
150.
▲
by
ChrisSD
5y ago
What's the Python issue?
More ›