yaccz

I'm satisfied by https://www.strengthlog.com/

reStructuredText is way better format while only slightly more complex than markdown.

POSIX_ME_HARDER

That's an issue of bad engineering culture, not TDD.

> the text is just a tool to manipulate some abstract model of the program.

yup.

> When you think about it this way, it becomes clear that using a textual source code is really inefficient way to manipulate this model.

Hard nope. All the attempts at different approach were a failure so far. Text so far is the best thing we have because text can be analyzed formally and computed with by computers. This is the result of the work that's being going for at least like 200 years in philosophy, logic, and math.

What we really need is to bridge the gap between programming and math as industry standard, not academical exersise somehow. But I highly doubt eliminating text as source code is it.

> The historic reality is that HTML served as a "backdoor"/gateway to let the linux community compete with microsoft: linux devs could ship their code for windows clients.

lmao. sources?

Some second level example addresses are actually reserved and not for use. See rfc 2606.

Problem is you need to remember the patterns first to be able to think "hey I know this pattern. Maybe if I look up what the identity is it will be usefull"

The claim is only missing a qualification that the impossibility exists within the framework of ieee 754. It can be easily inferred from context and it is important to note because thats what the major CPU architectures use to store native floating point numbers. Therefore, the point is, we need a non-native (wrt the cpu) way to store and calculate with irrationals and some rationals if mathematical precision is required.

> If something is being described that is hard to do, then the sentence is structured in such a way that it is comparatively hard to understand, by using an unusual word order etc. If things are far apart, the words are themselves far apart etc. For quick things, words are omitted that cannot be omitted in other languages etc.

But why?

60 FPS is garbage for a lot of games

Whats the problem with ${FOO_PORT:-1234}?

Sure, it doesnt exist in the language of Dockerfile but you can achieve the same effects in other trivial ways.

better displays are mostly engineering problems while better batteries are a science problem.

> As a math student, I would much prefer to be given a basic statement of the definition of a monad, a list of properties, and maybe a theorem to prove that some structure is a monad instead of having to fall back to the definition.

Have you looked into the original paper?

https://homepages.inf.ed.ac.uk/wadler/papers/marktoberdorf/b...

I dont think anybody argues that types replace documentation. However, documentation without types tends to get repetitive and requires you to come up with ways to structure it properly. Turns out, you can encode a lot of information into a type and now it can be automatically verified and frees you to write documentation for things that can not be expressed in types.

iirc FreeBSD is sticking with svn because git is GNU licensed

alias grr="grep -r --exclude-dir=.git"

Nobody is using resolutions larger then FHD because there is no GPU than can feed it at 144 Hz.

ADTs are not neccessary to implement Option.

Its from 2010

I find reStructuredText much better option for lightweight markup as it is comparably lightweight to markdown but there is only one version, is much more powerfull, and makes more sense to me syntactically. Org-Mode looks just like another markdown to me.

> Even worse than this is the underlined heading category.

I think its the best. Compared to the prefix style it actually looks like a headline in the text document.

> The user is completely irritated for multiple reasons. Besides the tedious manual work to align the stupid heading characters with the heading title

What is tedious on typing <esc>yyp <shift>-v r # to underline current line with #?

> it is not clear what characters must be used for those heading lines. If you've got a bigger document with different levels of headings you get confused which heading character stands for which heading level.

Using a convention where bigger headlines use bigger looking characters works for me.

  H1 uses # and is both under and overlined, the rest is only underlined
  H2 uses #
  H3 uses =
  H4 uses -

wow such insight much deep very agile programming used