hgs3

13 ms·

181.
by hgs3 3y ago
For what it's worth you can implement a C compiler in under 10kLOC. Chibicc is only a few thousand lines [1]. There is also Cake [2] and tinycc [3] which are both relatively small. [1] https://github.com/rui314/chi
182.
by hgs3 3y ago
You're not "wrong" but Sqlite isn't your run-of-the-mill project. "The SQLite file format is stable, cross-platform, and backwards compatible and the developers pledge to keep it that way through the year 2050.&quot
183.
by hgs3 3y ago
The "open ecosystem" does a poor job funding open source developers. It is completely understandable when a developer chooses to put food on the table over being part of their social club.
184.
by hgs3 3y ago
> Great to see we have alternatives. I'd rather see alternatives from individuals and small business. Microsoft can subsidize whatever freebie project they want simply because of their cash reserves. Redis, on the other hand, is the
185.
by hgs3 3y ago
Is there an equivalent of Reddit run by a non-profit?
186.
by hgs3 3y ago
We need proactive antitrust laws that break up companies beyond a certain size criteria. There are many markets beyond the tech sector that need a breakup. But no, lets wait until there is enough outrage before the DoJ laggardly assembles a
187.
by hgs3 3y ago
Why are antitrust laws so reactive? Why not have proactive laws that break up companies if they grow beyond a certain size criteria? Ideally, the criteria would be aggressive enough to kill large corporations leaving behind only small to me
188.
by hgs3 3y ago
For macOS, native historically (OS X onwards) means Cocoa and Objective-C. Swift and Swift UI are the new kids on the block. I haven't dabbled with them much, but my two cents is Swift is a lot more complicated than Obj-C and Swift UI
189.
by hgs3 3y ago
> It's genuinely difficult to understand why Rust gets rammed down everyone's throats lately Most software companies have a revolving door of developers and they need cookie cutter tools to limit the damage a "bad" de
190.
by hgs3 3y ago
> So, other than maintaining a legacy code base, why try at this point when other options are available? What options would you recommend in 2024? I write C (not C++) and work on projects that are inherently memory unsafe (the last one r
191.
by hgs3 3y ago
It doesn't sound like you're sick of tech but rather sick of profit-focused leadership corrupting it. I feel the same way so I'm starting my own business with values that matter to me. If starting a business doesn't appe
192.
by hgs3 3y ago
I've got an iPad Air 2 running iOS 15.8. My user agent will surely tell you I'm only one or two major versions behind the "latest and greatest" but the hardware itself is a different story. On this device modern GitHub c
193.
by hgs3 3y ago
Whether software blows up or not if an ID is "bad" depends on how it's written. Writing a token to a database without cleaning it up could lead to a security hole that has nothing to do with memory exploitation. I worry the f
194.
by hgs3 3y ago
If you've fallen victim to phishing you're hosed anyway as a malicious process can read and write to the address space of another process, see /proc/$pid/mem, WriteProcessMemory(), etc.
195.
Type-safe parametric polymorphism in C [pdf](open-std.org)
1 points by hgs3 3y ago|0 comments
196.
by hgs3 3y ago
> `cargo` can farm out to the programming language of your choice That's precisely why I like Make. Make lets you specify an input file, the name of an output file, and the shell commands necessary to generate the output file from t
197.
by hgs3 3y ago
> "cargo build", "cargo run", and "cargo test" What about "gcc mycode.c" or "make"? You shouldn't need to reinvent your build system every project.
198.
by hgs3 3y ago
> embrace code generators. You also don't need to limit yourself to the C pre-processor. There are other dedicated pre-processing languages, like M4, and templating languages you can use.
199.
by hgs3 3y ago
> In procedural C land, unit testing is nowhere near as relevant as it is in memory-safe OO lands. I'm not sure why you'd say this. Testing has more to do with the developer than the language. The SQLite project is written in C
200.
by hgs3 3y ago
Most GC concerns surround "stop the world" tracing collectors that "pause" the program unpredictably for an indeterminate time. These collectors are bad for real-time and soft real-time applications for obvious reasons.
201.
by hgs3 3y ago
I've dabbled in PL research before, and not to downplay the work as this is just my opinion, but the Rust ownership system is too invasive. It prevents entire classes of architectures and algorithms from being directly represented with
202.
by hgs3 3y ago
> The Dart compiler knows if I do a null-check, it can treat following references as safe, instead of if let x = x etc. Does Dart bind a new variable 'x' for the if-statement scope or does the if-statement scope refer to the sa
203.
by hgs3 3y ago
Correct me if I'm wrong, but the percentages on page 25 are lower then what you listed? Out of Bounds Reads => 10.1%; Out of Bounds Writes => 34%; Null-Ptr Deref => 4.6%; Type Confusion => 0.9% Uninitialized Pointer Access
204.
by hgs3 3y ago
Code that isn't tested, isn't done. Tests not only verify the expectations, but also prevent future regression. Fuzzing is essential for code that accepts external inputs. Heartbleed was discoverable with a fuzzer.
205.
by hgs3 3y ago
> The title is clickbait. The article is an advertisement for the authors own Go package that addresses the "problem."
206.
by hgs3 3y ago
> It's okay to want better tools. Based on the article I think that "better tool" is the fuzzer. As it points out remote exploits are overwhelmingly caused by bad input validation. These sorts of bugs can be found with fuz
207.
by hgs3 3y ago
Rewriting is questionable. Joel Spolsky has a famous blog post about this from two decades ago that's still relevant today [1]. [1] https://www.joelonsoftware.com/2000/04/06/things-you-should-...
208.
by hgs3 3y ago
TrenchBroom was built from the ground-up for 3D editing. You don't need to use the 2D grid view unless you want to. It looks more "simplistic" because many actions are now performed directly via the mouse in 3D.
209.
by hgs3 3y ago
> Coroutines are fun, but in real code please consider using actual threads. Coroutines are lightweight and trivial to synchronize. They are perfect for small bits of incremental computation, like iterators and tokenizers. Maybe you&#x27
210.
by hgs3 3y ago
> classical music Have you heard neo-classical metal? It's shredding at its finest. Yngwie Malmsteen is the OG, but there are many others I recommend like Hizaki and Syu. Guitarists in this subgenre often release solo albums (no voc

More ›