wibblewobble123
wibblewobble123 on Hacker News
But the inspirations differ https://inflex.io/blog/bibliography
The author already wrote about blogs that are trying to get views with various tactics vs old proper blogs that were just people rambling about their quirky interests or bad day.
http://pchiusano.blogspot.com/2013/05/the-future-of-software...
And that culminated in
Essentially all code is pure functional and content addressable, meaning it’s inherently distributable and transferable (including closures). Like Smalltalk but with more use of modern programming language theory.
I’ve commented on both Stripe and DigitalOcean’s terrible support, under different accounts, and had some XO give the “we’re so sorry, email me directly and I’ll personally look into it, our customers are really important to us” tripe.
There is no good work here. Only platitudes.
You’re not paying attention to the space but recalculating notebooks are gaining popularity.
If you want a list of employees each of which have different roles, and depending on the role you have different fields guaranteed to be available (not null), this is not possible to express directly in SQL.
You can express this with sum types in ML, Haskell or Rust.
In SQL you would have to split it out into separate relations, like:
create table employee(id it)
And then employee_boss, employee_dev, employee_sales which each have different sets of non-null fields.
You can express a foreign key constraint that these tables must link to an employee, but not the other way around. You can’t guarantee in the limited type system of SQL that every employee row has a corresponding employee_X table, and exactly one, not more.
This is trivial in languages with sum types but not in SQL. In this sense they are strictly more powerful.
Various triggers can be added to try to enforce this constraint, but that’s a runtime check: better languages tell you when you type check the code.