ghoward

12 ms·

91.
by ghoward 4y ago
Funny how you assume that my Windows system is not configured to my usage. I've turned off Windows Defender. I've turned off background tasks that I don't want. I've uninstalled every piece of software I don't want.
92.
by ghoward 4y ago
I have scanned the device. No errors. So now I have evidence contrary to the evidence you assume I have. Windows is still bad. It should work on HDD's.
93.
by ghoward 4y ago
I use HDD's on purpose. If Windows cannot use HDD's, that is bad programming. That's just how it is. Microsoft should not assume that HDD's don't exist. I use an HDD on Windows for two reasons: one, I am cheap, and
94.
by ghoward 4y ago
The disk is about one year old and uses less than 5% of the space available.
95.
by ghoward 4y ago
This doesn't explain why the slowdown is recent, though.
96.
by ghoward 4y ago
It would be sad if we, as an industry, do not take this opportunity to create a better OS. First, we should decide whether to have a microkernel or a monolithic kernel. I think the answer is obvious: microkernel. This is much safer, and se
97.
by ghoward 4y ago
I'm referring to the unions, not teachers. And when I have a kid, I will be homeschooling. Please don't assume. Also, I was briefly a bus driver for a school district during COVID. I was disgusted by how the school buses were run,
98.
by ghoward 4y ago
> Thanks for proving my point. "Inflict[ing] collective punishment" is not what anyone was trying to do. Maybe not, but it's what they did do. For some reason, people mix up intentions and consequences all the time. The
99.
Proprietary Environments Are a Trap(alexn.org)
4 points by ghoward 4y ago|0 comments
100.
by ghoward 4y ago
Thank you, and I agree; it needs to be played with. I've actually got a public "Show HN" scheduled for November 1, but it won't have any of the concurrency stuff then. (I don't have much time to work on it.) I hope
101.
by ghoward 4y ago
I realize I should answer the signal part. tokio::signal-type code would not work for `bc` signals. `bc` is a special program; most programs are I/O-bound, but `bc` is both I/O- and CPU-bound. And it's interactive, so it&#x27
102.
by ghoward 4y ago
I'm glad you said this because my impression of Rust async/await until now was that it was unavoidable, mostly because I heard that all of the big-name crates, the ones you would use in just about every project, use async/awa
103.
by ghoward 4y ago
Mutation will be disallowed in general, yes. It's a bit more subtle than that, but you get the gist. In my language, there are strings, which are fixed size and cannot be reallocated, and string builders, which hide the actual string b
104.
by ghoward 4y ago
> I 1,000% agree with this perspective. I also actually suspect that some form of professional licensing and/or personal liability would benefit the industry greatly, in that it would give more power to engineers to decline to build
105.
by ghoward 4y ago
> I'm trying very hard to not "no true scotsman" myself here. But I tend to think of it like this: there's people, and then there's Twitter personas. There's a lot of very strong, absurd opinions that Twitte
106.
by ghoward 4y ago
> Ah, of course. I knew that they were constants, but I didn't consider the short-circuiting of the comparison before indexing further into the string. No worries! That's why I specifically wrote it that way instead of a `strcm
107.
by ghoward 4y ago
I am part of the structured concurrency crowd, and I agree with you. We (royal we) ignore it too much. I personally like some of the ideas, and I'm implementing those ideas in my structured concurrency language.
108.
by ghoward 4y ago
> I’m sorry that people have implied that, but I feel most of the time when Rust people say languages like C should be retired or deprecated, are doing so because your skill and attention to detail does not scale. This is a fair argument
109.
by ghoward 4y ago
> Those qualifications are going to hold for any advice about technology. They should hold, but the RESF can be too absolutist. The wording of the tweet encouraged that, so I was just trying to push back on it.
110.
by ghoward 4y ago
I have macros for that that I use instead of the keywords. If the keywords appear in code that uses scopes like that, it's a bug. I still have a lot of technical debt with that, but I haven't gotten to it. However, when I do chang
111.
by ghoward 4y ago
No macros. This is one spot where Rust is better than C. (Though it is too limiting for my taste.) Instead, I use ThreadSanitizer and add locks where I may not even need them. Then I may remove some, or change them to different synchronizat
112.
by ghoward 4y ago
Because it is. And it is because you all say things that imply people like me are terrible, awful, evil, no-good, very bad people for not using Rust. We are not. We just have different preferences. You all have also implied that we are negl
113.
by ghoward 4y ago
Anything built without the -a option to configure.sh. You can try the library too, but I did mess up that one time that you already know about.
114.
by ghoward 4y ago
Okay, so I didn't say a release at first, but I meant to. That's only fair. Anything built without the -a option to configure.sh is "the program." That's the vast majority. You can try the library too, but there is
115.
by ghoward 4y ago
It's not lost on me at all. I prefer to finish software. [1] I get it to where it needs to be and put it in maintenance mode. I don't accept outside contributions. [2] I prefer to work alone to keep the scope of my software manage
116.
by ghoward 4y ago
Except that the tweet was pretty absolute. He could have had a reply tweet with something like "unless you have to or you're doing a hobby project." I took issue with the absolutism.
117.
by ghoward 4y ago
Notice that in my first post, I said to use Rust where practical. I never said that everyone should use C. I'm only claiming that I personally can do just as well in C as I could do in Rust, and that I prefer to work in C, so I might a
118.
by ghoward 4y ago
Yes, absolutely. This is how I do it. The test suite and asserts for every assumption are hugely important too. Testing under runtime is important.
119.
by ghoward 4y ago
This is where C fails against Rust. I have to use static analyzers to find such problems. But I do use them, and I also use sanitizers against large and thorough test suites, with excessive fuzzing thrown in for good measure. And I mix all
120.
by ghoward 4y ago
Well, you're not wrong, but I hate C++. With a passion.

More ›