blashyrk

That's simply because we live in a world where UFCS is restricted to niche languages and we're stuck with "methods" instead. At least Rust/Kotlin/Swift support type extensions (with a thousand papercuts, i. e orphan rules)

"The fix is not to lock the code away. The fix is to separate participation from final control. Give the entire team access to the code so people (with or without agents) can work on it. Keep merges limited to engineers."

Oh great. The engineers now have to review 100x more code AND still be the ones responsible when something goes wrong. How convenient!

Great

Just needs a pulse dialing option ;)

Why? You can use rechargeable AA batteries and if you want you can swap them out and basically never have downtime for charging. Also all embedded batteries degrade over time which is a non issue here

Okay and how many years is George Bush Jr and his entire administration serving currently?

What good is mentioning past mistakes if there's strictly zero consequences

> coding is the means to an end

...

> doesn't add value

What about intrinsic value? So many programmers on HN seem to just want to be MBAs in their heart of hearts

Wouldn't that basically be very similar to, for example, LLVM IR?

I felt the exact same way until I tried Hazelight's AngelScript UE fork. It is amazing, it brings the developer experience and iteration speed to Unity levels. They even made a VSCode plugin for it. Cannot recommend enough

Yes, I tried it recently for easy cross-compilation. You can use basically any C/C++ compiler, even TinyCC works (in most scenarios) if you want an extremely fast edit/compile/test cycle.

Macos window/desktop management is also stuck in 2001 with "magic gestures" tacked on. For someone who hates using these gestures especially when connected to an actually good kb/m, the base desktop experience is horrible. The dock is completely useless, the various cmd+tab or cmd+` shortcuts are unwieldy, Spotlight is growing increasingly worse year after year.

Rectangle/tiling window managers on top is the only way to make it workable.

Apart from wm, the existence of application notarization is a downright insult (though Windows is also guilty of this with smartscreen but to a much lesser extent).

Apple's "pay us 100 bucks a year or we'll tell your users that your program is malware" is just another step in the inevitable game of locking down macos and turning it into a mobile-like hellscape

Someone really needs to show Nim to the author :). It checks all of their boxes and then some

I second the Shenzhen I/O recommendation, because apart from only assembly programming, the game also has other constraints in the form of having to spacially arange various chips on a limited "enclosure" for the product you're building and connect them. It also rewards optimization both in terms of assembly and chip usage efficiency. Is a wonderful game, really.

I absolutely adore Nim.

That said, the edges are still (very) rough when it comes to tooling (generics and macros absolutely murder Nimsuggest/lsp) and also "invisible" things impacting performance such as defect handling (--panics:on) and the way the different memory management schemes introduce different types of overhead even when working with purely stack allocated data.

But even with all that it's still an extremely pleasant and performant language to work with (when writing single threaded programs at least)

Even more importantly, running at 60+fps while not breaking gameplay, physics, shaders, cutscenes...