I had the same experience, lol. I started with Crime and Punishment expecting thinly veiled philosophy where each character is a mouthpiece for one of the author's thought processes. Granted there's some of that, but I wasn't expecting such an exciting murder drama. Went into Karamazov expecting an exciting murder drama, and got the type of Russian literature I initially expected Crime and Punishment to be! Really it's a question of expectations.
So every time my ISP changes my IP, facebook pitches a fit, makes me solve a dozen captchas and authenticate on an existing login session, but in the meantime Meta' sother website doesn't even require using the registration email for a password reset?
Microsoft Go? I've used Go on windows for years now and this is the first I've heard of this fork. So it only exists because microsoft wants to have a crypto package that complies with an arbitrary regulation? Is there a reason that a better package requires a fork of the entire runtime rather than just, say, a normal Go package? It sounds like it requires cgo to call into third-party libraries, but that's already a common practice in "normal" Go libraries.
One thing I do appreciate is how the relevant issue in the upstream Go repo says: "A number of companies must comply with them, for example as part of a broader FedRAMP compliance posture. (If that's not you, you can ignore this. Run!)" [1]
Apparently I'm just not the target audience. Sounds like I'm correct in assuming it's security theater at best, and an avenue for new backdoors at worst.
The velocity of a spacecraft in low earth orbit is over 15,000 miles per hour. Smashing into the atmosphere is perhaps the most fuel- and cost-efficient way to slow down to a speed at which landing is possible.
Heh, so it's an 1897 version of what this guy on youtube attempted with a monster truck with mild success: https://www.youtube.com/watch?v=ohxGA7fpfu0 (warning: extremely redneck)
One thing the article doesn't seem to mention is noise. I've found that the "actual" air purifiers seem to be much quieter than box fans. Perhaps if you had greater control over the box fan's speed you could get the noise down to a comparable level, but I doubt the cheap type of fan used in the article is capable of such a thing.
The issue is that the "young" demographic mentioned in the article is ages 18-29, and high school must have changed quite a bit in recent years if students have not actually heard about the holocaust or WWII.
Judging by the project, it's implemented by instrumenting the source code; either manually modifying error returns with a wrapper function, or by running source files through an automated tool that will find and modify the return statements for you.
I'm not anyone involved in this thread (so far), but I've written a minimal PDF parser in the past using something between 1500-2000 lines of Go. (Sadly, it was for work so I can't go back and check.) Granted, this was only for the bare-bones parsing of the top-level structures, and notably did not handle postscript, so it wouldn't be nearly enough to render graphics. Despite this, it was tricky because it turns out that "following the spec" is not always clear when it comes to PDFs.
For example, I recall the spec being unclear as to whether a newline character was required after a certain element (though I don't remember which element). I processed a corpus containing thousands of PDFs to try to determine what was done in practice, and I found that about half of them included the newline and half did not---an emblematic issue where an unclear official "spec" meant falling back to the de facto specification: flexbility.
It's honestly a great example of something a GPT-like system could probably handle. Doable in a single source file if necessary, fewer than 5k lines, and can be broken into subtasks if need be.
Having to hold perfectly still (possibly in an uncomfortable pose) in a giant machine that's making loud, uncanny noises for 20+ minutes is indeed a very bizarre, meditative experience. It is interesting, but, in my opinion, you're probably going to be happier not having the health concerns that lead to getting an MRI in the first place!
Jon Bois is a genius, and this is the main example I return to when tempted to think that hypermedia is just a gimmick. It takes a special type of creativity to not just make it feel "tacked on." Perhaps the light jazz and dated look of the google maps visuals just meld well with the nostalgia evoked by the content of the story. The text alone would probably work as a good scifi short, but the additional material makes it so much more dramatic.
Here's an idea for how to maintain Go moving forward: keep making the damn tool however you want. The thing never would have existed in the first place if they had started with an industry survey. It was created to address a perceived need, by the people with the need, for themselves. This model is perfectly fine moving forward. Some industrial user wants a new Go feature or bugfix? Great. If it's enough of a problem, they can fix it and upstream a patch. That's how open source software is always supposed to work. Telemetry does nothing to improve this situation. If the Go team at google no longer has any ideas for what to work on (as must be the case if they're wasting their time on dumb crap like forced google spyware in a compiler) then they should just stop. Maybe focus on accepting PRs from people with ideas and strong enough motivation to work on them. I mean, there are 5000+ issues and 330 open PRs on the go github right now, so that should be plenty to keep them occupied. On top of that, how can literal thousands of issues not be a strong enough source of actionable usage information that they saw fit to try to get more? Do they plan on wrapping up all the open issues before looking at telemetry?
Yes, I was in the first category of people, where I am using GDNative to ultimately call a single function written in Go, not due to speed, but simply in order to leverage a huge amount of code I had already written in that language. Judging by the GDExtension headers, I can probably pull off something similar if I forgo all of the C++ bindings that I don't need. However, I am hesitant to dedicate any time to doing so at the moment.
Don't get me wrong, GDExtension seems awesome, but it's also true that it doesn't seem geared towards the case that I was using GDNative for.
As much as I'm looking forward to 4, has GDExtension been stabilized / documented yet? I know there's the existing C++ example [1], but I really, really don't want to jump through a scons & C++ project simply to call a single native function in a DLL. You can do such a thing with GDNative, and I presume that it is possible in GDExtension as well, though it isn't obvious how to do so. This strikes me as a huge barrier to adoption, since GDNative is one of the big things that will be incompatible with 4.
Boy, if only you saw how popular Beamer (a LaTeX presentation framework) was in certain academic circles. Spoiler: it leads to exactly the problem you describe, in addition to using some default styling that manages to be both hideous and crushingly bland at the same time. At least, based on the screenshots, this proposed framework doesn't have the second problem.
I guess, the way I view this is as a "better beamer" (which isn't saying much IMO) rather than a better powerpoint. Basically, it's a way for people who were going to make a text-heavy presentation anyway to produce something that looks OK, and to avoid using a heavyweight tool like LaTeX.