• 3 Posts
  • 714 Comments
Joined 2 years ago
cake
Cake day: March 22nd, 2024

help-circle




  • Small thing, but I don’t know how I’m going to top the surreality of waking up one morning on a trip to Austria with my high school orchestra to hear the TV playing a German-language kids show doing a puppet version of Monty Python’s dead parrot sketch. “Das vogel ist tot” indeed. Mostly I was surprised that I was able to recognize it given my total lack of German language skills beyond counting to 5 and saying “I’m sorry, I’m a foreigner and don’t speak German” because sometimes the American stereotypes are absolutely true.

    Overall I actually had a lot of fun on that trip, and got to be absolutely insufferable about having been to Europe when I got back. See again, American stereotypes.








  • This is fascinating. Ignoring, for a moment, the assertion that AI agents are sentient beings somehow, what struck me about both part 1 and 2 is the bafflingly sincere excitement about turning a fairly straightforward software project into “building a new civilization”, and the assumption that this whole process will be best repeated for every software project. Let’s even ignore the abysmal economics of needing to effectively invent the universe in order to add apple pie to your crappy flash game. It’s absolutely wild and possibly malpractice for an engineer to be this excited about the needless expansion of scope and complexity of a project. It really showcases the kind of mindset it takes to be this breathlessly excited about the sheer number of different components that are being worked on in order to eventually somehow make a game happen. This is the dopamine rush of seeing the agents do something combined with an abdication of any responsibility for exactly what they do.




  • I think there’s some truth to that, but it also bears acknowledging that the market demand existed already. The number of people who can get a lot of benefit from IT productivity tools is much higher than the number of people who are willing to do the work of maintaining and customizing their own stuff. From an organizational perspective, it often ends up making more sense to directly contract with a known and trusted third party instead of developing the native capabilities, and at that point the tools and skills themselves start to specialize in ways to provide IT as a service at scale. Economies of scale lend themselves to efficiency but at the cost of resiliency and concentrating power, and tech companies chasing the line ever upwards have been abusing the absolute hell out of that, but while they have been altering the deal (pray they do not alter it any further) their bullshit is not the only reason why the deal exists in the first place.


  • I read through the white paper and I have further concerns even for any readers who are comfortable fucking over blind people (for the record: fuck you if you’re reading this). It looks like this works off of the same kind of technique that allows fonts to render digraphs, positional forms, and emoji, leveraging the font rendering to allow it to jumble up the actual HTML that machines interact with. It’s clever, but the fucking with screen readers, form autofill, and basically anything other than direct text rendering is really obvious.

    I’m also not sure when it runs to generate the dictionary of mappings. The6biggest harm of the content scrapers isn’t that it’s ingesting the content it’s that the repeated requests spam servers and basically DOS smaller sites out of existence. This is why iocaine is so brilliant and imo remains the gold standard. If the dictionary is generated when the files ar uploaded to the server or set to be displayed then this merely fails to address the real problem, but if the expectation is that this mapping gets created and distributed at request time then that just makes scraping even more expensive for hosts. Given that it works on dynamic text in their example it looks like at least part of the mapping runs on the client, so it’s increasing the size of the package if nothing else. Bandwidth may be pretty cheap these days, but that’s no reason to be wasteful.




  • I think corporate consolidation is a huge part of it, but I think a lot of software and tech falls into the same trap that a lot of infrastructure projects do: even if everyone uses it, nobody wants to think about it. That general apathy (until it fails catastrophically in a bridge collapse or a major service outage) limits the avenues for feedback on whether software is actually good or not in the same way that people don’t have a lot of feedback on whether a water main is being routed in a reasonable way. It also creates room for grifters who specialize in obfuscating exactly what you’re paying for.