Not using Threads, but does anyone know if it requires a distinct new or account, or if you can login via your Instagram account? I'd imagine if the latter is the case, then this explain the high usage, if the barrier to entry is low (provided you already use Instagram). Also, I would be curious to see how many of the users remain active on the platform in the coming months.
The main reason, in my opinion, comes down to how Go as a language was designed. I have written some follow up posts to that, specifically this one: https://andrewpillar.com/programming/2022/10/24/a-simple-cru... wherein I explore creating an ORM-like library via generics in Go, this may be of interest to you if you want a better understanding of how some of these things would work in Go.
I consider the advent of this technology as whole, with the current state of Hollywood, to be concerning. It will ultimately lead to a world where actors will have their autonomy stripped away from them, even more so than they do now. Consider the status quo, whereby an actor's autonomy is somewhat determined by their start power. If you're trying to break into the industry then you have to put up and shut up with what you're given.
With the advent of motion-capture like this, actors will be reduced to a marionette of flesh to be puppeted around as the producers see fit. Perhaps Hollywood will be going towards a future where actors no longer act in movies, instead their likeness is simply licensed to a studio for a certain number of movies. Anyway, I'm a cynic when it comes to this, the industry itself is already plenty abusive and exploitive, and this could further that.
This is something they do, Marvel rely on outsourcing and using ununionised labour [1], and it shows in the recent films and TV shows they've made. There's a drop in the quality of the VFX. Wages for VFX artists aren't too high, as I've said, they are some of the most underpaid workers in the industry, and their protest against this is always stomped out. For a VFX worker it must be highly frustrating working in an industry where other workers are unionised, but they aren't.
>I'm not saying it is this way for everyone, but part of life is deciding if you want to work hard, have impact on things that matter, work on cool stuff, earn a lot of money, etc.
VFX people in Hollywoord are some of the most underpaid workers in the industry. Sure, it's cool that you can be a part of a team that helps make a movie. No doubt it must be pretty cool to see your work on the big screen, or even the small screen, and know that you played a part in bringing it there. But I think something the workers would also value is having some autonomy over their work, and being paid for it.
I'm not easily convinced by the argument of, "you get to work on cool stuff", working on cool stuff doesn't make up for risking povery, debt, or unemployment when you're underpaid. Furthermore, there's a difference between hard work, and exhausting working. And being put under crunch is exhausting work, not hard work.
The article says that there are similarities between the two industries, I see these similarities too between how the workforces are treated. Whereby Hollywood VFX workers are overworked and underpaid, and some even end up going under, and the Academy is always there to stomp out their protest during the few minutes they get at the Oscars [1]. Much like with game development, where waves of contractors are hired, then subsequently fired [2], or being just subjected to endless crunch [3]. I think it's fair to say that game dev companies are the sweatshops of the tech industry, and I feel for anyone who wants to break into what otherwise could be a creative industry.
On the contrary, I much prefer the fixed date of "2006-01-02T15:04:05" for formatting time strings. I find it much easier to write "Mon 02, Jan 2006", than what you would usually put for the strftime equivalent, "%a %d, %b %Y" (had to look it up, and at a glance it's not that obvious what it formats to). With Go, all you need to memorise is the date itself. Granted, coming from other languages it can take a bit of getting used to.
systemd, in my opinion (one that doesn't seem to be widely shared), really does make administering a Linux server easier. No longer do I have to wrangle with shell scripts for the process control of daemons, or worry about the dependencies between them, instead I can organise that logic in a nice and neat .service file for systemd to worry about. The templating feature as this article demonstrates is also incredibly handy for DRYing up some .service files you may write.
Another feature of systemd I really like are the timers [1][2] it introduces. It offers a much more sane approach to handling scheduled jobs, and allows for an easy overview of which jobs are running and when the next job will fire via systemctl --list-timers.
Thanks for the feedback. Regarding the configuration language, I don't think it's too hard to learn, I modelled it after the structured configuration NGINX uses since I find that easy to read and write compared to something like TOML, or YAML for the configuration I wanted.
Regarding the documentation styling, I appreciate the 40% width is a bit too narrow. The styling is something that has gone through multiple revisions, but some more work still needs to be done.
On the brevity of the documentation, especially on the manifest structure, I decided to err on the side of verbosity. But I will take your feedback on board.
Author of Djinn CI here. This is a CI platform that I developed, it is open source but there is also a hosted offering https://about.djinn-ci.com. Some of the features are detailed below:
* Fully virtualized Linux VMs
* GitHub/GitLab integration
* Variable masking
* Configurable artifact cleanup limits
* Multi-repository builds
* Repeatable builds with cron jobs
* Custom QCOW2 images for builds
I've written some posts demonstrating the features of the platform which I have posted here before:
Good article. Firecracker is something that has definitely piqued my interest when it comes to quickly spinning up a throwaway environment to use for either development or CI. I run a CI platform [1], which currently uses QEMU for the build environments (Docker is also supported but currently disabled on the hosted offering), startup times are ok, but having a boot time of 1-2s is definitely highly appealing. I will have to investigate Firecracker further to see if I could incorporate this into what I'm doing.
Julia Evans has also written about Firecracker in the past too [2][3].
Yeah, I think I stumbled across using the libvirt provider, however libvirt is just another abstraction (a very useful one) over multiple virtualization technologies. I much prefer working directly with QEMU for local dev environments since I only need a one and done machine.
A pretty interesting project I came across via reddit. Seems like a good lightweight solution for self-hosting git repos if you don't want to be burdened with the overhead of managing a full-fledged code forge. This also seems to come with a stagit offering for serving over gopher [1][2].
I get the hate for sprints, and the bastardisation of agile. I think however, the root cause of this is the way in which our society as a whole has been modelled, in a top down manner where control is wrested from the bottom, and perceived control is given to those in between. Each of these articles that make, valid criticisms in my opinion, always makes me think of Bullshit Jobs [1][2]. Most of our lives nowadays are inundated with menial bureaucracy, and each attempt to reform it within bureaucractic systems has simply lead to the red tape being rearranged. I think this stems from our hesitancy to have more horizontal models of ogranisation.
I've found the Arch wiki to be a great documentation source when it comes to most Linux tooling. It's detailed, and formatted in a way that is easy to read. I typically recommend the wiki for people when they want more information about a certain tool of Linux, because of its detail.