If i was making my own GitHub, i would make it possible to put one deploy keys to multiple repos, same as in Gitea. Why that doesn't work is beyond me and is a major pita with no simple work arounds
Sure the spec might be enormous but you don't need to touch it at all to be productive quickly. In no HTML or CSS tutorial i'v ever seen was a reference to the spec nor did i need to go there to solve something. And that in itself is another proof how nicely it is designed actually. Because on the other hand there are other document types or schemas where you absolutely have to go to the spec because it's is so cryptic and badly designed and not self-explaining that there is nothing else you can do.
Can you be more specific here? HTML and CSS can't be described like that in my opinion.
It is complex but not complicated. You can start with just a few small parts and get to a usable and clean document within hours from the first contact with the languages. The tags and rules are usually quite self-describing while consice and there are tons and tons of good docs and tools. The development of the standards is also open and you can peek there if you want to understand decisions and rationals.
"The core happening in the informational domain through digital platforms, which will soon migrate to synthetic virtual spaces." - wow, that sentence is packed! What is a "synthetic virtual space"?
Buying from local vendors doesn't have to do anything with politics. From groceries to software it makes perfect sense to me to buying locally. The money i spend in my town or country will have much bigger effect here again than when i spend it in a different country or even a continent
I have a T430s which was handed down to me by my boss 10 years ago. It has i5 from that time, 8Gb RAM. I'm still doing web app development on it same as 10 years ago and i don't feel any need to change it. I'm actually afraid there is no better laptop i could change it for when mine dies. Also i can't imagine no better keyboard :(
I also pay for Kagi and i'v never been happier with my searches. It's so nice not to have to slog through Google bullshit results. Kagi results are great and you can tweak the behaviour deeply to your liking. I'm also proud to support an alternative from a smaller company with same beliefs instead of Google who does a lot of damage to the medium i love be it ads or Chrome. So the few bucks are a no brainer. It's the same as paying for any other monthly subscription
Right now Kagi is a better search engine than Google. Why should some eventual demise in the future discourage anyone? There is no cost of switching and you can start using it right away
I'm using it for about two years and i haven't seen any sloppification. I see it as a feature that it is a paid service because i hope it will be a sustainable model for them to keep it as it is. I think it's a no brainer to pay for it instead of all the suffering people describe here. The founder remark i don't get
I have never heard or never had myself any problems with sleep on Linux laptops and i'm using Linux(Arch, Debian, Lubuntu) as my only driver for past 10 years
War and peace. You get to build a very close relationship with multiple characters whose life is unwinding during one of the greatest histories of human
Well i'm using importmaps on some projects but mostly i stick with Asset Pipeline and that is for new projects also. Over the years i iterated towards a setup which is very efficient and simple to use which is to have light JS dependencies and no JS frameworks. And when the need for complex client side arises i use Elm which is a joy to use once you get through the learning.
Also the Asset Pipeline stack is getting even lighter nowadays since with CSS nesting and other new features you can drop SASS completely
I develop a lot in Rails mostly as a single developer and and it's totally ok. With CSS and JS you can pick the approach you like and just stick with it. Importmaps(which i don't prefer myself btw) are the current default but it's very easy to use the older Asset Pipeline without any problems.
And frankly importmaps or the other possible aproaches are not so hard to understand. Any serious developer should be able to learn that. It's also not a Rails thing, it's just web