slowcache

This is great advice to become a pain in the ass that managers know they need to keep on a short leash.

There's a big difference between "I'm going to put this into prod on tuesday unless you tell me otherwise" vs "I'm going to put a prototype together for review on Tuesday unless you tell me this is a waste of time"

We would still expect an accountant to know the formula to arrive at the expected result if they did not have a calculator at hand

I'm not really sure what niche this fills.

To me, the main draw looks to be the invariants that you can supply within functions, but this isn't a new concept outside of it being a dedicated keyword. Otherwise this looks like rust without all of the functionality

high-performance data processing tools in JS

I may be naive in asking this, but what leads someone to building high perf data tools in JS? JS doesn't seem to me like it would be the tool of choice for such things

This is a cool website, and it looks great too

But it definitely could use some better moderation

The reviews must be heavily AI assisted in order to get that sort of volume in.

Either way, it doesn't surprise me that this number is so high. Productivity chasing is the name of the game for AI, regardless of how sustainable or helpful this extra work done actually is

This post is like 6 months late. I share the same concerns that others in the thread do, but the talking point is pretty tired by now

Really blown away at how well this works on mobile. Awesome stuff

I was also wondering this. I don't want my codebase to be a shared word document, how will it ever be in a compilable state?

Odin has been really growing on me lately as a language that checks all of those boxes. String types, first class allocators, built in tests, a batteries included philosophy, and ease of use are some of the things that really drew me towards it.

I really wanted to like rust and I wrote a few different small toy projects in it. At some point knowledge of the language becomes a blocker rather than knowledge the problem space, but this is a skill issue that I'm sure would lessen the more I used it.

What really set me off was how every project turned into a grocery list of crates that you need to pull in in order to do anything. It started to feel embarrassing to say that I was doing systems programming when any topic I would google in rust would lead me to a stack overflow saying to install a crate and use that. There seemed to be an anti-DIY approach in the community that finally drew me away.

I didn't think that this was much of a thing that needed to be investigated. Adding additional processing into your code will make it slow down.

On a related note, I had a consultant come into my work one time to the teach us some pragmatic things in C++. One of the lessons was that that gcc will not attempt to reorder the code within a try block to optimize it. This could be leading to some very minute slowdown in a C++ app in addition to the overhead associated with try/catch as a whole