HNHacker News
TopNewBestAskShowJobs

somnium_sn

308 karma · joined June 4, 2012

submissionscomments
somnium_sn··on A History of Source Control Systems: SCCS and RCS
For those following along, the blog post was updated to reflect some of the comments. Most importantly it includes an email that Marc Rochkind, the author of SCCS wrote me, with some anecdotes from the time.
somnium_sn··on A History of Source Control Systems: SCCS and RCS
Post author here! Fun fact Tichy was my professor at KIT in 2008-2013! “Fäden!!!!!”
somnium_sn··on A History of Source Control Systems: SCCS and RCS
Is that TeamWeaver? I’d love to learn more about it!
somnium_sn··on A History of Source Control Systems: SCCS and RCS
Oh this thread is gold! Thank you!
somnium_sn··on A History of Source Control Systems: SCCS and RCS
It means I am bad at spelling and it should say “missing” source control system.

Realistically knowing my track record, the series will probably take 2-never years to finish.

somnium_sn··on A History of Source Control Systems: SCCS and RCS
By the time it was open sourced, the DVCS wars were already at an end. Git (due to Github) was used everywhere. Bazaar saw it's last release in the same year as BK open sourced (2016) and Mercurial usage dropped slowly.
somnium_sn··on A History of Source Control Systems: SCCS and RCS
Post author her!

Super interesting! I heard rumors about it!

Do you know if that was just a matter of implementation or a matter of data structure usage? In my mind, the RCS approach makes more sense for common operations such as checking out the most recent version, particularly if history is deep. (Writing would still be same, given the most recent version is in top in RCS (and not just append only).

Would love to get more flavor on the his, and happy to amend the post with more information!

somnium_sn··on A History of Source Control Systems: SCCS and RCS
Thank you! Great idea!

I do have thoughts about waht the next generation of source control systems should look like! It hopefully will be the last post in the full series. So estimated arrival time for that post, by interpolation of how long it took me to write this post, is roughly 1-2 years :P

somnium_sn··on A History of Source Control Systems: SCCS and RCS
The quilt tool by Andrew Morton is one of these tools used for maintainance (https://man7.org/linux/man-pages/man1/quilt.1.html) of the kernel. It's actually quite nice to use. Early versions of git and mercurial had tooling around similar workflows on top of git/hg repositoires (guilt, being one of these tools).

My understanding is that even during the BK years, some maintainers refused to use it and would continue to use tarballs + patches.

somnium_sn··on A History of Source Control Systems: SCCS and RCS
> I think this is one of the most misleading and confusing things people seem to get taught about version control systems. Whether they store deltas or not underneath is actually an irrelevant implementation detail. But surely it's easier to think of version control systems as storing version? It's right there in the name! It's not called a delta control system.

Post author here!

I agree! One of the fascinating bits of SCCS is that it actually exposed the idea of deltas right away to the user. Of course in the 70s, the amount of users was limited, pretty much exclusively programmers familiar with the idea, and probably all people who knew each other :).

Nowdays a VCS should just care about snapshotting your work. In my experience, only Git is so confusing that people need to understand the underpinnings of the system (whats a GC, whats a tree, etc). Systems like SVN, Mercurial & Co all seem to mostly do the right thing for the user with minimal knowledge on the user side.

Fun side note: I had a heated argument with Olivia Mackall, the original author of Mercurial, when I wrote Mercurial bookmarks. I initially called it refs, since they were models after git refs. Olivia insisted to call it bookmarks, since it's the more intuitive english name for what it's doing (bookmarking a part if a book of 'history'). Nowdays I much prefer the name bookmarks, since it's an analogy that makes it easy to reason about what it's doing, rather than a technical term that needs to be learned.

somnium_sn··on A History of Source Control Systems: SCCS and RCS
Author of the blog post here!

I am super curious about your experience with SCCS! I have never really used it for personal projects, so the blog post is purely based on research and a bit of trying. Really curious what oyu loved and what annoyed you about SCCS!

somnium_sn··on Why Facebook doesn't use Git
I prefer the term "derived" from Mercurial. It was Mercurial and slowly but steadily morphed into what's a custom VCS now.
somnium_sn··on Personalized learning can feel isolating. Whole class learning can feel personal
Self directed learning like this happens within the social constructs in areas where people are very interested at a time or have a specific need. My understanding of the article is that is more focused on the general approach to learning, where the social construct, and help, support, even understanding where compared to others you are, is helpful.

These self directed platforms can be useful in certain use cases but can’t replace the base education system with classrooms.

somnium_sn··on Linux Namespaces Are a Poor Man's Plan 9 Namespaces
I don't know how zones were implemented in Solaris, but since the article brings up docker, I feel the original zones implementation in Solaris is a still significnatly better user experience than docker or anything similar on Linux. The combined stack of zones + crossbow and zfs was just a pleasure to work with.
somnium_sn··on Sapling: A new source control system with Git-compatible client
It stems from the original Mercurial implementation. The goal here is that every operation leaves the repository in a good state that can be pushed/pulled. That's why Mercurial and Sapling rely on commit/amend/uncommit, etc and for example usually discourage the use of interactive rebasing in favor of restack and other operations that add another "state". It facilitates the mental model for developers without actually removing workflows (they are just different).
somnium_sn··on Gov.uk Platform as a Service
I've moved from Germany to the US and then to the UK. gov.uk is by far the most impressive government website i've encountered. Accessible, consistent and just works. Really a good show of what a government website can offer if done right.
somnium_sn··on The sudden death and eternal life of Solaris
For some Solaris has been one of the first UNIX experiences, as it was one of the most popular unices out there. Most university used it before Linux became popular.

For others, like me, who learned Solaris fairly late (2006), Solaris was a testbed for one of the best operating system technologies out there. Modern filesystem (ZFS), dynamic tracing (dtrace), containerization (zones), dependency management during boot (svc) and virtual network stack (crossbow), have been in solaris way before Linux. Most of modern Linux tools, such as eBPF, systap, btrfs, etc are a direct answer to the research done by Sun.

So some are nostalgic as it's their first experience, others, because it felt like a really good operating system a few years ago (despite it's quirks).

somnium_sn··on Curl author asks Microsoft to remove 'curl' and 'wget' aliases from PowerShell
All the comments make me incredible sad. Established projects need a valid backwards compatibility policy, this is particular true for shells and programming language to not break existing scripts.

People make mistakes and it's been agreed that introducing these aliases years ago was a mistake, albeit I think back then an understandable mistakes, given the idea to bring a shell to windows that has the power of a traditional unix shell.

Now people are loudly complaining, laughing, etc but without any constructive feedback that takes the backwards compatibility needs of a tool that is literally shipped to hundreds of million of people into account and stomping RFC approaches that are pretty similar to those in other projects (see PHP RFCs, Python PIPs, etc).

Since when did people became so hostile towards open source projects that try to do the right thing?

somnium_sn··on Eve Online wages largest war in its 10 year history
I think there is a huge misconception of how eve works. It's not really necessary to fly one of the big ships nor train them. But then I started 2 years ago and have 2 super carriers and a titan. It's about getting into the right corporations find the right source of ISK and play the game the way you want it. If you want to fly a titan, you can do it within two years (or less) if you are smart about it.

However what makes EVE every unique is that a new player is valuable as a 10 year old veteran if they are willing to learn. A small ship can hold a carrier or super carrier in place till reinforcements arrive. It takes you 2 weeks to train into that. Hauling for your corporation in a 1 months old character can be as valuable as having a 100million skillpoint character. It's a sandbox after all and only you decide which route you want to go and how mcuh time you want to spend doing it.

somnium_sn··on Mercurial 2.8 Released
I like that Mercurial still tries hard to get new concepts into the core. There is something they call "phases" which is a boundary marking what was published and what not. Phases then forbid people to rebase changsets that were already published (unless you obv tell it to force it anyway), which is more more convenient than git's way. In addition they work on something called obsolete markers which will also record how changsets moved on rebase, etc giving it much more flexibility and power than git.
somnium_sn··on Mercurial 2.8 Released
When was the last time you looked at Mercurial? Recently the community put a lot of effort into performance and it should be very close to git's performance. On the flexibility site, Mercurial has the histedit extension as well as rebase which should give you most flexibility. The bare Mercurial is intended to not do much, but you have to enable a few of the shipped extensions in order to get all the functionality.
← PreviousPage 2 of 2