omrispector
Re:Cyphernetes: A Query Language for Kubernetes
on Monday December 16, 2024 @03:22AM (#42429038)
This is way cool. The ability to visualize the k8s object model as a graph and query it as such makes so much sense!
The hottest feature in my mind is applying this in an operator - maintaining state as defined by a simple graph query. It is much more readable, and does so with very little code.
Well Done!
Re:Git Does Not Have Branches
on Sunday July 16, 2017 @01:01AM (#14780572)
Actually, that is exactly the point - Git can be used in ways that obscure history. That is why correct and uniform use are important in a project.
As for your question -look at the graph again. fixA was NOT necessarily committed on featureB. Very likely it was not. But it looks that way, due to the way Git manages branches.
At Last: Multiple Inheritance in Maven
Re:Gamification, VR, ER & Social networks: Where is this leading?
on Tuesday October 29, 2013 @02:05AM (#6632298)
I find this movie to give an excellent discussion on where our culture may be heading. It's also technically well done.
SPOILER: I find that the end is not in par with the rest of the movie. I would hate this discussion to go down the road of Frankenstein syndrome/technofobia/conspiracy theory. There are so many more relevant issues with how this affects us without going down that (over-beaten) path...
Gamification, VR, ER & Social networks: Where is this leading?
Re:The best GitHub client is actually made of plastic
on Sunday October 14, 2012 @01:12AM (#4650743)
I totally agree.
Have been using Plastic for two years now (small teams, so I could use it for free) - and I have not seen it's equal. I used many version control systems (from VSS to ClearCase,CVS to SVN, StarTeam and of course - GIT) - None is as powerful and user friendly both as a developer and as a "version manager" (a.k.a. team leader/project manager/integrator).
Why isn't it better known? I think the reasons are:
- There is no "GitHub" - you have to install a server
- Above 15 people you need to start paying - open source people cannot accept this limitation. Startups could but feel uncomfortable
- Companies beyond startup stage are usually already entrenched with another source control. Even if they do replace - they want to go for something "safe" (which they equate with "popular" or "expensive")
Maybe it's just a matter of time, and Plastic SCM quality will get it a market share, but I am not sure...