Top Story

• Thanks to AI the future of programming may involve yelling in ALL CAPS. (Ars Tchnica)
  
  Or more specifically, involve "AIs" (which aren't) yelling at each other in ALL CAPS.
  
  In this case, ChatGPT (a chatbot) yelling at DALL-E (an image generator).
  
  And we know this because DALL-E is stupid (though good at producing images) and repeated the instructions ChatGPT yelled at it. It's an idiot savant to ChatGPT's idiot.

Tech News

• Scaling to 15,000 functions and beyond. (OpenFAAS)
  
  15,000 functions is a few megabytes of code. Sure, this would have been tricky on a CP/M system; even with a hard disk you'd have to be careful optimising your overlays so you weren't spending all your time swapping code in and out. For it to be a problem in 2023 has to mean you're doing something incredibly stupid.
  
  So, first thing: We're not talking about regular functions in a piece of code here; we're talking about "serverless" functions running in the cloud. These do have their place, though they are horribly inefficient.
  
  Second thing:

  I started off by looking to hardware that I already owned. My workstation runs Linux and has an AMD Ryzen 9 5950x with 16C/32T with 128GB of RAM. Then, behind me sits the Ampere Developer Platform with 64C and 64 RAM. I paid an additional 500 USD to upgrade the Ampere machine to 128GB RAM in order to recreate the customer issue.
  The container limit of 110 per Kubernetes node means that even if you have a bare-metal machine like this, it’s largely wasted, unless you are running a few very large Pods.

  It took me a moment to unpack this. Every single one of those functions needs to run on its own container - a lightweight virtual server. 15,000 functions means 15,000 virtual servers. That's insanity.
  
  The rest of the article discusses the struggles to get 15,000 virtual servers deployed, which is only interesting if you enjoy watching train wreck videos.
  
  So we have:
  
  1. Serverless functions, which are useful in a limited role.
  2. Some crazy people who want 15,000 separate serverless functions, which is insane.
  3. Some crazy people who deploy every single serverless function as a separate virtual server.
  4. The poor guy who has to make all that shit work.
  
  Every company has some of this nonsense going on: "Yes, I know we did this to ourselves, but we have to make it work somehow." But this example is truly spectacular.
  
  
  
• Unison is a language that is supposed to make this problem go away. (Unison)
  
  You define your functions, deploy them somewhere, and then leave it up to Unison to manage where the functions are running and send the calls to the appropriate servers.
  
  Sounds good.
  
  The website is terrible, though; half of it is reminders to join the slack channel.
  
  Also, this:

  tour/main> find : [a] -> [a]
  1. lib.base.data.deprecated.Heap.sortDescending : [a] -> [a]

  When a user asks for a list of the functions that take and return a sequence value, you should not sort deprecated functions to the top.
  
  
  
• Why could reviewers not run Geekbench on the Google Pixel 8? Because Google blocked it. (Notebook Check)
  
  And why did Google do that? One has to assume, because the scores weren't very good.
  
  And checking some reviews, that seems to be the case. The Mediatek chip I mentioned yesterday is significantly faster than Google's powerhouse - 40% single core and nearly 100% multi-core.
  
  
  
• The CEO of Hashicorp predicts that Silicon Valley will abandon open source unless open source stops, uh, being open source. (The Stack)
  
  If you didn't want to give your software away, mate, maybe you shouldn't have given your software away. It's not my fault that you're an idiot.

Posted by: Pixy Misa at 03:23 PM | Comments (5) | Add Comment | Trackbacks (Suck)
Post contains 655 words, total size 5 kb.