Since I have you, if you could humor me at all, what do you think the biggest current sticking point to average Rubyists just flat out switching to TruffleRuby is nowadays? Or isn't there one?
50,064 karma · joined May 1, 2007
twitter/x: cooperx86
Since I have you, if you could humor me at all, what do you think the biggest current sticking point to average Rubyists just flat out switching to TruffleRuby is nowadays? Or isn't there one?
But yeah, I agree with your point about native extensions. Ruby has gotten so much faster in every form in the past couple of years that I think we could bring a lot more "in house". I think there have been some efforts with this regarding Psych in core as well?
(Both running identical pure Ruby code, no extensions, in a long-running test scenario, no setup each time.)
Also it turns out it wasn't a Kodak camera, but a Casio QV 10 I had much earlier. You can sorta see what I meant here: https://medium.com/people-gadgets/the-gadget-we-miss-the-cas... .. though the resolution is far lower too. The weird blocky color aberrations aren't just JPEG artefacts but related to the same quantization ordering issue I think.
If you find your popular, expensive tool leans heavily upon third party tools, it doesn't seem a crazy idea to purchase them for peanuts (compared to your overall worth) to both optimize your tool to use them better and, maybe, reduce the efficacy of how your competitors use them (like changing the API over time, controlling the feature roadmap, etc.) Or maybe I'm being paranoid :-)
I can't help but wonder if this matter could result in an io.js-like fork, splitting Node into two safe-but-slow-moving and AI-all-the-things worlds. It would be historically interesting as the GP poster was, I seem to recall, the initial creator of the io.js fork.
This is one only data point but my dad was a programmer and frequently complained about cognitive decline once he hit his mid 50s. From talking to him, he remained sharp at a conceptual and high level, knowing what he wanted to do and how it would be done, but struggled with the tooling, the logistical details, etc. He didn't make it to the AI era, alas, but AI could be a god send for people who have the proven technical chops and background but find juggling a lot of minutiae is becoming difficult.
Right. If these tools are so good (and they are) there should be numerous better-than-Slack apps by now that let you do exactly what you want. It doesn't take Anthropic to make it. (At our company, we cheated and edited 37signals' Campfire instead because we got sick of Slack's ads pushed into our paid instance.)
I know you were simplifying, and not to take away from your well-made broader point, but an API-derived implementation can still result in problems, as in Google vs Oracle [1]. The Supreme Court found in favor of Google (6-2) along "fair use" lines, but the case dodged setting any precedent on the nature of API copyrightability. I'm unaware if future cases have set any precedent yet, but it just came to mind.
[1]: https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_....
I'd take that tradeoff. On my M3 Ultra, the inference is surprisingly fast, but the prompt processing speed makes it painful except as a fallback or experimentation, especially with agentic coding tools.
However, I tried "a picture of jacquesm planting a flag on the Moon" for a laugh, and I have to hand it to Google as the person was in a spacesuit, as they should be, and totally unidentifiable! :-D
It's no quick fix. The new six month (previously two year) unfair dismissal rules from January 2027 already impact annual fixed term contracts. As the end of a fixed term contract is legally a "dismissal", it'll be necessary to go through the full process.
I suspect some low-level service industry employers will sense the weakness of the jobs market and increase employee turnover by giving people contracts of under six months then rinse and repeat from the queue of applicants, which would suck for someone who wants a temporary job for a year or two like students.