Post AcewYJ2PFNV8S1cBOa by ignaloidas@not.acu.lt
(DIR) More posts by ignaloidas@not.acu.lt
(DIR) Post #AceZwxoqybImw843O4 by rain@hachyderm.io
2023-12-10T01:43:40Z
0 likes, 0 repeats
I refuse to believe this was written by actual practitioners in the fieldhttps://www.regulations.gov/comment/ONCD-2023-0002-0020
(DIR) Post #AceZwz1IVoqmf0tVQG by rain@hachyderm.io
2023-12-10T01:45:14Z
0 likes, 0 repeats
What kind of brain-dead response is "Vulnerabilities are found with any programming language, but it takes time to discover them"? This was actually written by the ISO C++ committee? What???
(DIR) Post #AceZwzpHVyphA2HQKe by rain@hachyderm.io
2023-12-10T01:47:26Z
0 likes, 0 repeats
To be honest, Rust is a pretty clear example of why formal specifications are worth less than they first seem to be! I'm glad people are working on one, but Rust has been successful at its goals without them. The fundamental soundness of its mechanics is pretty clear to anyone who has written production code in it, even though there are edge cases that need nailing down.
(DIR) Post #AceZx0kM5mUE12z0IC by rain@hachyderm.io
2023-12-10T01:57:05Z
0 likes, 0 repeats
What is this talking about??? Python has the with keyword, Java has had AutoCloseable since 2011, and even PHP has refcounting so resources are released if you don't duplicate a reference (and everything's cleaned up at the end of the request in any case). Saying that most newer languages don't have "facilities for handling resource release automatically" is a bald-faced lie! The people who wrote this should have to face professional consequences.
(DIR) Post #AceZx1bWu51MfxrTAu by feld@bikeshed.party
2023-12-10T03:13:29.376218Z
0 likes, 0 repeats
@rain > Saying that most newer languages don't have "facilities for handling resource release automatically" is a bald-faced lie!What's the trick to do it automatically for Go because, heh, I made a tool that keeps reopening docker's Unix socket to read from and ran the OS out of filehandles because they never closed.
(DIR) Post #AceZx3eRIEXL1ZEozI by rain@hachyderm.io
2023-12-10T01:59:30Z
0 likes, 0 repeats
Who wrote this anyway? The document just says "(identified below)" in the beginning but I couldn't find any names. The PDF title appears to be "DOE ISO C++ RFI" so did the entire ISO C++ committee sign on to it? That's exceptionally hard to believe, there are plenty of knowledgeable people on the committee
(DIR) Post #AceZx6ykv9ZRLRlaZU by rain@hachyderm.io
2023-12-10T02:23:13Z
0 likes, 0 repeats
I don't know where these numbers are coming from. "optimistically" 2000 lines/developer-year?????I just finished a year at Oxide and in the main repo I've worked on, to which I've dedicated around half of my time, GitHub says my contributions are +82,102/-50,485 lines. The rest of my time was spent in reviews, other repos, doing design work, written documents, presentations, and so on (all things that are part of the job with senior+ engineers).
(DIR) Post #AceZxAzG1ELfmA22uO by rain@hachyderm.io
2023-12-10T02:45:04Z
0 likes, 0 repeats
Of course this varies a lot by role and job requirements, many principal-level engineers are probably going to be busy conducting external meetings and such. But if you're rewriting a 10 million line application I straight up do not believe that the average contribution of a "good" developer will be 0.04% of the codebase/year.
(DIR) Post #AcecMrQlYEMmYoH3Am by ian@mckellar.social
2023-12-10T03:40:54Z
0 likes, 0 repeats
@rain @whitequark Does this also account for the enduring success of Perl?
(DIR) Post #AcewYJ2PFNV8S1cBOa by ignaloidas@not.acu.lt
2023-12-10T07:27:07.422Z
1 likes, 0 repeats
@feld@bikeshed.party @rain@hachyderm.io well, the answer is that go is a modern language only in the date it has been released and not much elseit's quite definitively 80's concepts wrapped up in 2010's language marketingthe only part of it not from 80's is channels for concurrency (those are from 90's)
(DIR) Post #Acex4vnoekrTwbLb16 by mcc@mastodon.social
2023-12-10T01:59:57Z
0 likes, 0 repeats
@rain ahh, but you see, other languages do scoped resource lifetimes using specifically-delineated blocks, whereas C++ is unique in doing it via *RAII*, which is better because it is wildly ambiguous and has awkward implications for compiler optimizations. *Why* has no other language chosen to use this idiom, you ask? Is it for a reason? Well, you see: Don't ask that question
(DIR) Post #Acex4y4uCBih0BMGvo by ignaloidas@not.acu.lt
2023-12-10T07:32:58.854Z
0 likes, 0 repeats
@mcc@mastodon.social @rain@hachyderm.io Hey, Python does give you the del hook, which probably has just as well defined exit point as RAII does 😉
(DIR) Post #AcfuMupssqFBSE9tia by BatmanAoD@mastodon.social
2023-12-10T18:03:44Z
1 likes, 0 repeats
@feld @rain I guess technically `defer`.