mcronce

6 ms·

241.
by mcronce 4y ago
Nope, as far as I know there's no serverside HTML generation crate. Granted, I haven't looked, but I feel like it would have come up on /r/Rust sometime. Everything else you mentioned is out there, although I didn'
242.
by mcronce 4y ago
Better suited in what way? I've written HTTP APIs in all of the above - plus Python and PHP - and choose Rust for new ones 99% of the time. Just recently I had a need for a fairly simple webapp. Whipped up the back end in Rust in, li
243.
by mcronce 4y ago
> I can see how it might be easy to get nerd-sniped trying to get rid of every last allocation Honestly, this is a really good way to put it, and that one minute rule sounds like a pretty good rule (ignoring cases where performance requi
244.
by mcronce 4y ago
That's what tokio does under the hood.
245.
by mcronce 4y ago
On the subject of phones with keyboards, I miss sliders :(
246.
by mcronce 4y ago
Hand-waving away the transmission/storage required to make intermittent energy sources "reliable" does not magically make them trivial, or even solved, problems. I don't really care whether or not nukes are cheap when th
247.
by mcronce 4y ago
I recall one with the CPU socket on the back of the board, maybe that's what you're thinking of? IIRC both LTT and GN did videos about it
248.
by mcronce 4y ago
It also removes a big chunk of metal and fans taking up space on your motherboard, covering other slots. It adds complexity, not really sure what the "overhead" here is that you're referring to.
249.
by mcronce 4y ago
> rust also incurs a non-negligible ongoing productivity cost for its complexity This isn't really consistent with my experience. Compared to writing other languages with varying levels of strictness (C, Python, Go to name a few),
250.
by mcronce 4y ago
When you ("you" in this comment is probably most usefully read as "a compiler" :) ) monomorphize a generic function or data structure with the various type parameters that it's been called with, you make a copy of t
251.
by mcronce 4y ago
I was thinking as I read that comment that it seemed unlikely you would not only (1) attempt to use companies' logos without their permission and without accurately representing the relationship, but also (2) get away with it
252.
by mcronce 4y ago
This seems to have worked pretty well with the "core return" system on used 12V batteries for ICE vehicles. Even with a pretty small (usually $15-20 in my experience) financial incentive, people do tend to bring them in.
253.
by mcronce 4y ago
> the costs of the backup generators and batteries Just to put an extra-fine point on this...the backup generators are typically fossil fuel fired, so the unpaid externalities apply to those as well.
254.
by mcronce 4y ago
I've only ever seen OKRs attempt to be used by ineffective management who want to reduce everything, people included, to a number.
255.
by mcronce 4y ago
Yep - I never really have an issue with a safety razor. At least, not on my face...the one time I tried to shave my head with it I looked like some shit out of Hellraiser until I showered haha
256.
by mcronce 4y ago
Having used both, one is no more "brainless" than the other. It's the same shaving process. The only difference is cost.
257.
by mcronce 4y ago
Also, in what universe are those expensive multi-blade razors faster or more convenient than a safety razor with a Feather blade?
258.
by mcronce 4y ago
I use Rust for just about everything and I can definitely think of plenty of warts, but none of them make it "not quite ready for serious work" for my definitions of "serious work". I guess my point is that I'm cur
259.
by mcronce 4y ago
In practice, it's been a pretty common problem at organizations I've worked in.
260.
by mcronce 4y ago
I'd choose Node or PHP over Go for a greenfield project. (Although I can't think of a case where I'd choose them over Python.) All of those languages at least give me an FFI escape hatch in case I need it that isn't ab
261.
by mcronce 4y ago
> runtime costs of the overuse of Interface{} (prior to Generics at least) Generics aren't going to improve this situation - at least not the current iteration of generics :(
262.
by mcronce 4y ago
> auto-bubbles up if not handled I'm guessing you already know this, but for anybody else reading - this isn't entirely accurate; Result::Err doesn't auto bubble up like an exception, you have to manually bubble it up.
263.
by mcronce 4y ago
> every mainstream language with easy FFI still has significant FFI overhead (so much so that many programs actually run slower with FFI). This isn't really true for Rust This isn't true for almost any language to the extent it
264.
by mcronce 4y ago
I'm not talking about an actual static binary, I'm talking about a typical "mostly static" binary with the handful of common dynamic dependencies.
265.
by mcronce 4y ago
And as a bonus, be statically linked with all the benefits that brings.
266.
by mcronce 4y ago
That would be great if Go provided better performance. With its awful FFI, you have no recourse when you hit its limits other than to rewrite the entire codebase in something else. As with many things, there's nothing stopping you fro
267.
by mcronce 4y ago
Serializing a request structure, making an IPC/network call, deserializing the request structure, serializing the response structure, sending it back, and deserializing it ... isn't really a solution when the purpose of an FFI cal
268.
by mcronce 4y ago
> Go is a language that gets out of your way, encourages you to solve your problem Maybe I'm just too dumb for Go, but this is not consistent with my experience at all. Go's insistence on pretending that complexity doesn'
269.
by mcronce 4y ago
> In my experience, people can't actually read everything on the screen at one time anyway, and the more dense/terse things are the harder it is to read (otherwise we would minify everything). Whether or not you can read everyt
270.
by mcronce 4y ago
Screen real estate is limited, especially vertical real estate. Compared to languages with saner error handling, I can read approximately 25% as much Go code at once. That's a real cognitive burden when maintaining code or learning y

More ›