Details
-
AboutA Java Enthusiast
-
SkillsJava, Elm
-
LocationEngland
-
Website
-
Github
Joined devRant on 11/16/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
GitHub Packages Sucks. Like, it REALLY sucks.
It sounds like the best thing in the world - being able to host your project packages alongside your code! It has full support for Maven, Gradle, Ruby Gems, Node packages, Docker images and even dotnet CLI applications. It even lets you view statistics on how many developers have downloaded a given package! For public repositories, the packages are free to host as well!
So, I decide to use it for my Maven project since it's "so great". I've never used a public Maven repository before, so this was all very new to me. I follow the documentation - simply run "mvn deploy ...." and use a generated GitHub personal access token. No problems there. Deployment is a success and I feel a wave of happiness seeing my packages online. I follow through the various links and it even adds automatically generated usage information for other Maven users - fantastic!
That was, until I decide to try and download one of the files from this package repository. In order to download a file, you must have a GitHub access token. Okay, makes sense I guess? What if another developer wants to use my library? To do so, they have to generate their own GitHub access token, store it in their local ~/.m2/settings.xml file and only THEN can they use my library. So clearly, this is significantly inferior to other public Maven repositories where you don't have to get an access token to simply USE a library.
Upon discovering this, I decide to simply delete all of the packages and continue using whatever previous system I was using. Except of course, they forbid the deletion of public packages because "other projects could depend on it". The only way to delete public packages is to either:
[0] Make the repository private (losing all stargazers and watchers), delete the packages and then make the repository public again
[1] Contact support and ask them to delete the public packages. They say that they'll only do this for "special cases", such as legal issues or GDPR breaches.
I've sent a contact form and I'm currently hoping that they see things in my favor. I mean seriously - a public package repository where in order to use it you have to have a GitHub account and then generate an authentication token - it's absurd!3 -
A few months ago, I changed my laptop from Windows to a dualboot of Windows and Linux (NixOS). Since then, Windows has never seen the light of day.
Best decision I've ever made - Windows is useless.17 -
I've finally reached the point in my life where coursework has taken precedence over my personal projects...1
-
I start by diving straight into the code. A blank brand new file in whatever language I have chosen to create my project in. If it's a language I'm unfamiliar with, I'll start with some templates of getting started (for example, I wanted to make a node.js application with a connected website, so I found some code using express to link the two together).
Once I've started, I'll eventually create a text file for ideas which I may or may not plan to implement later. If a particular feature is rather complex, I'll draw it out on my whiteboard, giving me a visual guide to help me.
My main aim is to simply get a "foot in the door"; once that's achieved, it makes working on the project much more enjoyable. I tend to turn it into a bit of "play" by coming up with suggestions which I would probably not implement in my final design, but add just for the fun of it. If I chose to drop those ideas, I'll save the code - chances are, I would have learnt something new in the process (For example, I learnt how to perform GET requests and figured out what cURL was for the first time by simply adding a "dad joke generator" to a discord bot, just for a laugh) -
I wish I could start my web based Brainfuck IDE with single stepping and breakpoints, as well as code formatting. I wrote it as a Java desktop application 2 years ago with no comments and I've never touched it since.
-
When my teacher says that you have to produce variable lists for each variable in your program, stating the name, type and what they're used for, if you're coding in Java, you know you're fucked with 16 classes of swing GUI...1
-
My friend left their macbook unlocked, so we parsed the entire story of Moby Dick into the text to speech and left it in the background on full volume. Never seen such a confused face in my life.
-
After being inspired by the other devRant projects, I started creating my very first android-related project of my own: Viewing rants on my Moto 360 when I'm in a boring meeting5
-
Finally installed a custom ROM (dirty unicorns) and added a designated devRant icon in the navigation bar because it's the only app I ever use on this phone5
-
Indentation. Trying to teach students that every expression needs its own indentation is such a pain.1
-
Playing articulate! with family and the word was zero. My description was "What is the first number?".
They didn't get it right first time.1 -
Using the console to print out variables is a perfectly valid method of debugging for new developers: often, it can help you resolve the problem faster than using a debugger.2
-
I was trying to complete some computer science coursework on an old school computer running Netbeans...
It took 10 minutes and lots of freezing to write one line of code which doesn't even work.