U sane, bro?
You mean `jj advance bookmarks`? It still seems like a pain to not just have it happen automatically on `commit`. (I use the "experimental" auto-advance-bookmarks feature, but it's got a lot of papercuts.)
I honestly get the sense that several, or possibly most, jj maintainers truly are not familiar with the "typical" way devs use git. They really do not seem to consider branches with many commits to be a common use-case.
I still don't understand your point. The comment you responded to says: >As a general rule, if someone ever posts any kind of career troubles on any platform, the only correct responses should contain sympathy or a…
I don't understand your point; what other type of messages are you saying should be acceptable as a response to a post about career troubles?
Why are you conflating "no intention of doing a rewrite" with his actual wording, "we haven’t committed to rewriting"? The latter does not at all indicate that there would definitely not be a rewrite.
This seems to be missing the point. Sometimes users see error messages. Sometimes they're good, sometimes they're bad; and yeah, software engineers should endeavor to make sure that error behaviors are graceful, but of…
> Reading C++ for dummies even though I had untreated ADHD and couldn’t sit still long enough to get much past std::cout. You may have lucked out. I also didn't get terribly far in that book, but I thought it was fairly…
Like a lot of blog posts, this feels like a premise worth exploring, lacking a critical exploration of that premise. Yes, "inevitabilism" is a thing, both in tech and in politics. But, crucially, it's not always wrong!…
If 20% of people really think they'd be better off as factory workers, that's actually kind of a lot. Can you imagine if 20% of the working population really did work in factories? That's an enormous number.
So the "right way" is to replace all hardware with new hardware, and the second-best solution is for CISC systems to emulate a specific RISC architecture? And you think this will be more maintainable, performant, etc?…
Are you proposing a kernel that would only run on risc-v hardware, or expecting that people would run some kind of emulator? ....or do you think that because RISC-V is "standard", assembly for RISC-V would run on any…
Any good Vim-emulator extension has macro support. VSCode also has an extension that lets you run the actual neovim server to manage your text buffer. The settings GUI in VSCode is just an auto-generated layer over raw…
Precisely true, but from a PHP background, I assume there's not much to prepare you for this.
That's...not...how threads or async work...? > Blocking I/O executed on another thread, with a callback to execute when done, becomes async I/O (from the user's PoV). That's not what we're talking about when we discuss…
That's...not precisely true. The C++ standard doesn't specify how std::async works, and for a while GCC just ran the operation sequentially, and later both GCC and Clang launched new OS threads by default.…
Well, yeah. Hence the rest of my comment. And if you don't go through glibc, then you still must follow the C ABI rules (since that's the only thing the kernel understands), and you are at risk of having your calls…
It's "organic" because, as this article is pointing out, creating alternatives is really difficult due to this exact lock-in, both at the OS level and at the hardware-vendor level. You shouldn't need a "miracle…
You still have to follow the C ABI when interfacing with C. That's the exact problem being called out in the post. Zig solves interoperability by incorporating an entire copy of LLVM. Go does do bare metal syscalls, but…
It used to have a motto that was something like "a shell for the github age", and I guess they never picked something more appropriate.
Nothing in this article seems to be saying that C "isn't useful". It also doesn't state that bounds checks are the "most difficult thing in software development." As the article mentions, C is 50 years old. The fact…
> I'd add a recommendation at the top of this to have a Rust compiler handy. If you haven't already, check out the Playground: https://play.rust-lang.org/ It's reasonably full-featured for a web IDE (much more so than…
I understand; I used Beamer back in college. It just seems like that's not really a good fit for the original purpose of PDF files. If they wanted to support presentations, maybe they should have created a new file type…
Did it, though? AFAIK Node still doesn't have OS threads, which are the expensive version. The "About" page still says that Node is "designed without threads": https://nodejs.org/en/about/
An `async` function _can_ call blocking functions, of course, it just blocks the entire thread of execution which could otherwise continue making progress by polling another future.
U sane, bro?
You mean `jj advance bookmarks`? It still seems like a pain to not just have it happen automatically on `commit`. (I use the "experimental" auto-advance-bookmarks feature, but it's got a lot of papercuts.)
I honestly get the sense that several, or possibly most, jj maintainers truly are not familiar with the "typical" way devs use git. They really do not seem to consider branches with many commits to be a common use-case.
I still don't understand your point. The comment you responded to says: >As a general rule, if someone ever posts any kind of career troubles on any platform, the only correct responses should contain sympathy or a…
I don't understand your point; what other type of messages are you saying should be acceptable as a response to a post about career troubles?
Why are you conflating "no intention of doing a rewrite" with his actual wording, "we haven’t committed to rewriting"? The latter does not at all indicate that there would definitely not be a rewrite.
This seems to be missing the point. Sometimes users see error messages. Sometimes they're good, sometimes they're bad; and yeah, software engineers should endeavor to make sure that error behaviors are graceful, but of…
> Reading C++ for dummies even though I had untreated ADHD and couldn’t sit still long enough to get much past std::cout. You may have lucked out. I also didn't get terribly far in that book, but I thought it was fairly…
Like a lot of blog posts, this feels like a premise worth exploring, lacking a critical exploration of that premise. Yes, "inevitabilism" is a thing, both in tech and in politics. But, crucially, it's not always wrong!…
If 20% of people really think they'd be better off as factory workers, that's actually kind of a lot. Can you imagine if 20% of the working population really did work in factories? That's an enormous number.
So the "right way" is to replace all hardware with new hardware, and the second-best solution is for CISC systems to emulate a specific RISC architecture? And you think this will be more maintainable, performant, etc?…
Are you proposing a kernel that would only run on risc-v hardware, or expecting that people would run some kind of emulator? ....or do you think that because RISC-V is "standard", assembly for RISC-V would run on any…
Any good Vim-emulator extension has macro support. VSCode also has an extension that lets you run the actual neovim server to manage your text buffer. The settings GUI in VSCode is just an auto-generated layer over raw…
Precisely true, but from a PHP background, I assume there's not much to prepare you for this.
That's...not...how threads or async work...? > Blocking I/O executed on another thread, with a callback to execute when done, becomes async I/O (from the user's PoV). That's not what we're talking about when we discuss…
That's...not precisely true. The C++ standard doesn't specify how std::async works, and for a while GCC just ran the operation sequentially, and later both GCC and Clang launched new OS threads by default.…
Well, yeah. Hence the rest of my comment. And if you don't go through glibc, then you still must follow the C ABI rules (since that's the only thing the kernel understands), and you are at risk of having your calls…
It's "organic" because, as this article is pointing out, creating alternatives is really difficult due to this exact lock-in, both at the OS level and at the hardware-vendor level. You shouldn't need a "miracle…
You still have to follow the C ABI when interfacing with C. That's the exact problem being called out in the post. Zig solves interoperability by incorporating an entire copy of LLVM. Go does do bare metal syscalls, but…
It used to have a motto that was something like "a shell for the github age", and I guess they never picked something more appropriate.
Nothing in this article seems to be saying that C "isn't useful". It also doesn't state that bounds checks are the "most difficult thing in software development." As the article mentions, C is 50 years old. The fact…
> I'd add a recommendation at the top of this to have a Rust compiler handy. If you haven't already, check out the Playground: https://play.rust-lang.org/ It's reasonably full-featured for a web IDE (much more so than…
I understand; I used Beamer back in college. It just seems like that's not really a good fit for the original purpose of PDF files. If they wanted to support presentations, maybe they should have created a new file type…
Did it, though? AFAIK Node still doesn't have OS threads, which are the expensive version. The "About" page still says that Node is "designed without threads": https://nodejs.org/en/about/
An `async` function _can_ call blocking functions, of course, it just blocks the entire thread of execution which could otherwise continue making progress by polling another future.