Yours is a good book (got both editions myself), but sadly language learning books will be hit the hardest by AI. Partly it’s what you said regarding copyright washing, but the other big reason is that people will code less; I am writing little to no golang and am prompting it instead. The book is still useful to me, since I want to continue to understand what’s happening, review code, etc, however I expect that my kind of software engineer will be in the minority in the future.
If you publish a 3rd edition and I’m not replaced by AI by then, I’ll buy it. :)
On other topics, using AI can fill some gaps, but books summarizing years of hard-won knowledge are priceless. NoStarch is amazing when it comes to such resources. They have an upcoming book on Linux kernel Memory Management for example, the classic Linux tome from Kerrisk and very specialized security books.
On the other hand I cancelled my O’Reilly sub because I didn’t read enough to make it worth the price and now I purchase DRM-free e-books individually, as needed.
I'd bet money I have more experience in this than you. Culture shock is very real (I've lived it), but culture's ain't countries and hell, I get culture shock when I go to the south here in America. It's just some old timey 1940s "we gotta keep these different cultures separated" nonsense. It's nationalism and racism (though it purports to be otherwise).
Things don't have to be this way, we choose them to and I'm getting awful tired of people keeping making the same choices over and over again because they think an imaginary line is somehow sacrosanct.
> I get culture shock when I go to the south here in America.
Or even from urban to rural areas.
> It's just some old timey 1940s "we gotta keep these different cultures separated" nonsense.
That's a huge mistake right there. Those who want to keep their culture should be free to do so, as long as they don't try to force theirs on others - that's a common and traditional American value which is now being attacked by both extremist segregationists and extremist pot-melters.
> It's nationalism and racism (though it purports to be otherwise).
You should learn what these words mean and stop purporting they mean something else.
> It's all made up. Even culture.
Bro, not only culture, the entire human civilization is made up. The issue is to make it good, not bad, but you seem to be all confused about it.
No, it's racism, because 9/10 times when someone says, "well these cultural differences are so vast" they really mean "I don't like people from that culture" which becomes "I don't like people from that country or who look like that."
Almost always. It's always the same thing. Fear of the outsiders and disdain for change. I'm not going to debate you on it, I'm just tired of hearing it.
And yet with all that experience you’ve still managed to come up with a conclusion which describes the exact opposite way humanity evolved and currently lives.
One of the authors commented below that the “teams” were actually persons and the Rust person was an intern.
This is even less serious than the typical pattern of grabbing random students for experiments and then drawing conclusions about the general population.
Not sure about your life experiences, but every new, from-scratch project I have undertaken has looked like 1-2 or at most 3-4 people on good terms who really pulled their weight, with the rest being basically not dead weight, but the management overhead they caused ate up most of the productivity they brought to the table.
All of these didn’t prevent Go from competing with Rust and I’m guessing that Fil-C will be the better choice in some cases.
Rust has managed to establish itself as a player, but it’s only the best choice for a limited amount of projects, like some (but not all) browser code or kernel code. Go, C++, C with Fil-C) have solid advantages of their own.
To name two:
* idiomatic code is easier to write in any of these languages compared to Rust, because one can shortcut thinking about ownership.
Rust idiomatic code requires it.
* less effort needed to protect from supply-chain attacks
To handle supply chain attacks, you need to know where yiur code comes from. That is often not a given when working with languages where it is easier to copy and paste in code from random other projects.
I have seen so must stuff copy and pasted into projects in my life, its not funny. Often it is undocumented where exactly the code comes from, which version it was taken from, how it was changed, and how to update it when something goes wrong.
When code is not copy and pasted it is over rewritten (poorly).
Code sharing does have its benefit. So does making it obvious which exact code is shared and how to update it. Yes, you can overdo code sharing, but just making code sharing hard on the tooling level does mote to hide supply chain security issues than it does to prevent the problem.
I doubt that ideomatic code is easier to write in C once you switch to Fil-C. Your code will just get killed by the runtime whenever it does something it should not do (and the compiler does not catch). You need to think about that stuff when your runtime enforces it.
Indeed, however Rust solves two problems in one language, the safety of managed languages, without having to use any form of automatic resource management, even if reference counting library types might be used, additionally.
As my comment history reveals I am more on the camp of having rewrites in Go (regardless of my opinion on its design), Java, C#, Haskell, OCaml, Lisp, Scheme,... Also following experiments of Cedar, Oberon, Singularity, Interlisp-D, StarLisp,....
However you will never convince someone anti-automatic resource management from ideological point of view.
Now would someone like that embrace Fil-C, with its sandboxing and GC? Maybe not, unless pushed from management kind of decision.
They would probably rewrite in Rust, Zig, Odin,... if those are appealing to them, or be faced with OS vendors pushing hardware with SPARC ADI, CHERI, ARM MTE,... enabled.
> However you will never convince someone anti-automatic resource management from ideological point of view.
It's generally accepted that 'explicit is better than implicit' and what you want in the end is deterministic, machine checked resource management. Automatic resource management is a subset of machine checked resource management. There is a large, somewhat less explored space of possibility (for example seL4 lives in this space) where you have to manually write the resource declarations and either the compiler or some other static analysis checks your work.
Except languages like Rust and C++, are full of implicit behaviour, so it is kind of interesting argument.
Even C has its implicit moments, with type conversions, signal handling, traps, setjmp/longjmp possibly hidden in libraries, thread handling across forks,
First you need to figure out if it’s a surface infestation because of condensation or if it’s a constructive thermal bridge. The latter can be solved by raising the surface (wall, ceiling, etc) temperature through insulation or more inefficiently special heaters designed for this purpose.
In both cases, the contaminated material is removed down to the plaster or masonry. Wood, wallpaper and similar materials will likely be deeply contaminated and must be removed. For areas larger than 1 sq meter, it’s better to get a specialized contractor which will use HEPA vacuum cleaners, special bags, etc to ensure that the mould spores don’t spread in other rooms.
For small areas the agents of choice are bleach or hydrogen peroxide, both available in products for home use.
The web and web apps as pushed by Google and others was another nail in the coffin of efficient software.
From Android to whatever web framework they’re peddling as development solutions, these are not designed for efficiency, but for time-to-market and consumption by front-end developers.
I worked on Windows programs similar to WinAmp, which had custom drawing, skins with custom shapes, etc. Usually written directly in WinAPI, VCL (C++ Builder, not Delphi) or a combination.
It was a matter of having access to the right (although limited) resources such as Petzold’s book, Codeproject and experimentation. There was no big rush, no start-up hustler mentality and most importantly hardware resources mattered a lot and it was a point of pride to create efficient software.
The development culture of present time is the opposite of that: developers are drowning in documentation, the default solution is technically inferior and the hustler mentality’s dominating.
If you publish a 3rd edition and I’m not replaced by AI by then, I’ll buy it. :)
On other topics, using AI can fill some gaps, but books summarizing years of hard-won knowledge are priceless. NoStarch is amazing when it comes to such resources. They have an upcoming book on Linux kernel Memory Management for example, the classic Linux tome from Kerrisk and very specialized security books.
On the other hand I cancelled my O’Reilly sub because I didn’t read enough to make it worth the price and now I purchase DRM-free e-books individually, as needed.
reply