- Reticulum
- I2P
- Mycoria
- Yggdrasil
489 karma · joined July 28, 2014
- Reticulum
- I2P
- Mycoria
- Yggdrasil
So its not entirely black-and-white, but I agree that for a large portion of people they do indeed never need to care.
Combine this with the fact that corporations are locking down what you can do on work computers, and forcing everyone to save files in the cloud (Office365 / Sharepoint / etc).
And you end up with a world where owning a computer is a niche thing, and most people only use it in a limited way for work or gaming.
You can buy "cheap" EInk devices [1] with an ESP32 and flash your own software on it, an ESP32 costs less than 5$, so the rest of the price is all down to the price of the EInk panel and controller.
[1] https://shop.m5stack.com/products/m5papers3-esp32s3-developm...
Lottie started out as a plugin for Adobe After Effects to try and let them export animations for use on Web. As far as I know this is the only "half-standardised" way of exporting animations between tools.
If you don't need animations from a dedicated animator then the better solution is using "a pile of JS + CSS transitions", and hopefully this is what Lottie for the web eventually "compiles" into.
The commit message is supposed to contain the details that you can't just glance from the code. Why a certain decision was made, or the pro's and con's of a decision, a link to a relevant Github / Jira issue, etc.
The enshittification continues...
> If your product is still around in 5 years, you’re doing great and you should feel successful. But guess what? Whatever framework you choose will be obsolete in 5 years.
However I feel like this point isn't entirely correct. According to StateOfJs [1] React have been the most used frontend library for the last 8 years (which I think is how long the survey have been done). React Hooks which is the modern way of writing React components have been around for 7 years (since 2018).
React is definitely going to be around in 5 years, and most likely still going to be the most used frontend library. I also don't think Vue is going away in the next 5 years (Angular might however, they are loosing usage numbers year after year).
So really I think there is an argument to be made that you should just use React and move on.
[1] https://2024.stateofjs.com/en-US/libraries/front-end-framewo...
The only reason that other engineering professions does things properly is that bridge building is not free marked capitalism, but government mandated rules. Just look at how much GDPR rules in EU does for actually making companies do the bare minimum to respect privacy.
In a professional capacity I use Docusaurus for project documentation, this is stored in the same Git repo as the rest of our products source code (so one monorepo both for code and documentation).
But from a project management perspective it does lack in some perspectives. This mostly depends on what you need and how you use it. Unlike Jira, Github issues does not come with plugin support and can't be customised as much. This makes it easier to work with for developers but might not give you all the power you might want while planning the project. For example, to my knowledge, theres no way of assigning "Story points" and having "burn down charts" in Github issues; as its not a tool ment for doing Scrum. But if you're not doing Scrum then it doesn't matter. It also doesn't have a concept of sprints and epics. But I does have both tags and releases which you can use for planning.
And the new Github Issues beta looks to add a lot of features: https://github.com/features/issues
But you should check to see if you have activated hardware encoding. Go to "Settings" and "Output", select "Output Mode: Advanced" and then in the "Encoder"-dropdown you should now see an option called "Apple VT H264 Hardware Encoder". That should hopefully help somewhat with CPU.