Cargo is one of the nicest build systems I've used. Coming from maven, I have nothing but love for what cargo brings and how easy it makes it.
The key thing for me with Cargo (and Rust) is the documentation. I'm able to quickly glean what I need to do from the docs, and often with useful examples that are close to my use case.
I do wish the package ecosystem was set up with namespaces. Abandoned crates, name squatting, etc. should really be a thing of the past. But I guess this fosters creativity in names.
Hi epimetheus2! There are probably going to be a few people here who say, "code in the morning, spend your time and mental energy on yourself before you spend it on your company". I agree with this, but I also want to point out a few things I've found for myself, since I'm coming from a similar background as you.
First, part of the thrill of coding when I was a kid was the discovering and learning new things. Even making my name flash on a screen was a really cool thing. At the time, coding felt like a mystic art that you had to master through hours of trial and error, and each thing you learned was another building block on your way to understanding.
Now that you're doing this for a job, you know how the sausage is made. You no longer are coding either elementary things (to learn whichever language), or even building things you find an interest in. You're using your skills for the purpose of making a company money (which hopefully pays you well enough to make up for the fact it's draining your own enthusiasm for this craft).
And that's probably one of the biggest things. You're taking this previously magical thing that you used to discover new and exciting ways to build [what you wanted] and using it for very mundane things, or for uses that you just have no passion about. Also, there are a million articles or Stack Overflow questions that tell you step by step what to do. You no longer have one old book from the library and 3 outdated Web sites that kind of talk about what you want to know. The excitement of discovery is lost since all of the answers are flashing on a bill board for you and everyone else.
I was feeling the same way as you from about 1 year ago until just 1 month ago. I also work as doing code (JVM stack and backend, as well). I also have about 3 projects of my own that I alternate between (1 backend, 1 frontend, and 1 that is both). About a year ago (Pandemic time) we laid off quite a few people, which meant all of my energy had to go into picking up a larger workload–effectively killing my motivation and passion for my projects.
Taking a year long break from my passion and projects was a very good thing. You shouldn't have to feel that you "need" to code for joy. That'd just kill the joy. Instead, find something that brings back that feeling of newness and magical curiosity that coding did when you were a child. Something that nobody is telling you what to do, or how to use your abilities.
Take up painting, photography, bike riding, wood crafting, a Raspberry Pi or other hardware (although, let's be honest, there are probably a lot of us who just buy them and leave them in a drawer :)). Even learning how to tend a flower garden would be something that you can pour energy into and feel invigorated when you get the results.
In time, your thirst for creating your own thing with code will come back (it did for me, anyway). And in the mean time, you can feel reinvigorated seeing the benefits of your work come to fruition, and have new knowledge that you can share with other people, or just enjoy thinking about as you go about your day problem solving how to solve your next curiosity.
Good luck! Life should be fun. You don't need to be the "coding as a hobby" person all the time! Feel free to jump around and only enjoy the things that bring you joy when they do that for you :)
I frequently travel, and bring my AppleTV with me to hook up to hotel TVs.
It would be great if they made a way to support Web logins for WiFi.
At the moment, I do t see a big change between this version and the one I own. If they added that feature, I’d buy it in a heartbeat so I could stop spoofing my AppleTV’s MAC on my laptop just to login to the hotel web portals.
I know people who plug the hotel ethernet into their own travel router to circumvent the captive portal. Though now you have to travel with another device
Kevin Rose and Alex Albrecht would put out weekly videos/podcasts where they'd talk about the top news articles appearing on Digg (which Kevin helped start).
Because Kevin was in the tech, media, and startup scenes, there was a lot of interesting information mixed in along with the humor and drinking.
It's nice to see PHP adding useful things like enums and async (green threads). My foray into Web development started with Perl, but quickly segued into PHP with how much simpler it felt. The ability to hop into vim on your server (or use CPanel back in the day) and edit your site live was exciting back then – but now that very thought makes me shudder with what could go wrong, haha.
While I've moved onto JVM languages and Rust professionally, I do hope PHP will continue getting future generations excited about Web development and building out their ideas quickly.
FYI: Not sure if the author will see this but some spelling mistakes in the article. [0] E.g. s/reslease/release/
Just yesterday I hopped into a server, attached to a running app, and did the copy/pasta thing to dynamically add some debug logging to a running app. It worked great!
What do they want async for? PHP's purpose is to run once to generate one HTTP response - they'd already forgotten this by inventing frameworks, but adding async seems to especially have forgotten this.
PHP already had curl_multi_perform which is very useful for running child tasks, but I'm not sure you need much more than that.
The usual asynchronous stuff like fetching data from two APIs to then prepare the HTML response to the user. Today, it's sequential, which is fine for DB calls to localhost, but less fine with API calls.
People also use PHP to write backend scripts, without web use at all.
While the original and primary purpose may have been for personal home pages, it has evolved considerably since then. Consider an accounting/aggregate billing script for a PHP application that runs on a scheduler. That isn't dependent on the web necessarily, but it does interface with the moving parts of the overall application. Async would be great here.
Another use of async is to build other kinds of servers like websockets, which need to hold long-term connections. ReactPHP + Ratchet works great for that in PHP. Currently it works with an event loop (multiple implementations under the hood, like libev, libuv, etc) similarly to Node. Fibers should make the internals of ReactPHP better, but it'll barely change anything in userland.
The adjective form of orthodoxy is orthodox. Think of something like the "Orthodox" church. And it's antonym is "unorthodox", for example: "the unorthodox church" ;)
The key thing for me with Cargo (and Rust) is the documentation. I'm able to quickly glean what I need to do from the docs, and often with useful examples that are close to my use case.
I do wish the package ecosystem was set up with namespaces. Abandoned crates, name squatting, etc. should really be a thing of the past. But I guess this fosters creativity in names.