still_grokking

Of course it still is.

The type hints have no runtime semantics whatsoever.

The actual type-checking still happens at runtime in Python, and is not related to any static checks. Out of the perspective of Python's interpreter the type hints don't even exist. They're like comments…

Static type checking is not part of Python!

> Python also has ADTs which match it in power to rust.

All Turing-complete languages match each other in power…

Besides that:

Python doesn't have a static type system in the first place, so it can't compete with Rust in this regard. That's not even the same game.

I have alone in this window here 4682 tabs open.

How it comes? Well, I just don't close them until I have decided whether I want to bookmark them. After month with a browser sessions quite some tabs pile up. (When it gets out of hands I bookmark whole windows… So there remains at least the theoretical possibility that I sort this out later. Even that happens only rarely.)

Before someone asks: From the technical standpoint it's quite easy to have so many open tabs. All you need is Firefox, Tree-Style-Tabs, and tab auto discard ("sleep"). It fits than in under 2.5 GB RAM even (which is less than Chrome with even a few tabs).

The ads aren't the problem.

The problem is the spy industry behind.

Surfing without content blocker is like selling your soul and your first born to the devil, to get nothing in return.

One person project…

Of course no security team…

We've run back than Napster and later eDonkey on those boxes just fine…

You mean like any proper P2P protocol?

Add to this multi-cast on internet level, and everybody could actually operate something like YouTube on their internet router…

But of course economic interests of some (already ultra rich) minority will prevent that forever, even we could have it just right now form the technical standpoint.

To the extend that TS's type-system is unsound, and everything may crash at runtime at random anytime.

Both things aren't exchangeable, of course!

Thread have direct access to process memory. Other processes usually don't. Big difference!

A lot of these systems are running actually on Windows, in version that aren't supported since years.

C, C#, C++, Dart, Elixir, Elm, Erlang, F#, Go, Groovy, Haskell, Java, JavaScript, Julia, Kotlin, Lua, Nim, Objective-C, PHP, Perl, Python, R, Ruby, Rust, Scala, Swift, TypeScript

The code looks good, and that's a great success. What else would you like?

Now one could speculate about the reasons.

Does Markdown have footnotes or endnotes? No?

People are still misusing it for everything! Especially for technical writing, which is just nuts.

https://netzpolitik.org/2013/angriffe-auf-informationssystem...

(Also the links there.)

Or a more "official" statement (as the German Wikipedia is mostly in the hands of state authorities), with some groundless relativization:

https://de.wikipedia.org/wiki/Vorbereiten_des_Aussp%C3%A4hen...

All "dual use" tools (like a simple port scanner!) can bring you into jail. That's a fact. The law doesn't have any exceptions for "friendly use"… (No matter what some "experts" cited on Wikipedia may say. That's just the usual German Wikipedia blow smoke…)

Form the alternatives I've seen so far it looks best. But EMACS? (I'm on Linux, but never liked EMACS or Vi(m)).

The second best looking alternative seems AsciiDoc. It has some more tooling as I see it.

But really like the .org syntax best so far. So any recommendations for tooling?

https://miro.medium.com/v2/resize:fit:720/format:webp/1*sojK...

Kotlin would be likely still nowhere without Google and Android.

In Germany we have even dedicated anti-hacker legislation. Hacking stuff is indeed illegal. You may end up in jail for "hacking"…

That's likely "the freedom" they are always talking here about in the west. /s

Imho Markdown is a overall terrible and (especially regarding technical writing!) very limited format. But nothing else seems popular. Why actually?

Are there any realistic alternatives?

Thanks for some hints!

> Alphabet also alerted its engineers to avoid direct use of computer code that chatbots can generate, some of the people said.

It's telling, and says imho a lot about the "quality" of AI generated code.

Haskell is an abnormality. Even in FP land.

There is likely no other language where you need to "understand monads" to understand `Hello World!`. Such "crazy stuff" has nothing to do with FP!

The syntax is of course also confusing. If you show the above line to a 6. grade child they will tell you that that line makes no sense, obviously.

That's why this example is so good! For someone without exposition to (imperative) programming it's completely nuts. But after some "brainwashing" people don't even recognize how weird the example is actually. My hope is always this makes people think (at least after explanation) a little bit whether they maybe just internalized some actually unintuitive stuff and now think that's the "normal" way to look at things, even it's actually not if you come in just with the knowledge from school.

Not everybody remember that but most people have for example major issues in grasping a loop with a counting variable in the beginning. It's just not so easy to "do the computation" in your head and track the state of your variable. Variables as such are already confusing to most people. Beginners often use them like constants and declare new ones when they actually need to assign a new value. I've see this pattern quite often! If you ask why it was done this way the answer is often "because re-assignment is confusing"…

That has nothing to do with FP.

That's mostly a Haskell (and the-like) thing.

"Hello world" looks in for example in OCaml like this: `print_string "Hello world!\n"`. You can interact with the outside world just fine without any "side-effect wrapping".

I guess not for everyone. Frankly.

I know quite some people who do programming for living but are more or less avert to any theory behind it. You get even called names if you come along with such topics… (I think it doesn't need to be said that it's quite difficult to deal with those people at times as they're kind of ignorant.)

You won't learn anything if you don't practice it.

But "learning" computer related stuff without the theory behind is also kind of moot. You wouldn't get the full picture this way, and you would end up with a lot of "knowledge" that isn't more than assumptions. Likely wrong assumptions…

I'm running Debian Testing so I had this command in fact since many years. Didn't know that it's actually quite "new".

Now I can understand how it could happen that Murex created a command name conflict. External tools don't test against Debian Testing most of the time…

> OK, how about

> x <- x + 1;

Better.

From such syntax you can at least guess that mutation is happening there.

Still nothing you would show a newcomer in a FP-programming introduction.

(I'm not sure why your comment got down-voted. I can only up-vote it, so I did; to battle stupid down-votes because "feels"…)

Maybe. But I just don't know why this discussion started in the first place. There is a `open` command on likely almost every desktop Linux box. So it's not Mac specific (which was my sole point in my first comment in this thread).

> Right, you said "alias" multiple times earlier. Symlinks and aliases are not the same thing.

You're technically correct. My fault!

I've called it alias as it's a symlink coming form the Debian alternatives facility. The alternatives mechanisms manages system wide command "aliases"… I should have been more exact in this point.

> I was saying I suspect Debian got the idea from macOS.

I have no prove but I doubt that. There were other tools on Linux called `open` before MacOS X came along as far as I know. The whole thing seems to be rooted in BSD (where NextStep got it's Unix parts form).

> For what it's worth "open" doesn't exist on my Ubuntu servers either.

Makes perfect sense. It's a desktop tool.

> And it was added to Debian only 2 years ago.

I don't think so. I had `xdg-utils` and it's `open` command installed for many years. It's at least 17 years old:

https://cgit.freedesktop.org/xdg/xdg-utils/refs/tags

> Anyway, this is all moot because there are easy workarounds for the naming conflict

I agree. The Debian alternatives system was made exactly to handle this kind of name conflicts around commands. So there's no big issue, indeed!