qwertyasdef

@qwertyasdef@programming.dev

• ⁨Comment⁩ on ⁨Monaspace - Microsoft presents a new font family for code⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  That texture healing looks super nice. Is that something fonts can just do or does it require special editor support?

• ⁨Comment⁩ on ⁨Introducing ONCE, a new line of software products from 37signals: Pay one time, own forever.⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  …What are they actually launching though? I mean I love the payment scheme but I can’t get excited over this without an actual good product being sold.

• ⁨Comment⁩ on ⁨Programming.Dev Feature Requests⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  No idea how hard it would be but it would be nice to have code blocks with syntax highlighting like on Github, so you could write something like

  ```python
  def f(x):
      return x
  ```
  

  and get syntax highlighted code def f(x): return x

• ⁨Comment⁩ on ⁨Do they know one second is slow?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  It’s a Substack thing, not added by the author

• ⁨Comment⁩ on ⁨Simply explained: how does GPT work?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Ask it a question about basketball. It looks through all documents it can find about basketball…

  I get that this is a simplified explanation but want to add that this part can be misleading. The model doesn’t contain the original documents and doesn’t have internet access to look up the documents (though that can be added as an extra feature, but even then it’s used more as a source to show humans than something for the model to learn from on the fly). The actual word associations are all learned during training, and during inference it just uses the stored weights. One implication of this is that the model doesn’t know about anything that happened after its training data was collected.

• ⁨Comment⁩ on ⁨How helpful languages create bugs⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Also Vector2f instead of Vector3f for the cross product example. I’ll give them the benefit of the doubt that that’s a typo instead of them not knowing what a cross product is.

• ⁨Comment⁩ on ⁨How helpful languages create bugs⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I disagree with the author on operator overloading. They claim that this function in C

  float foo(float a, float b) {
  	return a+b;
  }
  

  is perfectly clear because you know it’s doing floating point addition, while this function in Python isn’t

  def foo(a, b):
  	return a + b
  

  because you don’t know if it’s floating point addition, integer addition, or string concatenation, and what happens if the inputs are different types?

  I think that’s fundamentally mistaken. You could also ask of the C version if it’s doing normalized floating point addition, denormalized floating point addition, infinity addition, or NaN propagation. What happens if you mix different types of floats? And the answer is that it doesn’t matter. These are all just aspects of floating point addition. It returns the most sensible result in whatever format is best to hold that value, and you don’t need to worry yourself about how floats are stored under the hood.

  The same is true of the Python version. It doesn’t matter if it’s integer addition or floating point addition or string concatenation. Those are just different aspects of the addition operator and it returns the most sensible result in whatever type is best to hold that value.