No love for The Witness?
-Ōryōki [応量器] is a small, thin container for the web.
+Ōryōki [応量器] is an experimental web browser with a thin interface.
– 10 hours ago, via GitHub ?
The funniest/saddest part is that they bring this huge, advanced cross-platform component and the download is OSX only!
I’ll spend the rest of my days with the Handmade Network guys (https://hero.handmade.network/), they are onto something…
Imagine what a large browser built atop this illustrious stack would look like!
This was very well done - the memories of the BBS days keep coming back!
Also, I’ve just found out this hypertext version which is pretty meh.
I agree. Unless you work in a playground/sandbox or new tech is your product.
Anecdotally, as an indie dev, I am looking at things like Rust to build tools. But at work, I’m using PHP and MySQL (OK, I admit: mariaDB) for web dev. Python for embedded hardware. My recovery strategy is focused on being able to install an OS and copy some files back. It’s hard to KISS with a moving target.
I’m somewhere in the middle on this article but I hear you.
But I think you’re onto something with Rust at home, PHP at work. For me it’s more C# at work, Go at home. I want to stay ahead - I just don’t want my client to have to pay for missteps.
C++2003 at work (But used more like C with classes) and C++11/14/17 at home.
C++ for fun, that’s a bold move.
C++11 and C++14 are fun again
(Aaand actually a tiny bit of Common Lisp at work I managed to sneak in.)
When I was a student, I made a comment about how they taught what I felt was old-hat technology instead of the cutting edge new toys.
The professor replied “no manager ever got fired for picking Java and MySQL for a project”.
That’s a pretty prevalent bonmot, but it has issues. It assumes people get fired over technology choices.
No one ever got fired for choosing Elasticsearch or MongoDB. That might be a bitter pill to swallow for most technologists. They get fired because the project failed to reach expectations. Careless choice of technology can be an issue here and is rather often also at the core of the issue. Obviously, if a project fails horribly, you will search for the easiest approach angle to relieve a person off their post, and careless tech choices can be one of them. And pretty often, a risky choice and inability to master is also one of the actual issues.
If the project succeeds, no one will question all that.
Yes, of course.
But when a project fails, some people will point to the unproven technology stack that was selected. Whether or not it was the cause of the failure or not.
At this point, you are on the defensive trying to validate your choices and shift blame. If you’d have picked safe, conservative bets over new frontiers, this choice would have been easier to justify.
Python for Embedded? That qualifies as hipster!
Haha! I know! I use a Windows Phone and App.net is my only social network! :-]