Also: Banana - Although not technically living, it does make for a good size comparison.

It had to be added:

> Tyrannosaurus rex. One of the largest land predators ever, it had teeth the size of a banana

To be honest, all I see is https://xkcd.com/927/

All config formats are bad. You either don't need all the features at all, except key:value. Or you quickly run into weird limitations and quirks.

What I rather like instead, are custom build english-like DSL's, like:

- https://man.openbsd.org/pf.conf - https://man.openbsd.org/smtpd.conf - https://man.openbsd.org/httpd.conf - … and many more

OpenBSD's daemons' configs are pleasant. But then you have to maintain a DSL for even small projects. Most people aren't going to want to implement and maintain a whole one-off config language for their small project. Which is why having a common, minimal option is nice.

I've never started. ¯\_(ツ)_/¯ And also not going to. I see enough crap, colleges produce, to never touch this pile of dung.

… since 1994

That’s what I know since 1994 as well. thus surprised it’s published here with landing page only and no specific news. Unless I missed one? Is there some 31 years celebration or sth? :)

Read most of the comment, was hesitated. Then thought "it can't be that bad". Ok, it is that bad. I absolutely hate extra round corners and extra margin in the windows. Sigh.

It’s just change. People complain every time the UI changes on anything.

People will get used to it. Apple will refine some things over time.

It will be ok.

I usually agree (and enjoy reading angry threads years later), but wasting screen real estate and getting measurably worse in terms of accessibility is simply not a good design decision.

I guess you can bookmark this thread and set a reminder to revisit it in 5 years and see how it went.

I usually take it even a step further by skipping useless "hello".

Instead of "Hello, did you notice, that db is down? Can you check it please?"

Just terse "DB seems to be down. Please check it."

Hilarious, how an old joke from 2003 is still relevant today.

Please, please, please don't execute it. It will try to wipe you disk.

    cat "test... test... test..." | perl -e '$??s:;s:s;;$?::s;;=]=>%-{<-|}<&|`{;;y; -/:-@[-`{-};`-{/" -;;s;;$_;see'

Origin: https://www.linux.org.ru/forum/development/392747

Little known, but there is already calendar(1) [1] in OpenBSD with much more sane format.

[1]: https://man.openbsd.org/calendar.1

Grandfather of Protobuf is ASN.1

Very much so. Pretty much all of these protocols are simplifications of asn1 and in some cases (like protobuf) there are a handful of things that got lost because the wire formats didn’t have them as they didn’t need them. A schema indicator being the single biggest flaw in protobuf.

Why is the lack of a schema indicator the biggest flaw of protobuf?

It makes it impossible to write a general purpose dissector that takes captured messages or bytes and figure out how to parse it.

All they needed was a varint at the head of any marshaled from to at least provide some scoping clue.

If you parse a serialized protobuf byte array without having a .proto file, you have no way to dustinguish a byte string field from a nested message field. Thus you have no way to know how deep your parser should go.

Semi-related, one of the `imessage-exporter` contributors provided a great write-up on reverse engineering the handwritten and digital touch message protobufs [0]. The reconstructed proto files are [1] [2].

[0]: https://github.com/trymoose/handwriting2svg/blob/0eb56cf4582...

[1]: https://github.com/ReagentX/imessage-exporter/blob/beeb853b2...

[2]: https://github.com/ReagentX/imessage-exporter/blob/beeb853b2...

One usually has two grandfathers, so it still works out.

The telco industry, including GSM and its successors, uses ASN.1 widely.

Some more:

Quick'n'dirty:

    .model small
    .code
     org 100h
    start:
     int 19h                 ; Bootstrap loader
    end start

More "correct":

    .model small
    .code
     org 100h
    start:
     db 0EAh                 ; Jump to Power On Self Test - Cold Boot
     dw 0,0FFFFh
    end start

Even more "correct":

    .model small
    .code
     org 100h
    start:
     mov ah,0Dh
     int 21h                 ; DOS Services  ah=function 0Dh
                             ;  flush disk buffers to disk
     sti                     ; Enable interrupts
     hlt                     ; Halt processor
     mov al,0FEh
     out 64h,al              ; port 64h, kybd cntrlr functn
                             ;  al = 0FEh, pulse CPU reset
    end start