Sorry to be the bearer of bad news https://webkit.org/blog/13399/webkit-features-in-safari-16-1...
949 karma · joined July 4, 2017
I guess my spidey-sense starts tingling when my feeds get a particular interest that seem untimely/out of place.
Is this related to the twitter mess, and Mastodon being a natural successor? Then Mastodon bringing attention to the underlying protocol? Or is there some other less altruistic reason for the push?
Don't get me wrong, I've been following it for several years and I think it's neat, but I just don't trust my social feeds to always deliver content natuarlly and without bias.
Why do you say that? The linked repo doesn't seem to contain anything other than what's declared in the title. IIRC it was Zeit before a rebrand, and they had a similar/same offering. Please provide some context to your comment
>>> Every type in Teal accepts nil as a valid value, even if, like in Lua, attempting to use it with some operations would cause a runtime error, so be aware!
I know you can use (or implement your own in about 8 lines) strict.lua[2], but that just seems like such a shame to omit nil checks from a gradual type system. I still follow the project, but I put a little more hope in Pallene's[3] development, although the aims are slightly different.
[1]: https://github.com/teal-language/tl/blob/master/docs/tutoria...
One recent offering I enjoyed working with was esbuild, as I could use it's CLI as part of my existing build system incrementally instead of planning my whole system around it.
> My personal impression is the author is doing this from some mix of demonstrating how clever and low-level they are and nostalgia for earlier days of computing.
That's some armchair psychology right there. I think it's a neat project and I think the concepts are fairly reasonable. Why continue to create software for hardware that's capable of running anything. Making use of alt boards/otherwise scrap hardware is quite admirable in my opinion. Adding a little post-apocalyptic flavor to the project is likely the difference between frequent shares and dusty obscurity, so props to the author.
[1]: https://nelua.io
I think in concept that's a good idea and would create some interesting situations, but I imagine it would get super old real quick. There were already people taking advantage of those ideas, i.e. PKs hanging out at the cross roads, and vendor shops being placed in high traffic locations. When you started the game, assuming you didn't have some IRL benefactor gift you stuff beyond your level/ability, you usually did start as a pedestrian having to walk and use moongates to travel. I personally thought filling your first runebook was a rite of passage and gave me a sense of accomplishment.
I agree with you and Fowler, sketches are probably a better use. When UML came about I think designs were largely developed before hand by architects/analysts and astronauts and given to developers to implement as is, but now they are better used to aid in documentation or spec out specific interactions/concepts that belong to a larger system.
> A table with exactly one border is called a sequence. For instance, the table {10, 20, 30, 40, 50} is a sequence, as it has only one border (5). The table {10, 20, 30, nil, 50} has two borders (3 and 5), and therefore it is not a sequence. (The nil at index 4 is called a hole.) The table {nil, 20, 30, nil, nil, 60, nil} has three borders (0, 3, and 6) and three holes (at indices 1, 4, and 5), so it is not a sequence, too. The table {} is a sequence with border 0. Note that non-natural keys do not interfere with whether a table is a sequence.
> When t is a sequence, #t returns its only border, which corresponds to the intuitive notion of the length of the sequence. When t is not a sequence, #t can return any of its borders. (The exact one depends on details of the internal representation of the table, which in turn can depend on how the table was populated and the memory addresses of its non-numeric keys.)
Isn't that what people do when they buy games on Steam?