News for hackers. Stuff that matters.
Re:Zig 0.4.0 Released by jph on Monday April 08, 2019 @08:12PM (#19610440)
Zig's new release has a ton of improvements: new targets (e.g. LLVM 8, WASM, support tiers), C pointers, Vector type, better docs, and my personal favorite: Zig now makes things as static as possible by default.

I love seeing all the progress with Zig, V, Muon, and Rust. All these languages are potentially-better systems languages than C/C++, with better safety, better definitions, and better semantics. Zig has an explicit goal to be better than C and to replace it.

Re:Zig 0.4.0 Released by earenndil on Monday April 08, 2019 @10:51PM (#19611326)
Honestly, I don't see it happening. Zig and rust and jai and d all feast on c's remains, but the result can only be fragmentation. And then you lose one of the big draws of c: ubiquity. Zig has two compilers. Rust has one (serious) compiler. Jai has 1, d has either 1.5 or 3.5 (depending on how you count). And although all those languages want to replace c as the language-that-you-use-for-everything, and they might each be better than c as a language-that-you-use-for-everything, but for a given use a 'lighter' language like python is frequently even better. And it gets to the point where the only languages that allow you to program anything (lisp and perl6, really) are garbage collected and have heavy runtimes, so they won't be taking over games or the os.

C might die, but there's no replacing it. Sorry.

Re:Zig 0.4.0 Released by strmpnk on Monday April 08, 2019 @11:08PM (#19611425)
I don't see any single thing replacing C (or C++) but what's interesting here is many of these languages work very well with the C ABI, not just as an FFI concept but with notions of memory and data layout. The interesting side effect might be that we'll see Zig not just work with C code but Zig work with Jai with D with Rust. All of that code can still interface with C or C++ code (in both directions). This lowers the barrier significantly.

The hard part is build tool compatibility but I think there are a lot of good ideas being worked on actively, Zig and Rust being two examples of advanced programatic control over the build process. With a reasonable linker, it should be possible to combine these and more languages today.

An interesting counter example to the binary interface compatibility story has been Go, which seems to let cgo become less and less functional in each release. The pressure to keep everything in Go is an interesting trade-off. I wonder if certain kinds of systems will be paying for this lock-in later down the line while other languages give much easier ways to gradually evolve and reuse code or adopt libraries from multiple communities removing the need to do yet-another-rewrite in language X kinds of projects. Or perhaps this kind of interoperation is overrated? Time will tell.

Re:Zig 0.4.0 Released by earenndil on Tuesday April 09, 2019 @01:59AM (#19612179)
> The interesting side effect might be that we'll see Zig not just work with C code but Zig work with Jai with D with Rust. All of that code can still interface with C or C++ code (in both directions)

That already works, not a hypothetical. I can write, right now, a zig function, call it from rust, slap the whole thing into a library and wrap it with d. It hasn't taken the world by storm because these languages provide support the system c abi and calling convention, but do not embrace it. If I write a fancy templated function in zig, d, or rust, the name mangling, type-information, templating, maybe even call conventions -- are all different. This is why I have been and continue to be disappointed that things like COM or the jvm or cli aren't more popular, because they actually work that way. I can write, right now a clojure function, call it from java and then pass it into kotlin. Effortlessly, it's just an import away. Sure there are, for example, stdlib conflicts in scala but overall it's a much more frictionless experience. The problem? COM is windows-specific, jvm and cli are managed runtimes and people don't like managed runtimes.

Another place I look for a solution is racket, but again it wants to manage too much of the runtime to be practical. What zig is doing with the build system is great, the fact that the build script is actually a fully customizable script means it has a much better chance of taking off, but until I can import a jai module from d and call it in zig, we're gonna have problems.

EDIT: something which possibly almost could have had a good chance of pulling this off is llvm. Except that llvm comes too late in the compilation process to be used to resolve imports and symbols. Something like libclang, maybe, except not specific to c and c++.

Re:Zig 0.4.0 Released by jplayer01 on Tuesday April 09, 2019 @03:30AM (#19612536)
Wouldn't a managed runtime mean it isn't suited for systems programming? The benefit of something like Rust is it provides a lot of the benefits of a managed language while producing native code and "zero-cost abstractions". A runtime adds a lot of overhead etc.
Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @05:45AM (#19613071)
C also has a runtime, that is what takes care of calling main(), handling VLAs, floating point emulation, constructor/destructors (GCC C extensions), ...

Besides there are plenty of OSes written in type safe system languages to learn from, including surviving mainframe OSes.

Re:Zig 0.4.0 Released by earenndil on Tuesday April 09, 2019 @01:31PM (#19617047)
The operative word here is managed runtime. Jvm wants to completely own your program, heart and soul. You can also write freestanding code in c (and rust, d, zig I assume although I don't know enough about it). I believe there is a dialect of c# that allows you to write freestanding code, but it's not really c# so much as c#-flavoured c with some extra features, so it's inferior to other c alternatives.

As for type safe system languages, ada?

Re:Zig 0.4.0 Released by jstimpfle on Tuesday April 09, 2019 @06:03AM (#19613148)
I feel much of the negativity that you like to express towards C is unwarranted. Fact is, it's both very easy and efficient to interface with "C" or more specifically, platforms' standard ABIs.
Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @06:48AM (#19613344)
On platforms written in C.

As for the negativity, Morris worm is now 30 years old and the CVE database gets C derived exploits every month.

Re:Zig 0.4.0 Released by jstimpfle on Tuesday April 09, 2019 @08:13AM (#19613794)
You can interface with Object Pascal (which you frequently advertise) just fine.

(That doesn't make Object Pascal a practical language, though).

https://www.quora.com/Why-is-the-JVM-so-riddled-with-securit...

Another fact is, startup times alone make JVM impractical for many endeavours. For each task an appropriate tool I'll say.

Re:Zig 0.4.0 Released by jplayer01 on Tuesday April 09, 2019 @08:50AM (#19614047)
That Quora post is really only relevant when using Java applets. If you're running a local program, you're faced with similar vulnerabilities as with any other language with a managed runtime. Still doesn't make it relevant as a competitor to C or C++.
Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @08:44AM (#19614003)
JVM startup times are only an issue for those that don't want to buy a commercial JDK with AOT compiler support.

Good news, now OpenJDK and GraalVM offer it for free, gratis.

Object Pascal/Delphi is quite pratical on Windows.

Re:Zig 0.4.0 Released by jstimpfle on Tuesday April 09, 2019 @08:57AM (#19614093)
> Object Pascal/Delphi

It has a sane subset which is basically C with a slightly saner syntax than C (the begin...end and lacking data initialization syntax are terrible though!), and with a proper module system and much better compile times.

On the other hand, it was crippled by missing a usable preprocessor and an ecosystem that has bought into each hype since the 90's, resulting in 23 incompatible kinds of strings, 101 different dynamic arrays, and about 5 (really) incompatible object models with different kinds of memory management. Programmers with many years in the language don't really understand all the ways memory is managed in this language.

Now try writing something on top of the broken RTTI for that. Even official guides basically concede the fact by writing quirky code that easily breaks.

Also you have to declare typealiases for every little thing like pointer-to-types, before you can use that type in a function signature. This alone renders it almost completely unusable for my purposes.

It has a culture of goto-considered-harmful where people like to indent 13 times instead of using return/continue/break, which would yield readable control flow. If you want to return something, you need to write two lines - assigning to the result and calling exit(). You can't call exit() though when the current class has a method called exit(), since that method is closer in scope (REALLY REALLY WEIRD).

I know what I'm talking about. I've been paid to work in it, and refactored a subsystem written in idiomatic Delphi to be halfway maintainable, achieving real speedups of 100-1000x by following a straightforward "data-oriented" approach, just like I would write it in C, writing complicated code only where the straightforward approach was not feasible in the language. Despite completing the project successfully (there hasn't been a single problem since the rewrite), in the end I was burnt out due to having to work with the original code. Didn't work for 5 months afterwards.

Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @05:52PM (#19619326)
Ah, one of those USENET posts.

Except for when I write Assembly, the last time I used raw goto on an high level language, my MS-DOS 5.0 box was still relatively new.

System.exit was always a thing to avoid namespace clashes and since Delphi 2009, you could have used System.exit(value) instead. Next time better read the docs.

Regarding strings, you mean like 8 bit, 16 bit, wchar_t, DBCS, GString and many others used across C libraries?

Nominal typing is much safer for large scale engineering than type aliases, which don't provide a mechanism to prevent incorrect usage of types.

Re:Zig 0.4.0 Released by jstimpfle on Tuesday April 09, 2019 @07:46PM (#19620192)
> System.exit was always a thing

Do you suggest I should use System.exit everywhere (even though all the code you find on the net uses just "exit")? Just to be sure that Delphi will never ever choose the wrong function to call WHICH IT SHOULD NEVER HAVE DONE IN THE FIRST PLACE OMG IT'S TOO FRIGGING COMPLICATED PLEASE DELPHI APPLY SOME COMMON SENSE.

It's beyond me why I should write a function call and incur symbol resolution for such basic control flow in the first place.

> the last time I used raw goto

I was mainly speaking about return, break, continue, which don't seem to be popular in Delphi. Examples of Delphi code that isn't a messy nesting fest? As for goto, there are perfectly valid uses for it, in fact some where goto is the clearest and most maintainable choice when you simply skip downwards over a chunk of code without requiring an extra flag.

> Regarding strings

I'm talking about the culture. The culture around C is not one that makes anti-modular "abstractions" (at least if you stay away from MS). You will never see me using wchar_t, GString or any of that god-awful Microsoft string mess. I get along just fine with only char. In fact, the string handling I get by using C is the most painless, most modular I've ever gotten in any language. (No, I don't want to use split() or use any other high-level stuff that would do allocations when that isn't necessary).

In Delphi, different story. Everything you find in this culture is built around String and AnsiString and UnicodeString and WideString and what not. Try googling how to access command-line parameters. The stuff is pervasive. Entirely different story.

> Nominal typing is much safer for large scale engineering than type aliases, which don't provide a mechanism to prevent incorrect usage of types.

Exactly, typealiases are bad. And now explain to me why Delphi forces me to make a type alias (for use in function signatures) when that is worse than immediate Pointer syntax in every conceivable aspect? (Having written a compiler I know the answer: because it requires less code in the compiler to check for type equality).

So I guess I should just avoid pointers altogether and use only GC'ed boxed OOP NOMINAL types. And finally have some time for coffee again while my application takes 5-10 minutes to start up (as it did before I reworked the thing), instead of 1 sec.

                end;
              end;
            end;
          end;
        end;
      end;
    end;
Re:Zig 0.4.0 Released by pjmlp on Wednesday April 10, 2019 @02:01AM (#19622252)
I could go on, but I don't miss the bygone USENET C vs Pascal flamewars, so let's leave it here.
Re:Zig 0.4.0 Released by stevek on Tuesday April 09, 2019 @08:51AM (#19614056)
COM is not windows specific any more! Or rather there is a portable COM-like thing which looks like a good fit for cross language development https://github.com/Microsoft/xlang

It's from the team who delivered cppwinrt (aka moderncpp). So the C++ projection doesn't have all the nasty baggage one usually associates with COM. https://msdn.microsoft.com/en-us/magazine/mt745094.aspx?f=25...

Re:Zig 0.4.0 Released by timClicks on Tuesday April 09, 2019 @01:06AM (#19611946)
On build processes, it's surprising to me that the Rust community hasn't developed its own linker. I suppose LD works fine.
Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @05:43AM (#19613063)
On Windows we just use COM/UWP or .NET libraries most of the time, no need to be stuck with C ABI.

Same applies on Android, where using a Java based library, even if stuck on their Java 6 - 8 world is much more desireable than having to deal with NDK and JNI boilerplate.

Likewise IBM and Unisys mainframes make use of their language environments instead of C based ABIs.

Re:Zig 0.4.0 Released by Crinus on Tuesday April 09, 2019 @06:23AM (#19613238)
> COM/UWP

Assuming with COM/UWP you mean "UWP's flavor of COM" instead of "COM and/or UWP", is anyone actually using that outside of mobile trash and game engine backends for XB1?

All the Windows software i use and see people make are either Win32 or (much more often) built on top of Win32 (well, UWP is technically also built on top of Win32, but you are supposed to ignore that and act as if it isn't the case).

Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @06:50AM (#19613354)
Yes they are, UWP is the future of Windows APIs since Windows 8, like it or not.

Win32 is slowly being migrated into sandbox model with each Windows 10 release and hasn't seen any big update since Vista. All major APIs introduced since then are based on COM.

Re:Zig 0.4.0 Released by flohofwoe on Tuesday April 09, 2019 @07:13AM (#19613455)
I believe Windows will sooner become completely irrelevant than UWP becoming the dominant API to write Windows applications. Also seeing how MS is switching the system browser to Chromium, and kills the UWP version of MS Office, it looks like most people in Microsoft have lost faith in UWP too.
Re:Zig 0.4.0 Released by WorldMaker on Tuesday April 09, 2019 @02:15PM (#19617498)
Microsoft didn't kill the UWP version, they merged it. Office is only becoming increasingly a hybrid. An increasing number of the controls are becoming UWP XAML-based.

It doesn't look like Microsoft has lost faith in UWP, only that they gained faith in UWP/Win32 hybrids (and all the complicated engineering work to make that happen), and Office seems to have helped lead the way there. For instance, Office is way more sandboxed than it has ever been before. (Office's own App-V work as far back as Office 2010 helped prototype the sandboxing approach Microsoft is applying to all of Win32 with the now focused opt-in MSIX installer.)

It's probably still too early to tell exactly how much UWP Microsoft will add to their Chromium mix, but there's already some bits there. For instance, the Chromium-based Edge still supports Netflix because they already integrated a UWP Island to (UWP API) Windows Media Foundation to support hardware-accelerated PlayReady DRM.

Re:Zig 0.4.0 Released by Crinus on Tuesday April 09, 2019 @10:49AM (#19615227)
Based on previous history, chances are Microsoft will first abandon UWP (but leave its zombified corpse in Windows for backwards compatibility) and introducing something new-but-incompatible-with-anything-existing before Windows become irrelevant. Actually, they might do this 2-3 times before that.
Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @07:39AM (#19613598)
What?!? Office was the team driving the new UWP Fluent components and happy early adopters of the new C++/WinRT framework and XAML Islands on Win32.

The year of desktop Linux is just around the corner. /s

Re:Zig 0.4.0 Released by Crinus on Tuesday April 09, 2019 @10:11AM (#19614807)
> Yes they are, UWP is the future of Windows APIs since Windows 8, like it or not.

Well, i don't, but my two main gripes is that it seems to be an evolution of WPF which i never liked and that it is tied to a more locked down mobile-like approach that i abhor.

> Win32 is slowly being migrated into sandbox model with each Windows 10 release

What are you talking about?

> and hasn't seen any big update since Vista.

I'd say that it hasn't seen any big update since Windows 98 :-P but as long as it works i do not care.

> All major APIs introduced since then are based on COM.

COM or COM/UWP?

Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @11:36AM (#19615702)
I am talking about MSIX and the sandbox evolution model from Project Centiped, with the new Win32 project format for store deployments.

Based on COM, and UWP, which is nothing more than a saner COM, now being internally widespread via C++/WinRT adoption.

Re:Zig 0.4.0 Released by Crinus on Wednesday April 10, 2019 @06:20AM (#19623286)
That is for store stuff though, not Win32 itself and the vast majority of applications are not written for the store nor distributed through it (some do use it as a secondary means of distribution but from what i've heard the limitations are not worth it and the store itself is bad from a UX perspective).
Re:Zig 0.4.0 Released by pjmlp on Wednesday April 10, 2019 @07:22AM (#19623574)
Win32 is going into the store, that is the whole point of MSIX.
Re:Zig 0.4.0 Released by rat87 on Tuesday April 09, 2019 @01:04AM (#19611941)
Maybe I'm a bit of a rust fanboy and a bit of a skeptic but

Zig and Jai aren't going anywhere. Zig appears to be a largely single contibutor (https://github.com/ziglang/zig/graphs/contributors the creator has < 2/3 of commits). Jai does not have a public compiler and is not likely to get a public release anytime soon.

As for rust we don't know yet how big of a chunk of marketshare it will take from new c and c++ code.

Not many people still use c code for "everything", most have already switched.

Re:Zig 0.4.0 Released by StreamBright on Tuesday April 09, 2019 @02:10AM (#19612222)
What is the actual argument that you support with pointing out that Zig is "largely single contributor"? Linux was largely a single contributor up to a point.
Re:Zig 0.4.0 Released by ModernMech on Tuesday April 09, 2019 @11:06AM (#19615391)
There is nothing wrong with single contributor languages. But for every C there are thousands of flatlined github repositories of single contributor languages. Building a language is a marathon, not a sprint. It takes years and years to grow something worthwhile, and this requires a lot of persistence. In the meantime, technical challenges, finances, family, and even busses get in the way of languages being fully realized. Having a team rather than a BDFL increase the chances of a language flourishing and persisting.
Re:Zig 0.4.0 Released by AndyKelley on Tuesday April 09, 2019 @02:25PM (#19617582)
Fun fact, I'm also training for a marathon! https://twitter.com/andy_kelley/status/1109906861241847816

There are 8 people on the Zig team, all with significant contributions and deep understanding of the project. https://github.com/orgs/ziglang/people

Re:Zig 0.4.0 Released by AnIdiotOnTheNet on Tuesday April 09, 2019 @09:16AM (#19614229)
> Zig appears to be a largely single contibutor

Aside from starting Zig as his personal project, Zig is also Andrew's job now. As far as I'm aware that is not true of any other contributor, so it makes sense he'd have the lion's share of contributions.

Re:Zig 0.4.0 Released by rurban on Tuesday April 09, 2019 @02:20AM (#19612259)
> Zig appears to be a largely single contributor

That's a good thing. The less contributors, the better the project usually.

Re:Zig 0.4.0 Released by carlmr on Tuesday April 09, 2019 @06:48AM (#19613340)
Rust is especially attractive because of no-GC. Systems, embedded, performance oriented projects have real reasons to adopt this language.
Re:Zig 0.4.0 Released by rhodysurf on Tuesday April 09, 2019 @10:19AM (#19614901)
so does zig and jai tho..
Re:Zig 0.4.0 Released by kps on Tuesday April 09, 2019 @10:11AM (#19614801)
C was largely a single contributor.
Re:Zig 0.4.0 Released by bacon_waffle on Tuesday April 09, 2019 @12:18AM (#19611753)
I feel like C hasn't been a "language-that-you-use-for-everything" for some time, so it's more about replacing C in the situations where C is currently a reasonable choice for new development.
Re:Zig 0.4.0 Released by earenndil on Tuesday April 09, 2019 @01:49AM (#19612141)
C has been and continues to be a general-purpose language people use to write all kinds of things; just, fewer things are being written in it.
Re:Zig 0.4.0 Released by pjmlp on Tuesday April 09, 2019 @01:24AM (#19612031)
Just like when it was born, for C to die, UNIX has to die, that's the only reason it will be an herculean task to ever replace it.
Re:Zig 0.4.0 Released by mysterydip on Tuesday April 09, 2019 @06:16AM (#19613202)
Naïve thought of the day: What if instead of replacing c with another c-like language, there was a c library that you included in your code that overloaded operators and functions into safer ones? You would gain some of the benefits and retain the ubiquity.
Re:Zig 0.4.0 Released by MuffinFlavored on Monday April 08, 2019 @09:46PM (#19610971)
Re:Zig 0.4.0 Released by verdex_phone on Monday April 08, 2019 @10:26PM (#19611192)
That's not particularly charitable. The accidental AMA that happened on HN a few weeks back gave me the impression that V lang isn't as polished as a concept as some of the other offerings out there. BUT the author seemed tp have something brewing. And regardless we'll have some more evidence in the coming months.

Regardless, V lang is another data point that something besides C is a possibility with the modern tools that we have available to us. Whether or not it pans out is almost immaterial. Just the fact that so many people are finding some sort of success or making some sort of progress in this space is enough for me to continue to watch for any new progress in the C competitors.

Re:Zig 0.4.0 Released by amedvednikov on Monday April 08, 2019 @10:59PM (#19611373)
Yes, V is at a very early stage. I merely created an "about" page, then it got posted, got lots of attention, so I created a website and recently released a playground:

https://vlang.io/play

There's still a lot of work to do, but the language is going to be open-sourced very soon in early June.

Re:Zig 0.4.0 Released by AndyKelley on Tuesday April 09, 2019 @02:31AM (#19612297)
61 days ago you said [1]

> Yes, I've done a terrible job with estimations and for 9 months I lived in "release tomorrow" mode.

> Ironically this time it it really is going to be released tomorrow (Feb 7).

[1] https://news.ycombinator.com/item?id=19102431

Re:Zig 0.4.0 Released by amedvednikov on Tuesday April 09, 2019 @02:53AM (#19612399)
If you read the parent, it refers to Volt, and it was released.
Re:Zig 0.4.0 Released by AndyKelley on Tuesday April 09, 2019 @02:45PM (#19617772)
I'm sorry, I was mistaken. That was incredibly rude of me.

I mistakenly assumed based on the title of the original post "About V, the language Volt is written in" that the post was about V, but as you pointed out, based on the parent comment it was actually about Volt.

I think I'm just excited to see your source code for V :-)

Re:Zig 0.4.0 Released by dom96 on Tuesday April 09, 2019 @03:34AM (#19612558)
Why delay it's release? Just throw up what you have on GitHub already.

Btw you should update the language comparison page, see here https://forum.nim-lang.org/t/4758

Re:Zig 0.4.0 Released by amedvednikov on Tuesday April 09, 2019 @04:04AM (#19612668)
What should I update?
Re:Zig 0.4.0 Released by agumonkey on Monday April 08, 2019 @11:45PM (#19611602)
i don't want to sound harsh but in 2010s, the way you released (I assume you're V author) mostly make people dubious
Re:Zig 0.4.0 Released by amedvednikov on Monday April 08, 2019 @11:58PM (#19611669)
Well I haven't released anything yet :) Can you elaborate?
Re:Zig 0.4.0 Released by andrewchambers on Tuesday April 09, 2019 @09:07AM (#19614156)
Mainly because it seems like you constantly lie and make promises you can't keep. Some of your claims are outrageous without any evidence.

Of course I would like to be proven wrong.

Re:Zig 0.4.0 Released by amedvednikov on Tuesday April 09, 2019 @12:00PM (#19616008)
Can you give an example of my "constant lies" and outrageous claims?
Re:Zig 0.4.0 Released by andrewchambers on Tuesday April 09, 2019 @07:50PM (#19620220)
Release the code of your doom3 to v translation, release the code of your sqlite translation.

You can't because they don't exist. And don't say "release coming in 3 days" or some other BS like you normally do. It seems like a way to divert attention until people forget to check again.

It won't work. I can see 300 dollars a month on your patreon, which is probably why you exaggerate so much.

Re:Zig 0.4.0 Released by andrewchambers on Wednesday April 10, 2019 @12:16AM (#19621792)
Anyway, I didn't mean to call you a liar, I just meant I will be very happy once it is released. My apologies.
Re:Zig 0.4.0 Released by sincerely on Tuesday April 09, 2019 @05:22PM (#19619064)
Release dates have been consistently been pushed back for basically the last year. For months your program's website looked like it supported a lot of programs it didn't. Be clear and upfront about what you can do and people will trust you more.
Re:Zig 0.4.0 Released by agumonkey on Tuesday April 09, 2019 @11:12AM (#19615432)
it's a release, a N month long release but it's a release
Re:Zig 0.4.0 Released by saagarjha on Monday April 08, 2019 @09:58PM (#19611040)
I wouldn't call it "fake", but yes, it has not been publicly released.
Re:Zig 0.4.0 Released by Cyph0n on Monday April 08, 2019 @10:07PM (#19611085)
I’m honestly way more interested in Jai.
Re:Zig 0.4.0 Released by xena on Monday April 08, 2019 @10:22PM (#19611171)
Can you link to Jai?
Re:Zig 0.4.0 Released by saagarjha on Monday April 08, 2019 @10:32PM (#19611225)
Re:Zig 0.4.0 Released by Cyph0n on Tuesday April 09, 2019 @10:48AM (#19615209)
Here is a link to a primer written by the community: https://github.com/BSVino/JaiPrimer/blob/master/JaiPrimer.md

Right now, the only way to actually see the language in action is to tune in to Jonathan's livestreams on Twitch. He is writing his next game entirely in Jai. He also streams compiler development every now and then (last night was a compiler stream).

Re:Zig 0.4.0 Released by otabdeveloper1 on Tuesday April 09, 2019 @04:12AM (#19612702)
> All these languages are potentially-better systems languages than C/C++

No they are not. C++ has spent decades building "a better C/C++". Any language that ignores those lessons and takes the stance of "learning C++ is too hard, let's go shopping" is doomed to fail.

Re:Zig 0.4.0 Released by flohofwoe on Tuesday April 09, 2019 @05:23AM (#19612998)
Apologies for being a bit blunt, but:

<rant> For all the time and work poured into C++, it has remarkably little to show over plain old C99.

Some of those new "better C" languages are the work of individuals and very small teams, yet they are able to build more progressive "better C" languages than C++ can ever be because it is held back by the need for backward compatibility for 'failed features' and 'design-by-committee'.

If all that ever comes out of those small 'better C' languages is some sort of consensus of which core-set of features actually makes a 'better C', than they have already contributed more to programming language development than C++. </rant>

Re:Zig 0.4.0 Released by notacoward on Thursday April 11, 2019 @09:29AM (#19634258)
> For all the time and work poured into C++, it has remarkably little to show over plain old C99.

Exactly. I think of it as a path-finding problem. C was obviously not where people wanted to be. As with any path-finding problem, it's possible to make a wrong turn. Often, attempts to recover without backtracking only make things worse. I contend that C++ has done exactly this. They're at point where a mature, reasonable person would admit their error and backtrack until a better path can be found.

I doubt that many of C++'s critics are arguing from ignorance or afraid of complexity. More often, they're objecting to spurious complexity because they know how to do better. I've written compilers, and they're not even close to being the most complex things I've written. It's not so much "let's go shopping" as "let's return this defective merchandise" and build something that works. It's only the lemmings who insist on rushing further down the wrong path. "Turning around is hard; maybe if I get enough others to come with me they'll break my fall."

Re:Zig 0.4.0 Released by orbifold on Tuesday April 09, 2019 @12:31PM (#19616392)
Without starting a rant myself about people that think C++ has nothing to offer over C, what is in your opinions then the reason for any large company to develop their code in C++ and not C? I'm thinking of virtually all Adobe Products, anything related to the creative industry really, Google, CERN, Microsoft... No-one in their right mind would try to develop Adobe Photoshop in C.
Re:Zig 0.4.0 Released by p0nce on Tuesday April 09, 2019 @05:48AM (#19613082)
Here are some things that make C++ better than C

- RAII

- exceptions

- classes and objects

- inheritance

- templates

- the STL

C++ is strictly better than C when wielded correctly.

Re:Zig 0.4.0 Released by flohofwoe on Tuesday April 09, 2019 @06:01AM (#19613138)
All of those are very subjective.

- RAII: Only useful with 'smart' data which must run code for initialization, destruction or copying. It's entirely valid to work with 'dumb' data only which is zero-initialized, and can be copied and deleted without any additional custom actions.

- Exceptions: too brittle and complex, modern languages have switched mostly to option-return values, which contain both an error code and success-result.

- Classes, objects, inheritance: left-over artefacts from the OOP hype of the 90's

- Templates: Not the only option to write generic code, other languages do this better. Programming entirely without generics isn't too bad either, not all code benefits from this.

- STL: not sure what to say here, it's the main contributor to slow compile times, excessive hidden memory allocation, slow debug performance and bloated executables. There are not many parts of the STL that are 'acceptable', but of course that's entirely subjective.

Re:Zig 0.4.0 Released by p0nce on Tuesday April 09, 2019 @06:48AM (#19613343)
Well you learn to appreciate the value of RAII and exception working on high-availability software. It's almost impossible to have correct error paths and deinitialization without. I'm very doubtful the new crop of languages without exceptions and RAII actually care about correctness in the wild.

Better than template without uniform representation? template is just copy-paste you don't _have_ to use it. Same remark for STL. You want a hashmap of arrays of string, you can have it in C++ in one line. In C you would end up with a linked list instead of picking the right data structure.

Objects and inheritance are not a hype. See this page, which uses CSS, which implements inheritance. Having subtyping is a basic premise of being a useful language (or, a GUI language).

Re:Zig 0.4.0 Released by flohofwoe on Tuesday April 09, 2019 @07:18AM (#19613480)
I've been writing C++ code since around '98, and have only recently moved back to mostly C. To be honest, features in C++ that I thought are a "must have" are actually a variant of Stockholm Syndrome, after a little while (a few weeks to months) one realizes that the world would keep turning without C++ ;)
Re:Zig 0.4.0 Released by p0nce on Wednesday April 10, 2019 @02:14AM (#19622287)
None of my competitors use a language from the 70's.
Re:Zig 0.4.0 Released by tomp on Tuesday April 09, 2019 @08:00AM (#19613703)
> Well you learn to appreciate the value of RAII and exception working on high-availability software.

Alternatively, you'll learn to not appreciate the value of exceptions working on high-availability software. Not personal experience, but AFAIK Google (definitely lots of highly-available software) disallows using exceptions in C++.

Re:Zig 0.4.0 Released by erik_seaberg on Tuesday April 09, 2019 @08:23PM (#19620446)
They have a critical mass of bad legacy code.

> Because most existing C++ code at Google is not prepared to deal with exceptions, it is comparatively difficult to adopt new code that generates exceptions[....] Things would probably be different if we had to do it all over again from scratch. - https://google.github.io/styleguide/cppguide.html#Exceptions

Re:Zig 0.4.0 Released by rafaelvasco on Tuesday April 09, 2019 @04:27PM (#19618618)
"Left-over artifacts from the OOP hype of the 90's". Sorry, but anyone that bashes on OOP can't be taken seriously. There's no problem with OOP, it can be misused of course, but the same is true of any other paradigm. Every programmer with any worth uses OOP, Functional, Data-Oriented, etc, where they are most effective. They are complements to one another not replacements.
Re:Zig 0.4.0 Released by otabdeveloper1 on Tuesday April 09, 2019 @07:57AM (#19613687)
> All of those are very subjective.

They're not. People vastly more experienced and more intelligent than you came up with them. Learn why they exist before dismissing them.

You won't get anywhere trying to replace C with a "let's go shopping instead" mentality.

Re:Zig 0.4.0 Released by moomin on Tuesday April 09, 2019 @04:18AM (#19612734)
Which of these languages do you think hasn’t learned the lessons of C++? Rust, for instance, has liberally encoded “modern C++” whilst plan not providing a lot of the features that make C++ problematic.
Re:Zig 0.4.0 Released by otabdeveloper1 on Tuesday April 09, 2019 @07:59AM (#19613697)
Rust is the better choice, but they're still learning about the real world of error handling, generic library code and performance optimization.