News for hackers. Stuff that matters.
Re:GTK4 Bindings for Common Lisp by sylware on Tuesday September 20, 2022 @12:09PM (#32913754)
Does GTK4 finally implement its own C coded unicode text shaper (or at least, a roman script text shaper)? No I don't want that horrible c++ diareha which is harfbuzz.
Re:GTK4 Bindings for Common Lisp by audidude on Tuesday September 20, 2022 @03:38PM (#32916733)
Harfbuzz exposes a C API, why would you need to use C++?

Additionally, it works extremely well with GTK 4 via Pango and you can often interoperate between the two layers if you even need to touch a hb_face_t/etc. In fact, the only time I had to mess with Harfbuzz was when integrating GPU-rendered glyphs via Behdad's GLyphy shaders.

Re:GTK4 Bindings for Common Lisp by sylware on Tuesday September 20, 2022 @04:16PM (#32917208)
It has a C API, but it is written using c++. A long time ago, I did a build of GTK3, to remove the c++ dependency, I did an implemention of this C API in C, only for roman scripts though. I bet this C API was "obsolescence planned" and if I ever need GTK again (unlikely), I will code again a C implementation for roman scripts.

There is an alternative from IBM, ICU, it was properly coded in C, but it was switched to toxic c++.

Re:GTK4 Bindings for Common Lisp by audidude on Tuesday September 20, 2022 @04:40PM (#32917493)
Sounds like C++ has hurt you quite a bit.

I mean, I don't use it, and I've been writing C for a solid 25 years, but Behdad is one of the best engineers I've ever met in my life. So I definitely don't share your opinion of the code or the quality.

Re:GTK4 Bindings for Common Lisp by sylware on Tuesday September 20, 2022 @05:37PM (#32918137)
c++ is toxic for humanity because of its grotestquely and absurdely complex and massive syntax and its compilers. This is not a matter of opinion, this is an absolute unquestionable truth.

Carefull, I am not saying plain and simple C is better: it is only orders of magnitude less worse as there is already way too much in its syntax. Some would call that, the "most reasonable compromise".

Re:GTK4 Bindings for Common Lisp by pjmlp on Wednesday September 21, 2022 @04:18AM (#32922130)
So you also only use C compilers written in C, so no clang nor GCC for you I guess.
Re:GTK4 Bindings for Common Lisp by sylware on Wednesday September 21, 2022 @09:33AM (#32924927)
Indeed, I am currently trying to remove as much as I can gcc and llvm from my stack (I am now targetting much more, probably too much). llvm is financed by apple (vanguard/blackrock), and gcc by the MIT/redhat(IBM). I wish I had that much money to hire ppl in order to remove that toxic c++.
Re:GTK4 Bindings for Common Lisp by cowtools on Wednesday September 21, 2022 @12:27AM (#32920789)
There was article here the other day on a project by herb stutter to improve c++ syntax, I can link it to you if you want.

But I get the impression that the syntax is a fixable problem. Usually critics point so something like the template system or something.

Re:GTK4 Bindings for Common Lisp by audidude on Tuesday September 20, 2022 @06:03PM (#32918408)
Cool story.
Re:GTK4 Bindings for Common Lisp by sylware on Tuesday September 20, 2022 @06:36PM (#32918698)
The beyond sanity complexity of c++ is not a story unfortunately. The real sad story is that some ppl think they are smart because they code c++.
Re:GTK4 Bindings for Common Lisp by d_tr on Wednesday September 21, 2022 @06:02AM (#32922853)
The really sad story is the unjustified amount of shit C++ gets given its history and design goals.

C++ provides features to write much safer and nicer code than with C, for the same effort, with minimal overhead. You have proper constructors and destructors, smart pointers, the STL, templates, and much more.

Your comments in this thread make no sense.

Re:GTK4 Bindings for Common Lisp by sylware on Wednesday September 21, 2022 @08:20AM (#32923962)
It is perfectly sensible: c++ syntax and its compilers are grostesquely and absurdely massive and complex, and this is an issue.

There is no opinion here, just facts: for instance, due to the abysmaly (the word is fair) difference between c++ and C, it is reasonable for a team of averagely skilled individuals or individuals to write a naive C compiler, which is absolutely not the case for c++.

If you don't want to acknowlegde this is a issue, at least I tried to open your eyes on the matter.

Re:GTK4 Bindings for Common Lisp by colejohnson66 on Tuesday September 20, 2022 @12:32PM (#32914148)
What's wrong with Harfbuzz?
Re:GTK4 Bindings for Common Lisp by chris_wot on Tuesday September 20, 2022 @12:34PM (#32914180)
What is the problem with harfbuzz? we use it extensively in LibreOffice, works great!
Re:GTK4 Bindings for Common Lisp by nerdponx on Tuesday September 20, 2022 @01:39PM (#32915125)
I love that LibreOffice lets me use the full range of OpenType features in fonts. Do I have Harfbuzz to thank for that?

But please let me edit the sample text in the OpenType features modal, so I can actually see the effects of my changes without leaving the entire Font window :)

Re:GTK4 Bindings for Common Lisp by audidude on Tuesday September 20, 2022 @03:39PM (#32916756)
Re:GTK4 Bindings for Common Lisp by nerdponx on Tuesday September 20, 2022 @06:19PM (#32918558)
Based on the font chooser, absolutely. Thanks for this link.

...but did they fix the file picker yet?

Re:GTK4 Bindings for Common Lisp by chris_wot on Thursday September 22, 2022 @09:06PM (#32946728)
Without Harfbuzz, I doubt it would have been as easy to implement.