josephg

51 ms·

901.
by josephg 1y ago
This is great! I notice that’s on the ditto blog. I can see why the ditto developers are watching with keen eyes! I have a modern digital camera complete with wifi and bluetooth. There’s an app that lets me connect the camera to my iPhone f
902.
by josephg 1y ago
Australia and Denmark are on track to ban social media for kids. I hope scientists are watching - it’ll be fascinating to get some actual data on what happens.
903.
by josephg 1y ago
> Both are based on khtml. We could be living in a very different world if all that effort stayed inside the KDE ecosystem How so? Do you think thousands of googlers and apple engineers could be reasonably managed by some KDE opensource
904.
by josephg 1y ago
> As for IDE's, [...] Emacs and VSCode work fine with C projects, even when debugging interactively. I'm pretty sure VSCode still needs a compile commands file to do proper syntax highlighting. Again, difficult and annoying to
905.
by josephg 1y ago
> You make some good, if oft-repeated, points They're oft repeated because they're real problems. > a plain Makefile works. > C has LSP support, like every other language. I haven't noticed C support in editors to be
906.
by josephg 1y ago
What do you mean? Cargo downloads packages from the internet by default programs do exactly what they’re programmed to do. No more and no less. Just because you’re targeting windows xp doesn’t mean you need to run windows xp to do developme
907.
by josephg 1y ago
> I've few qualms about writing the server in C. Bad Unicode support. Lack of cross platform system libraries. Needing to deal with CMake / autotools / whatever. Poor error handling. No built in string, list or map types.
908.
by josephg 1y ago
> Any decent compiler should be able to shake dead code in source dependencies anyway, therefore there should not be any functional difference between importing specific members and importing the whole package. Part of the problem is tha
909.
by josephg 1y ago
> why is 70kb of source code a problem? Because javascript isn't compiled. Its distributed as source. And that means the browser needs to actually parse all that code before it can be executed. Parsing javascript is surprisingly slo
910.
by josephg 1y ago
Hah! Do you have a running search giving you alerts when lmdb is mentioned or something? > How is doxygen a disaster? I've just never read any good, user friendly documentation ever produced by doxygen. Even when I used it myself. I
911.
by josephg 1y ago
Can you give some examples? I’ve written js / ts for 10-15 years and I’ve never reached for lodash in my life.
912.
by josephg 1y ago
Oh god, without tree shaking, lodash is such a blight. I've seen so many tiny packages pull in lodash for some little utility method so many times. 400 bytes of source code becomes 70kb in an instant, all because someone doesn't k
913.
by josephg 1y ago
So your claim is that sufficiently careful C is just as safe as rust? Seems like a pretty wild claim to make in the comment thread of this article. Google has some of the most careful engineers in the business. They use valgrind & ubsan
914.
by josephg 1y ago
> The mobile internet gets cut locally and temporarily when the Ukraine attacks Russian cities trying to terrorize population. It’s hard to feel sympathetic when Russian bombs have been “accidentally” hitting Ukrainian civilians since da
915.
by josephg 1y ago
> Let’s be clear: the goal is to distribute a tarball which the receiver can build. Thanks for clearing that up. What problem does that solve? I've never tried to do that, but I can see how it would be a pain in the neck. I wonder h
916.
by josephg 1y ago
> I believe that Rust is the language benefiting the most from agentic AI Except in my experience, chatgpt and claude both struggle to write rust code that compiles correctly. Chatgpt is pretty good at complex tasks in typescript like &q
917.
by josephg 1y ago
Can you give some examples? Its hard to agree or disagree if you're not going to make any substantive claims.
918.
by josephg 1y ago
> Rust has a dogmatic, aggressive and self-righteous community that uses any available tactic to push their language through. I'm confused, because that's not been my experience of the rust community at all. I've been very
919.
by josephg 1y ago
> If a language is hard to write at first, it’s always hard to write. That seems obviously false. Most fancy programming languages are difficult to write at first, C++ included. But they all get easier over time. Rust got way easier to w
920.
by josephg 1y ago
> I'd say that rust has a weird level of being both verbose and terse in strange ways. If you ever have to deal with lifetimes, then the verbosity goes up pretty significantly. I find rust generally more terse than both C and - espe
921.
by josephg 1y ago
> That is a surprising opinion. Rust marketing is entirely based - like in this submission - on comparing its memory safety to C/C++ and saying that C is bad! I'm not really sure what you expect here. Like, a large driving fact
922.
by josephg 1y ago
> The compiler is also relatively slow. Would Rust have been worth working with on 30+ year old hardware? As I understand it, a lot of the slowness of the rust compiler comes about from llvm. And how rust and llvm interoperate. Rustc cre
923.
by josephg 1y ago
My favorite framing for this is that rust front loads all the pain. C and C++ are incredibly subtle languages. But you can get a lot of code written before you run into certain foot guns in C and C++. This gives those language a more enjoya
924.
by josephg 1y ago
> The way it should work is that before even writing code, you design a modular acceptance system that runs full suite of tests … Sometimes. It depends on what you’re working on. Part of the fun challenge in writing software is that the
925.
by josephg 1y ago
The only people I’ve met who seem to think it’s a feud war are a few dyed in the wool C++ fans who implicitly hate the idea of programming anything else. Rust is just a language. It has some strengths and weaknesses just like every programm
926.
by josephg 1y ago
Yeah; generally I find CMake rules are much easier to read and modify than autotools and makefiles. With Makefiles there’s about 18 different ways to write a rule to compile something, and I find I need to go hunting through a bunch of file
927.
by josephg 1y ago
> I cannot like Rust syntax, sorry. For me the ideal syntax is C/Go, just to be clear what I like. I’m sorry if this comes across as dismissive, but I find it hard to take people seriously with complaints about syntax like this. Lea
928.
by josephg 1y ago
Can you say more? I’ve found it a joy to use compared to CMake and friends. How does it make it harder to consume something downstream? Seems easy enough to me - just share the source crate. Are you trying to distribute pre compiled code or
929.
by josephg 1y ago
One big source of bugs in TS is structural sharing. Like, imagine you have some complex object that needs to be accessed from multiple places. The obvious, high performance way to share that object is to just pass around references wherever
930.
by josephg 1y ago
Once burned, twice shy. It’s going to take a few more generations to see how long they actually maintain that compatibility for going forward. I suspect consoles will move to arm chips at some point. When they do, will Sony and Nintendo bot

More ›